Database Develop

[Help} Phone won't boot past "Warning Bootloader Unlocked" after restart

I'm having the same issue as in this thread: http://forum.xda-developers.com/showthread.php?t=2417726
But there was no resolution that the OP posted.
I was running the 9/13/13 PacMan rom when I tried to restart because the phone was running slow. When the phone booted back up, it was stuck at the unlocked bootloader message.I could get into CWM, I tried to reflash the rom, and wipe everything but nothing worked. I also tried flashing all 3 of the stock firmwares (found here: sbf.droid-developers.org/dinara/list.php) in RSDLite, but they all fail. I was trying to follow the instructions in post #6 of the other thread, but they weren't making sense to me..... what can I try. Currently I'm just sitting here at the fast boot screen.
Thanks

skatingrocker17 said:
I'm having the same issue as in this thread: http://forum.xda-developers.com/showthread.php?t=2417726
But there was no resolution that the OP posted.
I was running the 9/13/13 PacMan rom when I tried to restart because the phone was running slow. When the phone booted back up, it was stuck at the unlocked bootloader message.I could get into CWM, I tried to reflash the rom, and wipe everything but nothing worked. I also tried flashing all 3 of the stock firmwares (found here: sbf.droid-developers.org/dinara/list.php) in RSDLite, but they all fail. I was trying to follow the instructions in post #6 of the other thread, but they weren't making sense to me..... what can I try. Currently I'm just sitting here at the fast boot screen.
Thanks
Click to expand...
Click to collapse
When you use RSD, why does it fail? If it fails because it can't find the device, go into your device manager(assuming you have windows) and there is going to be a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I believe it says Full Android Emulator) right click that one and install the driver by choosing one and use the Motorola ADB driver. Replug the device then try again.
Now, if you are using RSD and the device is showing, is it failing due to the XML files being wrong? Remember you have to delete the GetVar max download size lines, there is two of them, as described here http://forum.xda-developers.com/showthread.php?t=2231249&highlight=rsd

When trying to flash: 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml
RSD Lite is giving the error: "Failed flashing process. Unknown fastboot command. (getvar)"
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml
Error: "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL."
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
"Failed flashing process. Unknown fastboot command. (getvar)"
In Device Manager it says ADB Interface -> Mot Single ADB Interface.
I have use ADB commands with this computer to the ATRIX HD before so it should work.
In fast boot, I've noticed it says
"Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
UPDATE:
I have removed the "<step operation="getvar" var="max-download-size" />" lines from the .XMF files now I get the "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL." on all the files.

Make sure the files are put on desktop and not a folder and try again going to stock
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium

SVLAN said:
Make sure the files are put on desktop and not a folder and try again going to stock
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Click to expand...
Click to collapse
That didn't seem to help. Before I just had them on the root of the D drive but I am getting the same errors from the desktop. Not sure if it matters, but I'm running RSD Lite 6.1.5.
Update: Tried 6.1.4... no luck.

Maybe running the rsdlite as admin?
Open a new Fastboot without usb connection to PC then connect and open rsdlite again and try. I had this problem before and playing with it i manage to flash stock. I forgot how exactly I did though. Just keep trying. I know one of my issues was to put the att stock rom on desktop
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium

SVLAN said:
Maybe running the rsdlite as admin?
Open a new Fastboot without usb connection to PC then connect and open rsdlite again and try. I had this problem before and playing with it i manage to flash stock. I forgot how exactly I did though. Just keep trying. I know one of my issues was to put the att stock rom on desktop
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Click to expand...
Click to collapse
Just tried that, I am now using a real Motorola USB cable too.
If I remove the "<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="900113B868E61E8FC4E59F72C0B67193" />" line from all the files, I get an error that says "Failed flashing process. 1/22 flash sbl1 "sbl1.mbn" -> USB error occurred while reading/writing." Otherwise, I get the error "Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing."
I'm not sure what I'm doing wrong here. This isn't my first Motorola phone, I've used RSD Lite before in the past as well as ODIN for Samsung phones and have never had any issues so difficult to solve. I'm not even sure what file I should be flashing. I came from the latest 4.1.1 then flashed 4.3 PacMan rom.

