yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] kevinkoh:
I just tried that! and finally my PC seemed to have some reaction to the N7!

I suppose i have just managed to make the N7 boot into APX mode, the screen looks as though it is turned off though (no backlight), however, when i plug the device into the PC, it shows up as an unknown USB device (as shown in the attached image).

I do recall having the approriate drivers on this PC to recognise the device in ADB and fastboot mode though! Perhaps i may need another set of drivers to interface with the N7 in APX mode.

From what i can see, i think i screwed up my bootloader partition, i can't seem to even get into bootloader, and thus no recovery and system.

I guess i gotta find a way to flash the device in this APX mode? Does anyone have any experience in doing this?
[Nexus 7 Original Development] adstraylight:
This post might help:

http://xdaforums.com/showpost.php?p=30002160&postcount=10
[Nexus 7 Original Development] gorneman:
Pmic regulates power for the hardware components. In dmesg you can see what is "your" pmic.
[Nexus 7 Original Development] gorneman:
try this guide , good luck
[Nexus 7 Original Development] tudki:
could someone tell me if my device is suitable for 3.4 Kernel or not.
[Nexus 7 Original Development] KawaiiAurora:
How about you make a backup of your current ROM and just try it?
[Nexus 7 Original Development] tpuserhp:
I will wait a bit to try it. If [MENTION=2753705]kevinkoh[/MENTION] cannot save his grouper, then it might be too risky to try it.
[Nexus 7 Original Development] abhifx:
where is your XDA spirit where you try first and ask questions later?

i am just joking.
[Nexus 7 Original Development] gorneman:
Your grouper have max776663 pmic, probably it will not boot
[Nexus 7 Original Development] kevinkoh:
unfortunately, i didnt make a flatline backup of my nexus 7, thus i cant perform a restore with NVFlash. Good luck guys! its the end of road for my n7!
[Nexus 7 Original Development] Ziyan:
Impossible on a Nexus device! Keep trying various key combinations, like holding down all volume and power buttons while in that mode, so it'll boot into the bootloader. I got into the same scenario once as well. Not joking - it's really impossible to brick a nexus device like that.
[Nexus 7 Original Development] Vladimir2k9:
I break my nexus. At first boot hang up on boot optimization. And now recognized in APX mode. I try boot in bootloader but can not.

On russian forum found instruction (http://4pda.ru/forum/index.php?showtopic=355930&st=12500#entry28007059) and command

nvflash --resume --go

after it my Nexus recognised as unknown device.

On ebay I bought new motherboard with 32Gb flash memory, but now my touch screen not work, waiting for another motherboard from seller.
[Nexus 7 Original Development] AndDiSa:
You cannot use nvflash on a Nexus 7 unless you used the flatline process and have already created *your* binary blobs *before* your device was bricked.

Nevertheless being in APX mode is not a tragedy ad you can exit from there by pressing the power button *only* by about 15 to 20 seconds. After that the device should be switched off completely and you can use the standard combinations to boot e.g. into bootloader.
[Nexus 7 Original Development] pincher65:
I tried to explain them already it in the same place.

if primary loader is killed, then N 7 - it is dead.
[Nexus 7 Original Development] adeelraj:
is there any chance if this kernel will work on max776663 pmic
[Nexus 7 Original Development] kevinkoh:
I do hope so that i did not actually brick the device too! I do not have my device on hand now, but i would like to check if being able to see the google logo actually does mean that the bootloader is intact? This is because i think i might have screwed my bootloader by using the original TWRP (instead of the one provided in OP) to flash the AOSP 7 rom from the OP post.

But if i did corrupt my bootloader, wouldn't the N7 be bricked?

I understand that nvflash is not helpful at this point as i did not create my binary blobs. There has been some thread about cracking the encrypting behind it, but i havent had to time to look into it yet, perhaps in the future i will try it out!

I am actually not "stuck" in APX mode. I am able to exit from it just fine but holding power button. However, APX mode seems to be the only "bootable" sequence i have left, as i do not seem to be able to boot to system/recovery/bootloader.

I will keep you guys informed if i can unbrick the device!
[Nexus 7 Original Development] sheffzor:
hey guys,

If you are following our github you can see that we are hardworking to bring both N and kernel 3.4 taste for you, today I will leave you this candy:

OMNI-7.0

Soon we will post some new builds from aosp and twrp fully fixed.

All the roms will have f2fs support

Stay tunned.
[Nexus 7 Original Development] Ziyan:
There's no way you could have corrupted your bootloader like that. By using the original TWRP, you did nothing wrong, as there's no real reason to use the k3.4 TWRP just yet (other than testing it to see if it boots on different variants). :) And yes, the google logo comes from the bootloader.
[Nexus 7 Original Development] abhifx:
by the looks of it, tilapia seems to be up and running with RIL. Waiting to test the next update. any news on CM14 booting on N7?
[Nexus 7 Original Development] sheffzor:
It is ;)
[Nexus 7 Original Development] tpuserhp:
I've got the same error while upgrading my grouper to android n with 3.1 kernel. I cannot get to recovery. I can connect my grouper to PC and enter adb reboot bootloader. From there, I can select start to boot into android. I ran adb devices and see my device listed while in android. But I cannot fix the cache errors. I tried to run fastboot format cache or fastboot flash recovery twrp.img, I just got waiting for any device message. I hope I can save my device.

