Database Users

Trouble with Recovery...

I finally got my "Alltel Bee" rooted last nite using super one click. Before I roll out any custom roms etc, I'd like to make sure I get a backup, and my phone is hanging on the alltel logo whenever I try to boot into recovery (whether I boot in from Rom manager or from Hboot.) I always end up pulling the battery and rebooting the phone.
I do have an idea as to how I got to this point, and I have only myself to blame, but in my frustration of trying to root this thing I did try this http://forum.xda-developers.com/showthread.php?t=743289 and recovery has hung like this ever since.
I've got root now, and have installed Rom manager, used that to flash clockwork recovery, yet I still have the issue. After a few google searches, I've seen some suggest that fixing file permissions can fix this, and I've done that as well with no change.
Where do I turn next?

So after some more searching and reading and such, I've discovered that even though I have root access, booting into HBOOT shows S-ON still. Could this be the issue in my inability to get a recovery written? Anyone know how to deal with it?

How do you know it is a hang in recovery? If you see the triangle and nothing happens, just click the power button once and usually you will land in the recovery mod menu.

I don't get the triangle at all. I get the initial Alltel logo and that's it. I've waited several minutes before pulling the battery before, but I don't get to the triangle or the menu.

Super one click will only do a temp root. There are no hard roots for the bee that i am aware of. DO NOT TRY UNREVOKED AS IT IS FOR THE BUZZ AND COULD YOUR BEE OR A FROYO BUZZ
Sent from my GT-P1000 using XDA App

Doh! Thanks, I guess I'll wait patiently. (My network switches from Alltel to AT&T inside of 2 months, at which time I'll be provided an Aria.)
Still, it would be nice to customize this thing a bit before it turns into an mp3 player

Send me a boot.img from the bee and I'll get you a recovery
Sent from my HTC Wildfire using XDA App

Even though i dont have the bee would yoi mind clarifiying jacob
Sent from my GT-P1000 using XDA App

If I get a boot image from a shipped rom, I can extract the kernel and build a recovery image
Sent from my HTC Wildfire using XDA App

I'm more than willing to help, How do I pull what you need?
I also have the SDK installed, I've been looking into writing some code for this new toy...
edit: I think I have what I need to get this pulled. Ill see if I can find some time for it this weekend.

willing to help
just starting out. complete noob
But if i can help in any way let me know. in the same boat as the original poster. our section of Alltel is being acquired by at&t and switching to the aria. but would love to help any way i can
Would love to get my "bee" rooted to play with it some more to get familiar with it all

Just got through doing a romdump. Which files do you want?

I am also having this issue... has anyone successully extracted a recovery image for the bee?

Freaking out here might have bricked my phone...

So I was told to install the deodexed [sp] of the GB leak, so I did on top of my rooted, non deodexed version, without wiping. After this I wiped my data a few times, as I heard it would be best to do. Well, after doing so... my phone won't stop bootlooping. I can't access the bootstrapped bootloader, only the stock Moterola one, and I cleared my data with it hoping it would work too...
Help please? How do I "sbf" back to stock or whatever?

Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.

I hope its ok to post this link here:
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html

I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml

tried flashing it again, same thing happened. It failed at "switching phone to BP pass through" apparently. help me please

thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Now just do the system only sbf.it will work
Sent from my DROIDX using XDA App

Do you have the latest drivers installed? Try using RSDlite 4.9!

thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day

z06mike said:
Do you have the latest drivers installed? Try using RSDlite 4.9!
Click to expand...
Click to collapse
i found rsdlite 4.9 didnt recognize my phone but 4.8 did

itzjen said:
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
Click to expand...
Click to collapse
Like what did you say to them?

tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
this is totally being lazy AND the reason why everyone is raising their prices on insurance and why ppl like motorola are locking bootloaders. if it is too much or you're too lazy to do it. dont do it in the first place. sbf isnt hard there are a gazillion guides to sbf'ing. not trying to be rude but seriously?

Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.

thewanton said:
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
Click to expand...
Click to collapse
you have to sbf to .340 use z4 root to root then install DX bootstraper reboot to recovery flash gbrooted.zip if you get stuck in bootloop go into factory recovery and wipe data reboot download and install D2 bootstrapper yes D2, boot into recovery and flash gbrooteddeodexed.zip and let it try and boot it SHOULD bootup after a couple of minutes, if it doesnt get into stock recovery and wipe data, reboot
also it could bootloop because of corrupt downloads

tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...

slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.

itzjen said:
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
Click to expand...
Click to collapse
which is a problem that was caused by YOU because you take that and sbf

thewanton said:
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
Click to expand...
Click to collapse
most ppl overlook that as a typo

Funnyface19 said:
which is a problem that was caused by YOU because you take that and sbf
Click to expand...
Click to collapse
Yes it was a problem that I caused but at that momment I got scared and wasn't sure what I was suppose to do,and because I have no internet at home because i'm never home I use wireless tether when im there and my phone was messed up so wasn't able to look at guides to fix it.....So the easiest thing I thought of is calling them.I wouldn't have mind fixing it but again I wasn't able to at that momment.

I had the same thing happen. Put the letter p at the end of the file name and move it to c:\ this worked for me on rsd lite 4.8 I just kept pulling the battery and retrying until it went through
Sent from my Xoom using XDA Premium App

meshdub said:
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
Click to expand...
Click to collapse
I'd just like to point out that you don't actually need rsd lite 4.8 or higher. 4.7 has worked perfectly for me the several times I have SBF'ed

Issues installing SBF

I am having issues installing the SBF for 2.2. I am getting an error message about not being able to find initialization value. Did anybody run into this error and find out how to fix it.

zax10 said:
I am having issues installing the SBF for 2.2. I am getting an error message about not being able to find initialization value. Did anybody run into this error and find out how to fix it.
Click to expand...
Click to collapse
a) make sure your sbf is good.
b) what version of RSD lite are you using on what OS?

I got the sbf from the one attached to the thread. I am using rsdlite 4.5. It is the only one that would read that the bravo was connected. I am on windows 7 starter on netbook.
Sent from my X10i TripNMiUI using XDA Premium App

zax10 said:
I got the sbf from the one attached to the thread. I am using rsdlite 4.5. It is the only one that would read that the bravo was connected. I am on windows 7 starter on netbook.
Sent from my X10i TripNMiUI using XDA Premium App
Click to expand...
Click to collapse
You might could try RSD 5.0
Although, I had problems with RSD on my WIN7 Vaio also that I could never get around so I just used an XP to do the job.

I gave up with win7 netbook. Used my XP desktop and it started and finished perfectly.
Sent from my X10i TripNMiUI using XDA Premium App

I flashed the linked version via rsd and have no launcher. It started briefly then went to black. Everything works just can't initiate anything. It said it was ready to dl an update after flash so I clicked yes thinking this might be motoblur...BUT, it's waiting for offpeak hours because I cannot turn on wifi. Any thoughts on the next step?
Also, does anyone have a link to the stock 2.1 sbf just in case? I'm kinda in need of my phone right now. thx

ctcost said:
I flashed the linked version via rsd and have no launcher. It started briefly then went to black. Everything works just can't initiate anything. It said it was ready to dl an update after flash so I clicked yes thinking this might be motoblur...BUT, it's waiting for offpeak hours because I cannot turn on wifi. Any thoughts on the next step?
Also, does anyone have a link to the stock 2.1 sbf just in case? I'm kinda in need of my phone right now. thx
Click to expand...
Click to collapse
re-download the sbf in the other thread and re-flash it. it probably flashed wrong in some minor way that is messing something up.

Nahh still black. Thanks for the thought though. At least I can receive incoming calls and everything else for now. Then use the recent calls list to dial back after calling the bravo. :/

ctcost said:
Nahh still black. Thanks for the thought though. At least I can receive incoming calls and everything else for now. Then use the recent calls list to dial back after calling the bravo. :/
Click to expand...
Click to collapse
There is no 2.1 .sbf so if the 2.2 .sbf isn't working then something is wrong. If you can, do a factory data reset and reboot and then try to flash the 2.2 .sbf. see if that works.

Thanks Mcfarmfresh. Didn't want to go that route but didn't lose anything but some texts. It got me back to factory. Will try the flash again in the am.

Ladies and gentlemen, I'm proud to announce the birth of a brand new baby FroYo. Thx again Mcfarmfresh for pushing me in that direction. With Motoblur, all I lost were apps...no biggie.

