Related
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.
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Willem Kloppenburg said:
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Click to expand...
Click to collapse
thats just the default android boot screen, looks like the theme messed up your framework... hold on i'll make a .zip you can flash from recovery to fix it
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Willem Kloppenburg said:
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Click to expand...
Click to collapse
im just downloading the rom for you now so i can extract the framework, if you pull your battery out, you can either plug in your charger while its off, this will bring up recovery, or while its off, hold vol down and press power, that will take you to bootloader, and just pick recovery from the list, now when in recovery, if you navigate to the mounts and storage menu, choose the option mount usb storage, you can now connect to a pc as a disk drive and copy stuff to your sd card
im having trouble uploading attachments to xda at the min dya want me to upload it to megaupload for you?
AndroHero,
Thank you for helping me out. I didn't know about the vol down press power option which allows you to acces the sd card and intall a new rom. I had the revolution rom 2.0.9 already. It's installing as we speak. Much thanks for the tips!
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Everything is resolved. revolution is up and running again. I had to un the fullwipe.zip and that did it!
THANKS a lot for all the tips....again
Willem Kloppenburg said:
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Click to expand...
Click to collapse
Did you do a full wipe before re-flashing your ROM? even if you did just repeat the process , full wipe /cache, /dalvik-cache, /system and then re-flash the rom fingers crossed it should work
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
boot into recovery do a full wipe (system, data, cache and dalvik-cache) then re-flash your rom
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
Could it be possible that you installed cwm 3005 and tried a restore with that. I had the same problem. Went back to cwm 2.5.x and then restore worked.
Sent from my Desire HD
I think there will be a lot of scare because of this CWM 3x...
Same happened to me the other day, stupidly accecpted the update prompt from Rom Manager, did my backup and went to install Cyanogen 6... Got stuck at HTC logo next boot.
Thankfuly, had Leedroid 2.0 on the SD, too, and that one flashed properly
Thing is that when I try to downgrade the Recovery to 2.5x I get an error and really can't be bothered with ADB pushing stuff around, so using Cyanogen 7 for the time beeing
Anyhow, CWM 3.x is likely your problem, easy to fix ^^
Wanting to change my theme on the Samsung spica I had theexact problem on cyanogen mod. Had to redo the whole rooting and installing the Rom again to get to work.
Sent from my Desire HD using XDA App
yes, is some script...back to recovery 2.x
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only
Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?
If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App
3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.
i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.
hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?
OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.
I used the .zip file to restore my mytouch, but now it wont go into Hboot.
I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you
Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas
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
So can I or can't I root my phone?
Any tutorials? Searched for an hour. :/
Coming from MIUI HD2 by the way.
If gingerbread is on your phone (2.3.3)
http://forum.xda-developers.com/showthread.php?t=1218386
http://forum.xda-developers.com/showthread.php?t=1228566
If froyo is on your phone (2.2)
http://forum.xda-developers.com/showthread.php?t=838448
I don't mean to be mean, but 5 posts below yours answers your question.
mattykinsx said:
If gingerbread is on your phone (2.3.3)
http://forum.xda-developers.com/showthread.php?t=1218386
http://forum.xda-developers.com/showthread.php?t=1228566
If froyo is on your phone (2.2)
http://forum.xda-developers.com/showthread.php?t=838448
Click to expand...
Click to collapse
Stuck on "waiting on device". Followed instructions to a tee. On 2.3.3.
kariuki said:
Stuck on "waiting on device". Followed instructions to a tee. On 2.3.3.
Click to expand...
Click to collapse
Usually means debugging isn't on on ur phone. Go to setting/applications/ its in there
Papa Smurf151 said:
Usually means debugging isn't on on ur phone. Go to setting/applications/ its in there
Click to expand...
Click to collapse
Thanks for the reply, but I had recently uninstalled Sync, I restarted my pc, and now it's working.
Had everything working, when I tried to boot a ROM, it was stuck on the htc EVO 4G screen. I went into recovery and wiped everything. Now I'm definitely lost.
Bump, hope it's not bricked...
If you can boot into the white HTC screen, IT IS NOT BRICKED! Put your recovery so you can transfer another rom via usb to your sdcard, then flash a different rom after wiping everything!
Art2Fly said:
If you can boot into the white HTC screen, IT IS NOT BRICKED! Put your recovery so you can transfer another rom via usb to your sdcard, then flash a different rom after wiping everything!
Click to expand...
Click to collapse
I had to transfer a ROM from another phone to this one. Working now. Hope this is isn't a problematic phone.
kariuki said:
I had to transfer a ROM from another phone to this one. Working now. Hope this is isn't a problematic phone.
Click to expand...
Click to collapse
It also helps to know what recovery you're using to flash. Depending on the rom amonra works better than clockwork. I use amonra but that's just my preference. Not getting past the white htc screen isn't that problematic, battery pull vol down+power. How long you sit on the htc screen depends on the rom, some roms take all day to boot on that first one and you need to just let it sit and not panic. Some roms just don't work on some phones. I love Evolved's work but I could not get his "Directors Cut" rom to get past the white htc screen but my guy has the same hardware as I do and his booted right up. To me there is no perfect rom, it's the rom that's perfect for you. We're all different people and like different things. Happy flashing.
p.s.- Just make sure you do the usual wipes before flashing alot of devs also have a format zip that you should use as well. It really doesn't matter which one. Used them all and don't really have a preference to either of them.
Try doing a search next time buddy..
someonenewhere said:
Try doing a search next time buddy..
Click to expand...
Click to collapse
Why should he? Every question he asked, with attitude even, was answered in his thread even though the answers to all his questions were available all on the front page of the forum.
Sent from my Nexus S 4G using Tapatalk