Any help would be appreciated. Thx
[Nexus 7 Original Development] iwjosi:
Use nexus root toolkit to format /cache and /system. It works fine for me.
[Nexus 7 Original Development] abhifx:
if you are on bootloader mode, you can flash 3.1.x based TWRP recovery and format through there. this worked for me, you could try this.
[Nexus 7 Original Development] tpuserhp:
I've got fastboot device was not found using Nexus root toolkit.

Im reinstall the drivers Now.
[Nexus 7 Original Development] tpuserhp:
I don't see an option to format the cache partition in twrp. I want able to boot into twrp temporary and wipe the cache and dalvak cache. But I see those error msgs (unknown fs_type f2fs for cache and Can't mount /cache/recovery/last_locale.) when I boot in recovery. It could be I did not flash twrp (I was not able to flash using flashboot.) Im going to use the twrp app later and I hope it works. Thx.

It is all fixed now. I was able to restore from my backup and install twrp from the twrp app after booting into twrp temporary.

There could be better and elegant way to fix this issue. But I'm happy I can get my device back. Thank you [MENTION=1838085]abh[/MENTION]fix and [MENTION=5006708]iwjosi[/MENTION] for your help.
[Nexus 7 Original Development] ho0o0o11111:
Sorry for stupid question, May I know in details how to use "adb reboot bootloader" to recover the device in this case? I am facing the same situation with what NeoPreacher did.

I can't enter fastboot / bootloader, the device just in the bootloop of that error message, no choice to enter fastboot, no matter how many times I press vol- and power button.

In this case, I can't use adb/fastboot commands.

Thanks for your help in advance.
[Nexus 7 Original Development] AndDiSa:
Depends on the kind of bootloop you are in. If you have a kernel crashing most likely you will have cold reboots. In that case it's unlikely you have the adb interface already initialized and you will not be able to submit any adb command. But in that case it's sufficient to press one of vol- or vol+ button and on the next cold boot sequence the device goes to recovery resp. bootloader.

If the kernel is up but system initialization crashes and system initialization is restarting over and over, it's most likely the adb is up and running. Even if you are not able to connect to the device by 'adb shell' you can submit 'adb reboot bootloader' and chances are good, that the command is interpreted and the device reboots into bootloader.
[Nexus 7 Original Development] ho0o0o11111:
Thanks for your explanation.

I did cold reboot but the bootloop is the same so I think I am the second case you described.

(By the way, the only way I can switch off the device is to press vol + and power button together. Long press power button doesn't work in my case)

So in the second case, do you mean I connect the device to PC, restart it (in bootloop), and in cmd, submit "adb reboot bootloader" continuously (although "error: device not found" is shown), the command will work by chance?

(Tried, but the command seems not interpreted to the device)

Thanks again.:)
[Nexus 7 Original Development] Hubird:
I had the same problem and thought my device was bricked, I am no expert with this sort of thing but I was able to use the nexus toolkit to sort it out, it was still detected (as an ADB device I think) so you are able to boot into system / into a custom recovery (or flash a custom recovery).

Don't give up, your device is NOT bricked!

That being said the performance was great, still needs bugs squashed and some optimisation so it's a great start but more for the curious than to use as a daily driver.
[Nexus 7 Original Development] abhifx:
I will be lying if i say i dont care about eta. Cant wait for next update and kick my n7 more as car ice project. Maybe an interim build with fixed recovery could be posted?
[Nexus 7 Original Development] kk131:
The solution is covered earlier in this thread. You have to authorise play service permissions in app settings.

