Related
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??
So playing around with a modified Atrix rom... I am now locked. Trying to get the phone back up and running using the SBF and RSDLite but having problems getting the software to recognize the phone.
As the phone sits, it now reads at the initial boot.
Code:
Failed to boot 2
Starting RSD mode
I've tried to take it into recovery mode (created a nandroid backup already to the external microSD) without any luck.
I installed the atrix clockwork recovery (I thought I read somewhere that the atrix CWR worked on the X2) FAILED
Mine now reads same as the OP. Im having to redownload the SBF as Im on Vacation away from my PC that has everything on it.. SO, Ill post if I have additional issues
Hi, I am sorry you are having so much trouble. Hopefully I can provide the steps and help to guide you into successfully recovering your phone from this boot error.
From what I understand you're receiving the following error: "failed to boot 2. starting rsd mode"
I have encountered this error a few times while developing MinimalX. Fortunately, you should be able to recover this using the proper method.
First, turn off your device and plug it in. You will need a certain amount of battery life to perform an SBF without error, so, take advantage of these download times to increase your charge using a wall charger.
Next, you will need to download and install DX2 Drivers and RSD Lite.
You will also need the SBF file, which can be downloaded here:
SBF File
(note: be sure to unzip the file)
Once everything has downloaded and installed successfully, unplug your device from the USB. Plug your USB into your computer only. Then, run RSD Lite with administrator permissions. Browse to and select your SBF file (VRZ_MB870_DTN-14.8_1FF_01.sbf). Then turn on your device, and when you get the "starting RSD mode" prompt, plug in the usb cord from computer to phone. RSD Lite should then recognize your phone, and from there, simply, press start and leave the device and your computer alone until completion (not necessary, but extra precaution). Once this finishes and the phone boots, I highly recommend also doing a factory reset in settings > privacy.
I hope you the best and that this is able to restore function toyour phone. If you need any additional help, feel free to PM me or post in this thread.
Happy DROID-ing!
Sent from my DROID X2 using Tapatalk
Ran into this problem yesterday. Had issues with RSD Lite. Make sure you have the latest version or it will fail. Has to be version 5.3.1 and NOT 5.0 or whatever.
then it should work without a hitch.
Just a reminder, you will have your apps and stuff still installed including SuperUser. You will have to run Gingerbreak again to reroot to add the files back into the proper location, SuperUser doesn't work even with the .apk installed by itself. Just fyi.
Follow instructions here and download files from links provided...
http://forum.xda-developers.com/showthread.php?t=1175300
Yeah Don't Try And Flash The Atrix In Rom Manager, It Will Give You That Error Too.
Apparently there's a link floating around pointing to RSDLite 5.0 renamed and hacked to show 5.3.1. While the download says 5.3.1, the install says 5.3.1, it's still only 5.0.
Thanks again to those working to make the X2 a better phone. Perhaps we can get GB up and running on this thing before the OTA is released. Wouldn't that be egg-on-the-face.
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Using the guide from atrix4ghacks.com Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the message
SVF:405;1:2
Failed to boot 0x1000
1- RSD
2-Fastboot
3-NVflash
4- BP HW Bypass RSD
5-BP HW Bypass QC DLOAD
6-BP HW Bypass & Boot AP
7-BP HW Bypass BP only
8- BP SW Bypass RSD
9- Andriod recovery
10- Boot Andriod (no BP)
11- Device UID
12- Console
13- Early USB
14- BP tools
I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS. When I tried to execute the command via Command prompt. I keep getting unknown command errors (yes, directories within the command are good).
Did I just kill my phone?
I have found a few posts here related to this, though I havent found what seems to be a solid answer to a "fix" for this. I would highly appreciate if someone could try to help me with this.
Sorry, I have broken a noob rule (was pretty late when I watched the video), I thank you all in advanced for any help
STOP!!! YOU HAVEN"T KILLED YOUR PHONE JUST YET!
BUT IF YOU SBF YOU WILL!!!
Go into fastboot and repeat all of the unlock commands, reboot and your phone should boot fine after that.
Ok, I will give that a shot!
Hopefully this will work. THANK YOU!
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Grumbles said:
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Click to expand...
Click to collapse
Ugh... from what I heard the battery won't charge while in fastboot mode. You need a standalone charger or a different battery.
So, it doesn't let you get into fastboot at all, huh?
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Grumbles said:
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Click to expand...
Click to collapse
The factory cable would allow you to use the phone without the battery, but it might take more money and time to make then you think.
From what I understand, RSD threw you an error when you were flashing bootloader unlock.
Anyway, you need to find a way to charge your battery and they do the fastboot unlock commands.
If that doesn't work you need to reflash the pudding SBF, (make sure you install the drivers Windows x64 version here prior to flashing and that your phone is recognized in RSDlited)
Get the correct pudding file from here: http://forum.xda-developers.com/showthread.php?t=1136261
Use instructions here (start at step 1) : http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Note that after pudding is flashed successfully and you do the unlock commands, you will get a failed to boot error (seems like what you have now). You need to redo the unlock commands in fastboot and it will fix the problem.
Good luck.!
Alright!
Got the cable completed and works!
So, battery situation is handled, now to follow your steps
THANK YOU! I will report back and let you know.
Ok,
Clearly I am doing something wrong here.....
I followed the instructions using the newest Pudding_preroot.sbf file, and the RSD software sees the device (as a SE flash not a NS if that matters) and will start the flashing process.
Everything works to plan until the phone does its reboot(99$ executed), gives the fail to boot message again. Then wants to start back up in RSD mode.... The RSD application on the otherhand, it seems like its trying to switch the phone to"BP passthrough mode" I do not see that exact option, and after it failed while rebooting to RSD. I tried to move it to fastboot, BP HW Bypass RSD, and finally BP SW bypass RSD... All with the same failure on the RSD screen:
"Failed Flashing Process. Phone (0000): Error switching to BP Pass through mode (0x70BE); phone connected"
I have a funny feeling that this part is obvious, for that I am sorry for my ignorance.
I am pretty sure this thing is toast...
After getting nowhere after step 12, and multiple attempts to install the pudding_preroot file. I did some searching around and found multiple atrix users that would get the same issues. From the flash showing up as SE rather than NE, to the constant failing during the flash via RSD lite, with the same failure errors.
I noticed a "NV flash" option, and found this link that could establish a recovery USB driver to the phone. Do you think this maybe my next best route?
http://forum.xda-developers.com/showthread.php?t=1123429
My factory cable is good, so that option IS open..... Though I am starting to think this is toast.
We cannot use NVFlash unless we get the SBK (signature file). Currently, we do not have it. Motorola does, so plead to them
OK, well now it decided to only mount itself as a unknown APX device... Not sure the whats or whys there. Nothing has changed since the last failures?
Hey man, I think RSD shows the flashing process as failed since it can't fully reboot the phone.
Go into fastboot mode and try doing the unlock commands. (try this twice if ita fails after the first time).
In the worst case scenario if unlocking fails no matter what, you can flash a complete 2.3.4 rom via SBF and that should get you back up and running.
Let us know how it goes.
Remember, if you can get into RSD or fastboot - the phone isn't bricked yet!
1. Started RSD Light 5.3.1
2. Downloaded the 2.3.4 file linked here:
http://forum.xda-developers.com/showthread.php?t=1138204
3. Started the flash process.
Failed-- Error Switching phone to BP Pass through mode (0x70BE); phone connected
On the Atrix it says Failed to boot, no os detected, and asked me to choose one of the available modes, of which there are 14 in total.
At the bottom it says "starting fastboot protocol support".
What did I do wrong, and what should I do now?
The SD card is plugged into it. Should I battery pull, remove teh SD card, and try flashing the SBF again?
Thanks.
edit: btw I did unrar to get the sbf first and placed it in c:\.
OK I battery pulled, removed sd card, now only have fastboot protocol support, can't seem to re-do the RSD steps...
Oh, looks like this only happens on the first time you flash. OEM unlocked and it's booting up.
Model Name: MI Play M1901F9E
Problem: It is bricked, in bootloop. I cannot shut down the device until its charge gets depleted.
Abilities: It can get into recovery mode and fastboot mode. Pc detects the phone without any problem in both modes.
Observations:
- Factory Reset fails when it reaches 65%.
What is done:
- I tried flashing the latest stock ROM (V11.0.9.0.OFIMIXM) via recovery, using Mi Flash Tool Pro. Everything was going fine, however the percentage in the pc screen got stuck at 49% and after a while it gave a success result but nothing happened. I tried this a couple more times and same thing happened at different percentages (60%, 65%...)
- I tried using Xiaomi Tool V2. Everything was the same. After trying more, the percentage came to 100% and the program gave success result. However, after this process, phone started to count percentage again and it got stuck exactly at 55%.
-I tried using Xiaomi Adb tool via CMD. Similar things happened. It either gets stuck while flashing, or after flashing at different percentage values.
- I tried using MiFlashTool, however, it requires an unlocked bootloader. It gives error. I tried unlocking the bootloader via fastboot but it gives: "token verification failed". Tried Mi unlock tool, but it requires an authorized account.
- I tried using SpFlashTool, however, it requires an authorized account.
So, I'm stuck. I don't have usb debugging enabled, and I don't have the bootloader unlocked. I am not sure if there is any problem with the hardware. Any ideas? Does anyone know why does it get stuck during the recovery flash process via adb?