Database Users

Help.. Can't get phone to boot to recovery through rom manager

Everytime i tell it too boot into recovery it just shows the little android guy with a triangle and exclamation and then reboots. I've installed bootstrap and run clockwork recovery. What am i doing wrong? last time i did this and was able to manually go into recovery but when i flashed a rom i just got stuck at motorola bootscreen and had to use sbf. Please enlighten me someone.

Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?

boredmug said:
Ok.. i tried skipping clockwork and just booted into recovery through bootstrap.. Works. I try and flash a rom and the orange bar comes up and says it's installing. The bar never fully goes across but it says the installation is complete. When i try and reboot to try the rom i get stuck at the boot screen. Any ideas what is going on?
Click to expand...
Click to collapse
are you using 2.2? what ROM? you need to run the bootstrap once for it to work, and it will say clockworkmod installed is version 2.5.0.7 in ROMManager thats the bootstrapped version of clockwork mod.
then download the ROM, and don't touch anything after you hit the ok button on the screen that asks to backup current ROM and wipe user data. just let it work.

The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.

boredmug said:
The system info says 2.1update1. I did as you described. I just used bootstrap to boot to recovery and tried flashing a rom and it does the same thing. Just sits at the motorola bootscreen. I'm gunna try my nandroid recovery to go back to the rooted stock rom.. I really don't know what to do from here though because neither way is working for me.
Also, my clockworkMod Recovery is v2.5.0.6 not .7. Maybe this is the issue? when i used rom recovery it said i had the most recent version. I'm Nandroiding right now which seems to be working.
Click to expand...
Click to collapse
you should update to version 2.2
check http://rootzwiki.com/ it has the files you'll need

ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!

boredmug said:
ok. Thanks. Maybe this is the problem? I'm trying to flash a 2.2 rom and currently have 2.1 on my phone? So i've already done sbf back to 2.1 once last night. I'm assuming this procedure is pretty much the same. I'm guessing i will have to reroot my phone. Can i use the same method as 2.1 or is there another method for the droid x with 2.2? Thanks for the help!
Click to expand...
Click to collapse
just check the website i posted, it has guides for everything you need

well.. Now i have 2.2 on my phone but no root. adb can't find my phone.. WTF

Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.

boredmug said:
Thanks for pointing me in the right direction. Was finally able to get it all working. Now I have a working 2.2 custom Rom and can proceed with flashing this thing to cricket. Kinda sucks because I'm doing all this for a friend and using this phone I've kinda come to the conclusion that its a better made phone than my evo. Colors look better on the lcd, camera takes better pictures and the aluminum case is certainly nice too. Only drawback I see is the dev. Much more development for the evo, but then again it is an older phone.
Click to expand...
Click to collapse
I like my DX and it does have a few advantages over the EVO (e.g. battery life and build quality). However, I would gladly trade it for an EVO, since that device has 4G access, a front camera, cyanogenmod support, more accessible bootloader, etc.

MOD PLEASE DELETE Thread is of No use

I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it

U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App

afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything

download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing

Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?

distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery

I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?

menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else

sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....

menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk

a500 bricked unrecoverable bootloader error

i called accer and they were no help pay for shipping i think not, so i know yall can fix anything, i get a unrecoverable bootloader error (0x00000004) and none of the power and volume combinations work i have a $400 paper weight now lol any help would be greatly appriciated

you can try this update, I solved a problem of boot failure http://www.megaupload.com/?d=4CWLBDDN
if it works, you can install the latest version of 3.2, http://forum.xda-developers.com/showthread.php?t=1113878
then looks back at 3:01 this guide to make the root and install a cooked ROM http://forum.xda-developers.com/showthread.php?t=1276227

i tried the zip file and the tablet seems to not except the update zip? any suggestions

brycepaymaster said:
i tried the zip file and the tablet seems to not except the update zip? any suggestions
Click to expand...
Click to collapse
How about some info, like which version of HC were you on, and what were you doing when you bricked it?