I've had a reasonably reasonably good experience with this v7 AOSP ROM, it needs to be rebooted after a while to solve error messages. Hope that the TS can continue his good work! :good:
[Nexus 7 Original Development] gorneman:
[MENTION=4619263]sheffzor[/MENTION] [MENTION=5840086]zyian[/MENTION] repositories are in hidden mode. Is it to protect your work or due some problem? Thanks ( you are free to answer to the question or not)
[Nexus 7 Original Development] sheffzor:
http://github.com/Unlegacy-Android/

We are just moving the things to other level.
[Nexus 7 Original Development] mn.code:
[MENTION=4619263]sheffzor[/MENTION] [MENTION=2633638]Ziyan[/MENTION] do you guys think it would be possible to add support for OTG + Charging in 3.4?
[Nexus 7 Original Development] Ziyan:
I see you don't have CONFIG_SCHED_MC turned on, which tends to cause similar issues on 3.4 - try turning it on. I'd also recommend taking a look at our power hal.
[Nexus 7 Original Development] PJBrs:
I think I tried with CONFIG_SCHED_MC, and it didn't work. Then again, it's been such a long time, I'll give it another try. And perhaps that might be the root cause of the powergating bug.

Where are your sources currently located? I was already planning on copying your power hal. Also, I did build Marshmallow but it didn't boot, so I must have done something wrong, probably with the proprietary blobs, so it would be good to see what changes you've done on top of Lollipop.

Thanks for all the suggestions and advice!
[Nexus 7 Original Development] PJBrs:
Unfortunately, CONFIG_SCHED_MC did not make a difference. I understand your sources are now at https://github.com/Unlegacy-Android? You've got quite a programme running there! What is unlegacy-android? Am very interested. I did build an AOSP Lollipop myself, but it took a long time hunting for patches and then I couldn't keep up with the security patches anymore. But it was very fast and stable too, and everything worked except screen casting (but that was never supported anyway). I hope to use your sources to build my own marshmallow and then... :)

I did take a peek at your power hal. That also is quite a different beast. For now, I think I'll leave it, first need to get marshmallow up and running. After that, I noticed it says something about removing stutter during animations. Well, that's exactly what I meant by flashing and flickering in the UI. It's animations like changing screens and opening menus that make it stutter a lot, with tearing. Yet, for instance, as soon as I am in the settings, I have no problem. Would be great to not need the workaround to disable hardware overlays.
[Nexus 7 Original Development] seanp25:
I found this post here explaining a bit: http://xdaforums.com/showpost.php?p=68917738&postcount=727
[Nexus 7 Original Development] pingyunao:
The WeTransfer download is no longer available. Could someone please repost it somewhere?

