Database Users

help! Defy wont boot, white light at top, rsdlite doesnt recognise

Deleted by user

I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App

Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.

Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse

Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App

Guess what, it works!!!
Deleted by user

Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse

I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure

Deleted by user

got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable

To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...

Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd

I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do

Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave

Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder

I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

OH NO! Another messed up Droid X

A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?

check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html

After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.

Let us know what you did fix your situation.
Sent from my DROIDX using XDA App

Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/

It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!

My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community

[Q] Looks like I hard bricked it...

My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.

hayatohuseman said:
My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.
Click to expand...
Click to collapse
That definetly doesn't sound like a hard brick. Use romracers recovery and try to flash a fruitcake http://forum.xda-developers.com/showthread.php?t=1163009 which are much safer then sbfs.
By the way theres no need to apologize when posting in the "correct" forum .General or QandA is where this thread belongs. if this were development though then you'd be in a world of ****! LOL

if you are on big M (without any "failed to boot" ) you're soft bricked,
try to power on button+ volume down button...
if says "fastboot" then just volume up,
download the .img files in the fruitcakes section and follow the fastboot mode instructions...
you'll get back your phone.
read carefully the instruction where to put the files in your windows 7 user directory etc etc, 90% of the problem is because people don't understand where to place executables and run them
hope it helps

Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!

hayatohuseman said:
Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!
Click to expand...
Click to collapse
Kudos for doing some research and figuring out how to resolve the problem. Not enough of that going on. Doesn't it feel like more of an accomplishment?!

KeRmiT80 said:
follow the fastboot mode instructions...
you'll get back your phone.
Click to expand...
Click to collapse
hayatohuseman said:
all I had to do was flash to 2.3.4 with moto-fastboot
Click to expand...
Click to collapse
* 10chars

help for a dell noob

hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.

JDM-Bb said:
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
Click to expand...
Click to collapse
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember

Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.

Strephon Alkhalikoi said:
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Click to expand...
Click to collapse
thanks for the reply, so then what you are saying is that the phone was on GB at one point? man, i knew this guy tryed to flash a dif rom before he sold it. He told me he just got it replace by Dell and decided he didn't want it. i fixed my second problem but im still having the issue with the phone rebooting when data is turned on and then freezes at boot screen.
cdzo72 said:
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Click to expand...
Click to collapse
thanks for the reply
correct i do have drivers and adb in my PC and this is not my first time using adb commands. and yes i did bother reading many threads and using the search tool and found lots of great info but nothing pin pointing to the same problem im having with the phone not liking it when i turn my data on.
Btw i figure out why non of the GB roms were working, when i was doing the factory reset i was only doing it through streakmod recovery. but when i FR on the previous menu it worked.

i also made the diagnostic test through fastboot menu to test the sim and every thing else and everything is fine

Sorry for the late reply. I believe your data issues will resolve themselves by installing 407. From there you can install one of the custom ROMs.

hmm ok ill try that

Razr M XT 907 - Multiple Problems after flashing with RSD Light

Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?

Bump
Bump still looking for a solution

I have CM10 on mine and the camera is completely broken

Enter fastboot oem fb_mode_clear and problem gone.

v0ltage112 said:
Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?
Click to expand...
Click to collapse
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root

lulz
Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
Dude.. you know that you're responding to a thread that is literally a year old right?

cliMAKtic said:
Dude.. you know that you're responding to a thread that is literally a year old right?
Click to expand...
Click to collapse
And wath is the problem i cant help?

Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
Adriantech said:
And wath is the problem i cant help?
Click to expand...
Click to collapse
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.

lem22 said:
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.
Click to expand...
Click to collapse
ok