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
Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.
Well, I have combed and applied these posts for days hoping for a quick fix or previous problems, and because of a mix of user malfunction and super smart people typing in what seems elvish, I could only wish their powers worked on my new-to-me Cregs list phone.
History:
I bought a Samsung Galaxy S "Vibrant" T959 and discovered that when I entered my sim (when I got home) there was a "Invalid sim" icon close to the battery. I tried other sims, none worked in my phone... Figuring I needed to update software, I hooked it up to my PC, and using Keis light (because normal Keis wouldnt recognize it) Updated the software, BUT! During the update, my computer got the BSOD, and bricked my phone, as in (Computer-!-Phone). I frantically looked online for help and dove head first into XDA.
I flashed roms from Eclair to ICS, I dialed strange numbers with *#*# and flashed back when nothing worked, inserted "update.zip" files, downloaded strange packages, and combed through more posts... Now the phone wont go into download mode anymore. I dont blame it... I'm done.
This is my first cry for help. I know I'm a noob. but that's why I'm here.
Help me contribute helpful information to the collective.
Phone Info:
T-Mobile Samsung Galaxy S Vibrant
USA
SIM CARD: AT&T
[STATUS]
Phone Number: Unknown
Network: Unknown
Signal strength: -111dBm 1 asu
Mobile network type: GPRS
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
Etc.
[ABOUT PHONE]
Firmware Version: 2.1 Update1
Baseband Version: T959UVJFD
Kernel Version: 2.6.29
Build number: Eclair
Also,
Phone will not keep APN's, Even after getting official numbers from AT&T, they wont save. (I also have factory unlock codes that don't work)
Any help would be greatly appreciated. I work as a full time volunteer, and get paid about $140 a month through other means. I got this phone for $120, so for me it is an investment that I cant replace.
Thank you XDA! - Seriously, Thank you. :fingers-crossed:
So, to be clear. As of right now, your phone is soft bricked with phone- !- computer icon and won't get to download mode.
Alright. Sounds like your phone wasn't actually unlocked, would be why the invalid sim message was there.
We need to get back to Stock JFD, so pull the battery out of the phone and detach USB cable. Take sim and micro SD card out.
Plug USB cable into computer, and open Odin.
Pop battery into phone and try to get into download mode. (You may not see anything indicating this on the screen. That's OK.)
If you get a yellow COM box in Odin, you're there.
I will check in tomorrow with a more thorough help/follow up. There is a good chance your phone will be fine. Don't panic
Update: I reread your post. I don't have time tonight, but I get the impression you don't have Odin/haven't used it to get to stock JFD before. Sit tight until tomorrow or until you get some guidance.
In the meantime read through the stickies and Odin Guides. Also might want to download the AIO Toolbox so you have it handy.
Duncan_lives said:
Well, I have combed and applied these posts for days hoping for a quick fix or previous problems, and because of a mix of user malfunction and super smart people typing in what seems elvish, I could only wish their powers worked on my new-to-me Cregs list phone.
History:
I bought a Samsung Galaxy S "Vibrant" T959 and discovered that when I entered my sim (when I got home) there was a "Invalid sim" icon close to the battery. I tried other sims, none worked in my phone... Figuring I needed to update software, I hooked it up to my PC, and using Keis light (because normal Keis wouldnt recognize it) Updated the software, BUT! During the update, my computer got the BSOD, and bricked my phone, as in (Computer-!-Phone). I frantically looked online for help and dove head first into XDA.
I flashed roms from Eclair to ICS, I dialed strange numbers with *#*# and flashed back when nothing worked, inserted "update.zip" files, downloaded strange packages, and combed through more posts... Now the phone wont go into download mode anymore. I dont blame it... I'm done.
This is my first cry for help. I know I'm a noob. but that's why I'm here.
Help me contribute helpful information to the collective.
Phone Info:
T-Mobile Samsung Galaxy S Vibrant
USA
SIM CARD: AT&T
[STATUS]
Phone Number: Unknown
Network: Unknown
Signal strength: -111dBm 1 asu
Mobile network type: GPRS
Service state: Out of service
Roaming: Not roaming
Mobile network state: Disconnected
Etc.
[ABOUT PHONE]
Firmware Version: 2.1 Update1
Baseband Version: T959UVJFD
Kernel Version: 2.6.29
Build number: Eclair
Also,
Phone will not keep APN's, Even after getting official numbers from AT&T, they wont save. (I also have factory unlock codes that don't work)
Any help would be greatly appreciated. I work as a full time volunteer, and get paid about $140 a month through other means. I got this phone for $120, so for me it is an investment that I cant replace.
Thank you XDA! - Seriously, Thank you. :fingers-crossed:
Click to expand...
Click to collapse
Is your phone Unlock..?
Toast6977 said:
So, to be clear. As of right now, your phone is soft bricked with phone- !- computer icon and won't get to download mode.
Alright. Sounds like your phone wasn't actually unlocked, would be why the invalid sim message was there.
We need to get back to Stock JFD, so pull the battery out of the phone and detach USB cable. Take sim and micro SD card out.
Plug USB cable into computer, and open Odin.
Pop battery into phone and try to get into download mode. (You may not see anything indicating this on the screen. That's OK.)
If you get a yellow COM box in Odin, you're there.
I will check in tomorrow with a more thorough help/follow up. There is a good chance your phone will be fine. Don't panic
Update: I reread your post. I don't have time tonight, but I get the impression you don't have Odin/haven't used it to get to stock JFD before. Sit tight until tomorrow or until you get some guidance.
In the meantime read through the stickies and Odin Guides. Also might want to download the AIO Toolbox so you have it handy.
Click to expand...
Click to collapse
I have used Odin many times to flash what I thought was stock firmware... but that would make sense if it wasn't. I'll grab the toolbox this morning. It's really unknown when I'm able to get online, but when I do, I'll spend anytime needed to download/fix things.
When I get back later I'll have time to spend making sure your on the right track.
There are a couple apps in the store available to unlock your Vibrant too
As toast said its as easy as an app. First make sure you are rooted, then download Galaxy S Unlock by helroz on the play store. I have unlocked a handful of vibes and Cappy's. The app says it will work even if not rooted but it doesn't.
On another note, I don't believe you will get 3g service on your vibe with at&t service. It depends on a lot of variables.
sent from the depths of helly bean
Toast6977 said:
So, to be clear. As of right now, your phone is soft bricked with phone- !- computer icon and won't get to download mode.
Alright. Sounds like your phone wasn't actually unlocked, would be why the invalid sim message was there.
We need to get back to Stock JFD, so pull the battery out of the phone and detach USB cable. Take sim and micro SD card out.
Plug USB cable into computer, and open Odin.
Pop battery into phone and try to get into download mode. (You may not see anything indicating this on the screen. That's OK.)
If you get a yellow COM box in Odin, you're there.
I will check in tomorrow with a more thorough help/follow up. There is a good chance your phone will be fine. Don't panic
Update: I reread your post. I don't have time tonight, but I get the impression you don't have Odin/haven't used it to get to stock JFD before. Sit tight until tomorrow or until you get some guidance.
In the meantime read through the stickies and Odin Guides. Also might want to download the AIO Toolbox so you have it handy.
Click to expand...
Click to collapse
AHHHH!!!!
IT WORKS!!!!!!!!!!!!!!
You have No idea how I was about moved to tears when I saw that the "Invalid sim" icon was gone!
Here's what I did:
Flashed a stock rom using Odin (like I have done numerous times)
Downloaded AIO Toolbox (WHICH ROCKED MY WORLD!) from the internet to my PC
Using wifi, I got on the android market and got the Galaxy_S Unlock by Helroz.
Turned on phone
Activated USB Debugging mode
Plugged in the phone to my computer
Ran AIO Toolbox >Root the phone (Did I mention it rocked my world?)
Ran the Galaxy_S Unlock by Helroz app and CLOSELY FOLLOWED INSTRUCTIONS
and when I rebooted my phone, I nearly cried.
I cant believe after looking around for a week I never found AIO Toolbox. If I could click "thank you" repeatedly, I would.
Thank you XDA! :highfive:
Very glad for you! It always puts s smile on my face when I see that a problem has been solved! :Hooray:
Toast6977 said:
Very glad for you! It always puts s smile on my face when I see that a problem has been solved! :Hooray:
Click to expand...
Click to collapse
So, Follow up, I just realized that everything is working fine with the flashed ICS, except texting... I checked Carrier settings, installed alternate texting apps, and nothing makes them send. I can recieve texts fine, but it always errors when I send any. Very odd.
EDIT:
I entered *#*#4636#*#* on your dialer. It brings up another settings menu. Find SMSC and entered this number: 07913121139418f0 Clicked update, and hit back button. Just like that, texting works!
Hello,
I'm a little bit at a dead end after trying so much things.
My phone already was in repair for three times. The first time the replaced the mainboard because of a defective earspeaker. Before sending it in I was on the latest available Stock OTA update for my ROM (2.3.4, Retail DACH).
After I got it back after the first repair, I started to get trouble with GPS. Then also the touchscreen started to get a dead area and I send it in for repair the second time. I mentioned the GPS problems aswell, but they just changed the screen.
Then I send it in for the third time and now I have the third mainboard in my phone.
Unfortunately GPS still didn't work. Shows satelites, even sometimes gets a fix for some seconds, but the GPS Test App never reported a value for Accuracy.
Since I didn't want to send it in a again I started to search and found that this seems to be related to libnmea.so.
So I rooted the phone, exchanged the file, checked the permissions and tested it after reboot. Phone showed satelites, but the values for the satelites never went above 30 and it didn't get a GPS-fix within the 20 minutes I was testing it outside in the cold
So I followed another advice to flash a newer radio (N_01.77.36P) just to see if that helps. This required me to unlock the bootloader and install CWM Recovery, since this Radio I found was a fruit cake.
GPS isn't still much better now though... I drove a distance of 350 km (from work back to my home office) with always getting some satelites (approx. max. 7 at a time) displayed but only on the last 40 km I got my first fix, which then also displayed accuracy, so it might have helped a bit, I thought, but GPS fix only worked until I rebooted the phone the next time, since then it seems I didn't drive far enough to get a fix again...
Then I discovered the next problem...
Since unlocking killed my settings I had to make them again. My Exchange ActiveSync at work requires DeviceEncryption, and when the phone rebooted to enable encryption CWM Recovery came up with an error, that it doesn't recognize the parameter, and the phone didn't get encrypted and so I was without my contacts, calender and mails...
I couldn't find a way in the forums to restore the stock recovery, so I decided to reflash the stock-image with SBF.
Followed the guidance to delete cache, davlik cache and factory reset via cwm, and to erase different partitions using fastboot before using RSD Lite.
RSD Lite was 5.7 and the Motodrivers are 5.5.0, running on Win8 64bit.
RSD Lite flashed until 99% and then failed when trying to restart the phone in BP Bypass mode (0x70BE), and the phone was stuck with Error "Failed to boot 1".
I tried the ROM 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-rtdach.sbf
Then I found hints, that others were in the same boat and were able to recover from this error flashing this image
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf
But this didn't help me either, even after more retries. I also tried flashing on three computers and even tried to flash under linux using a Knoppix Live CD. Flash was always performed until the end, but after the last reboot I had the failed to boot 1 again.
Since I didn't find any more usefull guidance of things I could try, I thought "give it another try with the bootloader from the unlock (intl-fix-try1.sbf), can't get really worser now" and so did I and voila device is back and running.
Tried it again to flash a full sbf and came back to the same error, flashed the bootloader.sbf and it's working again...
After that I rooted it again and replaced the libnmea.so file again. But didn't have chance to test it yet, if this helped in any way...
I don't have much hope and think, that I 'll need to send it back to repair again, so again my question, is there any way, to get rid of the "Unlocked" of the bootscreen?
I can think of two possibilities, maybe there is a patched version of this intl-fix-try1.sbf available, that doesn't display this word or there is a way to really get back to the stock bootloader...
Best Regards
Mario
Exactly whats ur problem?????can u be more specific !!!
Sent from my MB860 using Tapatalk
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Mario1976 said:
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Click to expand...
Click to collapse
Mario1976,
I am encountering a similar problem with my AT&T Atrix 4G running Fruit Cake 4.5.141 with BL unlocked.
I cannot get the Data Encryption to work with CWM Recovery 5.8.1.8.
I'm beginning to think that I'll need to restore the stock Android Recovery to be able to get the Data Encrytion to work.
So far, my previous attempts at flashing the stock 4.5.141 SBF using RSDLite has met with the sec_exception: febe, 35, 35 error.
I also tried to use another set of instruction for restoring stock recovery onto another device on my Atrix but to no avail:adb push install-recovery.sh /data/local
adb shell
su
mount -o rw,remount /system
cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1Konker
Update:
I finally figured out that the sec_exception: febe, 35, 35 error meant that the SBF was not intended for the device. That led me to suspect that the system board is not an original AT&T US board. I gave an Asian stock SBF a try & viola! The phone was successfully restored to factory stock ROM with stock bootloader & the Unlocked words removed from the boot screen. Device encryption is also working without any issues.
I bought a Motorola Droid RAZR off of Craigslist. The ad said the phone was like new. I look at the phone and the screen shows where you can make an emergency call or to insert a SIM card. I did not have a SIM card to try out the phone but it looked good from the outside so I bought it. I get to the Verizon store to have it activated. I powered the phone off and started the reboot process. Well it never booted up. The Motorola logo came on the screen the it went to the Droid letters in white and its stuck there. I tried the factory reset and no luck. Can someone PLEASE guide me through the steps on trying to download and install the original software to see if the phone will boot up? I have downloaded Matt's utility and tried that. I started the phone in AP Fastboot. I ran the utility and pressed option 1 to install Jellybean. Everything seemed to go through ok. The phone started to reboot and the little green android guy was on the screen and the thing was spinning and installing files. Once it started to reboot after the install, it went back to being stuck on the Droid logo and thats it. I had plenty of battery when I tried to install the utility. I have a feeling I have to do more things in order to bring the phone back to life. I saw something about RSD Lite. I have no clue what steps to do. Can someone please explain the process to install the original software and get the phone back up and running. I really hate that I got ripped off and hoping someone in here can help me. Thanks in advance!!
Model
tlclermont said:
I bought a Motorola Droid RAZR off of Craigslist. The ad said the phone was like new. I look at the phone and the screen shows where you can make an emergency call or to insert a SIM card. I did not have a SIM card to try out the phone but it looked good from the outside so I bought it. I get to the Verizon store to have it activated. I powered the phone off and started the reboot process. Well it never booted up. The Motorola logo came on the screen the it went to the Droid letters in white and its stuck there. I tried the factory reset and no luck. Can someone PLEASE guide me through the steps on trying to download and install the original software to see if the phone will boot up? I have downloaded Matt's utility and tried that. I started the phone in AP Fastboot. I ran the utility and pressed option 1 to install Jellybean. Everything seemed to go through ok. The phone started to reboot and the little green android guy was on the screen and the thing was spinning and installing files. Once it started to reboot after the install, it went back to being stuck on the Droid logo and thats it. I had plenty of battery when I tried to install the utility. I have a feeling I have to do more things in order to bring the phone back to life. I saw something about RSD Lite. I have no clue what steps to do. Can someone please explain the process to install the original software and get the phone back up and running. I really hate that I got ripped off and hoping someone in here can help me. Thanks in advance!!
Click to expand...
Click to collapse
The model is an XT912
tlclermont said:
The model is an XT912
Click to expand...
Click to collapse
First things first: what are the white letters saying? What is displayed, line by line, when you power it on?
EDIT
Do you still have access to the boot menu?