Hello everyone,
I consider myself to be relatively experienced with flashing, but tonight I am having major difficulties. After wanting to switch from Cyanogenmod to a more stock related ROM, I encountered a major problem. After flashing, or even restoring a nandroid, the tablet completes the script and prompts me to reboot. After rebooting, it boots thought the bootloader, and then to the animation. After just a few seconds, the animation freezes and just sits there. Every once and a while though, it does return to the bootloader screen; repeating the process. Is there anything I am doing wrong? I have checked the bootloader numbers on both the ROMs, as well as the bootloader version on my tablet and they DO correspond. Help would be greatly appreciated!
Quick Update:
It just wiped my storage completely.
It's bootlooping. You cant jump from cyanogen to stock or vice versa without wiping. Maybe the wrong boot loader version as well? That's my guess anyway. If you want it to boot, ensure you are on the correct bootloader, factory wipe inside twrp and then flash your ROM.
Related
UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/
Hi folks,
It appears that I managed to soft-brick my device, while trying to revert everything back to stock.
To make a long story short, I'm working by efrant's guide, but once I try to flash the radio, it takes ages and doesn't really go anywhere, i'm waiting more than 20 minutes now.
In addition to the bootloader (which is unlocked and the computer recognizes), I can also access the recovery (TWRP) - BUT, when I tried to wipe all the data, it wiped stuff and then claimed that there's no OS installed. when I rebooted my device, it got stuck on google's logo and I had to force reboot into bootloader again.
Luckily, the bootloader is the only thing that currently works in this phone, whilst the recovery keeps "claiming" that there is no OS installed and i can't really do something with it.
so i try to flash the bootloader, it works. once i try to flash the radio, it gets stuck. i try to flash system.img, the same.
What do I do?
A lot of thanks in advance!
*update* - I managed to flash it back to stock, eventually. yey.
just flash any ROM and Gapps and It should work.
I've never had problems like this and I've been flashing custom roms and recovery since HTC G1 days. Maybe you chaps can enlighten me a bit.
I can boot into all partitions of my device just fine, regular system, recovery, bootloader all okay. My daily rom (Vanir), however, has been getting a little bogged down lately so I'm trying to do an update.
I transferred my rom and gapps files to the sdcard and boot into twrp 2.6.3.1 to update, but lo and behold, the files are now missing. All my other files are there, just not the rom or the gapps. Not too worried yet, I'll just use the sideload method instead.
Start up sideload and watch it transfer over the new rom (MIUI at this point, and I factory reset before hand). From the cmd line I can see it going over just fine and the device seems to be accepting it as well. It gets to 100% and starts a quick error free install on the device, but when I reboot, nothing has been changed and I'm back in Vanir. Okay...I'll update the recovery and see if a new one works.
So I boot into the fastboot to update the recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-grouper.img
Looks good, no error messages, cmd line shows it has been written, so I reboot into my new recovery, only its not new, its still twrp 2.6.3.1 and everything still doesn't work.
Long story long, I also tried installing CWM instead of TWRP -- didn't work, using adb push to move the files and that didn't work, and every time I seem to just lose the zip files after a reboot or update attempt. In fact, when I boot back into Vanir, all my regular files are there, but even though I haven't removed them none of the rom or gapps zips are anywhere. I am sure they have successfully transferred multiple times, but they never seem to make it through a boot sequence.
At this point I'm stuck, and wondering about my boot partitions being messed up. Any help you can provide is much appreciated.
Update, with new information.
I tried to do a complete wipe a la the guide that's stickied in this forum, and it's led me to a bit of new information. It seems that my bootloader is repeatedly failing to update from version 3.23 every time giving either the "InvalidState" error, or when I use older bootloaders that are supposed to work like the JWR66V bootloader mention in this post, it doesn't say "InvalidState" but still fails just the same with a blank where it would say "InvalidState".
I've also realized that none of my changes to my tablet are persisting through a boot sequence. If I download a new app, it is gone upon restarting. In fact, every time I power it up, it downloads the same 3 app updates to the device. Perhaps that can help narrow the problem down a little bit? Sounds like a data wipe is happening every time, but only for changes since I began to try to update the tablet a few days ago, all my files from before the update attempt are never removed or altered at all.
Lastly, according to Rom Manager, I have both TWRP and ClockworkMod as recovery. Actually, that makes me think it might be a boot.img issue. If anyone has any ideas at all, I am open to try any of them at this point. Thanks for reading and for your suggestions in advance!
I downloaded the m-kernel zip a75 (lollipop 5.1.1) and flashed it through cwm. It reported a successful flash. I rebooted and it went to the google screen, then the boot screen, and then.......... the horrid optimizing apps screen! So, I waited for the apps to be optimized, and then it reported starting apps. The window closed and I expected it to boot but up but instead met by a brief NFC thing failure message and the device went back to the bootscreen and started doing everything over and over again. Please help! I really don't want to reset my device! Why isn't it working and what should I do?
youre beat. i did the same thing. the kernel does not work with 5.1.1 so unless you TOOK A BACKUP BEFORE FLASHING there is nothing you can do but reset.
you can try reflashing the rom without wiping the data partition, or restoring only the BOOT partition from backup. it will work, thats what i did until they get the kernel situation figured out. youre not the first to encounter this.
Hi,
After doing some unlocking, installing recovery then rooting. I was able to complete root process but i had an issue where my sim cards were not detected. Foolish me, i tried to do a factory reset in the settings and it turns out that my system was not recovered back. Now, it is looping on TWRP and can't boot back to system. Not sure what to do next...
Done fixing: i flash back the original recovery. Stock recovery automatically proceed with "erasing" then it autoreboots. Hope this help others encountering the same problem. To prevent this, just don't do factory reset via system setting when having custom recovery.
jhonny173 said:
Hi,
After doing some unlocking, installing recovery then rooting. I was able to complete root process but i had an issue where my sim cards were not detected. Foolish me, i tried to do a factory reset in the settings and it turns out that my system was not recovered back. Now, it is looping on TWRP and can't boot back to system. Not sure what to do next...
Done fixing: i flash back the original recovery. Stock recovery automatically proceed with "erasing" then it autoreboots. Hope this help others encountering the same problem. To prevent this, just don't do factory reset via system setting when having custom recovery.
Click to expand...
Click to collapse
hello, the same thing happen to my phone and i want to ask where can i get the original recovery file?