So I bought a Moto E XT1526 from FreedomPop for my parents. Been working great for over a month. Then not sure what happened, dad calls me and said it is not working anymore. The phone is stuck in AP Fastboot mode. Tried recovery and Factory reset but it just reboots back in to AP Fastboot mode.
Tried unlocking and get the error, ' Check ;Allow OEM Unlock' in Developer Options. Well....cant cuz phone doesn't boot up.
Tried reflashing to stock and get error, Failed (Remote failure).
Is it a brick now? Not sure how it got to this state as my parents are not techy at all and does not mess with settings. Thx for reading.
emanon1982 said:
So I bought a Moto E XT1526 from FreedomPop for my parents. Been working great for over a month. Then not sure what happened, dad calls me and said it is not working anymore. The phone is stuck in AP Fastboot mode. Tried recovery and Factory reset but it just reboots back in to AP Fastboot mode.
Tried unlocking and get the error, ' Check ;Allow OEM Unlock' in Developer Options. Well....cant cuz phone doesn't boot up.
Tried reflashing to stock and get error, Failed (Remote failure).
Is it a brick now? Not sure how it got to this state as my parents are not techy at all and does not mess with settings. Thx for reading.
Click to expand...
Click to collapse
If the device is being recognized by adb flashing stock firmware is probably your only chance of repairing it. It might not work if android debugging isn't turned on in developer settings. Try flashing only the recovery and system. I'm not sure what else to tell you.
Not sure, but probably an OTA killed it if the phone was running an older version and was being updated.
Try downloading the 'latest' stock Rom and try updating it again. You will have to do a little research on this, there is a step-wise flashing method, with erasing the partitions, try searching threads which specifically talk about unbricking, that should help.
Related
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
After flashing the "zomgunlock-lite.sbf" you could have pulled the battery (then put it back in) and without turning it on just plug back into the computer and it would have turned on by itself and given you a menu in which you would have selected fastboot and then entered the commands for unlocking the bootloader.
I'm glad you got yours working and appreciate the info but there is a way out of it. Actually, someone has created an automatic script for just that occasion here:
http://forum.xda-developers.com/showthread.php?t=1182871
Just follow the directions for the error.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
This thread really did me a massive favor in telling me exactly what I was searching for when google was being useless. Thank you guys. Particularly the post above mine about soft bricks.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
Massive n00b post, nothing but misinformation.
Sweet.....
soft brick could be fixed.. my phone is hard one, can not be read by PC.. it is always booting loop.
and blemeIf
I have also hard bricked my Atrix. I have read many post on this forum and on google that phone can not be recovered after hard brick. Is it confirmed that there is no way to recover after a hard bricked? Please help.
mysticdrew said:
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
Click to expand...
Click to collapse
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
patsprobst said:
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showthread.php?t=1648947
dcarpenter85 said:
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
Click to expand...
Click to collapse
I can't believe it was so hard to find these particular instructions and that it is not listed anywhere on the sbf file. Thank you so much for your answer and the last sentence should be added to the sbf file. Actually your whole statement should be there. Thanks a lot. Saved me a lot of anguish.
You'll have to forgive me for making another one of these posts, but every thread I find with this problem has dead links to Megaupload and File Sonic.
I just got an Atrix today through Craigslist that I quickly (successfully) rooted. Problem is, when I tried to unlock my bootloader, I messed up and ended up with the "SVF:105:1:2 Failed to boot 0x1000" screen with. Fortunately I do have options beneath it, which I've gathered to mean my phone can be saved? Can anyone help me (with working links)?
If you have a menu of options below that 0x1000, you're not hard bricked.
Phones that took the official, over-the-air Gingerbread update get this soft-brick when flashing pudding to unlock the bootloader. When it gets to that "failed to boot" menu, it should automatically select fastboot mode after 5 seconds.
At this point, it's ready and waiting for you to issue the "oem fastboot unlock" command (no quotes, with your phone still connected to the computer) and complete the unlock process. When your phone comes back up, it will be factory reset.
Thanks for the response and advice. I'll be sure to try that when I get home.
EDIT: Worked like a charm!! Thanks a bunch man, you saved my ass (and my phone's!).
...and now I realize I stated the command backwards. "fastboot oem unlock", for crap's sake... Glad you got it working. (and, despite evidence to the contrary, there are actually girls on these forums. Sometimes.)
Go have fun with it. And for the love of all that is holy, don't use RSD Lite to flash a pre-Gingerbread SBF or you really will have a hardbricked Atrix on your hands.
My wifi kinda stopped working,so i restarted the phone. When the phone restarted it got stuck on bootloader and i cant move past it. I tried normal powerup,recovery all of which led to bootloader menu again and again with the same error "hab check failed,failed to validate boot image".
I tried flashing it with fastboot following this tutorial http://forum.xda-developers.com/showthread.php?p=52772182#post52772182
To know the android version i typed this command {mfastboot getvar ro.build.version.full} for which i got this {Blur_Version.23.201.3.condor_retaildsds.retaildsdsall.en.03}
so i downloaded this firmware {XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml} the one which i could get.
then i ran those commands,heres the screenshot of those commands and the errors i got:
https://postimg.org/image/gmtygv2ab/
https://postimg.org/image/bpwtxvlvx/
the only thing i havent treid is unlocking the bootloader and then flashing it.Should i try that?
This problem has occured once in the past but then i took the phone to motorola service center and they fixed it.I dont want to waste any more money on his phone.
khiladi_786 said:
My wifi kinda stopped working,so i restarted the phone. When the phone restarted it got stuck on bootloader and i cant move past it. I tried normal powerup,recovery all of which led to bootloader menu again and again with the same error "hab check failed,failed to validate boot image".
I tried flashing it with fastboot following this tutorial http://forum.xda-developers.com/showthread.php?p=52772182#post52772182
To know the android version i typed this command {mfastboot getvar ro.build.version.full} for which i got this {Blur_Version.23.201.3.condor_retaildsds.retaildsdsall.en.03}
so i downloaded this firmware {XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml} the one which i could get.
then i ran those commands,heres the screenshot of those commands and the errors i got:
https://postimg.org/image/gmtygv2ab/
https://postimg.org/image/bpwtxvlvx/
the only thing i havent treid is unlocking the bootloader and then flashing it.Should i try that?
This problem has occured once in the past but then i took the phone to motorola service center and they fixed it.I dont want to waste any more money on his phone.
Click to expand...
Click to collapse
Since no one has replied yet, I unlocked my bootloader and then tried flashing the phone.
Every command got executed except this one "mfastboot flash partition gpt.bin".Please help me i m begging. I m so close to fixing my phone.
khiladi_786 said:
Since no one has replied yet, I unlocked my bootloader and then tried flashing the phone.
Every command got executed except this one "mfastboot flash partition gpt.bin".Please help me i m begging. I m so close to fixing my phone.
Click to expand...
Click to collapse
Don't run the commands manually, use the .Bat file.
Might work
Hello,
This morning my Moto G8 Power spontaneously started booting into Fastboot Mode, with out any user input. So, as precaution i decided to wipe the userdata & cache, just incase there was a fault with the phone, so i could send it back if need be.
Since the whole issue with Fastboot, it's been refusing to boot into phone itself. Just on a loop. So , i've looked for the correct firmware, but i have had no luck so far. I keep gettting the same error "Preflash Validation Failed" which to my understanding is the phone being unable to accept the firmware as the firmware is lower, & so match that of the actual firmware on the phone.
I havn't wiped any of the actual partitions, only the userdata for obvious reasons, so im not as to why it's failing to boot. I don't have a nandroid backup either.
. Any help with solving this issue would be greatly appreciated.
Kind Regards
gliitch
gliitch said:
Hello,
This morning my Moto G8 Power spontaneously started booting into Fastboot Mode, with out any user input. So, as precaution i decided to wipe the userdata & cache, just incase there was a fault with the phone, so i could send it back if need be.
Since the whole issue with Fastboot, it's been refusing to boot into phone itself. Just on a loop. So , i've looked for the correct firmware, but i have had no luck so far. I keep gettting the same error "Preflash Validation Failed" which to my understanding is the phone being unable to accept the firmware as the firmware is lower, & so match that of the actual firmware on the phone.
I havn't wiped any of the actual partitions, only the userdata for obvious reasons, so im not as to why it's failing to boot. I don't have a nandroid backup either.
. Any help with solving this issue would be greatly appreciated.
Kind Regards
gliitch
Click to expand...
Click to collapse
What does getvar all say
Code:
fastboot getvar all
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Sent from my Moto E (4) using Tapatalk
I ended up sending the phone back in the end, as the power buttons & volume buttons would only respond very infrequently. So i don't think reflashing the Moto G Power would of ended up doing anything. It's a shame. as it's an awesome phone. waiting on a replacement.
Thanks for the help and the link to the firmware. I'll be sure to make a Nandroid backup this time, or at least try to .
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
https://forum.xda-developers.com/t/trouble-rooting-umx-u683cl.4518007
Yes, that's my original post from back in November. That post is no longer my problem, though I will set your response there aside for when I hopefully get the phone to do anything besides fastboot.
it's clearly same topic, you must not open new thread. add your second post to previous one so mods can delete this thread.
It's clearly not. It's the same phone, but a different problem. The old post was seeking help with rooting it (and got no action, you may note), this one is about getting it out of fastboot mode so I can reset the damn thing and try again.
you bricked that device as a result of trouble with rooting. all info belongs to the previous thread, so others can read the history that caused this situation. I am not arguing any further here. answer in other thread and close this one.
somnomania said:
I've been getting help on this over at Hovatek, but it's extremely slow going; I first posted there on December 11 and it's still not resolved. This phone is a former Lifeline phone, and I've been trying to get it rooted so that I can use the Tello SIM I obtained. The problem the phone was having is that it refused to do any updates, so Tello's troubleshooting as to why it wasn't detecting the SIM was completely halted.
I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
Click to expand...
Click to collapse
Here is the full firmware for the U683CL. Be sure to wipe the userdata and cache because I dumped the firmware from the same phone from a guy for $5 and it still has the guy's data and it contains pretty weird things...
BE SURE TO USE EDL CLIENT!
EDL CLIENT IS ONLY SUPPORTED ON LINUX SO MAKE A VIRTUAL MACHINE!
EDL CLIENT DOES NOT REQUIRE ANY RAWPROGRAM0.XML OR PATCH0.XML FILE!!
Link (I will make sure this link is never taken down and if it is, I'm reuploading the link no matter what): https://www.mediafire.com/file/js8ynkg8uum9ql0/u683cl_february_patch.zip/file