Database Develop

[Q] Milestone bricked? (boot loops, bootloader error)

Hello guys,
I hope you get not bored by these every day "I bricked my milestone" threads, but I do really need and would appreciate your help. So here is what's going on:
After Motorola delays the official 2.2 ROM again I decides to try CM6. I asked a friend, who has flashed his Milestone before, for an instruction and he gave me one.
I had an Milestone from O2 Germany with latest 2.36 update. First I made the recovery vulnerable. I downgraded to 2.34 and flashed the vulnerable-recovery only (of course the one for my 90.78 bootloader). I checked if the system was working right after every flash via RSD, and the phone bootet properly anytime. I applied the Androidiani update.zip and entered the OR. I wiped and applied the CM update via OR.
After I applied the CM update, the OR told me to reboot and so I did. I saw the Motorola logo and then the bootloader came up with an error message (Err:A5,70,39,00,27). I wanted to restore via Nandroid, but I no longer could enter the recovery (not to mention the OR). So I asked my friend again what to do and he told me to flash vulnerable recovery again via RSD (yes, I could enter bootloader mode) to be able to enter recovery again. After I flashed I could enter the recovery, but some new mad behavior appeared. The bootloader error disappeared, but every time I tried to boot, the phone ended up in boot loops (Motorola logo --> reboot --> Motorola logo --> reboot -->...).
Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again.
To conclude:
flashing via RSD --> boot loops (recovery and bootloader work)
flashing via OR --> bootloader error (only bootloader works)
Some guy from android-hilfe.de told me to flash the bootloader, but I know this is very dangerous. So I went to the #milestone-modding irc-channel and asked for help. They gave me the advice to try to flash other sbf's, maybe an old 2.0. As I tried this today I got a new problem: the sbf file won't work. When I press 'start' in RSD everything starts as usual. But when the phone should show the message "sw update in progress" nothing happens and RSD get stuck on 0%. At the and I get the following message:
'ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE003003F Command: ERASE (Error Code: e003003f)'
So I did not proceed. Anybody a suggestion what to do? I'm really helpless.
Greetings Luke
PS: the forum search lead me to this thread. The problem sounds pretty similar.

Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher

vladstercr said:
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
Click to expand...
Click to collapse
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk

Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.

LukeTS said:
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
Click to expand...
Click to collapse
Try a different version of RSDlite on a different machine or operating system.

Caz666 said:
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!

LukeTS said:
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
Click to expand...
Click to collapse
There is no GOT 2.1
GOT is only 2.2. You can try GOT 2.2 sbf and RSD v4.6

Oh, okay =)
I thought there is a version by them.
Gonna try your advices and post the results.
Thank you so far

Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot

killed said:
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Click to expand...
Click to collapse
Did that before and tried it now. Didn't work for me. But thanks for your advice
I also flashed 2.2 from GOT. I was able to flash with RSD and it did not fail. But there is still the boot loop. So nothing changed.
This time I did it with my Atom-netbook and used RSD 4.6.

Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?

LukeTS said:
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
Click to expand...
Click to collapse
You tried GOT 2.2.1 sbf and it didn't work? Can you access recovery? There was a suggestion of fast boot, but I don't know what that is (just in case you wanted to google it or something, not sure). Do you have the drivers installed for your computer?
You could try this:
milestonefail said:
for some people RSDLite doesnt work properly. One way to fix that is put the SDL.bat file (attatched as .txt, change to .bat before using) in the RSDLite installation folder, move the .sbf file you are using to the same folder, and drag that .sbf to SDL.bat.
)
Click to expand...
Click to collapse
Read the end of this post: http://forum.xda-developers.com/showpost.php?p=11372663&postcount=51 Read the end
Also look here for the link for the drivers: http://forum.xda-developers.com/showpost.php?p=11163403&postcount=27
Good luck! I am not responsible if anything happens to your device.

Yep, it didn't work. RSD said the flash passed, but I always get boot loops. I can access th recovery, but even nandroid in OR doesn't work (I get back to that bootloader error I described in my first post).
I also don't know what fastboot is, but just using google won't help me, because I don't know, what I meant to do with fastboot.
The drivers are installed. Without them I guess RSD wouldn't even recognize my phone.
I also tried the batch file you posted, but it didn't work. I wasn't able to start the flashing process. I guess, the only thing the batch file does is to start RSD with admin rights.
These are all methods I tried and they just don't work. I need something different to this usual helpful stuff. That's why I posted in this forum, because I tried everything and I'm helpless at the moment.
Thanks for your advice anyway. I hope someone has a solution soon.

fastboot most likely will do nothing for you if a nandroid backup fails. Fastboot is a way to flash individiual partitions in case your recovery or nandroid does not work.
It works like adb (command line from a conected computer) and requires nothing on the phone. But if nandroid works...it will not do anything different.
Basically, a nandroid is a collection of .img files (one per partition) that a script flashes in sequence. With fastboot, you could flash all of the .img files from computer command prompt.
I would:
1) try a different nandroid...download the latest leak (01/25 from the dev forum). It is in nandroid format. I would factory reset the phone first.
2) if this does not work, i would fastboot erase and the fastboot flash (look up the syntax) every .img in the nandroid backup. This is just in case you OR is corrupted in some way...not likely, but i am out ideas.
Sent from my Milestone using Tapatalk

Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!

