yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] KawaiiAurora:
Hey,

the Aug 22 CM13 build isn't installing for me. I used both the official TWRP 3.0.2 and TWRP 3.0.2 with 3.4 kernel (posted on this thread) and it still doesn't install :/ On both versions, after pressing install, it just stays "Patching system image" for a long time and sometimes it rants about some OTA things (just saying that it doesn't install correctly)

Thanks for all the hard work :)
[Nexus 7 Original Development] abhifx:
+1

Flashed old cm13 build and boot.IMG from new build and that got stuck too. Downloading aosp
[Nexus 7 Original Development] kash_si:
[MENTION=2633638]Ziyan[/MENTION],

Flashed twrp 3.0.2.0 & Omni 6.0.1 on the device last night with out any issues so far. Runs great. No crashes or boot loops.

Thanks for all your hard work. :good::cool:
[Nexus 7 Original Development] andre02:
I have the same problem only with CM13, AOSP one install pretty well except for google play services error. The whole system is smooth and the performance is very good. thanks devs for your hard work.
[Nexus 7 Original Development] adeelraj:
omni link is disappeared from OP

can u give link
[Nexus 7 Original Development] Ziyan:
Touchscreen problems (packet spam, ghost touches) fixed. Development will probably slow down a bit, as I need to learn for my finals from now on :(
[Nexus 7 Original Development] käsebr0t:
Hi Ziyan!

Congrats for porting this kernel to our device. I managed building it from your sources and after that I packed the zImage and the ramdisk.cpio.gz, which I extracted from the stock 5.1.1 boot.img, into a new .img-file using mkbootimg. Then I flashed my .img-file using fastboot, but my Tablet is stuck at the Google-Logo and won't boot. Any ideas why? Am I doing it completely wrong?

Greetings, käsebr0t
[Nexus 7 Original Development] HTCDreamOn:
Can you send a kmsg? Doesn't matter what kernel it's from, just take one from current running ROM and I'll have a look at some things. You might have a dodgy pcb as I did.
[Nexus 7 Original Development] anzi2001:
Guys can i help with some things?
[Nexus 7 Original Development] käsebr0t:
Ok, I'll post it right after I come home from work (in ~3.5 hours). Thx in advance ;)
[Nexus 7 Original Development] käsebr0t:
Here it is!
[Nexus 7 Original Development] USBhost:
are you sure you compled from the source

it says linux 3.1.10 not 3.4.35
[Nexus 7 Original Development] käsebr0t:
Of course it says 3.1.10. If I understood him right, HtcDreamOn wanted me to take a kmsg from the current running rom, doesn't matter which kernel.

He just needs it, to check some things about my pcb ;)
[Nexus 7 Original Development] USBhost:
Your so right I miss understood lol

Sorry
[Nexus 7 Original Development] HTCDreamOn:
Interesting, you have exactly the same pmic ic, project id, pcb id as me and I had problems booting originally but this commit should have fixed that. Probably your ramdisk... pull the ramdisk from the boot.img from the ROM you're currently running to make absolute sure it's ok and use fastboot boot boot.img after repacking instead of flashing as that's how we've been testing.
[Nexus 7 Original Development] käsebr0t:
It still does not boot :( Ok, maybe it's the best, if I describe the exact steps that I do:

0. I changed the pcbid and projectid in board-grouper-misc.c according to the values I got from my kmsg.

1.

export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=$(pwd)/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:$PATH

Of course, I copied arm-eabi-gcc to the directory, which is specified in the PATH variable

2.

make grouper_defconfig
make

3. I extract the boot.img from the rom that I'm using (Optipop, Android 5.1.1) with

unmkbootimg -i boot.img

4. I copy the ramdisk.cpio.gz to <kernel sources>/arch/arm/boot and build my boot.img with

mkbootimg --kernel zImage --ramdisk ramdisk.cpio.gz -o boot.img

Is there anything wrong with these steps?

EDIT: I attached a last_kmsg from the failed boot of the 3.4-kernel. There are some error messages at the end, but don't really know what they mean.

EDIT EDIT:

Ok, that doesn't look very good at all... :eek:
[Nexus 7 Original Development] Ophidian_DarkCore:
im no dev, but maybe it didnt like the voltages?
[Nexus 7 Original Development] 19dragon98:
After the help of [MENTION=2633638]Ziyan[/MENTION] i can boot 3.4.x kernel (just a little problem of Selinux and my ramdisk) Thanks for the Support Ziyan [emoji6]

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 7 Original Development] linuxxxx:
Tilapia or grouper?