hc 3.1 sorry im new to this whole forum thing i was using a custom rom when all this happen not the hc 3.1 cant recall the name entirely i used gingerbreak or bread cant recall to root it then i installed cwm on the tablet and flashed a rom from my sd card once again not sure what it was called because ive been trying to fix this thing for 2 weeks and ive seen 100s of files i flashd a rom from the sd card and when i did the tablet said acouple of errors something about a boot img. i think but dont take my word on it cwm was still working fine when i did the flash then when i restarted the tablet it was bricked central lol also i remember when i did clockwork recovery i remember i flashed the clockwork recovery i used the htc desire for my tablet which is the same as my rooted htc inspire it worked fine but i think that played a big part in why its bricked thats all the info i got if any helps it would be awesome

brycepaymaster said:
hc 3.1 sorry im new to this whole forum thing i was using a custom rom when all this happen not the hc 3.1 cant recall the name entirely i used gingerbreak or bread cant recall to root it then i installed cwm on the tablet and flashed a rom from my sd card once again not sure what it was called because ive been trying to fix this thing for 2 weeks and ive seen 100s of files i flashd a rom from the sd card and when i did the tablet said acouple of errors something about a boot img. i think but dont take my word on it cwm was still working fine when i did the flash then when i restarted the tablet it was bricked central lol also i remember when i did clockwork recovery i remember i flashed the clockwork recovery i used the htc desire for my tablet which is the same as my rooted htc inspire it worked fine but i think that played a big part in why its bricked thats all the info i got if any helps it would be awesome
Click to expand...
Click to collapse
Umm let me see if I understand. You flashed a ROM, but you can't remember which one, you don't remember what you used to root it with, then you installed a version of CWM that is used for the HTC Desire? Is that it in a nutshell?

ok so ive been trying to remember exactly what rom it was i was running hc 3.1 and it was a stock rom i used the new gingerbreak to root it, the one where its like one button tap and its rooted, also im almost sure the custom rom i flashed to the tablet was ROM][JULE8]-=Virtuous Picasso v. 1.1.0=- [Honeycomb 3.1][Kernel: UNITY V5] and i used the htc desire clockwork recovery when i flashed my a500 hopefully this helps more than the other info

brycepaymaster said:
ok so ive been trying to remember exactly what rom it was i was running hc 3.1 and it was a stock rom i used the new gingerbreak to root it, the one where its like one button tap and its rooted, also im almost sure the custom rom i flashed to the tablet was ROM][JULE8]-=Virtuous Picasso v. 1.1.0=- [Honeycomb 3.1][Kernel: UNITY V5] and i used the htc desire clockwork recovery when i flashed my a500 hopefully this helps more than the other info
Click to expand...
Click to collapse
OK great here's your solution:
You need this!

lol is there a way to fix it at all i dont care if its back to stock and i lose everything i just dont want a paper weight

Sorry, I couldn't resist. Seriously though, I think this may be your only solution if you can follow directions very carefully:
http://forum.xda-developers.com/showthread.php?t=1276227
It's gotten quite a few ppl back to 3.1!
Good luck!

is a stupid question (I was wrong as well ), the update. zip is on the SD and not on a USB stick

brycepaymaster said:
lol is there a way to fix it at all i dont care if its back to stock and i lose everything i just dont want a paper weight
Click to expand...
Click to collapse
I just thought of three more options and messaged them to you. Check your messages!

[GUIDE] 2011.12.16 ICS OTA on the AT&T 9020A

Someone mentioned a way to use the new T-Mobile OTA on an AT&T Nexus S. It wasn't totally clear so I figured I'd put up a little more info. I'll get the rough guide up and fill in links later. This will require a computer with fastboot, and either a wifi connection for the phone, or using adb on a computer to push files to the phone while it isn't able to connect to AT&T.
I take no liability for anything going wrong with your phone, cat, significant other, or anything else, as a result of the contents of this guide.
Problems
- Stock recovery keeps replacing Clockwork Recovery. I have to reflash clockwork by fastboot every time.
- This method will leave you with a non-rooted phone
1) Get the phone onto T-Mobile Android 2.3.6 - I did this by using the "Stock" install in Rom Manager, which is 2.3.3. It automatically downloaded the update to 2.3.6, which I then installed. This step is needed because the ICS OTA is an upgrade, not a full install.
2) Update to ICS. I had already directly downloaded the zip from Google, but you might be able to get it by the system upgrade check, or by Rom Manager.
3) Install an AT&T radio - the original stock image (2.3.3) works fine, but once you upgrade to 2.3.6, you have a T-Mobile only radio. The upgrade to ICS will stick with a T-Mobile only radio. Grab an AT&T radio from this thread and get it on the phone. Use fastboot to reset the recovery to ClockworkMod Recovery, and use ClockworkMod to install it. UCKF1 didn't work for me, but UCKE1 did.

