I think i bricked my Droid X. i was running Rubix Focused and tryed to flash GingerAle 3.0 and now it just sits at the moto "M" logo. i can get into the recovery by pulling the battery but even after a wipe and a recovery it still just sits. did i brick it, and if so how can i fix it? please help, reletivly new to flashing roms.
P.S. I'll love you forever if i can fix it =)
now i think i really did it. I tried running a recovery image from a few days ago and now i cant get back into the recovery menu...
Sounds Like SBF Time
Sounds like SBF is going to be your friend here, if you don't know how, head to
http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
and look for "SBF: What is it, and what does it do?!?"
OK, so i SBFed the phone, got all the way through it, got to the phone is rebooting and it just sits at the Moto "M" again. did i SBF wrong or what?
EDIT: I can get into the stock recovery... sort of. i can get to the ! with the droid next to it but nothing happens when i push the search button.
hmm, I know GB doesnt use the search button to pass that, try using vol UP+DOWN at the same time. perhaps the stock recovery isn't modified from SBF?
Woot that worked. got into recovery. wiped data and tryed a reboot, got stuck at logo again. should i try flashing back to the Rubix focused i had before?
Edit: it now boots into <3e> recovery and i get the e: signature verification failed instillation aborted when i try to install Rubix or Gingerale.
You can't install a custom roms from stock recovery
Sent from my DROIDX using XDA Premium App
try doing a full wipe data/cache a couple of times. that usually works for me
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
YAY
Fixed it!!! yay!! I had to flash the full SBF file, not just the system one. thanks for the help guys
thats ur best bet. full sbf
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Related
hello all
sorry if this is in the wrong section.
today i decided i didnt like my old rom and tried to install fission using the fission rom manager. in the install screen, i forgot to check the wipe box by mistake.
now my phone WILL NOT go any farther than the white moto logo at the very beginning of the boot animation. Is there anyway I can fix this? i am not that experienced at this stuff, so a good explanation is needed. please help!
i just figured out how to get to (stock) recovery from boot, but even after wiping and retryin a few times, it still wont work....
i have also not upgraded or updated really anything since i got my phone months ago, except root, and deodex, and flyx rom
-matt
You won't lose root, and when you sign back into google all your apps will come back. Did you make a recent backup? If so you can use it from recovery
Sent from my DROIDX using XDA App
You can even wipe and reinstall if you still wanna try fission since you're in recovery.
Sent from my DROIDX using Tapatalk
google has all of my tons of apps? sik. but from recovery there is no option to restore/backup nandroid, like bootstrap
the options are reboot, apply sdcard update.zip, wipe data/factory reset, wipe cache partition
Oh you're in stock recovery... Just wipe and reboot.
Sent from my DROIDX using Tapatalk
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Try pulling the battery, should reboot to clockwork recovery when you put battery back in, then you can restore a backup or flash a rom from sd card.
Sent from my DROIDX using XDA App
mattmartin77 said:
well thanks for helping, but even after i wiped 3 or 4 times trying, it still desnt work. any ideas?
idk if fission requires 2.3.32 or somethin, but i dont think i hav updated anything since i got my phone a long time ago, just thought id add that
Click to expand...
Click to collapse
Most roms require .320/.340. You definitely wanna upgrade if you plan on flashing in the future.
Sent from my DROIDX using Tapatalk
well neither of those solve my problem, i am debating on whether on not to take it to verizon, but idk if they will even help me.
if you can get to clockwork recovery you can download a rom by computer and transfer to your sd card, or put your card in another phone to download it. Then flash that rom. Be sure to mount the system before flashing
Sent from my DROIDX using XDA App
Hi matt.. soon after getting my X, I got stuck in your situation while flashing a rom. I took it to verizon and after trying to troubleshoot it for a few minutes, they decided to just overnight me another one. I told them that I woke up and the phone was stuck at the M. I didn't mention anything about being rooted or trying to flash a rom.
The phone was also within the one year warranty though. You might want to try this route if all else fails.
Good luck!!
Sent from my DROIDX using XDA App
If everything else fails you can sbf. I'll pm you a link for the 2.2315 full sbf, just download rsd lite 4.8 and google how to do a sbf if your not familiar. Then you can do the official ota and be up to date
Sent from my DROIDX using XDA App
thnx everyone. ive never sbf'ed before, but ill give it a shot. i wish i could get to clockwork, it would make everything so much easier.
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
mattmartin77 said:
i triedflashing a new sbf, but rsdlite gives me the error- could not find initial values in the ini file or somthin... any ideas? its my fisrt time putting on a new sbf.
Click to expand...
Click to collapse
What version of rsd are you using? you can just sbf .320 full then .340 system only and it will be updated no need to sbf an old file.
i am using the newest rsd i could find. 4.9 right? and it seems as if i need pst_flash.ini according to the sbf installation instructions i found here
edit: hey thnx everyone for the help. i took it to verizon and the techs said it was a "complete software crash". yay i bricked my phone:/... the good news is that verizon is overnighting me a new one.
when i get it i am going to root it. i also want it to be the latest sbf or whatever its called so i can get either fission or gummyjar on there. now i need 2 more questions answered.
1. which option in about is the one that tells me what sbf im on?
2. i kinda need a really good tut on how to flash a new sbf and get it to .340 because i clearly failed miserably at it last time, so anyone have a link or willing to write it up?
It should have.340 on it or be ready to update. You can check by going to settings, about phone, build number. It should say 2.2.340
Sent from my DROIDX using XDA App
oh build number. thnx bro, so many confusing numbers, why cant there just be simple names? lol
Full SBF isn't out yet for 2.3.340 you will need the SBF for 2.3.320 and then the patches to get to 2.3.340. Keep it handy just in case!
yah i have the .15 sbf right now for safe keeping but i cant find the .32 or the .34 patch, but it isnt urgent since i heard that the new phone that is coming will be preloaded with the newest everything.
can i just use z4root to root my new phone? or do i have to do the doroot thing in adb like i originally did on my first dx?
I also wanted to know if i could use one of the kernels i saw in the fission rom manager with a rom other than fission, such as gummyjar.
ok so i was using Liberty rom on my rooted droid 2 and decided to sbf it so and now im in bootloop. ive tryed to sbf it again, but nothing. i took it to verizon because my battery died and the dude took my phone and decided he would try and flash it but now in when the phones in flash mode it says its got bootloader 2.7. and before when i flashed it it said 2.3.2. so dones any one know how to fix it and anyone heard of 2.7 or did he think i had a droid 2 global or something?
Moved to general
ok its not 2.7, its 2.37
Can you get into recovery by holding x while turning the phone on? If you can, try wiping data/cache
Sent from my DROID2 GLOBAL using XDA App
i can but not into clockwork recovery, i get the ! triangle with the droid below, where can i go from there?
closedchannel said:
i can but not into clockwork recovery, i get the ! triangle with the droid below, where can i go from there?
Click to expand...
Click to collapse
After you get the triangle exclamation driod press the search (magnifying glass) on the keyboard to bring up the menu then use the volume keys to scroll and the camera button on the side to select. Wipe data and cache and you should be fine.
You won't be able to get into clockwork after an sbf until you re-root and re-bootstrap.
Sent from my DROID2
FIXED!!! thank you!!!
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
UPDATE: I had the system-only SBF. Found the SBF full and it worked.
Now try to figure how to install the zip files because my phone is not letting me
Venc said:
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
Click to expand...
Click to collapse
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
bigshotrob22 said:
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hey,
Is it even out? I don't see it online
EDIT: I think I found the full SBF. I'll try it. Thanks
UPDATE: bigshotrob22 you are awesome!! Thank you it worked!!! Now I have to cancel my order for the replacement LOL
That happened to me. I SBF'd back to .340 and still had the Red M logo from the Gingerbread .595.
I was unable to get into recovery at all. I eneded up not having the phone for the day and did the SBF again when I got home, you can still access the bootloader, just not recovery (or atleast I was able to) to do the SBF back to .340.
You said you have done the SBF before..my issue with was I did not go into the factory recovery FIRST and wipe all data. I have since done three SBF's and wipe data (in stock recovery, not BOOT STRAP) first. I wiped data, DID NOT REBOOT device. Powered off, and went straight into the bootloader to SBF.
That seems to work for me now.
If it is the samething that happened to me...the wipe did not completely do its job. I make it a habit to wipe 3-4 times before doing anything.
try pushing the volume button up& down at the same time instead of search
Sent from my DROIDX using XDA App
Hey guys I need some help here. I just rooted my droid x and installed the koush recovery as stated in the noobs guide to the droid x. i was able to boot into recovery and clear my data and cache and I installed Gingerale 3.0.
Well I cant get wifi tethering to work so I need to install a WUG's patch. Problem is, I cant seem to boot into koush's recovery anymore. I installed it again on the new rom and tapped bootstrap recovery and it said success. Then I tapped reboot recovery and my phone rebooted. The M came up then all I get is black screen with the backlight on. I have waited 15 minutes and same thing. I have to pull the battery and reboot. I can not for the life of me figure out why I cannot boot into clockwork.
I could use some help. Thanks.
Franteeko said:
Hey guys I need some help here. I just rooted my droid x and installed the koush recovery as stated in the noobs guide to the droid x. i was able to boot into recovery and clear my data and cache and I installed Gingerale 3.0.
Well I cant get wifi tethering to work so I need to install a WUG's patch. Problem is, I cant seem to boot into koush's recovery anymore. I installed it again on the new rom and tapped bootstrap recovery and it said success. Then I tapped reboot recovery and my phone rebooted. The M came up then all I get is black screen with the backlight on. I have waited 15 minutes and same thing. I have to pull the battery and reboot. I can not for the life of me figure out why I cannot boot into clockwork.
I could use some help. Thanks.
Click to expand...
Click to collapse
Try downloading ROM Manager from the Market. Once you open it up click Flash Recovery and select Droid X. Now try to boot into recovery from ROM Manager.
Thanks for the reply. I have done as you said and still no dice. The phone reboots, the M comes up then screen goes black with the backlight on and thats it. Any other ideas?
Franteeko said:
Thanks for the reply. I have done as you said and still no dice. The phone reboots, the M comes up then screen goes black with the backlight on and thats it. Any other ideas?
Click to expand...
Click to collapse
You might have to sbf.
I had the same problem. I installed the droid 2 recovery and got out back finally....
Sent from my DROIDX using XDA Premium App
I dont have a problem sbfing but I would hate to do that if its just going to happen again. A quick search on this forums brings up tons of results of people having the same issue and i have not been able to find a solution for it.
Any ideas?
Have you tried stock recovery? And you have d2 bootatrapper?
Sent from my DROIDX using XDA App
Now you need D2 bootstrap, DX doesn't work on GB
Sent from my DROIDX using XDA Premium App
So here's the story. Bought a used Droid X from a guy at work. Phone was fine. Never rooted or anything related to root. So I decided to root it. Used ZergRush method I believe. Installed Bootstrap Recovery. Wife used Rom Toolbox to change several notification icons, boot animation and boot logo. Everything was great for awhile, but she got tired of it always booting into recovery. So I was going to un-root and return to stock. Ran the same ZergRush Un-root app. Then removed Bootstrap and all other root apps. Then found out wife accepted an OTA before I un-rooted. Well, at this point the phone still worked, and was un-rooted, but still rebooted into recovery, still had custom boot animation and logo as well. So she then reset phone to factory defaults. After that is when we had problems. Basically it wouldn't load past the boot logo. I just pulled the phone out from its hiding spot after a month or so to try and tackle it again. But now I think the battery is shot because it won't turn on period, whether plugged in or not, and the battery looks like its swollen. Has a huge bulge in the middle.
My question is, do you think the phone is able to work again? Cuz if not, I'm not buying a new battery.
Yeah it sounds like a bad battery now but before would it would just boot to the red m? If so an sbf would probably do the trick
Sent from my ADR6425LVW using Tapatalk 2
Ya before it would boot to the M and stay there, until I pulled the battery. So hopefully new battery and sbf and it will work?
Well yeah an sbf should do you just fine
Just be sure once you do the sbf you boot into stock recovery (vol down+home+power then vol up+down together when you see the !) And do a factory reset or you'll just have another headache
Sent from my ADR6425LVW using Tapatalk 2
Alright cool. Looks like I'll be finding a battery and having a whirl at this. Thanks for the replies
So i sbf'd the shadow 2.3.4 using rsd and it said it was completed and to manually boot the phone. So i did and it still stays at red m logo. Only difference is its now the red m where as before the sbf it was the pink Android my wife installed. So some progress I guess.
Any ideas? Try a different sbf file maybe?
Sent from my R800x using XDA
EDIT: Nvm, tried a different sbf and it works fine now.
I know you say it would boot into the M but could you get it to boot into recovery?
Don't remember if i tried actually lol. Its plain now, no root or bootstrap, but it works
Sent from my R800x using XDA
Kasper DG said:
Its plain now, no root or bootstrap, but it works
Click to expand...
Click to collapse
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Nate2 said:
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Click to expand...
Click to collapse
Very strange indeed. Almost like I got the sbf to work or something
Sent from my R800x using XDA