Develop Bugs

[Q] Nexus 7 (2013) fails OTA update to 5.01 with Android Error

My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks

Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?

Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0

Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.

Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?

My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.

I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.

kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app

Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.

I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.

Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!

chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."

kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app

Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423

kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.

I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .

I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!

EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason

JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.

newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.

[Q] Nexus 7 2013 Stuck with two errors

Hello guys,
I had my Nexus 7 2013 (Wi-fi) for almost an year running stock rom and I decided to install CM12+ElementalX. It was all good untill yesterday when I returned it back to stock 5.0.2. When i started the tablet a message popped about 5.1 update and I started the update, but in the middle of the process it said "ERROR". I rebooted the device and now its stuck on the screen where you have to choose your language, with two errors constantly popping up - "PHONE HAS STOPPED WORKING" and "NFC Service has stopped working". I press OK like mad trying to skip some of the steps,but the "touch and go" (i think thats the name) is as far as i can go.
Is there any way I can flash the stock 5.1 without USB Debug Mode. There is no way i can get in the tablet's menu. I also saw some of the othere topics with this kind of problems, but i didn't find the answer.

You don't need USB Debugging to flash the factory images... use fastboot.

Telyx said:
You don't need USB Debugging to flash the factory images... use fastboot.
Click to expand...
Click to collapse
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on

Ramirezz27 said:
Can you please explain with few steps. I tried everything and i don't know what am I missing
P.s. I dont have custom recovery and i cant turn debug mode on
Click to expand...
Click to collapse
I have installed ADB i Android SDK. Everythink is working fine on my Nexus 5 , but i cant do anything with my Nexus 7 which is now constantly rebooting after i managed to go through all the starting steps , when it started to install my 36 apps it rebooted by itself and now it keeps doing it.

i am having similar issue. i have tried the root tool several times with no success. ive been rooting devices since the samsung moment and i cannot get this tablet going at all. with the root tool i am able to flash twrp recovery, but for some reason it will not mount to put a rom on the internal memory. i have even tried pushing a stock rooted rom through adb fastboot and it just hangs. what else can i possibly do? could it be hardware related? this all happened after i was prompted for the latest 5.1.1 update. any tips or suggestions would be greatly appreciated. tia

I cannot downgrade my device... is it not allowed?

Hey guys, I have a Nexus 7 16gb 2013 wifi running 5.1.1 lollipop LMY48G.
I'm trying to downgrade it to kitkat so I can install some software the only works correctly on kitkat on it.
I follow this guide: laptopmag(.com)articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and whenever I finish, I get a green android laying down with a red caution symbol ontop of him.
But the weird thing is I'm able to install 5.1.1 no issues using the same method, but if I pick anything older... The green android shows up..
Right now I'm back on a fresh 5.1.1 install.
Is there something I'm missing? From all my googling it seems like I should be allowed to installed kitkat no issues on this device. What am I missing?

Diesel47 said:
Hey guys, I have a Nexus 7 16gb 2013 wifi running 5.1.1 lollipop LMY48G.
I'm trying to downgrade it to kitkat so I can install some software the only works correctly on kitkat on it.
I follow this guide: laptopmag(.com)articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
and whenever I finish, I get a green android laying down with a red caution symbol ontop of him.
But the weird thing is I'm able to install 5.1.1 no issues using the same method, but if I pick anything older... The green android shows up..
Right now I'm back on a fresh 5.1.1 install.
Is there something I'm missing? From all my googling it seems like I should be allowed to installed kitkat no issues on this device. What am I missing?
Click to expand...
Click to collapse
Do you get that android after when you try to boot normally? If you turn it off and turn it back on again normally does it still show up? It is weird if it does because that sounds like the stock recovery, and shouldn't really show up unless you try to boot into it via the bootloader.
When you follow the guide, do you also do the last step, where you interrupt the reboot to lock the bootloader? If you do could you try to let it boot uninterrupted after the update?

theminikiller said:
Do you get that android after when you try to boot normally? If you turn it off and turn it back on again normally does it still show up? It is weird if it does because that sounds like the stock recovery, and shouldn't really show up unless you try to boot into it via the bootloader.
When you follow the guide, do you also do the last step, where you interrupt the reboot to lock the bootloader? If you do could you try to let it boot uninterrupted after the update?
Click to expand...
Click to collapse
Hello, Thank you for replying..
I ran the flash-all.bat from the 4.4.4 image files stock from google and it got this error:
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.05'.
Update requires 'FLO-04.02'.
I guess my bootloader is too recent? Google does not want us downgrading?
Update: I ran fastboot oem unlock and was able to run the flash-all.bat
Now i'm waiting on the device to boot up, its currently stuck on a black screen that has white text in the middle saying "google".
Update: It is permastuck on the google screen... I don't know what to do Also to answer your question, yeah I reboot it multiple times. It doesn't work. If I choose "start" from the bootloader it will be stuck on the black google page permanently.
Is there some way I can just wipe the device and install 4.4.4 on it? Kinda like a regular PC?