Inviato dal mio A0001 utilizzando Tapatalk
[Nexus 7 Original Development] käsebr0t:
Grouper.
[Nexus 7 Original Development] lupohirp:
Hi Ziyan,

Great work.

i really want to help, but unfortunately work takes me all time..... Howewer maybe i can give some tips. Can someone post logcat/kmsg when trying to activate wifi? Could be a driver problem or a protocol missing problem....

tnx
[Nexus 7 Original Development] 19dragon98:
http://pastebin.com/uQmwgNHU Here Logcat (tried several times to enable)

http://pastebin.com/XAzGvXMv dmesg

http://pastebin.com/EKPAq6XM last_kmsg
[Nexus 7 Original Development] Ziyan:
For some reason, enabling CFG80211 and BCMDHD in the kernel triggers this error: http://pastebin.com/qZs6QYcr :rolleyes:
[Nexus 7 Original Development] lupohirp:
Problem is related to NFS. Driver seems to work correctly.... We are building NFS with root support and stop.

We are trying to mount NFS in a partition that doesn't exist ( maybe NFS is trying to access to an ipotetical MMC or SD), so is explained the unknown block. We must mount NFS on internal Disk.

In ramdisk ( maybe i'm saying an uncorrect thing but i doesn't remember well, are years that i doesn't work at linux kernels) we should have this command :

root=/dev/nfs and other things...

mounting this partition to root...we SHOULD pass this problem.

What do you think? could be this the problem?
[Nexus 7 Original Development] Ophidian_DarkCore:
what the hell :confused:

how does a driver interfere enough that it keeps the rootfs from even mounting..
[Nexus 7 Original Development] Reptilez_DK:
CM13 and OpenGapps pico works fine on my grouper. :)

Nvm ! I'm stupid, and I need to update to latest build, before commenting. :rolleyes:
[Nexus 7 Original Development] KawaiiAurora:
The Aug 22 build? The Aug 20 build works fine for me too.
[Nexus 7 Original Development] Reptilez_DK:
Nope sorry ! Didn't see the update. :silly:
[Nexus 7 Original Development] mn.code:
Same here. AOSP works like a charm though.
[Nexus 7 Original Development] Salty Wagyu:
Just saw this linked from XDA Frontpage, does this offer something revolutionary to Nexus 7 devices? I soon stopped using mine since the lollipop days as couldn't get performance back to the way it used to be.
[Nexus 7 Original Development] abhifx:
out of others android 6 roms? yeah seems smoother. i dont know if kitkat or jellyb was better.
[Nexus 7 Original Development] chosin137:
Well looks like this is it now that Gtrcraft is done supporting the Nexus 7.
[Nexus 7 Original Development] z31nf0rd:
Is there planning for adding kexec-hardboot-patch for Multirom support? Thanks !
[Nexus 7 Original Development] chosin137:
Unofficial CM13 23rd installed fine with f2fs support... actually better than the latest Gtrcraft version.
[Nexus 7 Original Development] C--Mon:
For me all Roms still hanging on bootlogo and don't go any further.

Don't know what else I can do :(
[Nexus 7 Original Development] adeelraj:
undervolting work on ur kernel 3.4

yes or no?

---------- Post added at 03:08 AM ---------- Previous post was at 02:58 AM ----------

