Hi guys after having upgraded my AT & T Motorola Atrix gingerbread to version 1.83 I get this error: failed to boot 4.
how do I reset the phone? thanks
Flas sbf. Look in development for flashing sbfs. Tons of information. Also wrong section this should be under questions and answers section.
Sent from my MB860 using Tapatalk
Flash either full 4.1.26 or 4.1.57 sbf, then update OTA to 4.1.83.
And what do you mean Gingerbread?
Unless you flashed to 2.3.4 HKTW you don't have Gingerbread.
CaelanT said:
And what do you mean Gingerbread?
Unless you flashed to 2.3.4 HKTW you don't have Gingerbread.
Click to expand...
Click to collapse
commonsense suggests that, that's what he means.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
alexrita said:
Hi guys after having upgraded my AT & T Motorola Atrix gingerbread to version 1.83 I get this error: failed to boot 4.
how do I reset the phone? thanks
Click to expand...
Click to collapse
Failed to boot 4
me too,help!!!
help!!!
help!!!
help!!!
veafin said:
Failed to boot 4
me too,help!!!
Click to expand...
Click to collapse
What did you flash, and how? Is your phone unlocked?
I suspect "Failed to boot 4" is when a filesystem is missing a signature. (And "2" is when the signed hash doesn't match the data)
If you are using RSD and a Motorola .sbf, shouldn't be a problem. Please explain in detail what you have done. If you want a quick fix, after flashing 4.1.83 SBF, if you still have this problem, go back and flash The2d's PUDDING (unlocked BL.)
(This fix will only work if you have unlocked your phone.. but the only way you could get this error is if you are trying to use fastboot without first unlocking your phone, or you are manually editing boot/recovery, or making .sbf files yourself...)
Please provide clear, concise details of what you've done.
eval is right, I got both failed to boot 4 and 2 in the past
if you have an att atrix you just need to flash 1.2.6 sbf then the 1.8.3 over it, unclok your bootloader then flashboot will go.
My cell phone is Hong Kong release, flashed Chinese simplified ROM,"掘墓者ME860国行官方ROM_OLYGC_U4_1.21.0.DearTanker"
when the tip is：
SVF:105:1:2
Failed to boot 0x1000
can't get the "RSD" and "fast boot"mode.
What can I do?
Same here...got "Failed to boot 4" error...
I had leaked 2.3.4 HKTW installed
I was trying to move back to 2.2...Keep getting errors when flashing to 1.2.6 as well...failing at the step where it says "Switching the device to BP mode"....Please help....
Hi,
I got that error when I had an sbf flashed and then I flashed a system.img from another firmware. Such a mismatch would also occur if an sbf was interrupted.
Cheers!
veafin said:
My cell phone is Hong Kong release, flashed Chinese simplified ROM,"掘墓者ME860国行官方ROM_OLYGC_U4_1.21.0.DearTanker"
when the tip is：
SVF:105:1:2
Failed to boot 0x1000
can't get the "RSD" and "fast boot"mode.
What can I do?
Click to expand...
Click to collapse
You cannot boot into RSD by holding volume-up on start?
We are lucky, when our phones fail signature/hash check, we are dropped directly into RSD mode. This seems not to be the case for you. Also, this message "Failed to boot 0x1000" is new to me, and so far seems only to have happened to ME860 users. I suspect fastboot gets the kernel (or something else?) loaded into memory at 0x1000, see:
Code:
000D173C .Unrecoverable bootloader error (
000D1760 [Fastboot]: Fastboot Entry
000D1784 Point ..Failed to boot 0x1000..LOG.
in bootloader CG from an extracted SBF. But... fails to boot kernel/microBoot? Hard to understand how a signed CG, which passed the check for your Boot ROM (same encryption keys) can have a kernel/? that does not boot on your hardware. Unless Moto has used similar keys with some hardware changes that means that .sbfs from international ROMs are not purely interchangeable? =(
And this is strange, since fastboot gives this error, so it is alive and in memory, should take some input: hopefully booting power-on + volume-down would be enough to get the menu of options, which includes RSD, same for booting power-on+volume-up key ? The inability to get into any fastboot / RSD menu looks like it could be a serious Moto bug... I hope whoever posted that SBF puts a huge WARNING for users of your model of phone...
I forgot to ask the 0x1000 people...
During any point during boot, does the device show up in usb? Command "watch -n .2 lsusb" in linux would do..
Thank bro…. I’ve try this way “As the devices is booting hold the volume up button”
But it is no use … the device is continue booting … again and again…
If it is work … at the top of the screen will show “strating RSD protocol ….”
But now my atrix didn’t show anything ..
And the screen won’t show any MOTO’s logo….
Does anyone can help me to save my atrix ?? > <
Please …
Look here,Please:http://forum.xda-developers.com/showthread.php?p=14673911
Again, do you ever see it appear on usb? In linux
# watch -n .1 lsusb
and keep your eyes open for Motorola PCS
That is your only hope... if we cannot even communicate with the phone via usb, well, it is pretty much a hard-brick.
Who made this [email protected]! Others are OK with it??
veafin said:
Thank bro…. I’ve try this way “As the devices is booting hold the volume up button”
But it is no use … the device is continue booting … again and again…
If it is work … at the top of the screen will show “strating RSD protocol ….”
But now my atrix didn’t show anything ..
And the screen won’t show any MOTO’s logo….
Does anyone can help me to save my atrix ?? > <
Please …
Look here,Please:http://forum.xda-developers.com/showthread.php?p=14673911
Click to expand...
Click to collapse
Related
I was messing with the phone trying to do stuff and long story short I cannot boot up for nothing! Here's what I get:
- I turn it on, and all it says is:
FAILED TO BOOT 1
STARTING RSD MODE
Everything else is BLACK SCREEN
What I have tried so far.
Used rsd lite 4.9 and installed the SBF FILE:
OLYFR_U4_1.2.6_SIGNED_OLPSATTSPE_P012_HWolympus_1g_1FF.sbf
It reads and tries to flash but the atrix reboots on the SAME screen mentioned above. And the RSD on my PC says FAILED FLASHING PROCESS!
What more can I do guys/girls?
Is it bricked? Whoever shows me how to get it running I will gladly paypal you some money for your time. Thanks!
JasjarMan said:
I was messing with the phone trying to do stuff and long story short I cannot boot up for nothing! Here's what I get:
- I turn it on, and all it says is:
FAILED TO BOOT 1
STARTING RSD MODE
Everything else is BLACK SCREEN
What I have tried so far.
Used rsd lite 4.9 and installed the SBF FILE:
OLYFR_U4_1.2.6_SIGNED_OLPSATTSPE_P012_HWolympus_1g_1FF.sbf
It reads and tries to flash but the atrix reboots on the SAME screen mentioned above. And the RSD on my PC says FAILED FLASHING PROCESS!
What more can I do guys/girls?
Click to expand...
Click to collapse
You could start by removing external sdcard if you have one in there then try RSD flash back to 1.2.6.
CyberPunk7t9 said:
You could start by removing external sdcard if you have one in there then try RSD flash back to 1.2.6.
Click to expand...
Click to collapse
Removed it and the sim card.
Just downloaded RSD LITE 5.0 and it worked.
thanks cyberpunk for responding!
Should maybe not be in the dev forums???
sigh... This is why companies are making it harder to root.
Moved to proper forum.
Tried to install several roms but every time it says it can't verify the info so I decided to do SBF.
Plugged in phone PC downloaded motoflash driver even though I have latest moto usb driver and shows up as this in RDS lite
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x00C106
DRM Version: N / A
Phone Type: Engineering (1D1D3410D773020000003C060000)
It goes through a few things and then gets to flashing but says FAILED phone is not compatible with multi-interface super-file. (0x703B)
I verified the SBF was the correct one, wasn't corrupt and was the correct md5 and tried a couple times with the same result.
What do?
I have this same issue. Can anyone tell us what that error means?
Depending on whether your sbfing froyo or gingerbread you need the most recent sbf of the two
Sent from my MB860 using XDA Premium App
Same problem.
I am having the same issue. I think I may have actually completely bricked my phone. I didn't think it was possible.
I was attempting to use ROM Manager to flash to MIUI. It then went into a boot loop. However, it does not even hit the eye. Just the 'M' screen.
When I try to boot into recovery, I get Andy with the triangle exclamation point, but the search button does not bring up recovery.
Most of the time my XP PC tells me that it does not recognize the hardware. When it does and I try SBF using RSDLite (4.8 and 4.9), I get the same as above and the log have hundreds of these entries:
[0x0000137c] E(08) [1000] CPSTSerialTIHelper:rocessPingCommand - Failed to get DIEID ACK
I have Moto Driver updater 5.2 with the latest droid drivers.
I tried using SBF_Flash for the MAC, and It gets stuck on "Waiting for phone..."
My guess is that the component that communicates from the phone is corrupted. Any thoughts or suggestions?
Thanks
First, to get into stock recovery you have to use the volume rocker once you get to andy, not the search ket (atleast seach hasn't worked for me, and you need to press both at once)
Second, you need to go into bootloader (idk if you have, but I didn't see it mentioned)
Third, make sure you have the correct SBF file (I use the triplethreat full sbf, which redoes kernel and system)
Fourth, I haven't seen a phone bricked yet, and I've been doin this for a bit of time, that was more in the early days of android.
Sent from my ApeX-ed, Overclocked, and Automated Droid 2.
I fixed my issues. It turns out that both my PC and My cables were having issues. I used a new machine with a fresh Moto cable, and was able to flash. Took 2 attempts, though.
Good luck
Great!! Glad it worked!
Sent from my ApeX-ed, Overclocked, and Automated Droid 2.
Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!
http://droid.koumakan.jp/wiki/SBF
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!
ezsbf has helped a lot of people
Sent from my MB870 using xda premium
so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas
Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2
did you try wiping cache or data?
delete this
jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up
My provider is releasing an OTA in the coming weeks. If I purchase a new phone, can I somehow download the new OTA to my new phone, and run an update from the recovery menu of the broken phone? This phone cannot be unlocked at the moment.
techjohnny said:
My provider is releasing an OTA in the coming weeks. If I purchase a new phone, can I somehow download the new OTA to my new phone, and run an update from the recovery menu of the broken phone? This phone cannot be unlocked at the moment.
Click to expand...
Click to collapse
So whay you need to buy new phone to unbrick your old phone. Tell how do you bricked your phone and what are symptoms of your bricked phone? When you coonect your phone to usb did you getting black screen and white led? Is RSD lite detecting your phone? Tell us more information and when i will try to help you. P.S. Defy is unbrickible phone - so it very hard to brick your defy...
turffe said:
So whay you need to buy new phone to unbrick your old phone. Tell how do you bricked your phone and what are symptoms of your bricked phone? When you coonect your phone to usb did you getting black screen and white led? Is RSD lite detecting your phone? Tell us more information and when i will try to help you. P.S. Defy is unbrickible phone - so it very hard to brick your defy...
Click to expand...
Click to collapse
Okay, RSDLite sees the phone, recovery is locked, and phone reboots after showing RW (Republic Wireless) logo, which is about 2-minutes after phone is powered on. I've tried adb wait-for-device, but nothing.
It's a XT557D Republic Wireless phone. It was officially released 2-months ago. No ROM available. I replaced the Phone.apk to brick the phone.
techjohnny said:
Okay, RSDLite sees the phone, recovery is locked, and phone reboots after showing RW (Republic Wireless) logo, which is about 2-minutes after phone is powered on. I've tried adb wait-for-device, but nothing.
It's a XT557D Republic Wireless phone. It was officially released 2-months ago. No ROM available. I replaced the Phone.apk to brick the phone.
Click to expand...
Click to collapse
Try wipe data and cache from stock recovery. Did you tried this, before bricking phone: http://forum.xda-developers.com/showthread.php?t=2023933 .Try it via fastboot. Good luck
turffe said:
Try wipe data and cache from stock recovery. Did you tried this, before bricking phone: http://forum.xda-developers.com/showthread.php?t=2023933 .Try it via fastboot. Good luck
Click to expand...
Click to collapse
I've done a stock wipe/data/cache.
techjohnny said:
I've done a stock wipe/data/cache.
Click to expand...
Click to collapse
Try install cwm via fastboot. LINK: http://forum.xda-developers.com/showthread.php?t=2023933 .I know it's xt535, but it should work on xt557, because it's hardware same, just other career... Also, try this: http://forum.xda-developers.com/showthread.php?t=18273 I'm not responsible for bricked phone.
turffe said:
Try install cwm via fastboot. LINK: http://forum.xda-developers.com/showthread.php?t=2023933 .I know it's xt535, but it should work on xt557, because it's hardware same, just other career... Also, try this: http://forum.xda-developers.com/showthread.php?t=18273 I'm not responsible for bricked phone.
Click to expand...
Click to collapse
Thanks. I just tried running it from the stock recovery, and it says "signature verification failed."
techjohnny said:
Thanks. I just tried running it from the stock recovery, and it says "signature verification failed."
Click to expand...
Click to collapse
Last .: try to flash xt535 ics, i don't know if it will work, so i dont responsible for bricked phone. But i dont think that this could happen, because difference between phones are just career. Its is on general section of defy. Good luck. Edit: try to flash that file via fastboot, connect your phone to fastboot and then unpack zip and click on bat file..
turffe said:
Last .: try to flash xt535 ics, i don't know if it will work, so i dont responsible for bricked phone. But i dont think that this could happen, because difference between phones are just career. Its is on general section of defy. Good luck. Edit: try to flash that file via fastboot, connect your phone to fastboot and then unpack zip and click on bat file..
Click to expand...
Click to collapse
This phone had fastboot removed.
--tj
techjohnny said:
This phone had fastboot removed.
--tj
Click to expand...
Click to collapse
My last hope may have been removed! Here's a response from Republic Wireless on their OTA update, which I was hoping would replace my /system/app/Phone.apk that's causing my boot-loop on my XT557D:
---START
Hi ...,
I received your help request and wanted to let you know that you won't be able to move the OTA install file. It will be downloaded to the memory of the device.
---END
Would it be possible to download the digital keys that are used on this phone and sign an application to run update in stock recovery?
techjohnny said:
My last hope may have been removed! Here's a response from Republic Wireless on their OTA update, which I was hoping would replace my /system/app/Phone.apk that's causing my boot-loop on my XT557D:
---START
Hi ...,
I received your help request and wanted to let you know that you won't be able to move the OTA install file. It will be downloaded to the memory of the device.
---END
Would it be possible to download the digital keys that are used on this phone and sign an application to run update in stock recovery?
Click to expand...
Click to collapse
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
turffe said:
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
Click to expand...
Click to collapse
If I do this, I still won't be able to connect to Republic Wireless via WIFI, since they have a special ROM cooked that connects your phone to their network to update.
turffe said:
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
Click to expand...
Click to collapse
BLACK SCREEN. It looks as though it was going to flash successfully, but the M logo name came back. Now, it shows up at a modem device in my syslog of Linux. Guess I've totally bricked it now?
--tj
techjohnny said:
BLACK SCREEN. It looks as though it was going to flash successfully, but the M logo name came back. Now, it shows up at a modem device in my syslog of Linux. Guess I've totally bricked it now?
--tj
Click to expand...
Click to collapse
Can you enter to fastboot? Is it stuck on bootlogo or on animated bootanimation? If you can enter to fastboot you're just in bootloop. I will try help you much as I can.. I will try to search for XT557 files...
turffe said:
Can you enter to fastboot? Is it stuck on bootlogo or on animated bootanimation? If you can enter to fastboot you're just in bootloop. I will try help you much as I can.. I will try to search for XT557 files...
Click to expand...
Click to collapse
It doesn't even seem to want to power on anymore, but when plugged into USB, it shows up as a Qual Comm Modem?
techjohnny said:
It doesn't even seem to want to power on anymore, but when plugged into USB, it shows up as a Qual Comm Modem?
Click to expand...
Click to collapse
RSD Lite showing your phone or nothing?
turffe said:
RSD Lite showing your phone or nothing?
Click to expand...
Click to collapse
Nothing now. I forced me to manually power on the phone. I've noticed the flash model is different than the flash:
My phone: MSM7627
Flash file: MSM7227
Windows is requesting a USB driver for a modem.
No Charge LED when phone is plugged into AC.
Oh well. Didn't have high hopes this would work, but was worth the try.
techjohnny said:
Nothing now. I forced me to manually power on the phone. I've noticed the flash model is different than the flash:
My phone: MSM7627
Flash file: MSM7227
Windows is requesting a USB driver for a modem.
No Charge LED when phone is plugged into AC.
Oh well. Didn't have high hopes this would work, but was worth the try.
Click to expand...
Click to collapse
Hard brick.
XT557 spec: http://pdadb.net/index.php?m=specs&id=3753&c=motorola_defy_xt_xt556__xt557
XT535 spec: http://www.gsmarena.com/motorola_defy_xt535-4622.php
F***... Different cpu.... Sorry friend, but blame only yourself, because you started bootloop with your bad Phone.apk....... & not maded CWM backup before modding I think now you can buy new XT530 or if you have warranty sent it for repair or try to tell moto & tell that it powered down itself while charging. The service will replace board or with defy xt530 phone, which is as I know low activity device, but if you bootloop it, you can reflash stock ics via RSD....
XT557D repbulic bootloop
has anybody made any progress in the boot loop... my republic xt557d is in bootloop on moto nonanimated screen
I bought my Razr M XT907 online. It's JellyBean with sys ver. 98.12.4.XT907.Verizon.en.US.
I tried many methods to root it and finally succeeded. But now I got another flash failure
problem: Each time I reboot i get into the following screen:
AP Fastboot Flash Mode (S)
10.9B
Device is LOCKED, Status Code:0
Battery OK
Tansfer mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected.
If I press power, volume up and volue down simultaneously and select nomal powerup, I can get
pass the flash failure screen. But i have to do it every time.
I am from China and use China Telecom(CDMA) network.Kindly please tell me:
How to fix the flash failure? I did not an exact answer on google. Is DroidRazrUtility1.82
available? And UnbrickXT912Jellybean? Will I lose the China Telecom(CDMA) 3G service?
Thanks in advance.
I have fixed the flash failure error by flashing boot logo.
Please search Sports Themed Boot Logos on droidrzr for details cause i am new and not allowed to post outside link.
Help maybe...
betasu said:
I bought my Razr M XT907 online. It's JellyBean with sys ver. 98.12.4.XT907.Verizon.en.US.
I tried many methods to root it and finally succeeded. But now I got another flash failure
problem: Each time I reboot i get into the following screen:
AP Fastboot Flash Mode (S)
10.9B
Device is LOCKED, Status Code:0
Battery OK
Tansfer mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected.
If I press power, volume up and volue down simultaneously and select nomal powerup, I can get
pass the flash failure screen. But i have to do it every time.
I am from China and use China Telecom(CDMA) network.Kindly please tell me:
How to fix the flash failure? I did not an exact answer on google. Is DroidRazrUtility1.82
available? And UnbrickXT912Jellybean? Will I lose the China Telecom(CDMA) 3G service?
Thanks in advance.
Click to expand...
Click to collapse
I think if you flash it and remove the usb cable before it's completely rebooted after the flash the fastboot sticky bit gets stuck. There's also discussion about removing the <GETVAR> lines in the XML file. I'm not sure if the flash actually goes through, but may be reporting to the bootloader a failed flash.
My advice is to remove the <GETVAR> lines in the .XML file, flash, and wait until the phone has completely rebooted and RSD reports a PASS before unplugging the USB Cable.
dtrud0h said:
I think if you flash it and remove the usb cable before it's completely rebooted after the flash the fastboot sticky bit gets stuck. There's also discussion about removing the <GETVAR> lines in the XML file. I'm not sure if the flash actually goes through, but may be reporting to the bootloader a failed flash.
My advice is to remove the <GETVAR> lines in the .XML file, flash, and wait until the phone has completely rebooted and RSD reports a PASS before unplugging the USB Cable.
Click to expand...
Click to collapse
I keep getting flash failure every time. I looked in the xml and see no getvar to remove. If anyone can point me in the right direction id appreciate thank you in advance.
\
I need Help BADLY
dtrud0h said:
I think if you flash it and remove the usb cable before it's completely rebooted after the flash the fastboot sticky bit gets stuck. There's also discussion about removing the <GETVAR> lines in the XML file. I'm not sure if the flash actually goes through, but may be reporting to the bootloader a failed flash.
My advice is to remove the <GETVAR> lines in the .XML file, flash, and wait until the phone has completely rebooted and RSD reports a PASS before unplugging the USB Cable.
Click to expand...
Click to collapse
My Phone which is the exact same kind Droid Razr M non Developers model on Verizon won't even show up in RSD how do i get it to show up?
Im running windows 8 64 bit
Please Help this is my thread
The quickest way to get rid of that is to have a good flash. I suggest flashing the boot logo to fix this problem. Follow the directions here - http://aosp.us/?p=260
betasu said:
I bought my Razr M XT907 online. It's JellyBean with sys ver. 98.12.4.XT907.Verizon.en.US.
I tried many methods to root it and finally succeeded. But now I got another flash failure
problem: Each time I reboot i get into the following screen:
AP Fastboot Flash Mode (S)
10.9B
Device is LOCKED, Status Code:0
Battery OK
Tansfer mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected.
If I press power, volume up and volue down simultaneously and select nomal powerup, I can get
pass the flash failure screen. But i have to do it every time.
I am from China and use China Telecom(CDMA) network.Kindly please tell me:
How to fix the flash failure? I did not an exact answer on google. Is DroidRazrUtility1.82
available? And UnbrickXT912Jellybean? Will I lose the China Telecom(CDMA) 3G service?
Thanks in advance.
I have fixed the flash failure error by flashing boot logo.
Please search Sports Themed Boot Logos on droidrzr for details cause i am new and not allowed to post outside link.
Click to expand...
Click to collapse
---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------
You need the correct drivers installed and the device needs to be put in AP Fastboot mode.
jekovenatinsley said:
My Phone which is the exact same kind Droid Razr M non Developers model on Verizon won't even show up in RSD how do i get it to show up?
Im running windows 8 64 bit
Please Help this is my thread
Click to expand...
Click to collapse