I tried another computer and getting the same errors in RSD Lite. In Myth Tools, it says it's flashing the firmware for about 15 minutes but when it reboots, it seems to just go right back into fastboot.
I tried to manually push something using fastboot and this is what I get:
D:\Parker\Desktop\Myth Tools - AHD>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (99 KB)...
OKAY [ 0.022s]
writing 'sbl1'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.283s
D:\Parker\Desktop\Myth Tools - AHD>
Click to expand...
Click to collapse
Is it failing BECAUSE the battery is low? It doesn't seem to be charging.
I bought the Motorola Factory Adapter from Team Black Hat. I saw on write-up on droid life on how to create one but I really don't have the time to do it.

Buying the adapter solved the problem.

Were you able to flash other ROMs successfully & stably after that? I've been in the same boat & can't get past a reboot after flashing a custom ROM.

bsmitty said:
Were you able to flash other ROMs successfully & stably after that? I've been in the same boat & can't get past a reboot after flashing a custom ROM.
Click to expand...
Click to collapse
Yes I was. I installed a different ROM but... I woke up after leaving it on the charger all night a few days ago and the phone was off. Getting the unlocked bootloader message again... the only way to get around it seems to be reflashing. It's really annoying.

skatingrocker17 said:
Yes I was. I installed a different ROM but... I woke up after leaving it on the charger all night a few days ago and the phone was off. Getting the unlocked bootloader message again... the only way to get around it seems to be reflashing. It's really annoying.
Click to expand...
Click to collapse
What was your previous stock fastboot used and what rom are you trying to flash? I ask this because our development is based off of 4.1.2 RAZR HD stock and I've noticed 4.1.1 only flashers here sometimes have issues. Since the unlock, my stock changed to 4.1.2 Mex Retail (manually flashed everything via fastboot) and I've only been stuck on the bootloader screen once (had to do the sticky bit fix ).
Also, if you're an ATT user, the Mex Retail radio will give you a better signal and I can say that with 100% confidence. My Dad and I both have Atrix HD's, his runs stock 4.1.1 unrooted and mine running anything with Mex Retail radio, I've had 2 bars of service in known dead zones and my Dad had no service less than a foot away -- and that's happened in multiple dead zone/bad signal areas.

How do I go about flashing just the radio and staying on pac? @skeevydude
Sent from my PACMAN MATRIX HD MAXX

I think this method will work to flash a new radio without affecting the rom. I installed the Mexico Retail radio onto Holoblur without affecting Holoblur at all.
Assuming you have a Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file you got from the desired rom in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure the baseband is the one you wanted.

audit13 said:
I think this method will work to flash a new radio without affecting the rom. I installed the Mexico Retail radio onto Holoblur without affecting Holoblur at all.
Assuming you have a Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file you got from the desired rom in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure the baseband is the one you wanted.
Click to expand...
Click to collapse
Ya forgot one step
0) download snapdragon-fastboots.zip from Batakang and use that everywhere a fastboot command is used
/can also install it with the Android terminal emulator and a dd....
//su
///dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1

skeevydude said:
Ya forgot one step
0) download snapdragon-fastboots.zip from Batakang and use that everywhere a fastboot command is used
/can also install it with the Android terminal emulator and a dd....
//su
///dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
I just used the adb/fastboot included with Myth Tools. Not sure if those files will work for everyone though. I'm not very good at using Android terminal so I tend to stick with doing things from a Windows command prompt

audit13 said:
I just used the adb/fastboot included with Myth Tools. Not sure if those files will work for everyone though. I'm not very good at using Android terminal so I tend to stick with doing things from a Windows command prompt
Click to expand...
Click to collapse
Myth comes with the correct files. Very important to specify the correct fastboot because the stock sdk fastboot doesn't flash our images correctly and has led to a lot of confusion in the past.

skeevydude said:
Myth comes with the correct files. Very important to specify the correct fastboot because the stock sdk fastboot doesn't flash our images correctly and has led to a lot of confusion in the past.
Click to expand...
Click to collapse
Good advice for AHD owners to follow. Thanks.

