Alright, i was planning on selling my g4 so i put the stock ROM back on after having been unlocked for the time I've had the phone. Apparently since it was unlocked and it tried updating after i put stock back on, it messed with the boot loader (i assume) because it refuses to turn on now. whenever i plug it in, the led flashes but nothing else and i cant get into recovery, boot loader, etc.
is there any known way to fix this, or is the phone beyond fixing at this point?
Which stock ROM did you have on before you updated, and did this device have stock (Motorola) Nougat firmware on at any point? From what you've described, sounds like you may have flashed older firmware than what was on the device and then the update corrupted the bootloader.
If the LED is flashing and you can't get back to bootloader/recovery, you may have to try this blankflash:https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Bear in mind the blankflash may take a few attempts to communicate with your device before it works.
echo92 said:
Which stock ROM did you have on before you updated, and did this device have stock (Motorola) Nougat firmware on at any point? From what you've described, sounds like you may have flashed older firmware than what was on the device and then the update corrupted the bootloader.
If the LED is flashing and you can't get back to bootloader/recovery, you may have to try this blankflash:https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Bear in mind the blankflash may take a few attempts to communicate with your device before it works.
Click to expand...
Click to collapse
I got the firmware from the motorola site, ill try the blankflash and see how it goes
PMM55555 said:
I got the firmware from the motorola site, ill try the blankflash and see how it goes
Click to expand...
Click to collapse
Ah, which firmware did you download? Motorola hasn't updated those firmwares in a while, and as far as I know they are still Marshmallow.
echo92 said:
Ah, which firmware did you download? Motorola hasn't updated those firmwares in a while, and as far as I know they are still Marshmallow.
Click to expand...
Click to collapse
Yeah it was marshmallow and it tried downloading the nougat firmware, the blank flash worked. Thank you so much
PMM55555 said:
Yeah it was marshmallow and it tried downloading the nougat firmware, the blank flash worked. Thank you so much
Click to expand...
Click to collapse
Good to hear it worked, and good luck with selling your device. Just something to bear in future, try not to downgrade your stock firmware if you can, or if you do, don't take OTA updates. Motorola and other companies appear to be not keen on/do not formally allow users to downgrade, and cause the issues that you encountered as updates do not appear to recognise when parts of your firmware are not at the same update level as other parts.
Related
I have a Moto X Pure Edition - I received a software update. I updated the phone - and it's stuck in a bootloop. It goes to the Motorola logo, then to a black screen that says "No command." and then back to the Motorola logo over and over again.
Does anyone know how I can fix this?
were you rooted??
if u wer rooted and u installed the update then ur in a big trouble....
pls be more specific so that anyone can help you out....
SuperT.A. said:
I have a Moto X Pure Edition - I received a software update. I updated the phone - and it's stuck in a bootloop. It goes to the Motorola logo, then to a black screen that says "No command." and then back to the Motorola logo over and over again.
Does anyone know how I can fix this?
Click to expand...
Click to collapse
When you say you "updated the phone" did it actually flash anything or did it just go immediately to Andy on his back saying No Command? Are you pure stock?
You can try going into the recovery menu from there by pressing POWER+Vol Up and clearing cache then reboot.
Deleting the Cache fixed me when I took the Update after being Rooted as "Ace" says..
acejavelin said:
When you say you "updated the phone" did it actually flash anything or did it just go immediately to Andy on his back saying No Command? Are you pure stock?
You can try going into the recovery menu from there by pressing POWER+Vol Up and clearing cache then reboot.
Click to expand...
Click to collapse
I am on pure stock android. never rooted or unlocked the boot loader. update is straight from Motorola.
acejavelin said:
When you say you "updated the phone" did it actually flash anything or did it just go immediately to Andy on his back saying No Command? Are you pure stock?
You can try going into the recovery menu from there by pressing POWER+Vol Up and clearing cache then reboot.
Click to expand...
Click to collapse
I don't know - I hit 'update' and then left. When I came back, it was in the bootloop.
Restore to stock. Links.
By now you should have already found these links in this forum. Anyway, here they are below check them.
But remember, please don't blame me for any damage you will do to your device as I won't be responsible for that. Proceed at your own risk. Your warranty will not be void until unless you unlock your bootloader or flash an unofficial ROM. Again no guarantee here.
Restore to stock:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Download firmwares from here below.
*Note: Download only same or a newer version of firmware. Restoring to stock with versions older than you currently have will give you errors.
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
Good luck.
AlphaKilo09 said:
By now you should have already found these links in this forum. Anyway, here they are below check them.
But remember, please don't blame me for any damage you will do to your device as I won't be responsible for that. Proceed at your own risk. Your warranty will not be void until unless you unlock your bootloader or flash an unofficial ROM. Again no guarantee here.
Restore to stock:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Download firmwares from here below.
*Note: Download only same or a newer version of firmware. Restoring to stock with versions older than you currently have will give you errors.
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
Good luck.
Click to expand...
Click to collapse
do I use the LA version? model is US version, unlocked
SuperT.A. said:
do I use the LA version? model is US version, unlocked
Click to expand...
Click to collapse
If you have US version then you should download only US version.
The 'System version' and 'Build number' of your device should match with the one you are going to download. Latest version also good but don't download the older version than yours.
If you don't know exactly what version were you on, check on another moto X pure device if any of your friends got one.
I decided to take the phone back to where I bought it - they gave me a full refund. Thanks to everyone that tried to help.
Could a moderator remove or close this thread? It is no longer needed.
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
tcoursey said:
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
Click to expand...
Click to collapse
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
scrin378 said:
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Oh believe me my head hit the wall for sure! I got careless and wasn't thinking straight. No reason to lock the boot loader except it was on a list of steps to get back to stock..and I guess it was late! doh.
There are lot's of posts/videos I've seen that should allow what I'm trying to do with sideload adb but mine keeps getting a signature verification error. Each new full version of a release 7.0 8.0 etc..has the entire rom, images etc. So your suppose to be able to flash those even though they are OTA updates... *shrug*
It's a blur what I did exactly in some areas. I at one point may have tried to flash the set of Stock IMG files as well. But for sure now all I'm left with is a locked phone with who knows what on it! Stock recovery...some form of 7.0.0 that has NYC as letters...that I can find NOWHERE! on any official releases...
Prob trash, I really want that night back..lol.
Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!
I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.
Untouched? Is there anything on here like that?
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken
djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.
Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!
Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.
Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.
Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.
93-14 hasn't been leaked yet. So you'll be stuck for now.
Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.
Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.
Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.
Looking for any help or at least clues about what is wrong.
I was on ArrowOS 10, updated OTA to latest build two days ago, all was fine. Tonight it suddenly rebooted and when I unlock it, the desktop says the OS is loading, but it hangs, and then eventually reboots, bootlooping.
I had a working Nandroid backup, so I restored that from TWRP. Still cannot get the OS loaded. Wiped everything, even internal storage, backup still had same issue.
Then I tried reinstalling an older build of the ROM that I knew worked for me and I get stuck on the "Just a sec" after choosing a language. Eventually it reboots and hangs on the "Just a sec" before rebooting again. Wiped everything again and I tried another build of the same ROM, same problem. More wiping, tried Pixel Experience, same problem.
I'm thinking something is corrupted but I don't get any specific error messages so I'm not sure what to do. I repaired the data partition in TWRP, thinking that was the issue, but still cannot get any ROMs to load.
Any guidance is greatly appreciated as the phone is useless in this state. Thank goodness I have all my data backed up, but I really hope the phone is salvageable. Thank you.
twasbrillig12 said:
Looking for any help or at least clues about what is wrong.
I was on ArrowOS 10, updated OTA to latest build two days ago, all was fine. Tonight it suddenly rebooted and when I unlock it, the desktop says the OS is loading, but it hangs, and then eventually reboots, bootlooping.
I had a working Nandroid backup, so I restored that from TWRP. Still cannot get the OS loaded. Wiped everything, even internal storage, backup still had same issue.
Then I tried reinstalling an older build of the ROM that I knew worked for me and I get stuck on the "Just a sec" after choosing a language. Eventually it reboots and hangs on the "Just a sec" before rebooting again. Wiped everything again and I tried another build of the same ROM, same problem. More wiping, tried Pixel Experience, same problem.
I'm thinking something is corrupted but I don't get any specific error messages so I'm not sure what to do. I repaired the data partition in TWRP, thinking that was the issue, but still cannot get any ROMs to load.
Any guidance is greatly appreciated as the phone is useless in this state. Thank goodness I have all my data backed up, but I really hope the phone is salvageable. Thank you.
Click to expand...
Click to collapse
Sounds not so good. I would try to fastboot flash the latest signed Motorola firmware.
Here's a link where you can find it and how to do it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Sounds not so good. I would try to fastboot flash the latest signed Motorola firmware.
Here's a link where you can find it and how to do it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thank you! That fixed it. Any idea what happened? Could it have been from the OTA update two days prior? I'd like to prevent it from happening again if possible.
twasbrillig12 said:
Thank you! That fixed it. Any idea what happened? Could it have been from the OTA update two days prior? I'd like to prevent it from happening again if possible.
Click to expand...
Click to collapse
First of all good to hear you've got everything up and working again. Difficult to say what caused the problem, best would be to give these informations to the ROM maintainer/developer because he knows best what is changed in his custom ROM/OTA compared to the original stock firmware.
I would think it has been the OTA update that caused the trouble, OTA's are problematic for manufacturers and even more for custom ROMs with a smaller userbase and less employees.
My advice would be to avoid OTA updates if possible, often it's better to (dirty) flash the whole ROM by hand if available.
But the exact reason is not easy to find out, as said check the ROMs thread or PM the maintainer.
If you're in a situation like you've been it's always a good idea to flash original stock firmware, it brings the device to the most stable and recommended state.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
First of all good to hear you've got everything up and working again. Difficult to say what caused the problem, best would be to give these informations to the ROM maintainer/developer because he knows best what is changed in his custom ROM/OTA compared to the original stock firmware.
I would think it has been the OTA update that caused the trouble, OTA's are problematic for manufacturers and even more for custom ROMs with a smaller userbase and less employees.
My advice would be to avoid OTA updates if possible, often it's better to (dirty) flash the whole ROM by hand if available.
But the exact reason is not easy to find out, as said check the ROMs thread or PM the maintainer.
If you're in a situation like you've been it's always a good idea to flash original stock firmware, it brings the device to the most stable and recommended state.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Okay, I was planning on dirty flashing the next update anyway. I usually do since OTA's often don't work for me, but this last one seemed like it was. I'm definitely notifying the developer. Thanks again!