Also, I'm bootlooping and ADB can't see my device. How can I reflash if I can't connect to my device?
[Nexus 7 Original Development] ka_ru:
I can not build!! :(

repo sync...

. build/envsetup.sh

lunch 7

make

============================================

Checking build tools versions...

************************************************************

You asked for an OpenJDK based build but your version is

java version "1.8.0_102" Java(TM) SE Runtime Environment (build 1.8.0_102-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode).

************************************************************

build/core/main.mk:230: *** stop.

build/core/ninja.mk:163: die Regel für Ziel „/mnt/data/android/Unlegacy/out/build-aosp_grouper.ninja“ scheiterte

make: *** [/mnt/data/android/Unlegacy/out/build-aosp_grouper.ninja] Fehler 1

please, help.

Andr
[Nexus 7 Original Development] millosr:
You need to install openjdk-8-jdk .

http://source.android.com/source/initializing.html
[Nexus 7 Original Development] AndDiSa:
You can also change

requires_openjdk := false

in build/core/main.mk
[Nexus 7 Original Development] ka_ru:
Thank you.

so I can change JAVA 7 or JAVA 8

in JAVA_HOME
[Nexus 7 Original Development] AndDiSa:
Yes, I am doing so when switching between 6.x / 7.x builds.
[Nexus 7 Original Development] ka_ru:
Hello Guru,

help to understand where the error is. I want to learn how to create and upload their own modules.

my actions step by step.

repo ...

repo sync

cd ./kernel/asus/grouper/

export PATH=/mnt/data/my-android-toolchain/bin:$PATH

export ARCH=arm

export SUBARCH=arm

export CROSS_COMPILE=arm-linux-androideabi-

make grouper_defconfig

make menuconfig

set

set to <M>

save

cp .config ./kernel/asus/grouper/arch/arm/configs/grouper_my_defconfig

make mrproper

cd ../../..

cd ./device/asus/grouper

gedit BoardConfigCommon.mk

#TARGET_KERNEL_CONFIG := grouper_defconfig

TARGET_KERNEL_CONFIG := grouper_my_defconfig

cd rootdir/

gedit init.grouper.rc

add

cd ../../../..

bash

source build/envsetup.sh

croot

lunch 7

make -j9

make otapackage

copy ZIP to Tablet

adb reboot recovery

in TWRP install ZIP

after successful start.

adb shell

lsmod

nothing. the module does not LOAD

cd /system/lib/modules/

ls -la

-rw-r--r-- 1 root root 37156 2009-01-01 00:00 cdc-acm.ko

su

insmod cdc-acm.ko

insmod: failed to load cdc-acm.ko: Bad address

I have this error in Samsung S2.

I had to edit init.rc

Thank you

Andr
[Nexus 7 Original Development] brainvision:
hi guys, hi girls, hi devs! :D

I know that this thread is related to development discussion, so maybe my question will be ignored but I don't know where I could ask, so please sorry if I'm out of contest here :(

I'm going to flash this into my tilapia device: I chose CM 13 (unfortunately still no 7.0 for tilapia) and pico gapps.. but my question is related to the 3G of the rom.. in the past I flashed officials CM13 where the 3G module simply did NOT work at all.. so I would like to know if this build has the 3G module working (and tether of course)..

That's all. Thanks a lot for paying attention,

once more, sorry if I was not allowed to make such a question here, hope you'll understand

see ya! ;)
[Nexus 7 Original Development] aleks10393:
I installed the cm-13.0-20160823-UNOFFICIAL-tilapia.zip. after installing cm-13.0-20160823-UNOFFICIAL-tilapia.zip sound was very bad and quiet. What to do?
[Nexus 7 Original Development] eNVy:
Will there be an update for the CM13 version of the ROM with the kernel ?
[Nexus 7 Original Development] ka_ru:
In Android Lollipop 5.1, with SELinux enforced, the /init system process fails to load kernel modules

due to the sys_module capability missing from init.

Symptoms: In a /init.${ro.hardware}.rc OEM initialisation file, or in init*.rc file imported from that,

an insmod command is supposed to load a kernel module:

on boot

insmod /system/lib/modules/<module_name>.ko

However, when the SELinux rules are enforced, as in Android Lollipop 5.1, this silently fails. Debugging reveals that the init_module(2) system call, called from the insmod() function in system/core/init/buildin.c, returns -1 with errno set to EPERM. The reason for this appears to be init missing the sys_module capability.

One possible way to fix the issue is to add the following to external/sepolicy/init.te:

allow init self:capability { sys_module };
[Nexus 7 Original Development] jja2000:
Shouldn't this device in theory be able to use OpenTegra now instead of Nvidia's binary drivers? I can remember that the tf700t couldn't run a newer distro because of the older kernel (hence being limited to the binary drivers).

Maybe this is lifted on this device now?
[Nexus 7 Original Development] Nintonito:
That'a for Linux, not android.
[Nexus 7 Original Development] abhifx:
he is talking about distro so basically linux.

Hi [MENTION=4619263]sheffzor[/MENTION]! Any news with development?
[Nexus 7 Original Development] jja2000:
Yes I know, it's just that this is the Development thread for Linux 3.4 for the Nexus 7, so I thought this was suitable.
[Nexus 7 Original Development] abhifx:
ok so i just discovered that unlegacy android project has jenkins and it has just pumped a tilapia version.

although i dont know if this should be posted but brave XDA members might try this

http://jenkins.unlegacy-android.cf/job/android/
[Nexus 7 Original Development] abhifx:
jenkins has pumped out grouper too. sadly its not getting past google logo. anyone got it past that?

Edit: ok got it booting... flashed the provided recovery, sideloaded the ota package. and at least i have reached the android boot logo.

and it has booted and working fine

can anyone make a TWRP recovery out of this recovery?
[Nexus 7 Original Development] kk131:
Also managed to install and successfully boot with your help.

I get an error mounting sdcard in recovery, is anyone else having this problem?
[Nexus 7 Original Development] abhifx:
which recovery have you used?
[Nexus 7 Original Development] kk131:
recovery from http://jenkins.unlegacy-android.cf/job/android/195/
[Nexus 7 Original Development] abhifx:
GPS seems to be broken. here are the logs.. maybe it has to be do with gapps issue. Logs attached

Well ROM is just too smooth. feels like a new device. Great Job!
[Nexus 7 Original Development] abhifx:
i didnt face that issue then. Also are you having GPS issue?
[Nexus 7 Original Development] kk131:
No problem picking up GPS satellites and getting a fix.
[Nexus 7 Original Development] abhifx:
I stand corrected, fresh install gets me perfect GPS. this is the best one as of yet. last build has October security patches too.
[Nexus 7 Original Development] gorneman:
flashed recovery from http://jenkins.unlegacy-android.cf/job/android/195/ to test .Black screen after google logo. Now I can't access fastboot to flash vanilla TWRP recovery. Any help is appreciated
[Nexus 7 Original Development] kalafior12:
Ok, as i understand

1, flash recovery,img via twrp

2, flash aosp_grouper-ota-20161019.zip via new recovery

Is this rom f2fs ready? (data and cache)

Is This recovery a special version of twrp?

Regards

Wysłane z mojego LG-D855 przy użyciu Tapatalka
[Nexus 7 Original Development] abhifx:
The recovery is aosp based, i used adb sideload to flash rom. Edit: there was f2fs support in previous (manual) build so this should have it too. But... This recovery cant format in f2fs. I am on ext4 btw.
[Nexus 7 Original Development] abhifx:
can you boot to android or recovery?
[Nexus 7 Original Development] gorneman:
no, I try to use POWER + VOL DOWN to enter fastboot mode but after google logo, the screen goes black and nothing appears. After some times it start to bootloop. battery charging animation works. Thanks
[Nexus 7 Original Development] abhifx:
if it bootloops then maybe you can adb your way to bootloader

connect your tab to pc with drivers installed and issue adb reboot bootloader

when in bootloader mode flash twrp recovery and format stuff and flash again
[Nexus 7 Original Development] gorneman:
No, adb and fastboot don't see the device (driver installed).
[Nexus 7 Original Development] AndDiSa:
Sometimes it's sufficient to submit the adb command even when there is no adb connection yet. In that case the command will hang but will be sent to the device as soon as the connection is set up and then being executed.
[Nexus 7 Original Development] kalafior12:
Can You flash twrp over aosp recovery? Meaby after flashing rom you may have twrp again.

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Nexus 7 Original Development] kk131:
I used wugfresh to temporarily boot TWRP; formatted cache & data to f2fs.