can i make and restore lollipop 5.1 based roms backup with the given twrp in OP
[Nexus 7 Original Development] sheffzor:
Test it if you want and take your conclusions, if it doesn't satisfy you, just don't use it, simple! [emoji12]

We hope to turn this a daily driver all around as soon as we fine tune it, so we may add kexec hardboot in the future.

Flash recovery, full power off device, boot into recovery and after wipe system, flash the rom, let me know the results!

We haven't add any kind of performance customization layer in order to adjust voltages, so: no.

Maybe someone will unlock that for you guys since that isn't in our plans, we just want to keep it stable as much as possible.
[Nexus 7 Original Development] Vladimir2k9:
Yesterday I update to cm-13.0-20160823-UNOFFICIAL-grouper.zip on my nexus 7.

Has made backup from twrp and then update firmware+gapps. Has reboot device and it began optimization apps, on 12 from 85 he hangup, I reboot it with pressing three buttons. But now I cannot to on device.

Somebody can help me?

When I connect charger, I not see battery. Disconnected battery, but it is not helped.
[Nexus 7 Original Development] z31nf0rd:
Have you try connect to computer? It's Nexus, unbrickable
[Nexus 7 Original Development] abhifx:
So i had another SOD on latest build. Will post logs later
[Nexus 7 Original Development] sheffzor:
You accidentally boot into nvflash mode, the lowest boot level of grouper.

To do a "reset" you should only press power button for about 10-15 secs.
[Nexus 7 Original Development] shubu000:
hi all,

i tried to flash the recovery, but whenever i flash the recovery and reboot to recovery, it seems like the tablet is trying to boot into recovery but unable to.

Anyone seen that before?

Thanks
[Nexus 7 Original Development] fat-lobyte:
This is a stupid question, but why is 3.4 Kernel better than 3.1 Kernel?

I know it's newer, but are there features that make Nexus 7 better?
[Nexus 7 Original Development] sheffzor:
Since we were in 3.1, you have to follow up till 3.4:

https://kernelnewbies.org/Linux_3.2

https://kernelnewbies.org/Linux_3.3

https://kernelnewbies.org/Linux_3.4

That are the upstream changes.

Now in terms of android, if you guys noticed, google doesn't have a common android support for kernel 3.1, which makes difficult to follow some security issues on android kernel layer, as you can see here:

https://android.googlesource.com/kernel/common/+refs

In tegra3 SoC scene you can check the release notes @ nvidia dev zone:

https://developer.nvidia.com/linux-tegra-rel-17

(ignore the fact that they say that only tegra4 is supported, tegra2 and tegra3 are too)

In other hand, you have the nv-tegra.nvidia.com gits to browse and play around.

What about checking our kernel sources @ github and confirm what as been done in terms of drivers recoding/refactoring/remaking in way to make it possible to grouper be alive some more years, eventually in a future bring kernel 3.10 or 4.X if its reliable...

Last, you can always try it and take your conclusions, if you think it doesn't satisfy you (am I being repetitive?), don't use it yet. :)
[Nexus 7 Original Development] Vladimir2k9:
Thank you. How I can boot in normal mode now?

Today after work I connect to my PC at home and see what say dmesg, I think nothing.
[Nexus 7 Original Development] sheffzor:
Just do a reset.

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] adeelraj:
howz battery life compared to other 3.1 based kernel roms
[Nexus 7 Original Development] chosin137:
Well what I will say is that I don't have my OC ability anymore but its running a lot better on kernel 3.4 that I have stopped caring.
[Nexus 7 Original Development] adeelraj:
just stuck on the formatting system with ur given twrp

gone back to prevous twrp recovery which i was before

restored my backup

whast should it always stuck on formatting ssytem
[Nexus 7 Original Development] abhifx:
well it will be fun to eventually see 3.10x kernel on our grouper. however i have no idea how much painful that would be, but good to see that an aging tablet is getting this type of support.

