Related
Just got my workphone, Droid 2 Global. No stranger to flashing droid phones (my personal phone is a Captivate) I just had to flash it. I mucked it up once or twice flashing Droid 2 Roms on it and needed to get it back to stock. I know a few people have asked about recovering the Droid 2 Global but I haven't seen any instructions to that effect, so here goes:
Droid 2 Global Return to Stock
1. Download RSD Lite 4.9 - http://www.mediafire.com/?ufxs9lft9q2xwnu
2. Download DROID2WE_X6_2.4.29_FULL SBF - http://www.megaupload.com/?d=MD5K1YY8
3. Download Motorla Drivers - http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe
4. Install RSD Lite 4.9 and the Motorla Driver software. Unzip DROID2WE_X6_2.4.29_FULL to a convenient location, i.e. Desktop.
5. Shut off your Droid 2 Global, unhook it from USB or the AC adapter charger.
6. With the phone off, slide open the keyboard, hold the UP ARROW key on the keyboard and hold the power button. This puts the phone in Recovery mode. The screen will display white text and say something to this effect: "Bootloader D0.11, Battery OK, OK to Program, Connect USB Data Cable."
7. Start RSD Lite by clicking on the desktop icon, this brings up the GUI. Click the ellipse (...) next to the Filename dialogue box. If you put the DROID2WE_X6_2.4.29_FULL SBF file on the desktop, scroll down and select it and click Open. The File Properties box should populate with information about the SBF file.
8. Hook your USB cable to your phone, the text on the display will change. Click the Start button and have patience, this takes a while. RSD Lite will extract files to your desktop and begin flashing your phone. Do not interrupt the flash at any point or you will most likely have as nice paperweight.It takes roughly 5 minutes to flash the default rom and RSD Lite will reboot your phone.
9. If the Reboot fails and your phone loops through the starting animation. Pull the battery and put it back in.
10. Slide open the keyboard on the phone, hold down X on the keyboard and push the power button. This puts the phone in Recovery mode. You know you're in recovery mode when you see a triangle with a yellow exclamation and the green android logo.
11. Hit the Search magnifying glass key, this brings you in to the actual menu. You use the Volume Up and Down to navigate here and the Camera button for enter. Power button exits. Use Volume down until you get to the entry which reads Wipe Data/Factory Reset, push the Camera button. This will wipe your data and cache, I had to tap the OK button (The four little square button on the touchscreen) While it was running because the progress bar would stop. Your milage may vary. After it finishes, select the first menu option to reboot and push the Camera button.
That's it in a nutshell pretty much, let me know if I missed anything.
I've been trying to do this all day. My husband installed Liberty on my phone last night and forgot that it was a D2G, so of course it's all kinds of buggy. I'm trying to revert back to stock to try to properly install Liberty on the phone, but I can't get past the RSD Lite section. It keeps telling me "Failed Flashing Process 0x7100."
I've read a few forums about this issue and tried everything I could find. I'm running Windows 7, have run RSD lite as administrator, changed compatibility to Windows XP, moved the sbf file to every folder mentioned, moved RSD lite to the desktop, etc etc. I've also rebooted, uninstalled, reinstalled, in every fashion I could think of.
This is what I get when I check the error log:
17:01:30, May 03, 2011
Line: 868
ERROR: \\?\c:\users\user\downloads\droid2we_x6_2.4.29_full.sbfuèá contains an invalid path.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
17:01:30, May 03, 2011
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
I'm not sure what it means because most of the errors I've seen for RSD lite have been "was not found."
Any suggestions?
Also, I don't know if this is connected (I think it probably is), but for some reason when I plug in the phone it tells me MTP USB driver installation has failed. Each and every time.
Should I try to flash Fission over top of Liberty?
Thanks.
At first glance, i'd say to check the filename. There looks to be a space in what you copied from the errorlog, in the word full. Secondly, i'd redownload the SBF file, it's possible your download is corrupt. You can also try uninstalling and reinstalling the Moto software, it should install the drivers properly in recovery mode. I have windows 7 64bit and did not have to do anything other than what's in my directions.
Shorten the name of the SBF. Like - d2g.sbf for example. Put the SBF in c:\ and let RSDLite look for it there. It is known not handle well long paths or spaces in file name.
Is this supposed to put the phone back at original stock settings with no apps and everything? I can't find any videos of this, but the Droid X sbf guid it leads you back to the touch the android new out of the box screen. I followed this guide and when my phone rebooted, it had all my apps and widgets and stuff still, the only thing that was different was the firmware version had gone back down.
Nevermind, I somehow skipped the last few steps, I must be really out of it, ignore me.
i flashed it twice now and updated it. both times while flashing it told me to restart the device manually and when i did no change, so i closed the rsd and hit ok when it warns me of damaging my phone. phone was already on and running at the time.
Now i cant get my wifi to connect, it authenticates, then goes straight ot disconnected and then trys again.....any ideas of why this is happenning?
Did you follow steps 9-11?
What terrigan said. If you didn't do the last steps, then your phone will maintain all of its settings, but it will revert to the old firmware, 2.4.29 which is what I initially did. I believe that firmware has buggy wifi to say the least which might be the cause of your problem. You should do steps 9-11 and then after that go to settings, about phone, and system updates, and update to 2.4.330
Awesome!
Thank you for the post! You are awesome. Like a noob, I messed up my phone wile rooting/bootstrapping it and couldn't download from the marketplace, get updates installed etc. This fixed it all and I'm back up and running!
No prob, Wish there were more ROMs for the D2G though.
Worked like a champ, thanks!
Thanks muchly! Now that D2G Gingerbread is available, I'm reverting in the hopes to get the OTA update. Just waiting for the stock SBF to finish atm, will let you know how it goes..
Were not going to get the update until a couple more weeks...
Sent from my DROID2 GLOBAL using XDA App
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Chenoaem said:
Does anyone know if this works for the Droid 2 (NOT GLOBAL)...?
Click to expand...
Click to collapse
The steps and the RSDLite software will, you will need to find an SBF for your phone.
Droid 2 (Non Global) SBF: http://www.multiupload.com/R6VS5FFISB
I take no responsibility if this bricks your phone.
failed flashing process?
Hey, I was trying to revert my phone back, and while running RSD Lite, it got to 100% then it said that the flashing process failed?
the status came out as:
"Failed flashing process: Failed flashing process: Phone[0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected"
help please?
Is there a reason why this would work on one phone but not another? I keep getting a failed on one phone with RSD lite I get code error FEBE 0047. I search and says not compatible software, doesn't make sense. Phone stays in boot loop.
thanks for any help.
Hey guys,
Here's my story:
Just bought a brand new D2G from a friend who likes to waste money...he tried to root it using a D2 rom, and gets the bootloader error. I bought it off of him for $50.
Flashed back to the SBF file in the first post, and then I got a message saying a new update was available. It downloaded on the phone, installs, the phone reboots and I saw the android green robot logo with a box, and a status bar. Once it hit 100%, the phone rebooted again, and to the bootload error said "code corrupt, insert data cable"
Tried holding X and power button to go into recovery mode like I did before, but it just boots to this screen....
Battery just died too, so I had to take it to a verizon store where they are awfully kind to recharge it for free.
Any help is appreciated, otherwise I'm just re flashing back to the rom in the first post again, and never updating the phone!
Jon
Find the .330 D2G SBF file and that should solve your problem I think....
Sounds like the update corrupted during install or download.. theres a .330 sbf try it like the above post stated make sure its fully charged low battery can cause major issues
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
I am an android noob and I have been very frustrated because the OS boot setup does not allow me to control which apps will boot-up at start. I’ve tried various startup managers and none of them can keep apps disabled as they seem to auto start themselves so I have to constantly close apps in order to preserve resources.
I Then sought to root phone to gain control by using a collection of root apps; Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 all w/o success. I do not know why they failed only that these apps seemed to do no harm to the phone otherwise. The phone is a Samsung Galaxy I5500M through PC Mobile, the carrier being Bell Mobile. The following is the particulars on the phone:
Model number: GT-I5500M
Firmware Version: 2.1-update1
Baseband version: I5500MUGKE3
Kernal version: 2.6.29-perf [email protected]#1
Build number: ECLAIR.UGKE3
When I dial *2767*4387264636#.
Product code: GT-I5500YKMBMC.
When I dial *#1234# I get;
PDA: I5500MUGKE3
CSC: I5500MUGKE3
Phone: I5500MUGKE3
I have an acquaintance that has the same phone from the same source that attempted to install a custom ROM using the method outlined on the madteam website "cyanogenmod-7-installation-guide-for-g5-users"
Unfortunately after rebooting that phone it simply boot looped on the Samsung & Android logos. After many attempts to fix boot loop the phone was put aside, to my knowledge that phone has yet to be repaired.
Anyway, I really want to take control of this phone but am afraid of bricking it. Any help to be able to at the very least root it or even better to install a custom ROM would be very much appreciated. Thanks very much to all those that have contributed to this forum… it is amongst the most informative I’ve come across.
Hello there!
If your phone isn't rooted you won't be able to install a custom rom or anything, so I shall try and help you as much as I can, I'm a noob at this kind of stuff too so I'd wait for somebody to confirm what I say before you try it.
I rooted and installed Superuser on my I5500 using Universal Androot, took a few tries though so it might be worth trying it again.
Basically, can you put your phone into download mode? (Turn off device, hold down power button and the volume buttons and it should boot into Download Mode) If so then you could install Clockworkmod (Don't hold me to this, wait for some confirmation from someone with more knowledge) I'm not sure if your device has to be rooted to flash Clockworkmod v4. Even if it doesn't then surely accessing Download Mode and opening KIES will allow you to reset your device and get out of the boot loop.
Here is how to install a custom rom- I use Cyanogenmod 7.1, I'd recommend that to be honest, plenty of customization and many options to tweak performance.
Root your device (I use Universal Androot, it worked for me)
Flash Clockworkmod v4 via Odin.
Put the 3 Cyanogenmod files onto your SD Card.
Reboot into recovery on your device.
Select install update from zip.
Select the 3 files in the specific order.
Wipe data, cache and dalvik cache then reboot.
Then you're running CM7.1.
You can find the files and a more in-depth guide on the Development section under our phones name.
I hope I have helped a bit.
oh I almost forgot, have you tried hard-reseting your device by holding down certain buttons in a specific order? If so then you can reset your phone like that and maybe sort out the boot issue, should fix it, but again don't hold me to it. Hold down the menu/home key, volume key and power off button whilst your device is turned off and that does a hard reset.
Hi CurtisAndroid5,
Thank you for responding. To give a little history I have tried repeatedly using Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 to able to gain Superuser access all w/o success. As far as the custom ROM... that would be the ULTIMATE! But as mentioned on the original post there is someone I know that has possibly bricked one using the exact instructions outlined by the madteam when installing cyanogenmod-7 & spent weeks trying to solve a boot loop... still not fixed. The only reason I have not attempted to do this is I don't want to see the same result.
I have literally booked marked a dozen or more threads, have read hundreds of posts trying to find a solution to rooting this Bell Samsung phone. In my searches I've found on Samsung Open Source website a zipped update; "GT-I5500M_OpenSource_eclair_update2" that I no idea how to use. I honestly think that there are some subtle differences in how Bell sets up their phones that prevents rooting & Superuser access.
I will delve deeper into your suggestion and view posts under the Development section under the phone name. Again your response is deeply appreciated. Thanks!
Ah I see, like I said, I'm not the most experienced person in this kind of stuff so I can't help you any more seen as though my knowledge is limited. I hope you managed to sort your phone out, it will probably be a minor error and will be easily fixed, your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
I had the same problem with my samsung i5500, i just got odin, flashed clockworkmod with it then put in my custom rom, i'm currently on cyanogen mod 1.7.2
CurtisAndroid5 said:
your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
Click to expand...
Click to collapse
I wish mine was -.-
Hi I have Motorola Defy phone, which is rooted and I already update it on Android 4.1 once. But I wanted to make some changes so I made new update with this version: cm-10.2-20130801 and mini GAPPS both from this thread: http://forum.xda-developers.com/show....php?t=1768702. But when I try to start a phone the note: "Setup Wizard has stopped working" shows up and i can't do anything with that.
So I tried to get in recovery mode and install another version, but the yellow exclemation mark with green android (which apparently shows up in phones without root) shows up and then i can get in something like recovery mode in unrooted phone. There are only 4 options.
I'm starting to get really desperate because I really don't know what to do. I'll be very glad if somebody can help me and I'm considering some kind of reward for helping me.
Thank you.
I have an LG Viper LS840 that is running Android 4.0.4 ICS. This was my first time rooting an Android device. I read a bunch of tutorials and managed to root it. I then downloaded ROM Manager to it and loaded ClockworkMod to it. My phone is an LS840. I told ROM Manager that it was a MS840. I thought they were similar enough that it would not hurt anything. When I attempted to back up my current ROM. It booted to a blue menu that said:
Enter the fastboot…
Enter the fastboot…
Long time no see!
It just stays there. I took the battery out and the phone boots fine. It turns out there really are no good ROMs for this phone and it is kind of pointless to root it. So I want to restore it to the factory condition. When I do a factory reset it brings me back to the blue menu.
I have read a few tutorials that said that I can flash the phone with the stock LG ROM. I found a site that had a tutorial and a download with what looked like LG Flash Tools and a file that is named to look like what I need. It is in a .tot format though. The flash tools program does not appear to work with USB and the tutorial tells me to change COM ports in the device manager. I am using a notebook with Windows 8. There is no way to change the ports in the device manager manually because it is “ported” by the OS.
Would someone please help me and offer some more relevant advice? It would be greatly appreciated. Thank you.