skatingrocker17 said:
When trying to flash: 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml
RSD Lite is giving the error: "Failed flashing process. Unknown fastboot command. (getvar)"
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml
Error: "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL."
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
"Failed flashing process. Unknown fastboot command. (getvar)"
In Device Manager it says ADB Interface -> Mot Single ADB Interface.
I have use ADB commands with this computer to the ATRIX HD before so it should work.
In fast boot, I've noticed it says
"Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
UPDATE:
I have removed the "<step operation="getvar" var="max-download-size" />" lines from the .XMF files now I get the "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL." on all the files.
Click to expand...
Click to collapse
Old post, but still relevant issue. Hope this helps, anyone else getting these errors.
After unlocking bootloader and having flashed MX retail. When using RSDlite I had to remove the "getvar" lines. I've tried to flash back to ATT stock, but can not get past "gpt_main0.bin".
RSDlite can and will finish flash MX retail and Bell stock after editing out "getvar".

clockcycle said:
Old post, but still relevant issue. Hope this helps, anyone else getting these errors.
After unlocking bootloader and having flashed MX retail. When using RSDlite I had to remove the "getvar" lines. I've tried to flash back to ATT stock, but can not get past "gpt_main0.bin".
RSDlite can and will finish flash MX retail and Bell stock after editing out "getvar".
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me an hour ago. RSD no longer recognizes my phone in fastboot mode even though it did two weeks ago. Myth Tools however does recognize my phone, it just won't complete the whole flashing process without "intervention".
btw I am running Windows 8.1 Pro 64bit, and nothing has changed on that.
When using fastboot (mfastboot) to flash manually through the command prompt I get the same error when flashing "gpt_main0.bin" and a few others. Back to Myth Tools,, I was having problems even starting it until I just double clicked on flashing.bat or main.bat instead of running it as administrator. After all I AM the admin of my PC. Then, it worked perfect...until flashing "tz.mbn", it sent it fine, but froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I unplugged the USB while leaving the Myth Tools window open, which disconnected the phone obviously. I plugged it back in and Myth continued from where it left off, with a failure where I unplugged it obviously. It didn't actually fail though.
(Note: I did this a few weeks ago when I lost my radios and manually flashed "NON-HLOS.bin", which froze, but I followed the same procedure and it successfully flashed it)
Anyway, it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone then repeated the sequence of unplugging and replugging the USB and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Well, I had to reflash my radio again, but that was easy.
FYI: My xml file has the two "getvar" lines removes due to my earlier attempts with RSD. Any questions don't hesitate to ask.

[Q] Need help unbricking

Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature

Use an exact Moto cable. No substitutes! Check PC drivers or Moto Device Manager.
Sent from my GT-P3110 using Tapatalk

unbrick
zaros104 said:
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Click to expand...
Click to collapse
You are going to need rsd lite on your PC. The fxz files for your current build. A Motorola brand USB cord. And the latest Motorola drivers.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
http://forum.xda-developers.com/showthread.php?t=2728352
See post #7 for the fxz build you will need to use.

Did fxz work for you?

Unbricking
I ran into same problem before, with Motorola it's a pain to do anything especially charging the batteries on it once it's been brick. If you search around this forum you can find a little article about a guy tweaking his ps3 controller to charger his battery. I wouldn't recommend doing this if you don't know what you're doing. But what I did was buy this little device that charges any phone battery I'm not sure if I can link a photo but i'll try it, not i'll give a name. In order to RSD and use ab fastboot mode on the xt875 you'll need at least 70-80 percent battery life, at least that's what the guys here on the forum recommend. But I've been able to unbrick my device only 40 percent battery life. Now once that battery is charge to a reasonable charge. You'll have to download the cdma targa file for your phone. I don't think anyone matters as long as it's the exact same or newer of your phone's original firmware. Extract the targa file and then run RSD lite click the ... button to open file and locate your extracted cfc file. Now you may run into some flashing issues with failure in step 5/10 and if you don't, don't worry about it. but if you do you'll have to open up the cfc file with wordpad and remove a few lines from. here are the lines that need to be removed; <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />....there's another fail that happens but I haven't found anyone that had experience this problem. it seem like I was the only one that experience it. it has to do with something with the fail flash.bin or something I'm not sure. But I left a comment about this fix on this forum somewhere if you care to search for it. once you edit and remove those above mention lines save and run it again and it should operate flawlessly. I have also left a link down there for the edit cfc file and pictures of the device I was referring to about charging your batteries directly.
also you mention that it could be a cable thing. I read a lot of this but I've use the cable wires from my Samsung without any mishaps besides the above mention issues with 5/10 but this was a common problem that even thoses with a Motorola cable had faced. from what I know theses wires are exactly they're usb 2.0 wires and couldn't differ from each other that much. but it is probably better to use the exact cable than a non exact one. the reason it won't communicate is the battery is low as I have mention you'll have to charge this battery of yours to a decent 40 and up for it to run cause the process of re flashing can take anywhere 10-15 minutes and you don't want it to die in the middle of flashing your firmware. cause this I believe can lead to a hardbrick. the stock verification recovery will always have that return that value even from stock roms. Therefore it is recommend to use the RSD lite so you won't face that problem. I hope this helps.