good work guys!

---------- Post added at 12:43 PM ---------- Previous post was at 12:42 PM ----------

no such issue over here, i have installed the recovery through existing recovery. i have no idea if the installation procedure is an issue.
[Nexus 7 Original Development] gorneman:
Hi, I have a grouper (bootloader 4.23 hw rev.3) . TWRP recovery downloaded from OP boot but stucks at black screen after google logo. Same situation for ROMs. ADB does not work so I can't take last_kmsg log. Thanks for your hard work
[Nexus 7 Original Development] sheffzor:
Can you post here a dmesg of your 3.1 boot?
[Nexus 7 Original Development] gorneman:
Here it is . Thanks. From latest TWRP "vanilla" recovery
[Nexus 7 Original Development] DevUt:
Does the tegra 3 SOC support 3.10? https://github.com/NVIDIA/android-linux-3.10 (i know that it is on nvidias git but...)
[Nexus 7 Original Development] KawaiiAurora:
It could be ported but I doubt that it would be worthit...
[Nexus 7 Original Development] chosin137:
So far the update to 3.4 was worth it, seems to be running great on the 3.4 kernel. Good battery life and running well, no complaints so far, at least on the cm13 23rd rom build.
[Nexus 7 Original Development] frantisek.nesveda:
[MENTION=2633638]Ziyan[/MENTION], can you put this in the first post, maybe next to the CyanogenMod downloads, please? In a big ass font? For people who shoot first and ask questions later?

I installed CM yesterday, I set up my usual settings (including Live Display), and everything appeared to be working fine, but it was super laggy, so I thought to myself: "why is everyone so stoked about this?" I found the quoted post almost by accident when I went through the thread to find out if I did something wrong, so I disabled Live Display and now the UI is super smooth again :)

Thanks so much for this, you're heroes!
[Nexus 7 Original Development] abhifx:
just to add that after flashing AOSP rom, i am getting stock recovery. Dont know why TWRP is getting wiped. any ideas?

edit:i have redownloaded and flashed the ROM and now twrp remains... so weird!
[Nexus 7 Original Development] Ziyan:
Initial impressions with N: it seems pretty smooth, but OMX doesn't seem to work just yet, so once again, we have work left to do... :confused:
[Nexus 7 Original Development] abhifx:
Fantastic! Thanks for keeping the spirit of nexus where development never stops.

I guess without media rom usage is limited, however some people would like rock n7 with nougat as is. ;)
[Nexus 7 Original Development] marras:
So, can I install cm13, or aosp, using f2fs data partition only? I think that all the problem of nexus 7 came from memory, no matter what kernel are you using. Thanks f2fs and parrot mod, really improve the ovverral performance, and make it usable
[Nexus 7 Original Development] KawaiiAurora:
I use CM13 with ParrotMod and I use ext4 for data, F2FS regularly corrupts data for me so be careful
[Nexus 7 Original Development] chosin137:
F2fs on data and cache. Then wiped from previous versions. Ran the cm13 23rd / pico installer for Gapps / parrotmod all in one go. Works perfect.
[Nexus 7 Original Development] Ziyan:
Yeah, it seems like we need to implement a hardware layer for live display, otherwise, it uses software rendering on top of everything to make up the results.

Don't worry, we just fixed OMX! Which means, N is almost bug-free on our beloved device :) I'm expecting a test release soon.
[Nexus 7 Original Development] KawaiiAurora:
Thanks for all the hard work! I'll be happy to test any builds of Android N (both AOSP/CM14 - when it's out) and check if anything is behaving erratically :)
[Nexus 7 Original Development] iason747:
Awesome to hear that! How about Performance? Is it stuttering or lagging ?
[Nexus 7 Original Development] Ziyan:
Check yourself! :) it might take some minutes to settle after booting (some of the dexopting was moved to the background), but I think it is as good, if not better than M.

​