The ROM is running but play services etc. are occasionally crashing.
[Nexus 7 Original Development] gorneman:
I have no luck, I think my grouper is gone. Thanks to all for suggestions.
[Nexus 7 Original Development] sheffzor:
Theoretically, it's impossible to brick a nexus device playing only with the rom, that is this case, so, I believe that you're not being patient, when the first time that Google logo appears after powering up, immediately press volume down, you must be really fast, that should lead you to bootloader menu were you can flash recovery again.

Again, this rom won't brick your device, we know that we have some se linux policies to fix on f2fs domain that can lead to the issue that you have, but soon we will release a build with all that fixed.

Since this is a development thread if you guys must be familiar with basic fastboot, bootloader, booting process of a device, you shouldn't be playing with this, usually when sh*t happens, people tend to give up easily, if we, as developers follow that idea, the public domain would never have new flavors, new kernels, new Roms, and all of that.

So all we ask to you is to be patient, and try until it work, we think we have covered all the hardware variants based on original 3.1 kernel code, so don't give up and don't think your grouper is dead, it is not.
[Nexus 7 Original Development] gorneman:
You are right and I appreciate your hard work. I know the possible risk of modding and do not blame you for something (never blame modders!). I do not give up easily, but I used my grouper for years and the money I spent for, I think are completely compensated. So, if I can not bring to work my grouper, it's not a tragedy.
[Nexus 7 Original Development] erk1725:
I had an issue similar to yours I believe....there are quite a few posts in this thread explaining how to revive the grouper.....I felt the same way tho. Thought I was going to have to throw it out! You can bring it back....I have faith....search, read, and give it another go:good:

Edit: here is where I think I started having problems and working towards a solution....also you want this build from [MENTION=3803126]Vocco[/MENTION]derism

http://xdaforums.com/nexus-7/orig-development/wip-linux-tegra-nv-3-4-bringup-t3128195/page51
[Nexus 7 Original Development] abhifx:
Or you can always gift it to me :D

---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------

That is happening on ext4 rom too. So i guess things are fine
[Nexus 7 Original Development] kk131:
Has anyone managed to install ROM's later than 18 Oct.? I receive an error during flashing.
[Nexus 7 Original Development] kevinkoh:
I am in the same situation as you, i have tried almost everything, could you give more details as to how you managed to get the computer to recognise the bootlooping device? to which mode did you boot the device into?