[Q] Flashing Stock fails - Motorola Droid RAZR

Hi there! An update of CM11 failed on my xt910. The result was the laying Android an no normal Boot was available.
While downloading RSD and stockroms ( SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot and SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot from motorola ) the battery drained in the bootloop.
Finally I was able to select the fastboot option in the bootloader menu but the program printed "Battery low"
After some research I crated a factory cable.
Now the battery is ok and I was able to flash via RSD.
But in RSD I always get the error that the flash failed. (Phone returned FAIL)
I don't know what to do now. Some ideas?

Razr xt910 driver installation
Hi I am having XT910 Razr, ICS with 673.94.328.xt910.asiaretail.en.03 firmware. Now I have two problems 1) battery sucks and 2) USB drivers failed to install. So am not able to root or change the firmware. I have tried everything but failed. have downloaded the blur version of the same firmware but in the recovery mode it is showing signature verification error. Service center is also not able to help me and asking a huge money. Can some one help me on this.

Hi amit81276. You should open a new thread for your specific issue. If you give detailed error messages or behaviour I may could help.
1) battery - if the battery is too low to flash ("Battery Low" message in bootloader ap fastboot mode (access bootloader through power + vol up + vol down (to turn off and enter bootmenu))) you have to make a factory cable that allows you to connect the phone while powering it.
2) I have trouble with the drivers too. Install the Motorola Device Manager. Use C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Motorola Driver Installer.exe and bruteforce the driver to be installed. (Open the Device Manager to ensure the Mot Driver is running properly) (Sometimes I had to Clean&Install 10 times, reboot, use other USB port - very annoying)
Later I switched to another PC and there was no trouble at all.
BTT
I was able to fix the phone now. The problem was that http://sbf.droid-developers.org/ only offers 4.0.4 sbf for xt910. But I remembered that my phone was on 4.1.2 - so I was able to find the sbf on a thread here on xda ->
RAZR XT910 Firmwares SuperThread (Jelly Bean)
Remember:
Failed flashing process. 1/10 flash cdt.bin "cdt.bin_signed" -> Phone returned FAIL
Failed flashing process. flash system "system_signed" -> Phone returned FAIL
Failed flashing process. flash boot "boot" -> Phone returned FAIL
should indicate you that you are trying to flash a wrong / lower version ROM. (a downgrade won't work but in special cases)
I suggest try flashing with moto-flash! It uses fastboot which gives you real errors instead of "Phone returned FAIL". For example it returns Battery low if the battery is too low and it won't flash! Very useful to find errors! In my case the error was always 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned Fail that's not usefull at all.

Related

[Q] [HELP] failed to boot 4

was going from gingerblur 2.5 on 1.56 then sbf to 1.83 and now it just says that after flashing.
tried to sbf 1.23 and 56 and same thing
am i doing something wrong?
in the rsdlite it sees the phone but says n/a for everything
Please HELP
Updated: I tried again fresh start on different computer and it worked!
must have been error in download, unzip, or there is something conflicting on my pc
hi i have same problem , went i flash OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf ,
always after finish and rebooting then failed to boot 4 error raise,
i have use other computer to flash and the result is same failed to boot 4
i have install
- RSD Lite and 5.0
- Handset_USB_Driver_32_v4.9.0
plz can anyone help me ?
Sbf 4.1.26 or 4.1.57, then OTA to 4.1.83, root, sideload enable, flash CWM, flash GingerBlur.
bullghost said:
hi i have same problem , went i flash OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf ,
always after finish and rebooting then failed to boot 4 error raise,
i have use other computer to flash and the result is same failed to boot 4
i have install
- RSD Lite and 5.0
- Handset_USB_Driver_32_v4.9.0
plz can anyone help me ?
Click to expand...
Click to collapse
i have the same problem
aaurnab said:
i have the same problem
Click to expand...
Click to collapse
please help
CaelanT said:
Sbf 4.1.26 or 4.1.57, then OTA to 4.1.83, root, sideload enable, flash CWM, flash GingerBlur.
Click to expand...
Click to collapse
thanks bro, i thinks that's the best way to update till 4.1.83,
here a little experience i have done
first time i try flash sbf 4.1.83 failed with that error booting,
and pull battery and back again to turn off the phone, and i flash the 1.26
then success with sim card inside,
iam not happy with failing on flash 4.1.83, then i thought the 4.1.83 sbf file is corrupt then i redownload again , after finish download,
i do the second time flashing with new 4.1.83 sbf
this second time is so frustrated, couz it fail again with same error.
until i have success full recover my atrix i do over 10 time flashing
and changing between computer and my notebook
and changing from windows 7 and windows XP
flashing random sbf from 1.83 and 1.26
the lasting i lost my hope , then suddenly the flash was success, WTF ,
lasting i remember is i pull the battery and pull out the sim card , then put back the battery, and do the flash,
the last time i flash 1.26 sbf
i thing
there is something no right with driver or RSD Lite not sync or missing something
until now iam still don't know how to solve it ,
pls anyone can find out what the problem and how to solve it
After about 4-5 hours and 7-8 tries using sfb method to upgrade to 1.83, I finally have a working phone again.
As to how I got stuck on the:
boot fail 4
starting RSD
and in RSD Lite, the phone's device name showing up as "SE Flash Olympus"
I decided to do a few things.
1. Go download the newest USB drivers. the 2.00.52 is what you should be on. If you can't find them, go to Motorola website and get MotoHelper 5.0 or whatever..install and then update your drivers. Restart your pc and keep trying to update your drivers until you get to USB 2.00.52 drivers.
2. USE THE ORIGINAL DATA CABLE THAT CAME WITH THE PHONE.
3. Make sure the connections are not loose at all (could've been why mine was messing up)
4. If you already have motohelper installed...go to the 'driverinstaller.exe' change operation mode to clean and reinstall, make sure the phone is unplugged. and click on start. (note, this part will be anywhere from 2 - 5 minutes depending on speed of your computer)
5. Restart RSD Lite, make sure you're using the latest one, and 'Run as administrator'.
**Go to config>Flash/Flex options... > only "check" Restart after Flexing..**
6. Now, I learned this the hard way...and many forums have it up there... GET YOUR BATTERY TO ABOVE 80% or IT WILL FAIL. (I had to go to a friend's at midnight to charge my battery from his atrix...hahaha)
7. Now turn your phone on again and it'll go to the "failed to boot 4 starting RSD" ...
8. Next, plug it in to your USB cable and click "Show Device" and then click once under the "USB 1 line" to view the device information at the top left. (Everything should be N/A except for your bootloader and you will also read "NS Flash Olympus now, instead of the SE Flash Olympus)
9. Put that '1.83_pudding.sfb' file in the "C:\ " directory to avoid any further complications.
10. Select the "...." browse to the '1.83_pudding.sfb' file and click start. It should work.... Now if it doesn't work... try and try again...
What I did was switched back and forth from 1.23 to 1.83... when I got mine to work, the device was registering as "SE Flash Olympus".
And for the longest time under bootloader, it would register as N/A...I finally decided to switch cables and it worked... once again, make sure to follow these:
* Full battery/80% above
* Stock Atrix USB cable
* 2.00.52 USB drivers
* RSD Lite 5.3.1
EDIT: GOOD LUCK! PM me if you need more assistance as those forward to XDA app
vash8806 said:
After about 4-5 hours and 7-8 tries using sfb method to upgrade to 1.83, I finally have a working phone again.
As to how I got stuck on the:
boot fail 4
starting RSD
and in RSD Lite, the phone's device name showing up as "SE Flash Olympus"
I decided to do a few things.
1. Go download the newest USB drivers. the 2.00.52 is what you should be on. If you can't find them, go to Motorola website and get MotoHelper 5.0 or whatever..install and then update your drivers. Restart your pc and keep trying to update your drivers until you get to USB 2.00.52 drivers.
2. USE THE ORIGINAL DATA CABLE THAT CAME WITH THE PHONE.
3. Make sure the connections are not loose at all (could've been why mine was messing up)
4. If you already have motohelper installed...go to the 'driverinstaller.exe' change operation mode to clean and reinstall, make sure the phone is unplugged. and click on start. (note, this part will be anywhere from 2 - 5 minutes depending on speed of your computer)
5. Restart RSD Lite, make sure you're using the latest one, and 'Run as administrator'.
**Go to config>Flash/Flex options... > only "check" Restart after Flexing..**
6. Now, I learned this the hard way...and many forums have it up there... GET YOUR BATTERY TO ABOVE 80% or IT WILL FAIL. (I had to go to a friend's at midnight to charge my battery from his atrix...hahaha)
7. Now turn your phone on again and it'll go to the "failed to boot 4 starting RSD" ...
8. Next, plug it in to your USB cable and click "Show Device" and then click once under the "USB 1 line" to view the device information at the top left. (Everything should be N/A except for your bootloader and you will also read "NS Flash Olympus now, instead of the SE Flash Olympus)
9. Put that '1.83_pudding.sfb' file in the "C:\ " directory to avoid any further complications.
10. Select the "...." browse to the '1.83_pudding.sfb' file and click start. It should work.... Now if it doesn't work... try and try again...
What I did was switched back and forth from 1.23 to 1.83... when I got mine to work, the device was registering as "SE Flash Olympus".
And for the longest time under bootloader, it would register as N/A...I finally decided to switch cables and it worked... once again, make sure to follow these:
* Full battery/80% above
* Stock Atrix USB cable
* 2.00.52 USB drivers
* RSD Lite 5.3.1
EDIT: GOOD LUCK! PM me if you need more assistance as those forward to XDA app
Click to expand...
Click to collapse
People 51_OLL iron-4.5.2A-lite 5.6 rsd 49_SIGNED_STABLE45LAOLYMPGBPERAR_P011_A026_M001_HWpd_Service1FF with ... and my error:
"Failde to boot 4"
rsd starting mode
I am reading is the battery problem that has to be for 80 %+...
If I turn on the power but the volume key + I fastboot protocol enters
If it lights only the error:
"Failde to boot 4" starting mode rsd
I can do twice the iron sbf with 2.3.6 official stock continues to give me the same error.
Lei may be because the battery is not 100% so fails.
How do I charge if the wall charger no load and light me alone with the legend:
"Failde to boot 4" rsd starting mode.
It can be for this, because this is not a 100% Bateias??
Another query may be that by command fastboot mode can be fixed??

[Q] Razr gsm bricked ics ap fastboot dont work

Hi,
I was on last gsmleak ICS :
- Blur_Version.651.167.26.XT910.Retail.en.EU_2
Battery draining too fast so i reboot in recovery and wipe to factory (bad idea) --> phone never boot anymore
Now i can just access to apfastboot and recovery
But i when i try to connect my phone to pc in AP FASTBOOT nothing can be detected on pc so RSD can't work and fla**** with adb same "no device found" ... (i tried another pc same pb, install again drivers no change)
I tried to put the phone on BP SBF FLASH my pc detect and install drivers but rsd can back to APFAST and flash xml
I tried to flash in recovery again the Blur_Version.651.167.26.XT910.Retail.en.EU_2 but there is error when it verify
assert failed ... kindle.apk (freezed with titanium)
ap fast boot info : 0A.74 device is locked Status Code : 0
Battery Ok Ok to program Connect USB Data Cable
So now i have no solution if anyone can help ... maybe another way to flash something or a file to use with recovery ?
t.y
No help
i tried to flash again the last ota, but there is error because i disabled some apps with titanium like kindle.apk
is there a way to flash this ota wo verify check ???
http://forum.xda-developers.com/showthread.php?p=26915046
Follow Post Nr. 6 (T-Mo to Retail)
Sent from my XT910 using Tapatalk 2
I can t my ap fast boot mod seem to be unavailable, pc don t detect the phone when it s connect
So i cant use rds and adb cmd :/
tel is not detect on pc (i tried different pc cable and drivers without success)
So no idea?
gonna send it to sav but i have got doubts :/
same problem here.. no solution still.
No solution i confirm, i send it to an official moto repair but when i read their check i refused to pay for it :
- motherboard replacement
- speaker and screen have to be change
- and flash
= +140€
and i have to pay +27€ to get back my phone
i m gonna send it to another repair we ll see
http://www.youtube.com/watch?v=WBySMO8n1r4
have u tired ths link??

AP Fastboot Failure OA.74

Hi,
I get the below message whenever I reboot. It started when I tried to flash an ICS update from GB.
I have treied the solutions mentioned in the other threads on XDA but whenever I reboot I just get the error below. I cannot go into AP Fastboot message as when I select it from the menu I once again get the message below.
I dowloaded the ICS update from the Settings About Phone Update menu and it starts to install then tries to reboot to complete the installation but of course gets stuck at the first step with the below message.
I tried downloading the radio empty_radio.img file from this solution thread http://forum.xda-developers.com/showthread.php?t=1634223 and flash it using RSD lite 5.7 but when I try to select the file it is not listed as a suitable file type.
I seem to have run out of options. Please will somebody help. I am ready to punch the wall!
Thanks
Fergy
Here's the message (I have googled solutions for this but found none that mention the QA.6C but not the QA.74 as below):
The Device Error LOCKED. Status Code: 0 "
"Fastoboot AP mode (S) (Flash Failure)
QA.74
To return to normal mode - first press power key to power down
Device to LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable "
You haven't specified which carrier you are using. Try going to sbf.droid-developers.com and locating the ICS build version for your carrier. Download it, then extract the dukes, and point rsdlite to the xml file.
Make sure your battery doesn't go under 50% since you can't fastboot if that's the case.
Good luck
Sent from my XT894 running ICS
I am with Telstra in Australia. I bought the phone in HK.
I cannot seem to flash anything. Flash always fails.
What are dukes? I don't really understand your instructions as I am old
Thanks for answering. I really need to fix this.

Invalid flash mode (s) (boot failure) + bootloop

Hi all, I'm new in this forum but i read a lot of your thread in order to learn about android phone.
First of all, sorry for my bad english.
I have a problem with my razr maxx. I bought it on ebay (a used one). I use Razr/Maxx XT912 (Matt Droid Razr Utility) and now the phone is in bootloop.
This is the error message:
invalid flash mode (s) (boot failure)
0A.77
emmc info: seize 16gb
Device is LOCKED. STATUS CODE 0
battery ok.
ok to program
transfer mode:
usb connected
AND
Invalid cg otv (CG:system): invalid sp data
invalid cg version (cg:system)
invalid cg otv (cg:system)
I'm trying to resolve with this old thread http://forum.xda-developers.com/showthread.php?t=1524011
My phone model is xt910 type name m0c2e fcc id : ihdp56me2 ic id 109o-p56me2 and it has verizon apps. (i red the it on the back of the phone) BUT I also use the imei in the motorola's support to find out the model of the phone, and this is the answer: XT912 (Spyder LTE) (i also find a screen of the phone with some info -> see the attachments ). [the phone is only with motorola brand].So which is the right model? I also have (or better had) supersu already on it. I use it with a sim card (i use it with in gsm mode but it has also cdma mode. The languages are only spanish and english )
I arrive at this point ( from this "guide" http://forum.xda-developers.com/showthread.php?t=1524011) http://forum.xda-developers.com/showthread.php?t=1362956 but i don't know which one i must download.
ps.
i also tried:
1-download cdt.bin ( http://www.mediafire.com/?ua1nj6ds6r0vtue )
2-download fastboot files ( http://dfiles.eu/files/bih3tmg7b )
3-restart your phone in to bootloader ( fastboot ) mode
4-connect your phone via usb cable
5-open cmd.exe in your pc an go to fastboot files
6-flash cdt.bin via this command -------------------------------------- fastboot flash cdt.bin cdt.bin
7-restart your phone in to stock recovery
8-do triple wipe and restart your phone
and you can see the result in the attachments..
What can i do in order to resolve the bootloop? I'm desperate
Thank you
Hi!
Flash this rom with RSD Litehttp://sbf.droid-developers.org/download.php?device=9&file=788
Let me know if worked. You battery may be drained by this time, if so, you'll need to use a factory cable.
But, let me know if you could flash with RSD Lite first.
Cheers
i'm trying but it failed. (usb error at status 22/24 and 18/24). Now i repeat the action. I have the original cable and the phone is in fastboot flash mode
It's working ! THANK YOU!!!
In order to avoid the same problems, How can i change rom? (which one can i use ?) Which programs and apps do i need to use? Where i can find a guide? Which is the best way in order to improve the gsm signal?
Thank you,
Roncallica
An other idiot question. Now it is without supersu and it is locked. What can i do?
roncallica said:
An other idiot question. Now it is without supersu and it is locked. What can i do?
Click to expand...
Click to collapse
Hi!
Glad it's working first place. You'll find all you need just navigating throught the Development section. You have a root method easy to use to your phone, a safe to use recovery and a lot of kernells and roms to pick up onde of your choice.
Before doing anything like flashing roms or installing things be sure you've charged you phone, always. Remember Razr battery are not removable, so, if you brake it while doing some stuff you need no return to your previous rom and start all over again.
First step now? Root this thing!
Cheers
Do i have to use this guide? I mean in order to root xt912 http://forum.xda-developers.com/showthread.php?t=2230140 or can i use this one? (http://www.youtube.com/watch?v=YIEO0pedtzE). Can i modify kernells and radio in order to obtain more gsm signal? i don't find a safe recovery for xt912 spider, what can i do? I have some problems with internet and it's a bit slow
thank you!
Having a simillar problem with my XT910, when I power it on it doesn't boot but goes straight to the error message saying
AP Fastboot Flash Mode (S) (Recipe Failure)
0A.77
eMMC Info: Size 16G
To returno to normal mode - first press power key to power down
Device is LOCKED. Status code: 0
Battery OK
OK to Program
Connect USB
Data Cable
If I try to flash ROM via RSDLite, it recognizes the phone but I got flashing error on the first step. If I press power to shut it down, then VOL+/- with Power key, and select Normal Powerup, in more than 90% phone goes to a bootloop, sometimes it boots normaly and then everything works. If I select BP HW Diag & Boot AP, it boots every time but when I try to connect it my PC asks for some drivers for Diag and so which are not installed on PC and the phone won't charge a battery when connected to a charger - everything else is working.
Phew, that was a long post! :laugh: Any idea what might be a problem?
I forgot to mention that I bought the phone in this condition so I don't have a clue what a previous owner flashed (or tried to flash). Android version is official 4.1.2, system version 982.124.14.XT910.Retail.en.EU, build number 9.8.20-124_SPUEM-14.

Pls HELP: Moto E2 stuck at Bootloader

Hi there,
My moto e 2nd gen got stuck in bootloader and won't boot.
The monitor displays as below:
**********************************************
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
EROOR: Failed to pass validation, backup fastboot
Fastboot Reason: Fall-through from normal boot mode
BL:
Baseband: M8916_2020629.41.03.21.51R SURNIA_RECTA_CUS
Product/Variant: surnia XT1527 8GB P3
Serial Number:
CPU:
eMMC:
DRAM
Console [NULL]: null
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Connect USB Data cable
**************************************************
In the Recovery Mode display, I see "qe 0/0" which I learned from the other thread that it means the device has never been rooted.
Below is how this happened;
I used the app called KingRoot.
But the app says failed to root the device.
My phone acted weird so I uninstalled KingRoot.
Then I tried to remove the .exe file of KingRoot but failed somehow.
Right after I just turned on some secure feature (which warns the user that the app may be harmful?) of the device, the device went black and displayed the bootloader screen.
Below is what I have done so far:
Wipe cache partition (successful), then Reboot the system (Failed)
Wipe data/factory reset (successful), then Reboot the system(Failed)
Apply update from ADB with the stock Rom I found in the [http://firmware.center/firmware/Moto...Stock/XT1527/] but received error as below,
***********************************************
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong.
E:signature verification failed.
Installation failed.
************************************************
Then, I flashed three image files (recovery, boot, bootloader) using fastboot command (without unlocking bootloader).
I did not use the bootloader unlocking command.
So I thought the flashing would failed but somehow succeeded only with recovery.imag.
I believe my device has never been rooted and the bootloader has never been unlocked.
Is it possible that KingRoot has modified some system files even when the device has never been rooted and the bootloader has never been unlocked?
And how can I fix my bricked moto e?
Could someone help me out on this please? :crying:
quicksand99999 said:
:
Click to expand...
Click to collapse
Are you following the steps as mentioned in this thread ?
Also you are getting signature failed error. In such cases, download the firmware again and check
Hi there,
Thank you for the reply. Sorry that it took so long to reply back.
I did what the above mentioned guideline tells for the first time.
And after I tried second time, finally my phone started working again!!
The first time with an older version stock firms, some file failed to be flashed.
So I used seemingly-newer-version-than-my-original-firmware the second time.
Even though "mfastboot flash system system.img_sparsechunk.5" was missing from the stock firmware, my phone was able to recover to the normal state.
THANK YOU SO MUCH!!!
I went to some shops that claim they can fix bricked phones but all of them said that motorola phones are difficult to fix. But I could fix it after second trial.
Developer Forum >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Shops
moto e xt1521 bootloader unlock?
**********************************************
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
EROOR: Failed to pass validation, backup fastboot
Fastboot Reason: Fall-through from normal boot mode
its displays when i flash
how to fix it?
Read drs22's post above ! He's mentioned the link you can follow to fix this, follow the steps to the 'T' and ensure you download a more recent version of the ROM.

Categories

Resources