Starting from today, we're switching our AOSP builds to N, with the first release (09/01) available now. I'm quite happy that we managed to fix up almost every issue; there might be some remaining, but they're really minor:

- NFC might not be fully working

- DRM services broken (breaking Netflix and Google Play Movies)

- SELinux and seccomp is enabled for maximum security, but with the potential of breaking something

- anything else you notice and report here ;)

I honestly have no idea how to use GApps on N (personally, I use F-Droid), or how to root - figure it out yourself ;)

I'd also mention that Google dumped the AOSP Browser from N, and replaced it with an extremely dumb Chromium shell... which can't even download files! Luckily, we at least have a built-in file manager (Settings -> Storage -> Explore) to install APKs (for example, F-Droid downloaded using another ROM or copied to the device). The built-in AOSP Music app is kinda broken as well, I suggest disabling it as soon as possible after booting.... just like Search. It's sad that Google is moving all the apps away from AOSP to the proprietary Play Store variants, but there's not much we can do (other than installing F-Droid and Amazon App Store for a good GApps-less experience).
[Nexus 7 Original Development] KawaiiAurora:
Hey! This seems to work on Android N on the 6P (Method to root, I'll test it ASAP)

http://xdaforums.com/showpost.php?p=68315371&postcount=293

EDIT: SuperSu v2.76 works and it's still ok after updating the SuperSU binary!

UPDATE: Google Keyboard is pretty unstable and might be crashing applications.. The Settings app only shows the phone version and the switcher doesn't show the border of every application properly.
[Nexus 7 Original Development] NeoPreacher:
Attention please

Game over,... I guess. Installed 0109 n aosp on vanilla twrp. Tried it with n open gapps without success after first boot. First boot worked without issue. But then I tried rebooting into twrp (shutdown, reboot using power + vol down) and it resulted into what you can see in the attached pic. The device constantly reboots showing only this for around 5 seconds. Seems hopeless but suggestions are highly welcome. Anyway, i hope it's useful. I don't blame cause i know about the risk.
[Nexus 7 Original Development] Ziyan:
Simply reflash TWRP using fastboot. What you're seeing is the broken AOSP recovery.
[Nexus 7 Original Development] käsebr0t:
Great work! I flashed the Nougat-Rom together wit SuperSu 2.77 and ParrotMod and it worked fine. Then I tried to install GApps and found, that the only package small enough is Open GApps pico. After flashing them, I got lots of Google Play Services FCs, but I could resolve that problem by giving permissions to Google Play Services, Google Play Store and Google Contacts Sync. Now, I'm restoring my Apps using Titanium Backup. I will use this as a daily driver for the next time, and report any issues, that I stumble upon.

Just one question: Do you plan to update the kernel 3.4.112, or is there a specific reason, that it is on version 3.4.67?
[Nexus 7 Original Development] NeoPreacher:
constantly auto rebooting as reported, so no flash possible. i'm not able to change into any boot option. only bootlogo then error message (doesn't matter if booting normal or into fastboot). result's the same.
[Nexus 7 Original Development] abhifx:
Super! Going to test it this weekend. Didn't expected it to arrive ao soon so left my tab at home :D
[Nexus 7 Original Development] chosin137:
I had the rebooting issues as well. Download and install the Nexus Root Toolkit. Go into advanced and flash through fastboot with twrp.img. This will interrupt the bootloop. Then scroll down to Start on the nexus 7 screen and that should boot you back into AOSP 7 and then you can do what you need to do.
[Nexus 7 Original Development] dilongl:
is there any plan to switch to linux3.10？
[Nexus 7 Original Development] sheffzor:
While we don't achieve a mature level, there's no reason to upgrade to the latest upstream patches, BTW, that will not make any noticeable change.

When your device is rebooting constantly, the easy way to stop is to just press volume down and nothing else and just wait until it boots into fastboot, it should happen nearly in the next boot when google logo appears.