ctcost said:
Ladies and gentlemen, I'm proud to announce the birth of a brand new baby FroYo. Thx again Mcfarmfresh for pushing me in that direction. With Motoblur, all I lost were apps...no biggie.
Click to expand...
Click to collapse
Awesome! Good to hear. Glad I could help.

ctcost said:
Thanks Mcfarmfresh. Didn't want to go that route but didn't lose anything but some texts. It got me back to factory. Will try the flash again in the am.
Click to expand...
Click to collapse
HELP! I meet the same problem! How can you resolve it? Please help me!

OK I had CM7 working and then I did something stupid and bricked my phone. When I do the SBF, it goes through and then upon reboot it boot-loops. I used the SBF from the other post and am using RSD 5.0, but am not sure what else could be going wrong. I wish I could have wiped things, but when it bricked it wouldn't get to the point for me to get into recovery. I hope I didn't brick it too bad...
edit: I found a post on how to get to the recovery mode to wipe the data. If you need to wipe data after installing an sbf, press the down volume button and hold then press the power button until you see the moto symbol. after you see the exclamation point, press BOTH the up and down volume buttons together to get to the options. The last post I found was a little confusing because some people say you have to touch the bottom right of the screen, which doesn't work.

dontbejeff said:
OK I had CM7 working and then I did something stupid and bricked my phone. When I do the SBF, it goes through and then upon reboot it boot-loops. I used the SBF from the other post and am using RSD 5.0, but am not sure what else could be going wrong. I wish I could have wiped things, but when it bricked it wouldn't get to the point for me to get into recovery. I hope I didn't brick it too bad...
edit: I found a post on how to get to the recovery mode to wipe the data. If you need to wipe data after installing an sbf, press the down volume button and hold then press the power button until you see the moto symbol. after you see the exclamation point, press BOTH the up and down volume buttons together to get to the options. The last post I found was a little confusing because some people say you have to touch the bottom right of the screen, which doesn't work.
Click to expand...
Click to collapse
Did this end up working for you?

Yes it did. I am back using CM7 on my Bravo
Sent from my MB525 using XDA App

The posts relating to pushing the corner of the screen relate to Eclair, 2.1, recovery menu. Froyo, 2.2 ^ is pushing both Vol ^ and v.

Bricked Vibrant

Sorry in advance if im posting this in the wrong thread or if this has been posted before....
I have a Vibrant and i was updating using samsung kies. I never rooted my phone or did and customize things to it. i was going through the updating process when samsung kies said that the update failed and to disconncet my phone. so i disconnected my phone (the screen said download mode and do not turn off target). now when i try to turn my phone on i get a black screen with a phone triangle and computer logo. it will not go in to recovery. cau u please help... thanks
hopefully there is a way to fix this without using odin

odin and download mode there is a thread in development about in the bible i think about unbricking a vibrant, its very hard to brick a vibrant completely, I have done so before, but you can recover via odin.
Your phone is not fully bricked. and your better off than me half the time

How were you trying to boot into recovery if you've never rooted or customized? Your phone is not completely bricked if its turning on so I'm sure there's a fix.
Sent from my PG06100 using XDA Premium App

http://forum.cyanogenmod.com/topic/6998-howto-recover-from-a-soft-brick-on-your-vibrant/
that should have everything you need, you wont be able to get into recovery you need to get into download mode

Rooster85 said:
How were you trying to boot into recovery if you've never rooted or customized? Your phone is not completely bricked if its turning on so I'm sure there's a fix.
Sent from my PG06100 using XDA Premium App
Click to expand...
Click to collapse
You can boot into recovery without being rooted... i did it before when i wanted to do a hard reset.. plus the tmobile rep wanted me to try and boot into recovery to do a hard reset and clear all user data.

BossLady said:
Sorry in advance if im posting this in the wrong thread or if this has been posted before....
I have a Vibrant and i was updating using samsung kies. I never rooted my phone or did and customize things to it. i was going through the updating process when samsung kies said that the update failed and to disconncet my phone. so i disconnected my phone (the screen said download mode and do not turn off target). now when i try to turn my phone on i get a black screen with a phone triangle and computer logo. it will not go in to recovery. cau u please help... thanks
hopefully there is a way to fix this without using odin
Click to expand...
Click to collapse
remove the battery for five minutes, then reinsert it. You can now go back to the normal download mode. ANd I think you can even boot up normally. The former scenario happened to me so I am quite sure of that.

