Hey guys, got a weird situation here, search on forums didn't find a solution. My gf's N7 is stock and locked BL, tried today to update from 5.1 to 5.1.1 with no success. It restarted, started the system update but seems not to be able to finish it, reboot and then restart the system update, ending in a loop. Reboots, begins to update, never finishes, reboots and again and again.
Here is what i tried: Turning it off; doesn't work, it starts updating again ending in the same loop.
Going into BL; reboot to BL and boot, same thing. Going to recovery just goes on update system. Booting the device from BL only turns to a black screen where nothing happens.
Is there any solution without unlocking the BL flashing a factory image?
LucidSomnia said:
Hey guys, got a weird situation here, search on forums didn't find a solution. My gf's N7 is stock and locked BL, tried today to update from 5.1 to 5.1.1 with no success. It restarted, started the system update but seems not to be able to finish it, reboot and then restart the system update, ending in a loop. Reboots, begins to update, never finishes, reboots and again and again.
Here is what i tried: Turning it off; doesn't work, it starts updating again ending in the same loop.
Going into BL; reboot to BL and boot, same thing. Going to recovery just goes on update system. Booting the device from BL only turns to a black screen where nothing happens.
Is there any solution without unlocking the BL flashing a factory image?
Click to expand...
Click to collapse
You could try to go into recovery and sideload an OTA that you manually download.
See this thread: http://forum.xda-developers.com/nexus-7-2013/general/nexus-7-2013-stock-ota-urls-t3083546
That might get it out of the bootloop. Hope that helps.
ExDis said:
You could try to go into recovery and sideload an OTA that you manually download.
See this thread: http://forum.xda-developers.com/nexus-7-2013/general/nexus-7-2013-stock-ota-urls-t3083546
That might get it out of the bootloop. Hope that helps.
Click to expand...
Click to collapse
I said i can't get into recovery, and its not a bootloop. It's a loop between boot and system update that never finishes.
LucidSomnia said:
I said i can't get into recovery, and its not a bootloop. It's a loop between boot and system update that never finishes.
Click to expand...
Click to collapse
Thought you said you could get into bootloader...
Nevermind, I see what you wrote.... sorry, other than flashing a fresh system, I have no other ideas.
PHP:
ExDis said:
Thought you said you could get into bootloader...
Nevermind, I see what you wrote.... sorry, other than flashing a fresh system, I have no other ideas.
Click to expand...
Click to collapse
I can get into bootloader, but when i hit recovery, it starts updating.
LucidSomnia said:
PHP:
I can get into bootloader, but when i hit recovery, it starts updating.
Click to expand...
Click to collapse
Finished update, now stuck on google logo. Trying to unlock BL through fastboot, stucks on "erase userdata" forever.
Related
Im in big trouble right now...
I had installed the StockPlusRom, and for some reason servers went down, so i decided to do a fresh start, boot into CMW and instead of wiping, and also format everything, after that, it obviosly broke everything, after that i tried sideloading (via CMW) 2 different OTA updates, with success, but they get stuck at boot logo (logo freeze), so i tried the StockPlusRom again, and with that option, i only get a black screen...
Is there a way to fix this screwed up ouya?
thanks
nevermind i already fixed it
tanquef said:
nevermind i already fixed it
Click to expand...
Click to collapse
how ? I got the same problem
Gomnom said:
how ? I got the same problem
Click to expand...
Click to collapse
Make sure to clear cache and dalvik. Not doing it can cause it to stay on the boot screen.
When it ends the install it will ask you if you want to keep recovery, I choose no... And tried to boot, but still gave me the freezing logo, but next time I tried I boot Into the original recovery, I installed from there the last version and it worked.
My friend's phone somehow got into a reboot cycle. It loads up, launcher starts, notifications start working. Then there is a nullpointer and a core service that is failing to start then it reboots.
So as a solution I thought try wiping data/cache. When booting the bootloader it was already unlocked - not sure if we did that a while ago or what. So going into recovery, trying the data wipe, it says success and then when I start the phone it is the same, no data is gone, apps are there, reboot problem continues.
So next step, try flashing the os. I downloaded the most recent yakju build, jwr66y. My bootloader version is PRIMELA03 and the build comes with MD04, so I try:
fastboot flash bootloader <bootloader_img>
And it reports success, everything looks fine. So I reboot the bootloader and it says BOOTLOADER VERSION - PRIMELA03.
Try fastboot oem lock, says locked. Reboot, UNLOCKED. Tried flashing the bootloader and the main img with and without restarting but always get the error:
Device version-bootloader is 'PRIMELA03'.
Update requires 'PRIMEMD04'.
when trying to flash the stock rom.
I also can't boot the stock image via 'fastboot boot'. It looks successful up until it says booting and goes to the Google screen with the padlock at the bottom and just hangs.
If I try using adb sideload to push the stock update, it says verifying, then aborts.
I also tried flashing the recovery with a cwm recovery but the same problem - it says writing, OKAY, no error message, everything looks fine, then boot recovery and it's the stock recovery.
What it looks like to me is that the bootloader and possibly the entire system is failing to write to the system flash but for some reason thinks it's succeeding. How is this possible? Is the flash dead? Am I missing something basic? I haven't rooted a phone in a couple years so it's quite possible I'm just missing a step.
Thanks in advance for any advice.
I just tried flashing an older stock (imm76i), starting by flashing the radio, but again the radio flash looks successful but the kernel won't flash because it complains about an out of date baseband and sure enough, the old one is still the one it's reporting, not the one just flashed.
tried fastboot erase system and fastboot erase recovery. Both report success but recovery boots as normal and system boots as normal (still in a reboot cycle).
I should also mention, that after the system boots, there is enough time to uninstall an app. It says successfully uninstalled, but after a reboot, the app is still there (this was the first attempt to stop the reboot cycle as a custom keyboard app was suspected). But again, the changes to flash seem to not be sticking.
Hi,
Have you resolved the problem? I'm in the same situation and I don't know what to do to stop the continuous reboot. I've already tried to flash a stock 4.3 factory image, erase the user data or only unlock the bootloader but nothing works. I'm running Android 4.3 stock without root and my bootloader is locked.
thank you in advance.
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Have you tried booting to TWRP and booting The other [email protected]
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
mikeandjaimie said:
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
Click to expand...
Click to collapse
Thanks. I'll try that and see if it works. But I let it sit for 5 or so minutes.
Edit: I'll go ahead and add it was stuck at the Razer logo. It never got to the actual boot animation.
Edit 2: I let it sit for 20+ minutes and it wouldn't boot or get past the Razer logo.
RUNNERX said:
Have you tried booting to TWRP and booting The other [email protected]
Click to expand...
Click to collapse
Yes I've tried switching slots and it didn't work.
Any luck with the stuck at logo screen? I followed instructions from Razer and fkashall and now it won't boot to recovery download or system . It just hangs at the logo screen for better part of 2 hours now so it's not a waiting game .. any luck in fixing yours?
hi there, same here after flashing google pixel experience on razer phone1. seems to be a general problem for many users. Any hints?
Best regards
Michael
I have the same problem, but I wasn't updating or installed any new app. I was just ordering food from an app and then all of a sudden my phone restared and got stuck in a bootloop.
I reflashed the stock rom, over and over, slot a or slot b, hoping that would fix it somehow... it's just stuck there now. I could go into download mode and recovery mode. but, it's only until there.
now it's bootloop until it gets into download mode...
ThatGuy94 said:
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Click to expand...
Click to collapse
I could fix it. After flashing (even Android Pi) you have to do a factory reset.
IMPORTANT: THE FACTORY RESET IN TWRP DOES NOT WORK. So you have to flash the boot-sector in your system partition with the stock boot.img and reset to STOCK RECOVERY by typing "fastboot reboot" and pressing the vol-up button. Once in stock recovery, do a factory reset and return to bootloader. Now you can flash the boot.partition with twrp boot.img, install in recovery the stock boot.img, install the twrp-installer.zip and reboot to system. The bootlogo will not stuck anymore.
I hope, I could help you. Do not forget to backup before trying.
Best regards
Mellus
sry for my bad english
I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.
I'm rooted. Sideloaded the newest OTA.
Usually at this step I would reboot and it would say I've lost root, then I would go to the bootloader and flash the (newest) patched boot.img and be good to go.
But this time, instead of booting first, I went straight to the bootloader and flashed the patched boot.img after flashing the OTA.
Now I'm stuck in a bootloop. It boots to the G logo, has the loading bar, and then eventually just reboots and repeats.
How do I get out of this bootloop?
Thanks in advance for any help!!
_________
EDIT: Now when I boot it says your device is corrupted, and then goes to the Google logo (not the G) and just sits there for a couple minutes then turns the device off.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
finshan said:
I'm rooted. Sideloaded the newest OTA.
Usually at this step I would reboot and it would say I've lost root, then I would go to the bootloader and flash the (newest) patched boot.img and be good to go.
But this time, instead of booting first, I went straight to the bootloader and flashed the patched boot.img after flashing the OTA.
Now I'm stuck in a bootloop. It boots to the G logo, has the loading bar, and then eventually just reboots and repeats.
How do I get out of this bootloop?
Thanks in advance for any help!!
_________
EDIT: Now when I boot it says your device is corrupted, and then goes to the Google logo (not the G) and just sits there for a couple minutes then turns the device off.
Click to expand...
Click to collapse
Did you leave any modules installed before you updated?
Tulsadiver said:
Did you leave any modules installed before you updated?
Click to expand...
Click to collapse
Ya I did. I got past the bootloop by reflashing the OTA, but are things broken now? Is the fix now to disable any modules, reflash the patched boot.img, and be good to go?
EDIT: can't disable any modules, because there technically aren't any because it's not rooted. I reflashed the patched boot.img, we'll see what happens...
finshan said:
Ya I did. I got past the bootloop by reflashing the OTA, but are things broken now? Is the fix now to disable any modules, reflash the patched boot.img, and be good to go?
Click to expand...
Click to collapse
When rebooting after rooting again, at the Google logo, hold volume down, it'll vibrate and boot to safe mode. Afterwards, just reboot your phone. Modules will be disabled.
Tulsadiver said:
When rebooting after rooting again, at the Google logo, hold volume down, it'll vibrate and boot to safe mode. Afterwards, just reboot your phone. Modules will be disabled.
Click to expand...
Click to collapse
Thank you!
So the patched boot.img did cause it to bootloop again, but doing what you said allowed it to boot normally and keep root. Thanks!!