LukeTS said:
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
Click to expand...
Click to collapse
Why give up without trying? I believe you should flash it to see if it changes anything...How worse than this can it get?
Please...do not take my words for granted...Inform yourself from other sources before you try this...and if you do let us know if you successfully managed to get your phone back!

You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?

LukeTS said:
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
Click to expand...
Click to collapse
I dont think that is possible. I've read here on the forum somewhere that downgrading the bootloader is not possible...but you should search, maybe you find that it's possible.
Anyhows, I dont think your phone is lost, I just think we're missing something!

I also think it's not possible. I've read this in some forums, too.
It seems that it isn't lost. I was happy, as I found out, that I can enter recovery and bootloader. I thought it could easily be restored. But then nothing worked for me. So we must miss something, but I have no clue what.

What do you mean by:
"Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again."
Are you sure you have enough battery?
You could try restoring a nandroid from other recovery. Replace the recovery from your sd-card. If you use Androidiani 3.3 try an older version of it or another OpenRecovery.

New update bricked my phone

I was hoping I could get some help with this, I don't have an unlocked bootloader and everything is unfortunately stock, so here's hoping.
I was upgrading with verizon's upgrade tool while plugged into my computer and it got about halfway through updating before just stopping. Now the phone just automatically boots into fastboot flash mode. When I try to select any option aside from power off, restart bootloader, or barcodes it just flashes the motorola logo and goes back to the menu and the log says it failed to validate the system image. I looked at the unbrick thread and got nowhere and when I try to use the fastboot upgrade option with what I believe is the right image it gives me an not found error.
Is there anything I can do or is this just a paperweight now?

EnormousAxe said:
I was hoping I could get some help with this, I don't have an unlocked bootloader and everything is unfortunately stock, so here's hoping.
I was upgrading with verizon's upgrade tool while plugged into my computer and it got about halfway through updating before just stopping. Now the phone just automatically boots into fastboot flash mode. When I try to select any option aside from power off, restart bootloader, or barcodes it just flashes the motorola logo and goes back to the menu and the log says it failed to validate the system image. I looked at the unbrick thread and got nowhere and when I try to use the fastboot upgrade option with what I believe is the right image it gives me an not found error.
Is there anything I can do or is this just a paperweight now?
Click to expand...
Click to collapse
Was anything non-stock on your phone when you tried the update?

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?

At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.

PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.

I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!

ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk

Moto e5 play issue.

Hello everybody! I need help with my Moto e5 play XT1921-3 the problem that I have been facing is that the phone won't turn on like it used to. It still, charges, but I can only get it into ap fastboot mode and it does not let me access any of the features like recovery mode, because when I select it, it just turns the phone off and flashes a charging logo over and over again. I have never rooted my phone or have done anything riskful with it. It is very difficult to get it into ap fastboot with the battery inserted in the phone, but it is possible. This problem happened out of nowhere. All I did was take out the battery of my phone, after Shutting it off all the way. Then when I put the battery back in, this is when this problem started happening. This has happened to me before and I have fixed it before, using rsd lite, but now when I try to use rsd lite, I get a failed error everytime saying "failed partion gpt.bin/32" I also tried to fix that error, but I just keep getting an error after error message, I even took it to the T-Mobile store and they told me to keep it charged overnight. This is starting to get very stressful because I need my phone. If anyone can please help me, that will be very appreciated. Thank you.

Here's some stuff that should get you going again. The 3 links I posted all contain the necessary files to flash your phone to stock. You'll need the latest firmware for your phone as well. Install the Moto drivers, adb and fastboot files, and use the xml to batch converter to convert the firmware to a Windows batch script (assuming you use Windows). All the links will have instructions on installation and usage. If you need any more help let me know. I have the same device. http://www.rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
http://rootjunkysdl.com/files/?dir=Adb Fastboot Files
http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola

Phone refuses to comunicate at bootloader

Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.

priviet.toledo said:
Hello, recently i had some issues with my phone, and i thougt. well i should do a factory reset, just in case, but when i did the reset, the phone was in the same condition as before, so my next step was to reflash the stock rom, im not in custom ones btw, and my phone is still locked, long story short, with every program comand, and even oficial software, my phone refuses conection, with android cmd tools, its always stuck forever in a line called, sendig partition (45kb) and thats all it can be there for hours, the phone is just doing nothing, also the booloader oficial cmd, cant extract the key just sit there doing nothing, however, my phone is not bricked, bootloader devices detect my phone but i cant reflash the phone, i already tried the blank flash cmd, just say waiting for device. can someone help me with this issue? im not a noob, i already save one moto x with blank flash and rooted several past generations of moto phones.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

I had a similar problem just now - could not do anything in fastboot mode, LMSA failed as well. To solve it, I switched to another PC, and stopped using USB3 to USB-C custom cable, and used the original one I got with the phone (USB-C to USB-C). So my guess is, you need to connect to the PC with the original cable, directly, or just with a better cable than the one you were trying with.

my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help

Gingerale2020 said:
my motog7 Lenovo android is stuck in bootloader mode tried to reset or restart nothing keeps jus sitting there Help
Click to expand...
Click to collapse
What does getvar all say
Code:
fastboot getvar all [/Code
[url]https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039[/url]