Hey guys, so my 7 is working fantastic, except if I reboot into the bootloader, then choose recovery, it just hangs on the Google screen. If I then reboot and choose boot into recovery from rom manager, it works perfectly.
Any ideas? Not the biggest deal, but annoying.
I rooted with the nexus toolkit and have tried various kernels, which didn't change anything.
Thanks!
Sent from my ADR6400L using Tapatalk 2
SubliminalME said:
Hey guys, so my 7 is working fantastic, except if I reboot into the bootloader, then choose recovery, it just hangs on the Google screen. If I then reboot and choose boot into recovery from rom manager, it works perfectly.
Any ideas? Not the biggest deal, but annoying.
I rooted with the nexus toolkit and have tried various kernels, which didn't change anything.
Thanks!
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Same here, expect I manually unlocked and rooted. The only way beyond rom manager for me is with adb or if the rom has a power menu with a recovery option.
Noob question here, but how do you get into recovery from adb. Haven't familiarized myself with adb yet
Edit: found this threadhttp://rootzwiki.com/topic/30460-anyone-having-trouble-booting-to-recovery/page__st__10
Sent from my ADR6300 using xda app-developers app
It's a bug, just use rom manager or reboot recovery from terminal emulator
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!
Hello guys,
I wonder if somebody can help me. I bought a new Nexus 7 few days ago. As usual like with any other new device, I unlocked and rooted the device with the nexus root toolkit. After that I flashed via recovery a custom ROM. Everything worked fine, but after few hours, I wanted to try another rom, so I rebooted into recovery and the mistake I made was, that i wiped the inernal storage instead of cache. I was not able to get the custom ROM to the internal storage and the ROM was deleted, so the only option to bring the tablet to work was flashing original ROM via the toolkit or fastboot. Now I'm running on the original ROM, because when I try to flash any custom ROM, the insallation finishes fine, the tablet restarts and it gets stuck on the bootanimation.
I already tried 3 different ROMs, but the problem still persists and I have always to flash back the original ROM to get the tablet working.
Does anybody know, how to solve this problem? I really want to have a custom ROM running.
I appriciate your help!
Thanks for any ideas!
Sent from my Nexus 7 using xda app-developers app
Re download the rom of your choice to the tablet. Goo manager is my preferred method Keeps from adb push to the device...
Then Boot into recovery.. TWRP is what i use..
Wipe dalvik cache and system...
you can also in twrp .. copy your rom to usb/sd media boot into twrp with a connected usb media.. do full wipe and flash the rom from usb storage.. Great for those who have issues with internal storage. This way you can wipe it as well...
Good Luck....
Hello Erica, of course iI didit this way. As I wrote, I tried 3 different ROMs and the problem is always the same. I stucks on bootanimation.
First time I flashed custom ROM without any problems, but after flashing original ROM via the root toolkit, I am not able to get any custom ROM running.
Sent from my Nexus 7 using xda app-developers app
Wipe caches and if it gets s stuck at the boot screen sometimes you just have to turn it off for a bit and try turning it on in a couple minutes
sunman277 said:
Wipe caches and if it gets s stuck at the boot screen sometimes you just have to turn it off for a bit and try turning it on in a couple minutes
Click to expand...
Click to collapse
did you flash a custom kernel? you are not suppose to before the first boot
Sunmann, I will try.
billchen, In the custom ROMs I tried was always a custom kernel. So it flashed kernel as well.
Sent from my Nexus 7 using xda app-developers app
Hello guys, I'm back again. It still doesn't work flashing any of the custom ROMs. Does anyone, please, have any other idea, what could cause the problem?
Thanks a lot!
Hi, if you're reading this, thanks for taking the time to help me. I want to flash Cyanogen 10 on to my rooted Nexus 7. Its currently running the stock JB 4.2.2 ROM. A few days ago I flashed the motley kernel (build #249 for Jellybean 4.2.2) to OC the CPU to 1.6 Ghz using ROM Manager to flash and Trickster MOD to OC. I understand how to flash Cyanogen 10 to the Nexus 7, but is this safe? I've heard some users report that they get a boot loop when trying to flash Cyanogen 10 on top of a modified kernel. Has anyone here experienced a problem doing this?
The kernel lives in the boot partition and that is formatted when the new rom installs and it flashes its own boot.img into place. No worries. Just make sure you do a factory reset and wipe system prior to flashing cm10.
Okay. So I should boot into recovery, then do a factory reset. After that, unlock bootloader again and re-root. Then install Rom Manager again, and flash CM 10, then flash motley kernel?
Sent from my Nexus 7 using XDA Premium HD app
pindleton said:
Okay. So I should boot into recovery, then do a factory reset. After that, unlock bootloader again and re-root. Then install Rom Manager again, and flash CM 10, then flash motley kernel?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
A recovery factory reset does not relock or unroot your devices. Pretty much every rom out there will be pre rooted. So what you are going to do is download your rom, boot to recovery, perform a backup, factory reset, format system, then flash rom and gapps package and kernel, then reboot.
Oh awesome. Thanks for the help!!
Sent from my Nexus 7 using XDA Premium HD app
Hi guys!
I just want to get some idea of what could be the real problem of my Nexus 7. I can boot on its bootloader, i can access also it's recovery menu. The problem is my Nexus is in boot loop. It can't pass through the nexus boot animation (5.1.1) and I am trying to downgrade it to 4.4.4 or at least fix its' boot looping issue.
I tried reflashing a stock ROM via cmd and Nexus Toolkit, still it didn't resolve the problem. It looks like the whole partition was in READ ONLY that right after completing the flashing procedures and rebooted it all went back to the same problem. Bootloader is Unlocked
I would appreciate if someone can give me an idea on how to resolve this. TIA
Sent from my iPhone using Tapatalk
Check if cache partition is there if not create in recovery
Sent from my Nexus 6 using Tapatalk
Cache is present also..
Thanks for the input..
Sent from my iPhone using Tapatalk
My N7 has latest Pure Nexus, GApps and Parrot Mod. Try flashing it by first formatting system, data and caches. Recovery is TWRP 3.0.2 If it boots performance will be much better than stock
Sent from my Nexus 6 using Tapatalk
Will try that.. Thanks!
Sent from my iPhone using Tapatalk