THANKS!!!!
big thanks to everyone i got my phone up and running again. i used odin (which was tricky) and followed the steps i saw in a youtube video. right before i was about to give up i called tmobile and ordered a replacement phone ....lol...tried one more time and it worked im SOOOO HAPPY this is a great community of people , couldnt have done it without u guys THANKS AGAIN!

I always brick my baby, and Odin is always there to save me

[Q] SBF and now stuck SOS

Hey guys so i mistakenly updated to 2.3.3 the other day and really didn't like it so I rooted my phone, and was about to flash Miui when I changed my mind and tried to Deodex my phone, because i had already rooted the phone I tried to do the manual deodex shown in the "noobs guide post" i did everything according the the instructions but it didn't work. So I grabbed the SHADO_X6_2.3.34_SYSTEM-ONLY.SBF file and loaded it in RSD lite to flash back and un-root my phone.. well half way into the process the phone rebooted to the Red M logo.. and everything I've done since has been to no avail.. i tried to download other SBF files that were supposed to be the "full" sbf but for some reason RSD lite wont even let me flash them... If i boot holdig the menu button the phone will bring up the recovery menu and from there i can still select the 4 different options but even after doing the factory data reset and formatting the catch nothing seems to change.. I have been looking for several hours now to get this working and I'm getting really frustrated. So i just want to apologist if this situation has already been dealt with but if you guys could help me out to get my phone working again i would be incredibly great full.

Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App

STAYFROSTY777 said:
Look into the full sbf using the linux iso 1kds did, wish I would post links
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think I read something about the but havn't been able to find where to get the linux iso, am i correct in saying you can temporarily boot linux from the disk to do this? BTW Thank for the sugestion, my wife was about to make me sleep in the dog house for messing my phone up lol so when i get off work i'll try to find the Linux iso, maybe i can even find a thred that has a walk through to fix it.
In the event that I do get everything working again, is it easier to flash roms from gingerbread or from Froyo? or if you want a gingerbread rom i'm assuming you have to flash it from gingerbread correct?

Yes your correct about the roms from my understanding, and haha I know the feeling, yeah just burn the iso onto a disc (its not very big) on boot from disc on your computer, follow the instructions, and it will sbf you to froyo, probably be doing this for me tomorrow since in have some problems with tethering, good luck man, let me know how it goes
Sent from my DROIDX using XDA App

sweet I'll be happy to have my phone back.. lol i miss it, i feel lost without it to be honest. I never knew how attachedi was to my phone. but anyway I'll forsure let you know how it goes i'm praying that this will fix my phone, I have never really come accross a true definition of how to tell if your phone is "bricked" or not. it seems like everyone says their phone is bricked just because they cant get it to boot up but i always thought that the term "bricked" refered to the phone being so screwed up that you can no longer fix or salvage it.. does anyone know the actual definition?

I was recomended to look at this web page it was incredabley helpfull!! i'm running throught the process right now so i'll report my results when done but i'm pretty optimistic about this.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html

Awesome man, i used that method, might be doing again after work today to change roms
Sent from my DROIDX using XDA App

yeah i was so happy that it worked although i was still worried at first because the phone still boots to the Red M logo but after a sec it goes the the droid eye and then load GB anyway now i just need to really understand how to deodex and flash a rom right way, but at least now i know how to fix the phone if i screw something up. One more question, would you guys say that my phone was considered bricked? if so than is it safe to say that there is nothing you can do to it that you can't fix using the Linux boot SBF method?
btw the actual page i used with all the downloads of Linux is right here in case anyone else needs it.
http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html

It doesn't sound like it was bricked, and so for I haven't seen anything to bad where you can just use the Linux way, unless you mess up the hardware lol

well thats somewhat good to know lol thanks for all the advice

Anytime buddy, always glad to help
Sent from my DROIDX using XDA App

The reason why the first sbf didn't work is because you used a SYSTEM only Sbf and it was for froyo 2.3.340 instead of the FULL sbf which reverts everything back to froyo instead of just the system.
Sent from my DROIDX using XDA App

hmm so how is the system only sbf any different than doing a factory reset while running 2.3.340? i mean does doing the system only sbf undo rooting your phone?