Reserved. At the bar.
Sent from my Nexus S using XDA App

FWIW
holtenc said:
yeah thats where got the radio. but it doesn't specify which is for att. just that they are for 9020a,
either way I figured it out. ATT needs the UCKE1 radio. and it works
so ive got GT-I9020A on AT&T working with this ICS ---- WOOT
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
***I saw he successfully posted he flashed the tmo version, had no cell service and I just quoted what he wrote.

UCKE1 works!!!!
you save me and my NS!!!!

laydros said:
Problems
- Stock recovery keeps replacing Clockwork Recovery. I have to reflash clockwork by fastboot every time.
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh. This probably something people have long forgotten...
You can do that right after flashing 4.0.3 in CWM. Just
Code:
adb shell rm /system/etc/install-recovery.sh
Remember to mount /system if it's not mounted already.

Second that. Worked for me.
Instead of ROM Manager I downloaded T mobile 2.36, 3.04 and radio first.
Then flash CWM, 2.36, CWM, 4.03 & radio and then deleted recovery.sh as mentioned.
Working so far.
I assume we can do the same to revert back to official 9020a 4.03 when it drops.
Happy flashing.
---------- Post added at 07:52 AM ---------- Previous post was at 07:19 AM ----------
Market not working.
I am using adb install to push apk's directly to device.

How stable is the tmo ics on the at&t nexus s, I'm getting impatient waiting for the official update

vargasels said:
How stable is the tmo ics on the at&t nexus s, I'm getting impatient waiting for the official update
Click to expand...
Click to collapse
It works fine. I haven't had crashes. It is a bit slower than gingerbread but not terrible. I did a complete wipe after updating and I haven't had any major battery issues some reported.
Btw, you can flash the radio right after flashing 4.0.3. There is no need to boot into ICS, reboot into recovery, and then flash the radio. That way the initial setup can work of 3g not just wifi.

bozzykid said:
It works fine. I haven't had crashes. It is a bit slower than gingerbread but not terrible. I did a complete wipe after updating and I haven't had any major battery issues some reported.
Btw, you can flash the radio right after flashing 4.0.3. There is no need to boot into ICS, reboot into recovery, and then flash the radio. That way the initial setup can work of 3g not just wifi.
Click to expand...
Click to collapse
alright seems easy enough, when the official update comes i can just flash back gingerbeard and go from there right?

vargasels said:
alright seems easy enough, when the official update comes i can just flash back gingerbeard and go from there right?
Click to expand...
Click to collapse
Yes. You will just need to reflash clockworkmod recovery (since stock recovery doesn't let you downgrade) and flash the full the full 2.3.6 rom.

Checking in on this thread to see what radio i9020a people are using on 4.0.3. I currently have XXXKB3 but find that data loses connection when i'm deep indoors. Any suggestions?

I'm currently using UCKD1 but am not entirely satisfied. I occasionally lose my data connection and have to reboot the phone, although I don't know if it is radio-related or not. On ICS 4.04.

crabnebula said:
I'm currently using UCKD1 but am not entirely satisfied. I occasionally lose my data connection and have to reboot the phone, although I don't know if it is radio-related or not. On ICS 4.04.
Click to expand...
Click to collapse
I tried UCKD1 today and for the most part it worked well but I did experience the dreaded search bug about 4 times in one night. It has managed to keep the connection without dropping even once in something like 9 hours.
I also tried flashing UCKE1 earlier but it gave me some kind of error when flashing and was unsuccessful. From what i've read, UCKE1 is a bit better than KD1 but doesn't have the search bug problem.

i just updated my 9020a from 2.3.6 to 4.0.4 i justed flashed the update zip its working great
http://androidforums.com/nexus-s/465048-official-ics-4-0-x-discussion-links-thread.html

[Q] soft bricked ls980

so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.

omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?

XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"

omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup

XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.

omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm

XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work

w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD

omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on

another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/