yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] ruicc:
I was on Pure Nexus Project by GtrCraft, with parrot mod. No dirty flash, always do a clean flash

I flashed exactly as it was described on page 51...but it just bootloop.it gave me 2 errors when was flashing:

E: unknown command [log]

E: unknown command [log]
[Nexus 7 Original Development] erk1725:
I got this when flashing also.....I think its not a big deal and should still flash.....you waiting long enough? It does seem to take a good while to boot first time
[Nexus 7 Original Development] ruicc:
Almost 15-20 min....and nothing :( really don't know what i'm doing wrong.

I have a log with recovery
[Nexus 7 Original Development] KawaiiAurora:
Did you flash Android N? If so, is your bootloader version 4.23? You should also have TWRP 3.0.2 with the 3.4 kernel for the best results. Android N worked well with Pico GApps/SuperSU for me altough I won't recommend it as a daily driver.
[Nexus 7 Original Development] erk1725:
im using the twrp 3.0.2 from twrp.me as suggested by [MENTION=4831205]vocoderism[/MENTION] on page 51 with the included links for aosp 7.0 opengapps pico and still on bootloader 4.18! ha:confused::rolleyes::eek:
[Nexus 7 Original Development] ruicc:
Yes, mate, my bootloader is 4.23 version. Also, the TWRP it's the last one, which i've downloaded from TWRP site yesterday.

I just flashed the rom along with SuperSU, i think gapps aren't essential ...But i leave the recovery log again
[Nexus 7 Original Development] KawaiiAurora:
Bootloader 4.18 seems to work but I had issues with bootloader 4.13 so I don't really know, I'd suggest he does a clean wipe, avoid from flashing anything after Android N and make sure that the partitions are ext4
[Nexus 7 Original Development] ruicc:
I'll wait for a more stable version. I've downloaded all the file twice, because it could be a corrupt download.

But something it's preventing my Nexus 7 to boot up.

I always do a clean flash, wiping 2-3 times, cache, dalvik, system and data. Then flash the rom and supersu.

Gonna try one last time.

Well, thank you all for your support :good:
[Nexus 7 Original Development] mi_guel69:
try it without supersu
[Nexus 7 Original Development] ruicc:
The same, stuck on boot :rolleyes:
[Nexus 7 Original Development] vocoderism:
Stuck on google logo?

Try this build and report back

https://www.androidfilehost.com/?fid=24591000424963398
[Nexus 7 Original Development] MiGuPa:
When I install the Rom AOSP 7.0 I have this problem. Later I stuck on bootloop. :( (Grouper)
[Nexus 7 Original Development] jbaumert:
Looks like you're installing via MultiROM? I've tried myself and had errors, but I was installing as secondary so it didn't affect booting.
[Nexus 7 Original Development] MiGuPa:
If I try with normal TWRP, it will work??
[Nexus 7 Original Development] ruicc:
Same result, tried both versions...from OP and that...i just get stuck on google animation
[Nexus 7 Original Development] vocoderism:
Can you post log pls?
[Nexus 7 Original Development] chosin137:
Let me guess, you are all trying to install SuperSU with the rom on first boot. Not a good idea this time. :P Ran into the same issue, then I ran into the issue where i was getting error messages on the Fastboot screen. Flashed TWRP, formatted data and system.. and cache for good measure. Then installed the build, booted into Nougat once. Made sure it was all working good. Rebooted installed SuperSU 2.78 NON SYSTEMLESS. Bam works fine. Well I mean you still have to go in and turn on all the permissions for google play store and its still buggy downloading stuff, but eventually it gets there.
[Nexus 7 Original Development] InterrtuptoR:
Hi ppl, i have lg p880, it has tegra 3... So our dev needs some 7 rom where camera works... does camera fully work in 7.0?
[Nexus 7 Original Development] ruicc:
I tried different combinations...with or without SuperSu, with or without gapps, with or without SuperSu/gapps, also formatted system and cache with TWRP...just can't pass the Google animation. I guess installing only the rom it's enough to boot into Nougat. And i'm using bootloader 4.23

Also i take a look at updater-script and saw this line:

package_extract_file("boot.img", "/dev/block/platform/sdhci-tegra.3/by-name/LNX");

Thought this could be the problem i extracted boot.img and flashed after the rom...same outcome.
[Nexus 7 Original Development] ruicc:
Here's a recovery log, mate
[Nexus 7 Original Development] McRacoon:
I ran into the same problem. Trying to flash as a secondary rom in MultiRom, where Pure Nexus is my primary rom. I also attached my recovery log (not sure whether it is helpful).

Were you able to solve the problem? Any help is appreciated.
[Nexus 7 Original Development] yeepeekai:
Hi,

I have a problem with the aosp_grouper_3.4-2016-09-01...

I have installed the rom, tried it, found it very responsive, tried to install gapps, no gapps appears so I think doing a factory reset will be cool => wrong idea....

now I have a nexus 7 stuck into the facvtory reset mode each time I launch it. Didn't manage to go out of there, tried all combo keys without success.

here's a video of what happend : https://goo.gl/photos/kU8AmYwXwBR1AxcV9

and here's what it prints on screen : https://goo.gl/photos/1aLQQqs4PRaw12NN9 (got it by pressing power and vol+)

Does anybody knows how can I get out of here ?

thanks.
[Nexus 7 Original Development] Ziyan:
As you can find out on the last pages, all you need to do is connect to a PC and issue 'adb reboot bootloader', flash TWRP and format your /data there.

We have fixed the AOSP recovery (and a few other things) already, so this won't happen again in the upcoming release.
[Nexus 7 Original Development] yeepeekai:
I don't manage to launch adb, my devices is never found. I have tried with my nexus 6 and no problem so is not an issue with adb, fastboot neither.

All I have is that screen at start up trying to format my N7... is there any key combination I miss ?
[Nexus 7 Original Development] Ziyan:
I might try replicating this issue if you don't manage to fix it by tomorrow. Did you try holding down both volume buttons, plus the power button for at least 15 secs to get into the bootloader?
[Nexus 7 Original Development] supertiger1234:
Hmm I did the same thing, factory reset and then install Gapps and everything went fine. But I did a factory reset in TWRP.

Also maybe you need to install adb drivers?
[Nexus 7 Original Development] yeepeekai:
I just tried to hold both volume and power for at least 15sec and nothing.

By holding power and vol+ I think I am in a mode where the tablet is powered but not the screen because I hear a very little noise from the speaker but I can't do anything with adb and fastboot, there's no device found.
[Nexus 7 Original Development] sheffzor:
Nexus 7 only have 2 boot modes using the volume keys and power:

fastboot mode: volume down + power

apx mode: volume up + power OR volume up + down + power

(apx mode is a low level bootloader, it's before the fastboot/google bootloader, and it's the first boot layer on tegra3, it's used to flash bootloader, create/change the partition table and/or flash roms, but less user friendly, the tool to access to APX mode is called "nvflash" and should be used after APX driver is correctly installed)

recovery mode: its only possible via fastboot mode, navigate with volume keys to "recovery mode" and then press power.

Typically, what happens is that the most people just panics and aren't patient to do the things with logic.

Try debugging this way:

With the USB cable connected between the tablet and the PC check if there is a device called "APX" in "Other devices" on windows "Device Manager", if it's there, just press volume down + power button and wait until "APX" device desapear from the listed devices on Windows Device Manager, in this scenario, the normal behavior would be a "reset" happen and the device just boots to bootloader/fastboot mode, if this doesn't occur, don't panic and don't press more buttons, your device have just discharged bellow the expected minimum level defined on bootloader charger driver, because of that, the battery animation will not apear as usual when it is connect to a charger.

This is actually a hardware bug that permits battery to discharge to 0% when device is booted into APX mode, and I believe that you guys, in panic, press the volume buttons with power and had booted to APX mode.

How to solve that? the best way would be to open the back case of nexus 7, disconnect the battery terminal, wait 5 seconds, reconnect the terminal, put the case again, connect to the WALL CHARGER WITH A MINIMUM OF 2A of power, and let it charge at least one hour without touching in any button.

Report your tries...
[Nexus 7 Original Development] Loser.lon:
You misspelled the Omni Rom for grouper. it says "tilapia" should be "grouper"
[Nexus 7 Original Development] sheffzor:
Tanks! :)
[Nexus 7 Original Development] yeepeekai:
Thanks you for your reply.

I have just started my working day. I Will try that as soon as I can and I will give you feedback.
[Nexus 7 Original Development] ruicc:
No, i was unable to solve it.

Flashed a dozen times...always stuck in Google boot, so i gave up, don't wanna ended up with a dead Nexus 7.

I'll wait for a new version, a stable one...for now, my Nexus 7 is performing very well with this MM rom.

Big thanks to rom's devs.
[Nexus 7 Original Development] ruicc:
Install this ADB drivers, it's working. Run everything in administrator mode, install ADB in system wide.

Open you Nexus and pull out the battery for 1-2 min.

Then try to reboot into bootloader or recovery using combo keys. If it fails use adb commands. When i use adb devices, no devices listed appears, but if write adb reboot recovery, my nexus goes to recovery mode.

If you need bootloader get it from here: http://xdaforums.com/showthread.php?t=2150251

Think your Nexus is trying to format cache in F2FS but that partition is now ext4...
[Nexus 7 Original Development] yeepeekai:
ok guys so, I tried to pull off the battery for may be 10-15min but it was unsuccessful, my Nexus always want to go in reset mode and I was enable to go in recovery => same result, it goes on reset mode

Next step was to try the adb drivers from ruicc. Not very sucessful too, unable to adb.

Next step was to take an old computer with windows 7 and try the drivers from ruicc and.... tada ! what a surprise when I saw an "alcaltel ADB device" in my devices manager. So from there I was able to do an "adb restart bootloader" => devices unknow discovered and unable to fastboot something => test recovery => reset mode :(

After many tries with different drivers, usb cables and usb port I was able to have an "android bootloader interface" in my devices manger and now I will try to install a factory image at first.

So I want to thank you for your advice and help, I can now have something else better than this reset screen ^^

edit :

Was able to install the factory image 5.1.1, I was afraid when an old reset screen appears but all goes well the tablet restart in a normal mode ^^

Thanks again
[Nexus 7 Original Development] gorneman:
dmesg from TWRP 3.0.2 3.1 kernel (original). I hope it will be useful. I think the problem is somewhat related to inizialization of the screen: the screen is powered on (you can see the light around the screen) , but no image is "drawn". Thanks again.

P.S: Can someone post dmesg and last_kmsg from a working grouper? I'm curious. Thanks [MENTION=4619263]sheffzor[/MENTION] : Maybe the problem is caused by an insufficient voltage for "our unlucky" platform? Thanks
[Nexus 7 Original Development] ruicc:
Mate...believe me, when i read your post, i was very, very happy with your happy end. :)

I felt very glad to help you out. Lets hope this unfortunate issue never repeat again.
[Nexus 7 Original Development] RatanSingh:
Which partition to choose?

Hi all.

So I own a Nexus grouper and was going to flash Android 7 AOSP ROM. And just like you suggested, I was going to flash the twrp recovery for 3.4 kernel first because my device is currently on 3.1 kernel. However while flashing the twrp recovery, its asking to select a target partition with two options which are "Boot" and "Recovery". I am not sure which one to choose. Please advice. TIA.
[Nexus 7 Original Development] STEF SPICA FR:
Hello, I followed the instructions. N7 boot. I wanted boot in the recovery but impossible, since N7 will not boot. What should I do. thanks
[Nexus 7 Original Development] ruicc:
If you are flash a new TWRP you'll choose recovery
[Nexus 7 Original Development] gorneman:
Hi, flash original twrp from twrp.me and post last_kmsg and dmesg to help developers to identify the "hardware" of you nexus 7. Thanks
[Nexus 7 Original Development] C--Mon:
Hi [MENTION=4619263]sheffzor[/MENTION] thank you so much for your effort.

But sadly this new grouper image also doesn't work for me. Still stucking on aosp bootlogo.

It followed the guide from the first page step by step and also reverted my device to stock before to have the most possible "clean" flash.

After flashing the aosp 7.0 rom, I flashed your new kernel image afterwards separately, before booting the system.

But as I said above, still no luck :(

If I can provide you somehow with more logs/infos, just say so!

Greetings and many thanks
[Nexus 7 Original Development] gorneman:
Could someone post last_kmsg and dmesg from a working grouper? Thanks.
[Nexus 7 Original Development] bd177:
I installed this in the same way I installed the 7.0 rom on my n7 2013 :

Wipe system, caches, data

Flash rom

Wipe caches

Reboot to Recovery

Flash pico 7.0 open gapps, then SuperSu 2.78, then Adaway systemless zip

Wipe caches

Reboot to Recovery again (don't know if this is needed, but I do it anyways)

Reboot to system.

I had to mess around with the permissions but all is running now.
[Nexus 7 Original Development] Ravel74:
Wow... this keeps our nexus 7 alive for a longer time... Thanks!
[Nexus 7 Original Development] fwayfarer:
order of execution. iirc drivers are brought up before all mount points that arent required at boot time.
[Nexus 7 Original Development] Ziyan:
When I first got this problem, I tried appending root=/dev/mmcblk0p2. That didn't seem to help :rolleyes: I'm thinking it might be some regulator set up wrong... or something's buggy. I'm working on merging in android-3.4 atm, will give wifi another try after it's done.
[Nexus 7 Original Development] Streetwalker:
Looks to me like it can't unpack the ramdisk (line 269) so it just finds itself without a rootfs (Android never mounts a partition on /).

My tablet is f2fs and I don't feel like doing a factory reset nor porting it over from cm atm so I can't test anything.
[Nexus 7 Original Development] Sage:
subbing :) great work all.
[Nexus 7 Original Development] Ophidian_DarkCore:
[MENTION=2633638]Ziyan[/MENTION]

not booting past google logo

sources: https://github.com/lgrootnoob/android_kernel_asus_grouper/commits/nv-3.4-android-merge

attachment is the last_kmsg

If someone could give their opinion i would appreciate it.
[Nexus 7 Original Development] käsebr0t:
My kmsg looks exactly the same (look a few posts back), but I don't know why :(
[Nexus 7 Original Development] Ziyan:
You seem to have one of those third board versions that still doesn't boot :confused: I'm pretty busy right now to mess around with this... hopefully, someone will figure that out. Thanks to HTCDreamOn, boards with Maxim PMIC are fixed (my board has the TI pmic, so I couldn't fix it without testing), I don't know what's up with your board yet - you seem to have the Maxim PMIC as well... but still, something's different. As a note, you really shouldn't cherry-pick F2FS and use custom toolchains yet. Better stick with the Google GCC 4.7/4.8 :)
[Nexus 7 Original Development] Fenix46:
ready to help with the development of the kernel ;). I bought a grouper days ago, and are almost ready to begin the development of the kernel, I'm glad I got this device :)
[Nexus 7 Original Development] canodroid15:
[MENTION=2633638]Ziyan[/MENTION] I'll gladly test as well if need be ?
[Nexus 7 Original Development] namerke:
Subbed,

Great work so far, hope this comes through until a stable release.

Wish I had the time to compile and test it. :P

Anyway, keep rocking [MENTION=2633638]Ziyan[/MENTION]
[Nexus 7 Original Development] Ophidian_DarkCore:
Hey, i'm new to kernel compression and I wan't to get a better understanding. Is piggy.xzkern the zImage? does it get copied to the zImage's place after building? Do I need to use it instead? If I use a gziped ramdisk will that prevent it from booting?

ELI5 plos

EDIT: also, what is "Image". and why does 'file' call it "data"?
[Nexus 7 Original Development] Ziyan:
Image is the uncompressed kernel.

zImage is the compressed, self-extracting kernel.

piggy.xzkern is the initially compressed Image (like if you compressed it using a file manager) - this will hopefully shed some light on it: https://github.com/Ziyann/android_kernel_asus_grouper/blob/linux-tegra-nv-3.4-grouper/arch/arm/boot/compressed/Makefile as you can see, it's not the final zImage - it needs to be aligned properly first, and also lacks a decompressor, for example.

About ramdisk, only gzip is supported atm: https://github.com/Ziyann/android_kernel_asus_grouper/blob/linux-tegra-nv-3.4-grouper/arch/arm/configs/grouper_defconfig#L113 however, you could enable all of those options, and use any of those compression methods for the ramdisk then :)

By the way, wifi is now fixed - looks like zImages larger than ~5.5mb won't boot properly, resulting in the ramdisk not being loaded. Switching to XZ kernel compression fixed that, the zImage is now ~3.6mb. However, the fix for boards with maxim pmic sets conflicting voltages, resulting in broken wifi (at least on my ti pmic board). Reverting it fixes wifi completely for me, so I need someone with a maxim pmic to help/test another workaround :)
[Nexus 7 Original Development] NeoPreacher:
How to find out about the board type? I can be a tester if I got the needed type
[Nexus 7 Original Development] xiedaddy:
How to use

;)Hey I'm a noob geek so i have a little question to ask....how to use the source code of the kernel?i mean...where is the kernel. zip that i can straightly install..﻿
[Nexus 7 Original Development] Streetwalker:
https://source.android.com/source/building-kernels.html

No flashable zip since it needs device-specific data to be hardcoded in the source code.
[Nexus 7 Original Development] anzi2001:
[MENTION=2633638]Ziyan[/MENTION] can i ask why do we need to hardcode the pcb for it to work? And why we dont need to do it on 3.1 kernel? And is there a fix for that? Thanks for the work man :D
[Nexus 7 Original Development] Ziyan:
It's been fixed - the only thing missing from the kernel is the fix for those third board variants (mentioned in post 46). So if you're lucky enough not to have one of those variants, the kernel should work for you, with very few semi-working things (like audio). In fact, that's the only major issue remaining... almost everything else works just fine (with slow resuming ofc). The interactive governor will need some tweaks to achieve better performance (it's pretty lazy, compared to the overly sensitive google tuned one in 3.1) though.
[Nexus 7 Original Development] anzi2001:
Nice :D and 3.4 google branch merged yet? And will boot img and zip be available soon?

Btw how can we check what board we have?
[Nexus 7 Original Development] fra9090:
Awesome work guys! Thanks a lot :D
[Nexus 7 Original Development] NeoPreacher:
As this was my first try ever I took the sources to compile this kernel. And after a while I got it and had the boot.img and zimage. But flashing doesn't work and it doesn't boot. Now I'm still interested to try but I need a hint how to hardcode this PCB stuff. Would be very nice if someone would be so kind to show me the direction of a possibility.
[Nexus 7 Original Development] jschill31:
Hello,

Working great here as well. I actually flashed ROM, then PICO and Root in the same recovery...just not stacked. There is something up with the initial setup but power through it and you will be OK. I also had to adjust permissions before the Google Play would allow me to login.

Thanks to the OP for the hard work

Update:. Working well, good battery life and more responsive than M. Only issue I have seen is Play Movies which I suspect is a DCM problem as Plex & Netflix play fine.

Cheers
[Nexus 7 Original Development] DariosF:
+1 I noticed it too.
[Nexus 7 Original Development] erk1725:
My daughter has a grouper and my son has one also....my daughters is straight stock, not rooted, locked bootloader....stock. My sons grouper is running the 7.0 AOSP posted on page 51 or whatever page it was posted by [MENTION=4831205]vocoderism[/MENTION] and his tablet charges just fine, no issues. My daughters is extremely slow at charging and neither were purchased new, so Im not sure if it is just the battery being approx. 4 years old or what. I guess this post isnt helpful! lol....just wanted to voice my experiences:good:
[Nexus 7 Original Development] gorneman:
[MENTION=4619263]sheffzor[/MENTION] [MENTION=2633638]Ziyan[/MENTION] : It may be that the function "grouper_query_pmic_id()" is not working?
[Nexus 7 Original Development] Luvletter520:
It always show me Google play service has stopped when I flashed gapps from open gapps.org.
[Nexus 7 Original Development] voyteckst:
I'm running AOSP N from the first post with pico opengapps and supersu and it just errors works fine.
[Nexus 7 Original Development] kevinkoh:
Hi guys!

I need some help, i think i might have actually bricked my N7 grouper.

At first i tried installing the twrp-3.0.2-0-grouper-k3.4-20160822.img through flashfire.

When i rebooted to recovery, it didnt boot. So i booted back to android and use flashfire to flash the original TWRP 3.0.2.

Using that recovery, i flashed aosp_grouper_3.4-2016-09-01.zip and tried to reboot to system.

However, i am now permanently stuck in a bootloop, it boots with the google logo, followed by a black blank screen, looping back to the google logo ~10 seconds later.

The same boot loop occurs no matter what key combinations i use to boot the device (vol down + power, vol up + power, just power).

I have tried taking disconnecting the battery before booting it.

Plugging a power source to it when it is switched off still shows the charging battery icon fine (seems like this part is still not broken)

I have tried plugging the device to the PC while the device is in bootloop, adb devices, fastboot devices does not work. adb flash bootloader/recovery does not work either.

Device manager does not show anything that resembles APX device or android bootloader device.

I feel like i am out of options as i am unable to boot the device into recover or into any mode that can be recognised by the PC to unbrick/reflash it.

I would hope to seek some assistance from the people here in unbricking my device.

I would really appreciate any help!
[Nexus 7 Original Development] gorneman:
[MENTION=2753705]kevinkoh[/MENTION] Probabily, you have a grouper with max77663 pmic. This hardware variant have problems with boot of 3.4 based Roms. So,just flash a ROM based on linux 3.1 and post dmesg and last_kms .
[Nexus 7 Original Development] kevinkoh:
[MENTION=2711858]gorneman[/MENTION]

Yea it would seem so. How should i go about flashing a linux 3.1 ROM now? I can't access my recovery nor bootloader nor download mode.
[Nexus 7 Original Development] HeikoE:
Hi,

What's that IC for? Is there a way to determine which one is in my Grouper before installing the new kernel?

Thanks for your good work.
[Nexus 7 Original Development] adstraylight:
Did you try holding both volome buttons + power?

I went through the same sequence you did some time ago, apart from going so far as to unplug the battery, and this is how I got back to the bootloader.