I just bought the new 32 GB Nexus 7. When I came home and set it up, the tablet did a quick update. When it came back up, I got a message that a new system update was available and when I clicked on the icon it said Jelly Bean 4.3. I was surprised because I thought that the new Nexus 7 came with 4.3. I did the update anyway, and when the Nexus booted back up, it froze. It has now been on the Nexus logo for more than 10 minutes.
It came with 4.3 but it had developer keys instead of release keys. That first update while you initially set it up was to switch to release keys.
The 2nd update was to upgrade you from 4.3 JWR66N to 4.3 JSS15J.
If it stays stuck on the X for a while, boot into recovery and do wipe data/factory reset.
If you aren't familiar with booting to recovery on this particular device see this post:
[Info] Guide to entering safe mode, bootloader, stock recovery
sfhub said:
It came with 4.3 but it had developer keys instead of release keys. That first update while you initially set it up was to switch to release keys.
The 2nd update was to upgrade you from 4.3 JWR66N to 4.3 JSS15J.
If it stays stuck on the X for a while, boot into recovery and do wipe data/factory reset.
If you aren't familiar with booting to recovery on this particular device see this post:
[Info] Guide to entering safe mode, bootloader, stock recovery
Click to expand...
Click to collapse
Thanks, in the end I just power it down and restart it.
Related
As a disclaimer I was on rooted stock 4.2, with 160 dpi. Restored backup of build.prop then went to install the system update (worked fine that way from 4.1.2 to 4.2), rebooted and almost instantly had the Android recovery logo with a red triangle and said error. Stuck on that screen, so I held the power button to turn it off, then when I tried to boot it up I just get the Nexus logo and it never boots. I went to bootloader tried to boot into recovery (clockwork) and it said it wasn't there or something.
What are my options?
Kitten Mittens said:
As a disclaimer I was on rooted stock 4.2, with 160 dpi. Restored backup of build.prop then went to install the system update (worked fine that way from 4.1.2 to 4.2), rebooted and almost instantly had the Android recovery logo with a red triangle and said error. Stuck on that screen, so I held the power button to turn it off, then when I tried to boot it up I just get the Nexus logo and it never boots. I went to bootloader tried to boot into recovery (clockwork) and it said it wasn't there or something.
What are my options?
Click to expand...
Click to collapse
A couple of things. You could boot into the bootloader and use fastboot to flash a custom recovery, then flash a ROM from there. Otherwise you could download the stock 4.2.1 images from Google and use fastboot to flash back to 100% stock and start over.
Wug's Toolkit may come in handy here if you're not comfortable or familiar with all the command line options.
Think I'm just going to flash the factory 4.2.1 image, will I be able to root 4.2.1?
Kitten Mittens said:
Think I'm just going to flash the factory 4.2.1 image, will I be able to root 4.2.1?
Click to expand...
Click to collapse
Yes.
- Sent from my US Cellular SGS3
I updated to Lollipop using adb and stock recovery. That worked great. Then I flashed TWRP and made a nandroid backup. I have not rooted again since I'm switching to Nexus 9. So I want to reflash stock recovery, but I didn't save it.
I have the original stock recovery from the mantaray-lrx21p factory image, but when I flash it and boot into recovery, it's just blank screen. I'm assuming the OTA update also updated recovery? Does anyone have a copy of stock recovery after the OTA Nexus 10 update I could borrow?
Thanks,
Steve
Interestingly, I find that if I flash the stock recovery from mantaray-ktu84p, then it works. So it's the stock recovery in mantaray-lrx21p that just shows blank screen...
Same issue here to? Fix
Galaxy 6s Os 6.2.8▪Ss° Pen
I think the fix is we need to get someone with the latest Lollipop patch to extract and give us the recovery.img?
When blank screen appears, press power button for few seconds until the green robot appears, then press power + volume up ( or down ). the stock recovery menu will show up
I don't get any robot when pushing power button on blank screen. After 10 secs, device reboots. Are you sure it works like this now?
Well this is strange. I started all over with ktu84p, then applied the OTA lrx21p update. After the update, the recovery still says ktu84p so it did not get updated by applying the OTA update. Is that what everyone else sees as well? If I flash the recovery.img from the lrx21p factory image, then I get the blank screen instead of robot.
I did an OTA update of Lollipop on my nexus 4, it got stuck on the 'installing system update' for about an hour, so I tried to restart the phone and it loaded the new lollipop animation, but got stuck there for 20 minutes, so i restarted it and it still didn't want to load into Lollipop, so I went into the bootloader and hit recovery and it came up with 'installing system update' again and still gets stuck. when i'm in the recovery, it won't recgonise vol + and power button press to do a factory reset, it just does nothing. my computer also doesn't recgonise the device... is there anything I can do?
Thanks!
Start into bootloader and try to flash the factory image via fastboot.
boot to fastboot and flash a custom recovery. you can use twrp or cwm to do a standard factory reset and you should be fine.
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Check my thread, I had the same problem. 5.0.1 was fine but sensors went kaput, yes all of them. Flashed factory image 5.1, endless boot screen. After a day or two of flashing 4.4.4 (sensors were back working okay, wow big surprise), tried flashing 5.1.1 pure stock, same.
I'm back to 4.4.4 after restoring apps and data. Not sure I want to use 5.0.1 due to hte memory leak and other bugs that should be fixed with 5.1. But I'm certain that the factory image of 5.1.x won't boot on the N4.
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
Try doing this
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Hope that helps
PermissionToPanic said:
Hello All,
Hope you guys are doing well. I'll write in jot notes so I don't end up with an essay.
Bought Nexus 4 16GB in February 2013 from Google Store and have been running stock software since. Never had issues.
Updated from latest Kit Kat OS to Android 5.0.1 OTA yesterday and it installed fine.
Then tried updating to Android 5.1 (also through OTA) right after and encountered the "Error" message with the Android logo on its back during install. Phone is now unable to move past the swirling, coloured balls animation upon rebooting (referred to as a bootloop?).
Based on some websites' recommendations, I went into the recovery mode (hold Power+Volume Down and select from list) and wiped the cache partition (hold Power+Volume Up and select from list), which took a second. Wiped cache several times.
Tried rebooting the system after but I still get stuck on the swirling balls animation.
I'd be fine with using 5.0.1 or even going back to the latest Kit Kat as long as I can actually get my phone working again and not have to factory reset everything through the recovery mode (which, at this point, seems like my only option).
Thanks.
Click to expand...
Click to collapse
I don't think that the factory reset will solve the problem. Have you tried waiting for 10-15 minutes for the phone to boot up? After OTA's and clearing cache the phone usually takes a while to boot up. If that doesn't work, factory reset using a custom recovery (this will delete your /data folder but not /data/media so your internal storage won't be wiped)
Blacksmith5 said:
.. Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
My, that text looks familiar....
So i pretty much screwed up my Nokia 6 TA-1033. Luckily i have another phone spear that i can use in the meantime.
So i was running Oreo 8.1 - May Patch, and silly me thought i'd try root it following instructions to install an OTA update before December.
Long story short it didn't work and i got stuck with my phone booting into recovery.
So this is where things get weird for me and that somehow i got 2 recoveries installed on my phone.
1st recovery: If i powered my phone completely off and then powered on until "NO COMMAND" appears and then entered recovery (Power + VOL UP) Android Recovery shows 8.0.0
2nd Recovery: If i insert USB from PC to Phone and then powered on until "NO COMMAND" appears. I then push and hold (Power + VOL UP) until phone powers off (still hold the buttons), the phone will power on and after about 5 seconds reboots again and powers on a second time and then the phone would boot into the second recovery. This time the recovery version displays Android Recovery 7.1.2.
I am really confused as to what has happened to my phone.
Now to make things even worse my son had a play around with it more while i was at work and has somehow put TWRP and replaced that second recovery that i just explained.
Is any of this normal?
I have a locked bootoader, 2 recoveries (Android 8.0.0 and TWRP) and no way to boot the phone it an OS?
HELP!
Seems you'd overwritten boot partition with recovery.img from Android 8. Wonder what version of sbl/aboot you've got after all that mess. Guess sbl/aboot is from Nougat if your son managed to install TWRP. You just need to rewrite boot partition with boot.img, you can extract it from any Oreo OTA zip.
sokkaia said:
So i pretty much screwed up my Nokia 6 TA-1033. Luckily i have another phone spear that i can use in the meantime.
So i was running Oreo 8.1 - May Patch, and silly me thought i'd try root it following instructions to install an OTA update before December.
Long story short it didn't work and i got stuck with my phone booting into recovery.
So this is where things get weird for me and that somehow i got 2 recoveries installed on my phone.
1st recovery: If i powered my phone completely off and then powered on until "NO COMMAND" appears and then entered recovery (Power + VOL UP) Android Recovery shows 8.0.0
2nd Recovery: If i insert USB from PC to Phone and then powered on until "NO COMMAND" appears. I then push and hold (Power + VOL UP) until phone powers off (still hold the buttons), the phone will power on and after about 5 seconds reboots again and powers on a second time and then the phone would boot into the second recovery. This time the recovery version displays Android Recovery 7.1.2.
I am really confused as to what has happened to my phone.
Now to make things even worse my son had a play around with it more while i was at work and has somehow put TWRP and replaced that second recovery that i just explained.
Is any of this normal?
I have a locked bootoader, 2 recoveries (Android 8.0.0 and TWRP) and no way to boot the phone it an OS?
HELP!
Click to expand...
Click to collapse
If u have 2 recovery right now or 8.0.0 and twrp or something,
Follow these steps to get it back
1. Goto the very first page of this thread
https://forum.xda-developers.com/nokia-6/how-to/updated-mirror-link-ota-monthly-updates-t3733784
2. Download from the first row (between dividers)
a. December ota 2017 and
b. February official oreo 2018 ota
3. Put them into the external sd card
4. Goto 8.0.0 recovery and first install December one.
5. After u get error installing the December ota, reboot, it will take u to nougat 7.1.2 recovery
6. Now this time install February ota
7. Done, u will get back to system
Tip: while doing this keep patience
Happy flashing
sltushar said:
If u have 2 recovery right now or 8.0.0 and twrp or something,
Follow these steps to get it back
1. Goto the very first page of this thread
https://forum.xda-developers.com/nokia-6/how-to/updated-mirror-link-ota-monthly-updates-t3733784
2. Download from the first row (between dividers)
a. December ota 2017 and
b. February official oreo 2018 ota
3. Put them into the external sd card
4. Goto 8.0.0 recovery and first install December one.
5. After u get error installing the December ota, reboot, it will take u to nougat 7.1.2 recovery
6. Now this time install February ota
7. Done, u will get back to system
Tip: while doing this keep patience
Happy flashing
Click to expand...
Click to collapse
So i followed these intructions. I am still not getting anywhere.
When i enter Android Recovery recovery and select "Apply update from SD card" it starts the update but then phone restarts and goes into TWRP Recovery and finishes the update there. It says failed to reboot so i reboot it and then it starts in Android Recovery 7.1.2.
I then select Apply update from SD card" and it does the same thing. Starts loading then reboots and heads into TWRP to finish the update. It restarts but im still stuck at the "NO COMMAND" screen
sokkaia said:
So i followed these intructions. I am still not getting anywhere.
When i enter Android Recovery recovery and select "Apply update from SD card" it starts the update but then phone restarts and goes into TWRP Recovery and finishes the update there. It says failed to reboot so i reboot it and then it starts in Android Recovery 7.1.2.
I then select Apply update from SD card" and it does the same thing. Starts loading then reboots and heads into TWRP to finish the update. It restarts but im still stuck at the "NO COMMAND" screen
Click to expand...
Click to collapse
Do one thing then, when u get 7.1 2 recovery, boot into bootloader and start flashing mena firmware, after that goto system update, u will get the official oreo update then u know what to do