You don't need anything of that, toolkits just uses the fastboot mode and adb in a seamless way, its easy and good for you to learn that this devices don't brick (unless you notice a smell of burned PCB!! [emoji123] [emoji123] [emoji123] [emoji28] ), fastboot and adb are very easy to use. [emoji12]
[Nexus 7 Original Development] pincher65:
tell please how to add a language package? I can't switch to russian
[Nexus 7 Original Development] gusto5:
I actually have the same issue. I can't seem to format or write to system with the provided recovery image in OP. I've tried flashing the recovery from within TWRP as well as fastboot flashing it, but it still can't format system, or even if system is formatted with vanilla twrp, it won't install to it. Any ideas?

Update:

I can't seem to update TWRP from within anymore, it gets stuck on "calculating restore details"
[Nexus 7 Original Development] sheffzor:
That's on the ROM side, we aren't developing the ROM itself, we are fitting the device in the ROM, essentially in aosp since all other ROMs are based on aosp.

So, if you are using aosp, blame google on that.
[Nexus 7 Original Development] abhifx:
no such issue over here, yes sometimes i can see AOSP recovery instead of TWRP after flashing gapps. but everything works as expected.

has anyone considered repartitioning grouper? system partition is just too low.
[Nexus 7 Original Development] sheffzor:
It is possible but complex process over apx mode using nvflash and it's not possible using fdisk or parted since bootloader locks gpt.
[Nexus 7 Original Development] gusto5:
With the twrp-3.0.2-0-grouper-k3.4-20160822.img, here are the outcomes in advance wipe:

Dalvik/ART Cache: Success

System: Freeze

Cache: Freeze

Data: Freeze

I don't think I'm being impatient if I am waiting the same amount of time with vanilla TWRP and the wipes are successful right? For instance wiping system takes about 11 seconds in vanilla TWRP, but I'm giving the other TWRP 10+ minutes.
[Nexus 7 Original Development] abhifx:
true.. it is as quick as 3.1.x based TWRP. if this continues in other TWRP too, then you might have to go through factory images installation as last resort.
[Nexus 7 Original Development] NeoPreacher:
It's more a constantly flashing up then a reboot (was really late yesterday). And i guess i need to make it more clear, there are no options to choose our any way else to interrupt this. It's leaving the bootlogo and then it starts repeatedly flashing up. No fastboot possible.! This device is dead
[Nexus 7 Original Development] Ziyan:
I just tested this, and the simplest way to get out of this is to connect your grouper to a computer, and with the help of adb: 'adb reboot bootloader'. You can do whatever you want from there. And don't worry dude, if you're a little bit familiar with Nexus devices, there's almost no way to brick them with a software ;) we'll fix the AOSP recovery in the next release.
[Nexus 7 Original Development] adeelraj:
My emmc is kingston one

Maybe thats the reason

What's ur emmc make

Try to flash twrp 3.0 with pc via fastboot
[Nexus 7 Original Development] vocoderism:
sorry try to wipe all then before install rom go to mount and untap flag on /system

the install rom 7.0 supersu 2.76 or above and opengapps pico variants
[Nexus 7 Original Development] Sanitch:
Hello. After flashing 7 AOSP I have bootloop. At firs time the system loads normal, but after reboot only bootloop. And I can't load bootloader, recovery and so. Errors and green android only a few seconds on the display. I can power off the device if battery plug off manual. What can I do?

Supported API: 3

E: unknown fs_type "f2fs" for /cache

E: Can't mount /cache/recovery/last_locale
[Nexus 7 Original Development] NeoPreacher:
That was useful!! Seems I'm back in the game and a lot smarter. Thanks for paying attention. :victory::victory::victory::highfive:
[Nexus 7 Original Development] supertiger1234:
cant get a success on gapps. google play services keeps stopping
[Nexus 7 Original Development] gorneman:
Hi, last_kmsg from 3.1.10 . I hope will be useful