I've seen a few similar threads, but no one has a solution to this problem yet.
My Milestone tried to reboot while using the Motorola Update program, and has been stuck at the M screen since.
It is impossible to get into Recovery Mode.
Bootloader mode works. I have tried flashing an sbf, both with RSD and sbf_flash on Linux.
RSD always finishes and asks me to reboot the phone manually. sbf_flash simply tells me it's finished.
Either way, I'm right back where I started. I can remove the battery, get into bootloader, and reconnect and RSD will tell me it Passed. It has not.
I have tried a plain vulnerable recovery, GOT, Stock 2.2.1 and stock 2.1 sbfs for Great Britain, Southeast Asia, and Europe. I have downloaded each at least 2 times.
I have used RDS lite versions 4.6, 4.7, and 5.0, and sbf_flash for linux. I have tried Windows XP and 7.
I can still charge my phone with a wall charger, though very slowly.
What do I do? Are there some kind of error logs that could help? Some other, fool-proof image to try flashing? I appreciate any help, I'm rather desperate.
Have you tried updating your USB drivers for your phone? Perhaps there is something there that is not allowing a successful flash.
Several times, and the problem isn't just in Windows.
Surely someone must have some ideas. Please help me.
Related
Cant connect to RSDlite with my droid x
Here is the story.
I could really use some help here. I had originally rooted my droid x and then tried moving the bin to xbin to keep root. But being that i am really new to this i did not know you couldn't update to 2.2 if you had anything custom installed. so i SBF flashed my phone to stock.. left root off, then updated. Being dumb i tried using the root program for 2.1 on my 2.2. says its rooted fine.. it didn't.. no big deal i hope. i don't know if this has any affect as to why this issue is happening but i figured its worth mentioning. Anyways... so now i want to downgrade from 2.2 to 2.1 so i can root and move the bin file properly but i cant. Every time i try to connect to my computer in PC mode, it fails to load/install the driver for my X. my computer recognizes that its the MB810 but fails... so i cannot connect properly to RSDlite in order to perform the flash.. i have tried connecting in all modes media sync... charge only.. PC mode.. etc.. and yes USB debugging is enabled.. i have been trying to figure this out for a couple days now and I'm going crazy. Any help would be greatly appreciated.
BTW i am using windows 7 64bit
UPDATE:
I now have the drivers installed and the phone connects properly to my computer, not sure if i am connecting properly to RSDlite but it still will not allow me to flash the sbf. the sbf i am using is the phoxus -the gift- for the life of me i cannot figure out why it will not let me flash. i open RSD..select my sbf.. connect my phone.. and the start button will not light up.
o0gamerbear0o said:
Cant connect to RSDlite with my droid x
Here is the story.
I could really use some help here. I had originally rooted my droid x and then tried moving the bin to xbin to keep root. But being that i am really new to this i did not know you couldn't update to 2.2 if you had anything custom installed. so i SBF flashed my phone to stock.. left root off, then updated. Being dumb i tried using the root program for 2.1 on my 2.2. says its rooted fine.. it didn't.. no big deal i hope. i don't know if this has any affect as to why this issue is happening but i figured its worth mentioning. Anyways... so now i want to downgrade from 2.2 to 2.1 so i can root and move the bin file properly but i cant. Every time i try to connect to my computer in PC mode, it fails to load/install the driver for my X. my computer recognizes that its the MB810 but fails... so i cannot connect properly to RSDlite in order to perform the flash.. i have tried connecting in all modes media sync... charge only.. PC mode.. etc.. and yes USB debugging is enabled.. i have been trying to figure this out for a couple days now and I'm going crazy. Any help would be greatly appreciated.
BTW i am using windows 7 64bit
Click to expand...
Click to collapse
I would delete the drivers and install the Motorola driver that you can get at Motorola. I have 2.2 which is running great but I still had to reinstall the drivers see that my PC could See my DX.
Before you can do anything your PC has to See your DX with no issues.
Hope this helps
I'm on 7/32
o0gamerbear0o said:
Cant connect to RSDlite with my droid x
Here is the story.
I could really use some help here. I had originally rooted my droid x and then tried moving the bin to xbin to keep root. But being that i am really new to this i did not know you couldn't update to 2.2 if you had anything custom installed. so i SBF flashed my phone to stock.. left root off, then updated. Being dumb i tried using the root program for 2.1 on my 2.2. says its rooted fine.. it didn't.. no big deal i hope. i don't know if this has any affect as to why this issue is happening but i figured its worth mentioning. Anyways... so now i want to downgrade from 2.2 to 2.1 so i can root and move the bin file properly but i cant. Every time i try to connect to my computer in PC mode, it fails to load/install the driver for my X. my computer recognizes that its the MB810 but fails... so i cannot connect properly to RSDlite in order to perform the flash.. i have tried connecting in all modes media sync... charge only.. PC mode.. etc.. and yes USB debugging is enabled.. i have been trying to figure this out for a couple days now and I'm going crazy. Any help would be greatly appreciated.
BTW i am using windows 7 64bit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=760955
Switch the mode of the device when pluggied in and the drviers should load fine. That said change it from PC mode to Windows Sync Mode and you should be good to go.
Follow this to get your computer to recognize your DX running Froyo, you need new drivers.
1. USB Mass Storage without Development Mode on.
2. MotoConnect will prompt; Install.
3. PC Mode with Development Mode on.
4. ADB activate again on leaked Froyo.
Thanks for all the quick replies. I really appreciate it. I will try all of this when I get home. Thanks again. I'll keep you posted.
Sent from my DROIDX using XDA App
I could do everything except "mass storage" on win 7 x64. I finally had to reinstall windows to get it working again. Hope you have better luck.
Sent from my DROIDX using XDA App
ok i have ADB access which i have never used before.. but all the drivers are installed now and i still cant flash the SBF file still using RSDlite.. im so confused.
o0gamerbear0o said:
ok i have ADB access which i have never used before.. but all the drivers are installed now and i still cant flash the SBF file still using RSDlite.. im so confused.
Click to expand...
Click to collapse
which file did u dl, its the full SBF zip file which was almost 300MB.
yea i do have the full sbf. its 235 some megs or something.. i have used it before.. now i reintalled windows and the RSDlite is working and the phone is connecting and i have the option to click the start button but now i am getting this error.
Failed flashing process. Failed flashing process. Phone (0000): Phone is not compatible with multi-interface super-file. (0x703B); phone connected.
any ideas?
o0gamerbear0o said:
yea i do have the full sbf. its 235 some megs or something.. i have used it before.. now i reintalled windows and the RSDlite is working and the phone is connecting and i have the option to click the start button but now i am getting this error.
Failed flashing process. Failed flashing process. Phone (0000): Phone is not compatible with multi-interface super-file. (0x703B); phone connected.
any ideas?
Click to expand...
Click to collapse
no sorry, i just did the downgrade and had no problems.
well as it turns out.. somehow i got it working, but i dont know how.. but i did. so yea. i guess installing a new copy of windows seemed to do the trick. I hope this thead can help others also. GOOD LUCK and thank you all for helping me out.
You can also go to ubuntu and get a copy of linux for free, burn it to disc, then boot into linux from the disc. No install needed. Once in, use SFB_Flash (google it) to flash the SFB file...P3Droid and Birdman both recommed this vs the RSDlite.
Full error message: Failed flashing process. phone(0000) Phone is not compatable with multi-interface super-file. (ox703b): phone connected
This is information only hopefully for someone who experienced the same issue that I did.
Long story short, I ended up boot looping my X by replacing a system file through Root Explorer and not setting the permissions properly before. Going into a panic, I started gathering the files to re-flash 2.1. When I tried to run RSD, I received the above error message. I tried different versions of RSD, different "gifts", different computers and operating systems. I hit google and was unable to find anything to help. I ended up returning my phone to Wal*Mart and got a new one (told them it bricked during an OTA update...)
After sending some messages to rootzwiki and alldroid for some help, I found that it was because the battery was not at 50% or higher (which makes sense because I let the phone loop for a couple hours disconnected from the PC in HOPES that it would come back). I'm not saying this may be the fix for all issues with the above error message, but it may be something else to try if you have tried everything and just about pulled your hair out...
Hope this helps!
FYI the only version of RSD Lite that will work with the X is veriosn 4.7, but you also have to have the OMAP patch file installed otherwise it will still not work. That said I'm not sure which version you tried or if you had it setup correctly but that could be why you wer having issues also besides the battery not being charged enough.
will2live said:
FYI the only version of RSD Lite that will work with the X is veriosn 4.7, but you also have to have the OMAP patch file installed otherwise it will still not work. That said I'm not sure which version you tried or if you had it setup correctly but that could be why you wer having issues also besides the battery not being charged enough.
Click to expand...
Click to collapse
I started with 4.7 and worked backwards with RSD. I have been able to flash my second X with the same config settings on 4.7. The only thing that changed was the charge on the battery
Where can I find the omap patch file is it the ini file located in the rdslite 4.7+patch.zip? Im getting the same error above but my battery is 96% full. This is happening on two differnt Windows 7 32 bit machines..
Sent from my DROIDX using XDA App
Never mind it is the patch and its now restoring.
I can upload my version of RSD and the patch I have when I get home from school.
It is going to be about 3 hours.
No need, found here: http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X/Page-3.html
Direct link to SBF: http://www.wikifilez.com/Root Files/MotoDroidX/RSDLite-4.7+patch.zip
uninstall all the moto drivers and re-install them again. see if that works.
Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron
first try reinstalling the drivers and try again. if you can get download mode, should be repaired.
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.
So anyone figure out why some ROMs fail to flash on to some devices?
I have a theory, I think it has something to do with "fastboot flash partition gpt_main0.bin" failing to flash on certain devices depending on which rom it's sourced from, also depending on which the device currently has already flashed successfully..
Although this is beyond my comprehension, I don't know the reasoning and or the correct wording. Perhaps someone with more knowledge could shed some insight..
I.E. I can successfully "fastboot flash partition gpt_main0.bin" on my device using MX retail, Bell and AT&T versions/copies will fail to flash on my device and I think it is because the last complete successful flash I was able to do with RSDlite was MX retail.
Anyone got any ideas?
The Atrix HD can be a pain
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]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 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and 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 hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when 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 the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
TheJeremyWhite said:
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]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 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and 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 hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when 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 the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
Click to expand...
Click to collapse
Fails to downgrade.
clockcycle said:
Fails to downgrade.
Click to expand...
Click to collapse
Haha, you're absolutely right. Thanks for pointing that out.
Sent from my MB886 using XDA Premium 4 mobile app
OK, this post might be long. Feel free to skim. I just want to let people know everything that I've done.
So, my VS980 was rooted and I was trying to install a new ROM. I was going to try out Cloudy G2, but the installation routine only gave me international variants to choose from. I picked one anyway and my phone has been hosed since. I didn't have any download mode or recovery or anything.
I was able to get download mode back by extracting part of the firmware out with the LG Firmware Extractor and flashing that through fastboot. So, that part worked. I have download mode. I was going to try to restore my 24A firmware with a KDZ file and the old LG flash tool v 1.8.1 (the one where you put the ADB interface on COM41, and you use the updated megaunlock.dll, etc), but that no longer works for me. It keeps giving me the "failed previous load" error. I can't find a fix for that.
So, I've been trying to flash it (or firmware 26) with the LG Flash Tool 2014 (the one where you pick "Republic of Korea"). That will only get to between 25 and 49%, and then crash with an unknown error.
In between trying that option, I found instructions for extracting all of the bits out of the firmware and then flashing them to the phone partitions one by one. That seemed to work except I kept getting a security error on bootup. The only fix I found for that was to flash with the first flash tool I mentioned. Ugh.
The last time I rooted my phone and ran a custom ROM, my desktop USBs couldn't communicate with my phone very well, but my laptop could. This time not even the laptop's working. I even bought a new USB addon card (I needed it anyway, the USB3 ports on this suck). That seemed to get the computer to see the phone better, but it didn't solve my problems.
Can anyone help with this? I've scoured tons of directions already.
Thank you for any help
Wackman
A little bit of progress
So, I finally got the older flash tool v 1.8.1 to start working. I've almost got it to flash the stock .TOT file (the KDZ file keeps giving me the "failed previous load" error). Now, I've kinda hit a new roadblock.
I think I mentioned that I got into this mess by trying to flash the CloudyG2 ROM, but that it's for international variants. When the flash tool tries to flash the firmware for the VS980, it thinks I have an F320S, and says wrong phone. Anyone know a way around this? I still only have access to download mode. No fastboot, no recovery, no ADB.
any luck? I bricked my G2 last night and I'm trying the flashtool to get back to stock 27A right now. Did you update your C++ library? I read somewhere that that can cause issues with flashtool..