You need to flash the bootloader before executing the flash-all file. To do that boot into the bootloader then use the command
"fastboot flash bootloader 'bootloader file'"
where bootloader file is the file with bootloader in its name you got from your zip file. Then
"fastboot reboot-bootloader".
Then you can use the flash-all file.

bootloop after wrong img (N2G47Z instead of 4CoreOreo)

Hi everybody,
tried to look for soulutions but without any luck...
I wanted to go back to Android 7 from the 8 (because i had the feeling the 8 is much slower).
I couldn't manage to flash the 7 as long as the phone would lock itself everytime while starting the downgrade so i flashed the N2G47Z 4 core image file on top of the Stock 8.1. I know, i should have used a 4CoreOreo....
Result: i'm an idiot with a phone in bootloop. Cannot go into recovery or anything. i manage to see the Google word and the warning that i should lock the bootloader and go to website g.co/ABH
I will wait until the battery drains and try to switch it on again but than what is the right procedure to follow in order to fix it? (if any)
thank you

Pippolinus said:
Hi everybody,
i flashed the N2G47Z 4 core image file on top of the Stock 8.1. I know, i should have used a 4CoreOreo....[/U]
I will wait until the battery drains and try to switch it on again but than what is the right procedure to follow in order to fix it? (if any)
thank you
Click to expand...
Click to collapse
UPDATE
i put the phone in the freezer (couldn' t wait the battery to drain) and i discover that if it is switched off you can enter in fastboot mode for one time (than you go back to bootloop)
I flashed the 4CoreOreo and now i get the same warning and error but after 30 seconds it goes off and it start to load the system.
However it doesn't finish to load it becasue it says Android is corrupted and a full wipe is suggested. I did the full wipe but nothing changed.
So now i'm stuck but in a kind of "light bootloop". I tried to updload Android 7 following the procedure through ADB but it doesn't work.

Try to go to fastboot and flash factory image of 7 from official site, and use the flash_all.sh / flash_all.bat. While you're doing that instead of flashing boot.img from the factory. Use the 4 core for 7 from the https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199 thread. Use the nougat boot.img. That's it. You'll be back on track.

Pippolinus said:
i put the phone in the freezer
Click to expand...
Click to collapse
Literally one of the worst things you could do to a smartphone(or any other type of electronics).
Your phone is probably begging for a motherboard replacement right now...

Danish Fayaz said:
Try to go to fastboot and flash factory image of 7 from official site, and use the flash_all.sh / flash_all.bat. While you're doing that instead of flashing boot.img from the factory. Use the 4 core for 7 from the https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199 thread. Use the nougat boot.img. That's it. You'll be back on track.
Click to expand...
Click to collapse
Hi, thank you for the answer.
I' ll try again changing the boot.img inside the folder ... when i tried yesterday (i tried to flash the 7 and the 8 even with the Nexus toolkit) it was not possible because everytime i unlock it (throught ADB for example) at the first reboot goes back to locked automatically, so the process stops showing some errors.
Changing that .img the problem goes away?

Pippolinus said:
Hi, thank you for the answer.
I' ll try again changing the boot.img inside the folder ... when i tried yesterday (i tried to flash the 7 and the 8 even with the Nexus toolkit) it was not possible because everytime i unlock it (throught ADB for example) at the first reboot goes back to locked automatically, so the process stops showing some errors.
Changing that .img the problem goes away?
Click to expand...
Click to collapse
If your bootloader automatically locks itself, that's a hardware issue. While booted in the bootloader, you should see "No RPMB" along one of the lines. This means that Your motherboard was replaced.
Sent from my Nexus 5X using Tapatalk

Moto Z Play has no OS

OK, so my Moto Z Play has no OS on it, and it boots into TWRP.
It's been awhile since I touched the phone since the part of the screen shattered, so I don't remember doing anything related to twrp on it.
Anyway, I want to know if there is any way to get it running again, or is it trash?

timster01 said:
OK, so my Moto Z Play has no OS on it, and it boots into TWRP.
It's been awhile since I touched the phone since the part of the screen shattered, so I don't remember doing anything related to twrp on it.
Anyway, I want to know if there is any way to get it running again, or is it trash?
Click to expand...
Click to collapse
Damn. That sucks. I guess you're in the same boat as me needing some help too.

If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701

masivb said:
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
Click to expand...
Click to collapse
Although I have had TWRP on an old device before, I know Android 8 and later doesn't like to be messed with. And Android 8 Oreo is what I want to update it to since it only had 6 now.
It's an XT1635-02 Internationa version that was sold in Mexico and has the attmx software channel. I of the understanding that the software channel doesn't really matter.
Can I update it with RSDLite through fastboot? And would "ADDISON_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I got from androidfilehost.com be the correct firmware to update it with? Also the current baseband is "M8953_10203.02.04.42R ADDISON_ROW_CUST" with a build number of "MPN24.104-25". Does that make a difference?
I do appreciate someone finally trying to help. Thanks, Masiv.

masivb said:
If it boots to TWRP all you would need is a ROM on an SD card...
If you're looking to go back to stock try this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-motorola-z-play-xt-1635-02-t4063701
Click to expand...
Click to collapse
I was able to get a rom from alberto97 loaded, but want to go back to stock and am stuck at step 4 of your instructions
when trying to enter a fastboot command, the cmd window just sits on <waiting for device>. I'm not sure where to go from here.

timster01 said:
I was able to get a rom from alberto97 loaded, but want to go back to stock and am stuck at step 4 of your instructions
when trying to enter a fastboot command, the cmd window just sits on <waiting for device>. I'm not sure where to go from here.
Click to expand...
Click to collapse
If you're stuck on step 4 most likely OEM_Flashing is disabled
Type:
Code:
fastboot flashing unlock
to re-enable fastboot flashing and repeat step 4.
Edit:
<waiting for device> could be driver issue. re-install Moto usb drivers: https://support.motorola.com/us/en/drivers

moto z play does not switch on and it shows no os
hello sir,
i tried to install lineage os 17 for moto z play. it shows in twrp that updater process ended with error 7. so look up for what is problems solution. so i made some changes to transcript. but problem doesn't solve.
but after that i can switch on my phone. when carefully search my twrp. so when i click on reboot, it shows no os installed. and my phone doesn't open at all. it only shows your phone boot in 5 seconds. then black screen. after some time again it shows your phone boot in 5 seconds.
so i tried to install android pie version through sd card.and i download custom rom for that procedure.but again it end with updater process ended with error 7.
now i'm very bored, confused and whatnot. so i search for moto z play stock rom and so i can reinstalled my older version. so i look up your article about it.
but when i open cmd through your file and give command of fastboot. it shows no cmmand regarding fastboot.
so i'm stuck. please help me.
phone- MOTO XT1635-02
after go to work whrn return i see that my phone does not goes into fastboot mod.
it only blink white light on top.

masivb said:
If you're stuck on step 4 most likely OEM_Flashing is disabled
Type:
Code:
fastboot flashing unlock
to re-enable fastboot flashing and repeat step 4.
Edit:
<waiting for device> could be driver issue. re-install Moto usb drivers: https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
Thank you. I was able to restore Android 8.0 onto the Z Play.

LunaEros said:
Although I have had TWRP on an old device before, I know Android 8 and later doesn't like to be messed with. And Android 8 Oreo is what I want to update it to since it only had 6 now.
It's an XT1635-02 Internationa version that was sold in Mexico and has the attmx software channel. I of the understanding that the software channel doesn't really matter.
Can I update it with RSDLite through fastboot? And would "ADDISON_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I got from androidfilehost.com be the correct firmware to update it with? Also the current baseband is "M8953_10203.02.04.42R ADDISON_ROW_CUST" with a build number of "MPN24.104-25". Does that make a difference?
I do appreciate someone finally trying to help. Thanks, Masiv.
Click to expand...
Click to collapse
RDSLite I don't know enough about but I know it can hard brink your device if a flash goes wrong - I wouldn't recommend it.
That also sounds like a Marshmallow ROM. The latest stock on your phone is most like Noguat or Oreo bootloader so you won't be able to flash marshmallow so that explains why it wasn't working.
The easiest thing to do is download the April Oreo patch zip and use fastboot flash it back to stock from the link I posted previously. That should get you out of every scenario as it has been verified by me to work even from a bricked state back to stock.

It's all good. I was finally able to flash it up to 8.0.0. Thanks.

pankajr95 said:
moto z play does not switch on and it shows no os
hello sir,
i tried to install lineage os 17 for moto z play. it shows in twrp that updater process ended with error 7. so look up for what is problems solution. so i made some changes to transcript. but problem doesn't solve.
but after that i can switch on my phone. when carefully search my twrp. so when i click on reboot, it shows no os installed. and my phone doesn't open at all. it only shows your phone boot in 5 seconds. then black screen. after some time again it shows your phone boot in 5 seconds.
so i tried to install android pie version through sd card.and i download custom rom for that procedure.but again it end with updater process ended with error 7.
now i'm very bored, confused and whatnot. so i search for moto z play stock rom and so i can reinstalled my older version. so i look up your article about it.
but when i open cmd through your file and give command of fastboot. it shows no cmmand regarding fastboot.
so i'm stuck. please help me.
phone- MOTO XT1635-02
after go to work whrn return i see that my phone does not goes into fastboot mod.
it only blink white light on top.
Click to expand...
Click to collapse
Hello friends,
my motoz play has been hard brick for almost half year now.
i search what i can do for solution. but doing some research, i have able to unbrick my phone.
how it is i don't know.
but i can what i have done to go through problem.
i have download
1. moto device manager
2. minimal adb and fastboot version 1.4.3
4. qualcomm usb driver for windows
3. Rescue and Smart Assistant
4. blank flash file
so after installing Qualcomm USB driver, my device shows in divece manager......