Related
I was getting ready to install MIUI v5 when this happened. I was on an older version of Paranoid Android, I'm not too sure which one but it's not the most recent 4.3 one. I tried to boot into clockworkrecovery mod, but now I'm just getting a boot loop. I see the Google symbol with the unlocked lock at the bottom, and then it goes to the Clockwork logo for like 3 seconds. At the bottom it shows the version number, v6.0.4.3, but then it starts to boot again. Right before the logo disappears, the whole screen gets brighter for a split second. How can I fix this?
Any help is much appreciated
Thanks,
jjjnmk
jjjnmk said:
I was getting ready to install MIUI v5 when this happened. I was on an older version of Paranoid Android, I'm not too sure which one but it's not the most recent 4.3 one. I tried to boot into clockworkrecovery mod, but now I'm just getting a boot loop. I see the Google symbol with the unlocked lock at the bottom, and then it goes to the Clockwork logo for like 3 seconds. At the bottom it shows the version number, v6.0.4.3, but then it starts to boot again. Right before the logo disappears, the whole screen gets brighter for a split second. How can I fix this?
Any help is much appreciated
Thanks,
jjjnmk
Click to expand...
Click to collapse
Try flashing recovery again via fastboot
Code:
fastboot flash recovery recovery.img
RajatPatel said:
Try flashing recovery again via fastboot
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've been looking into that, but I don't have the proper drivers installed on the computer I have with me (which I know is really really dumb). Is there a way to install the drivers even if my phone can only get to fastboot?
jjjnmk said:
I've been looking into that, but I don't have the proper drivers installed on the computer I have with me (which I know is really really dumb). Is there a way to install the drivers even if my phone can only get to fastboot?
Click to expand...
Click to collapse
If you don't know driver stuff, use GNex Root Toolkit. It will guide you to install adb/fastboot drivers.
http://forum.xda-developers.com/showthread.php?t=2208865
http://www.androidrootz.com/2012/08/how-to-get-install-correct-driver-for.html
For basic stuff take a look at this, it's worth to bookmark the following link for future reference:
http://forum.xda-developers.com/showthread.php?t=1828061
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
metalblaster said:
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Dunno if I'm allowed to, but...
BUMP!!
metalblaster said:
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
You're absolutely right! Always, always make a backup/nandroid before flashing a different rom. But if you don't and like to live dangerously you should at least have the sdk installed and know how to use adb/fastboot! One thing though about restoring a backup, it does not restore the bootloader. Android L uses bootloader version 4.04 and KitKat uses 4.02. The first L preview used the same bootloader as KK but the new preview does not. I have no idea what kind of bugs or worse would result from restoring a KK nandroid onto the 4.04 bootloader. Maybe nothing but I purposely didn't try to find out if it would cause any problems. Couple nights ago I checked out the preview for maybe an hour then went back to 4.4.4. I flashed the 4.4.4 factory image using a modified flash_all batch file then restored on top of that. I guess I could have instead fastboot flashed the bootloader then went straight into recovery to install my backup. Just something to think about, bootloader versions.
CasuallyDressed said:
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Click to expand...
Click to collapse
You said previously "The tablet will now only display 2 screens: Google with unlocked padlock, or recovery." Unlocked padlock means your bootloader is unlocked and your device now can have images flashed to it. Recovery or bootloader screen? You need to be able to get into the bootloader screen. Press and hold the volume down button, while still holding down the volume button press the power button for a few seconds release the power button and it should go into the bootloader screen. There are a couple toolkits that might help, Wug"s and One-Click Restore come to mind. I've never used them so I wouldn't be any help as far as they go. I can try to help if you want to use the sdk. Do you have the android sdk installed?
i had the same problem , i tried one click restore and it works fine
Wow don'T!!!!
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
Don't delete your user data before backing it up!
See WugFreshs Threads on XDA!
So I used ATGAdmin's guide here: http://forum.xda-developers.com/showthread.php?t=2381582
Used "Dead_Nexus7.bat" and it fixed me right up. Plus, I love the "Look you dumb motherf**kers" attitude he has in his video.
I appear to be all sorted anyway! Thanks to those who suggested 'One Click Restore', it set me on the right path.
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.
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
Click to expand...
Click to collapse
I have the same problem
I actually was about to start a new thread near exact to yours.
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
Click to expand...
Click to collapse
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I don't want to flash it manually, and I want it to be able to install OTAs normally because I'm trying to sell it to a friend and don't want them to constantly to be seeing a "Update Available" notification that wont go away.
Nothing? No ideas? ......Anyone?
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I tried this using ADB sideload, got "signature error"??
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......