I purchased a 2013 moto x, used, unlocked, updated it using the official ota update, now when I boot the phone I see Andi on his back with "No Command", I can boot into fastboot, so I tried flashing the most recent update both manually and via RSD lite. No matter what I get " security version downgraded PIV block validation for (got/system) failed.
I've been through just about every thread there is about restoring to stock, and everything seems to say I'll be fine if I flash the same version, but I continue to get errors, not sure where to go from here, any help would be appreciated,! Im not a complete noob, but I'm definitely not a pro..I had intentions of rooting the phone after updating, but now .I'm just afraid I permanently bricked the new phone....
You need to flash the same ROM that you had before the update with fastboot. Also you need to turn off your phone and boot on it with Power button + volume down or you won't be able to flash the ROM.
Thanks for the reply
After an entire day of not sleeping and flashing the EXACT same firmware on my device a dozen different ways it finally worked!
RDS lite, and manually flashing didn't work, but I tried moto recovery fixer tool I found on a different forum. And flashed the same firmware, but this time it was successful and the phone is up and running like new. I think I'll be returning the phone, but I appreciate the reply and the help I found in XDA! Y'all rock!
Related
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
MortaLPortaL said:
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
Click to expand...
Click to collapse
Do you get a pre verification error? I just posted this question yesterday, and I was helped out. I had exactly the same issue as you had, i think
http://forum.xda-developers.com/moto-g-2014/help/help-asap-fastboot-preflash-validation-t2949337
mahendru1992 said:
Do you get a pre verification error? I just posted this question yesterday, and I was helped out. I had exactly the same issue as you had, i think
http://forum.xda-developers.com/moto-g-2014/help/help-asap-fastboot-preflash-validation-t2949337
Click to expand...
Click to collapse
Funny thing is, it was the firmware I was using along with ADB not being installed.
I got everything up and running. Rooted w/ TWRP. But I am unsure if I can unroot and lock the bootloader so I can hopefully get the OTA to 5.0
MortaLPortaL said:
Funny thing is, it was the firmware I was using along with ADB not being installed.
I got everything up and running. Rooted w/ TWRP. But I am unsure if I can unroot and lock the bootloader so I can hopefully get the OTA to 5.0
Click to expand...
Click to collapse
You don't need to lock your bootloader to receive the update. What you need is stock recovery, stock rom which in essence is everything stock. Just let the bootloader remain unlocked as I've heard that there still isn't a way to unlock the bootloader if you upgrade with it locked.
Mind you this is all heresay
mahendru1992 said:
You don't need to lock your bootloader to receive the update. What you need is stock recovery, stock rom which in essence is everything stock. Just let the bootloader remain unlocked as I've heard that there still isn't a way to unlock the bootloader if you upgrade with it locked.
Mind you this is all heresay
Click to expand...
Click to collapse
I tried to flash the recovery with the recovery.img and it worked until it showed the android with the red triangle. never goes any further than that. Reflashing TWRP is fine but stock is a no go.
MortaLPortaL said:
I tried to flash the recovery with the recovery.img and it worked until it showed the android with the red triangle. never goes any further than that. Reflashing TWRP is fine but stock is a no go.
Click to expand...
Click to collapse
The Android with the red exclamation sign IS your recovery! To see the options: press the volume up button for 10-15 seconds. Then press the power button with it, and let go! Voilà: your stock recovery! It's hidden, because it's not meant for the 'common user'.
smitharro said:
The Android with the red exclamation sign IS your recovery! To see the options: press the volume up button for 10-15 seconds. Then press the power button with it, and let go! Voilà: your stock recovery! It's hidden, because it's not meant for the 'common user'.
Click to expand...
Click to collapse
haha well thank you!
I feel hella stupid in a sense..but I appreciate you guys for being awesome and patient.
MortaLPortaL said:
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
Click to expand...
Click to collapse
your post helpme to find what i was doing wrong.
in my particular case, i just needed to find my own Firmware (stock version) of kitkat 4.4.4 for my country, COLOMBIA. and that just went great. after that, again, flash Titan 2.0.3beta, that was it. Smooth as a criminal!
So here's the deal. I had a Moto X Dev Edition with TWRP recovery and the latest CyanogenMod ROM, working properly.
I returned to stock using a Motorola ROM and their instructions, did get a gpt_main error in the process, but since it worked for a certain Reddit user (goo.gl/2sEmjz -- can't post links yet!) I decided to continue. It booted fine into stock, but when I did system updates, it would reboot into TWRP. So I flashed the recovery.img file. After that, the phone booted, then rebooted, and went into a recovery "installing updates."
I walked away for a second, came back, and the screen was black. I can't "force it off," it doesn't appear to be running, and I can't get into fastboot. Is the phone bricked (which I'm leaning to), or is it still running and I just need the battery to run out, or is there some other way to revive this phone via USB?
Hoping there's some expert I can get advice from, and thanks in advance!
Hello, i have been researching for this issue that i have for over a month now, and yet i haven't found any solution or even a clue on how to fix it, and im sure lots of people are having the same issue that im having, let me explain what exactly happened to my phone and what i exactly tried
i was running on 5.0.1 G920TUVU1AOCG, and at that time "Ping Pong Root" was not yet available, so the only way to root the phone was to flash the "g920t_of6_aou_kernel_v1.tar" witch i did and installed SU using "g925t_of6_aou_twrp_recovery_v13.tar" and the phone worked perfect after that, and after the 5.1.1 lollipop came out, i decided to upgrade to that, so i flashed stock 5.1.1 odin firmware and flash the custom kernel "g920t_of6_aou_kernel_v1.tar" to get it out the bootloop since it was flashed previously on it, it worked and booted up and all seemed to be fine, i also wanted to perform a factory reset, and here is where the PROBLEM started, i forgot to turn on OEM Unlocking in Dev options, so after the factory reset, the phone got stuck on the bootloop "Samsung galaxy s6; powered by android" and the only way to make it bypass this bootloop is by flashing the "g920t_of6_aou_kernel_v1.tar" again, but i cant flash that because i forgot to turn on the OEM Unlocking in the dev options, and every time i try for flash any custom recovery or custom kernel and will give me "Custom Binary (BOOT) blocked by FRP Lock", so now im stuck on the bootloop, i cant access the phone to turn on the OEM Unlocking, Phone is basically STUCK.
I have tried flashing all stock firmwares that are, i have tried flashing all available kernels, i have tried Factory resetting the phone and wiping the catch, i have tried every guide on XDA and nothing ever worked for me.
i apologize for the long explanation, but i just dont want people to think that i am repeating the same question over and over since a similar question was asked by other members on XDA previously.
Thank you very much for taking the time and reading my question.
Do you still have recovery mode?
EDIT: In this thread: http://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-t3152054 every person that had the problem fixed it by flashing the stock firmware. make sure you're flashing the stock firmware that's the exact same as the firmware when your phone worked. So if you were on OI1 for example, you have to flash OI1 firmware or it wouldn't work. Try a couple times too, I've heard ODIN can be wonky sometimes.
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
ameenz77 said:
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
Click to expand...
Click to collapse
Try to factory reset in recovery and flash the tar trough ODIN again. If that doesn't work, try to restore it with SmartSwitch. A lot of people have success restoring their phone that way. If that doesn't work then I don't know.
Hi there,
I got a bricked G5S+, which I reported in another thread already.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
That happened after I rebootet the cellphone for a longer time.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me and now cannot access android anymore to do so.
Anyway I thought: fine: I will just flash the stock OS again taking care of the software defect.
After having had some issues I flashed Sanders (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) following that thread here:
https://animetrick.com/flash-stock-rom-moto-g5s-plus-locked-bootloader-2018/
It is quite similar as this thread, which deals with installing a stock OS to a bootloader-locked phone:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
The thing is I followed all steps but still get the same error:
A lying down android with a red questionmark and saying 'no command'.
Does anyone have an idea what else to try?
I am not aversed to install a custom Rom, such as the official RR v6.0.0, but I have no idea how to do so with a currently bricked phone.
Maybe you guys have a solution for me to unbrick and finally use my phone again.
Thanks a lot!
Regards from Germany
Matt
Hey bro Im not sure if you still need help but, if so can you try to boot into a recovery?
Hi Carlos,
yes I still need help.
I can boot into recovery. And fastboot runs and detects the phone, too.
Any idea what I can do?
Go ahead and download twrp from the Roms sections and also begin the process to unlock the boot loader, we can see if it still can be done without having enabled the setting in the developer sections, and if so we can either then flash the recovery and a custom rom or install stock again.
Sent from my iDevice running Smoothshake v11.3.1
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
There is no need anymore to install a custom rom (at least not currently )
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
I have fallen into same issue, i cannot install any custom rom or recovery to it but i can access fastboot & one recovery that has update via adb sideload / sd card but nothing works, shows failed line 2 error / install aborted .
the device just showing oem locked in fastboot & rom install or recovery install fails & says cause too many links
the phone starts & stucks after the motorola logo
anybody with any idea?