Bricked
I thought my phone was history. The solution was using an actual Motorola USB cable. It made all the difference.

Maybe you installed an incorrect driver.

[Q] Can't Flash Fix Droid Razr M - Tried Everything - HELP!

I can't get my Droid Razr M off the boot screen, endless boot loop happening with the startup screen.
I downloaded the RSD Lite 5.6 (then 5.7) and tried both. Neither is recognizing my device.
I downloaded the AdbDriverInstaller.exe for Android. Did not even recognize my device - the device is plugged in, I'm looking at the AP Fastboot Flash Mode (S) on my phone. Says Device is Locked (whatever that means). Status Code: 0. Transfer Mode: USB Connected. So it recognizes that there is a USB plugged into it.
I ran ALL of these firmware versions from this website through the RSD Lite - sbf . droid - developers . org - NONE are working.
I keep getting Status: Failed Flashing Process: 1/19 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I saw some forums that said within the actual firmware XML file, to delete these lines of code, so I did (note: I tried running them before and after the file edit):
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="oem" var="fb_mode_clear" />
SOMEONE HELP!

Make sure the battery is fully charged then I will give you a link to what I use to fix this issue
Sent from my XT907 using Tapatalk

Go to Google search and search for Motorola RAZR m utility 1.20 it was created by mattlgroff
Sent from my XT907 using Tapatalk
---------- Post added at 10:39 AM ---------- Previous post was at 10:26 AM ----------
Use this http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using Tapatalk

HELP : RSD doesn't flash my Moto X

Wanting to return stock from a previous custom rom I formatted the phone via TWRP
I put the phone in fastboot mode, the connection to the PC USB, boot RSDLite and load the rom, launch the command of flash that will stop after a few seconds ... with the words FAILED FLASHING PROCESS. UNKNOW FASTBOOT COMMAND
in the box to the left, the phone is not recognized.
I tried aggionare Motorola drivers, I tried to install the new version of RSDLite 5.7, I restarted my pc, I tried anch with another pc with win xp .... nothing to do .....
in the phone there is neither the TWRP recovery nor the stock
What can I do?

panic .....
solved forgot to erase: the line <step operation = "getvar" var = "max-download-size" />
you can delete, thanks

toroloco you "is" loco as hell:laugh:
Glad you are sorted out
toroloco73 said:
panic .....
solved forgot to erase: the line <step operation = "getvar" var = "max-download-size" />
you can delete, thanks
Click to expand...
Click to collapse

Accidentally checked all wipe options...

Hello, guys.
I was installing a new rom and accidentally checked all wipe options on recovery, including system, data, and everything else.
Now my phone is only booting in "bootloader unlocked warning" screen.
I still can enter the fastboot mode, but any option i try the phone reboots into "bootloader unlocked warning" screen.
I can connect via RSDLite while in fastboot mode but no information is shown in "Device Properties".
I tried to flash the stock firmware but it fails and give me the message "version downgraded for primary_gpt".
Is there a solution for that or i just ruined my phone?
Do a technical assistance can fix this?

I figured out that the bootloader unlock was the reason of the flash fail and the reason of the error message "version downgraded for primary_gpt".
So i edited the
Code:
flashfile.xml
and removed the following lines:
Code:
<step MD5="04152bcb31ceb8e11ebb2de9ac216b0f" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="800900bc769adc8cb030e93771e6e4f4" filename="motoboot.img" operation="flash" partition="motoboot"/>
Just in case someone else is having the same issue.
Thank you.