Database Users

[Q] OK so i know my GF's phone isnt bricked but...

Hey MT4G guru's i need your assistance.
1st off im an Evo user..rooted and all so im not to shabby at doing this. 2nd I rooted her phone using visionary.
So on to the problem. I tried to flash her a theme. I nandrioded (backup) first as usual. The theme which ended up being a full ROM--> http://forum.xda-developers.com/showthread.php?t=929101
It flashed successfully but when i rebooted it gets stuck at the white MT4G screen and stays there forever.
**I can still get into the bootloader & recovery.**
Tried to restore...NO LUCK. It restores, I reboot then the Same white screen.
Tried to factory reset, dalvik & cache wipe..... NO LUCK
Tried Update.zip Nothing!!!
Even tried pd15img in the bootloader. NOTHING!! It doesnt even recognize it!!
Guys i even looked into odin which i found out it isnt needed on phones with recovery.
Hate to sound like a noob but Help!!!!
...A fixed phone will result in 30,000 "thanks" button presses.....cause shes pissed to say the least....
Edit: Ok i believe i found the problem. I had clockwork 2.5.1.2 instead of 3 on her phone. Ok so now that i found the problem how do i fix it??

go to this link http://goo.gl/K0xTy and follow the instructions. you are flashing a cm7 rom and for this phone requires a different recovery. Then flash your rom

Flash cm6 first it will boot with 2.5
twiztid

If you made a nandroid backup, which you always should do before flashing a new rom, you can restore it using clockwork 2.5.1.2. If you don't have a backup you can do two things. You can use fastboot to flash clockwork recovery v3.0.0.5 to the phone then reboot into recovery and successfully flash CM7. If you don't know how to use fastboot then you can use the existing recovery to flash a froyo based rom on the phone. Either iced glacier or CM6 will flash ok. Perform a full wipe before you flash. Once you have a froyo rom working you can follow TrueBlue_Drew's thread about getting clockwork 3 on the phone without issue. I'm on my phone so I can't provide the link but it is in the mt4g development section. It is in a sticky called Resource Bible. In the OP, scroll until you see the header Recoveries and choose the link called Easiest way to install clockwork 3.0.0.5 by TrueBlue_Drew. Follow his instructions and you'll be able to switch between clockwork versions with no hassle. Of course, once you have clockwork 3 working you can flash CM7.
EDIT: Drew replied before I finished writing so follow his link once you are able to boot successfully.
Phillysphinest1 said:
Hey MT4G guru's i need your assistance.
1st off im an Evo user..rooted and all so im not to shabby at doing this. 2nd I rooted her phone using visionary.
So on to the problem. I tried to flash her a theme. I nandrioded (backup) first as usual. The theme which ended up being a full ROM--> http://forum.xda-developers.com/showthread.php?t=929101
It flashed successfully but when i rebooted it gets stuck at the white MT4G screen and stays there forever.
**I can still get into the bootloader & recovery.**
Tried to restore...NO LUCK. It restores, I reboot then the Same white screen.
Tried to factory reset, dalvik & cache wipe..... NO LUCK
Tried Update.zip Nothing!!!
Even tried pd15img in the bootloader. NOTHING!! It doesnt even recognize it!!
Guys i even looked into odin which i found out it isnt needed on phones with recovery.
Hate to sound like a noob but Help!!!!
...A fixed phone will result in 30,000 "thanks" button presses.....cause shes pissed to say the least....
Edit: Ok i believe i found the problem. I had clockwork 2.5.1.2 instead of 3 on her phone. Ok so now that i found the problem how do i fix it??
Click to expand...
Click to collapse
Swyped on my rooted MyTouch4G

XfooYen said:
If you made a nandroid backup, which you always should do before flashing a new rom, you can restore it using clockwork 2.5.1.2. If you don't have a backup you can do two things. You can use fastboot to flash clockwork recovery v3.0.0.5 to the phone then reboot into recovery and successfully flash CM7. If you don't know how to use fastboot then you can use the existing recovery to flash a froyo based rom on the phone. Either iced glacier or CM6 will flash ok. Perform a full wipe before you flash. Once you have a froyo rom working you can follow TrueBlue_Drew's thread about getting clockwork 3 on the phone without issue. I'm on my phone so I can't provide the link but it is in the mt4g development section. It is in a sticky called Resource Bible. In the OP, scroll until you see the header Recoveries and choose the link called Easiest way to install clockwork 3.0.0.5 by TrueBlue_Drew. Follow his instructions and you'll be able to switch between clockwork versions with no hassle. Of course, once you have clockwork 3 working you can flash CM7.
EDIT: Drew replied before I finished writing so follow his link once you are able to boot successfully.
Swyped on my rooted MyTouch4G
Click to expand...
Click to collapse
Dooohhh!!! Thanks for cleaning this up for me. I forgot to tell him he needed to DL and install a 2.2 rom using his current recovery if he cant restore the nandroid. on a side note....I'm typing this from my laptop that is using my wifi hotspot from my friends truck somewhere (middle of nowhere) in Colorado in a snow storm. got to love technology. I am also downloading the latest nightly. Only 28 minutes left on this slow edge connection, but at least its working

TrueBlue_Drew said:
Dooohhh!!! Thanks for cleaning this up for me. I forgot to tell him he needed to DL and install a 2.2 rom using his current recovery if he cant restore the nandroid. on a side note....I'm typing this from my laptop that is using my wifi hotspot from my friends truck somewhere (middle of nowhere) in Colorado in a snow storm. got to love technology. I am also downloading the latest nightly. Only 28 minutes left on this slow edge connection, but at least its working
Click to expand...
Click to collapse
Stay warm..
Swyped on my rooted MyTouch4G

TrueBlue_Drew said:
go to this link http://goo.gl/K0xTy and follow the instructions. you are flashing a cm7 rom and for this phone requires a different recovery. Then flash your rom
Click to expand...
Click to collapse
twiztidmyt4g said:
Flash cm6 first it will boot with 2.5
twiztid
Click to expand...
Click to collapse
UPDATE:
Ok.........(drum roll please)..........and the winner to the simplest answer that i should of thought of myself but i didnt cause i paniced is.....
TrueBlue Drew & Twiztidmy4g
All I needed to do was full wipe & flash a compatible ROM & it booted up fine!!!
**Attention XDA**
National crisis averted!!!! Woman is now satisfied. We nearly missed a nucular meltdown!! Thanks guys!!!!!
MODS PLEASE CLOSE OR COMPLETELY BURN & DELETE THIS WORTHLESS THREAD!!!!!

CM6 download
New to mt4g and have the same problem, i know i cant got o rom manager because i cant boot, can you provide a link to a cm6.zip file that i can run using clockwork 2.5.1.2
Thanks and yes i searched ont he forums for mt4g and i only see cm7 ....

"You can use fastboot to flash clockwork recovery v3.0.0.5 to the phone then reboot into recovery and successfully flash CM7. "
So how do you use fastboot to flash clockwork ? need help here i have clockwork on the sd card and installed using recovery but when i power volume down i am still in clockwork 2.5.1.2
How do i change clockwork to 3.0.0.5 from fastboot ?
Found it.... http://forum.xda-developers.com/showthread.php?t=876632
Installed it and then updated clockwork now in CM& ... wow Thanks .... ?

cmboud said:
So how do you use fastboot to flash clockwork ? need help here ......
Found it.... http://forum.xda-developers.com/showthread.php?t=876632
Installed it and then updated clockwork now in CM& ... wow Thanks .... ?
Click to expand...
Click to collapse
Didn't even have to reply. The search button is a marvelous thing. Good lad!
Swyped on my rooted MyTouch4G

[q] omg need help. Mytouch 4g stuck on mytouch 4g screen.

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

Rom Manager

Ok guys so here is a little something i have been working on for yall. some of you may know rom manager and all its abilities (download roms and flash them without needing a computer, aka "OTA custom roms") well its done. only one team has the roms up and listed right now. now here is for the issues;
-rom manager does not recognize anything but 2.5.1.0 which is the first version of cwm we had going. afaik there are no plans to let it see cwm3 on teh epic
-any roms put on the list will be under premium, sorry ive tried talking to koush but this means you would need to have rom manager premium
now i am hoping we can get more rom devs up on the list and push for cwm3 to be recognized so that users of a certain rom can get notifications of updates and download them via wifi/4g/3g whenever they want. obviously i dont expect people to pay for the premium rom manager when they cant get the free one working.
if any rom devs wish to have their roms added to the list i will not do it for you but after a couple of hours of screwing with the lists (they are javascript.... >.<) i can offer some help on what may not be working. i am in the irc channels almost all the time, if you cant reach me there then shoot me a pm..
P.S. you may be wondering why i posted this in general eh? because this is partially for devs, but its for the users of the epic.. if this is a feature you want then yall need to speak up cuz as it stands now its pretty useless, im hoping by putting this out there that there will be enough of a cry for it that the situation gets handled and then everyone can use koush's awesome program

shabbypenguin said:
Ok guys so here is a little something i have been working on for yall. some of you may know rom manager and all its abilities (download roms and flash them without needing a computer, aka "OTA custom roms") well its done. only one team has the roms up and listed right now. now here is for the issues;
-rom manager does not recognize anything but 2.5.1.0 which is the first version of cwm we had going. afaik there are no plans to let it see cwm3 on teh epic
-any roms put on the list will be under premium, sorry ive tried talking to koush but this means you would need to have rom manager premium
now i am hoping we can get more rom devs up on the list and push for cwm3 to be recognized so that users of a certain rom can get notifications of updates and download them via wifi/4g/3g whenever they want. obviously i dont expect people to pay for the premium rom manager when they cant get the free one working.
if any rom devs wish to have their roms added to the list i will not do it for you but after a couple of hours of screwing with the lists (they are javascript.... >.<) i can offer some help on what may not be working. i am in the irc channels almost all the time, if you cant reach me there then shoot me a pm..
P.S. you may be wondering why i posted this in general eh? because this is partially for devs, but its for the users of the epic.. if this is a feature you want then yall need to speak up cuz as it stands now its pretty useless, im hoping by putting this out there that there will be enough of a cry for it that the situation gets handled and then everyone can use koush's awesome program
Click to expand...
Click to collapse
I thought this app was a cool idea when I first saw it..... then I realized it didn't work, and I never installed it anymore. if you can get it going, that would be awesome.... you've got my vote!

yogi2010 said:
I thought this app was a cool idea when I first saw it..... then I realized it didn't work, and I never installed it anymore. if you can get it going, that would be awesome.... you've got my vote!
Click to expand...
Click to collapse
He got it working <_<'
Thanks a bunch shabby! This should help with user error issues when it comes to flashing =D

I never see any roms when I go to download roms and I have the premium I thought that was bs.
Epic 4g

jbadboy2007 said:
I never see any roms when I go to download roms and I have the premium I thought that was bs.
Epic 4g
Click to expand...
Click to collapse
tahts because no one ever took the time to post em on there. im hoping to change that

I'm currently running cwm3; but when I open ROM Manager it tell me im running 2.5.1.0...
With that said.. I wonder if it'll work? ;p

wait you get rom manager to work with cwm3???

shabbypenguin said:
wait you get rom manager to work with cwm3???
Click to expand...
Click to collapse
No no no. I'm a moron disregard what I said haha.
All thats happened is ROM Manager thinks I'm running 2.5.1.0 when I'm not.
But; shouldn't this just be a redirector issue?

right but even with it thinking you have 2.5.1.0, what version of cwm do you have? does it pop up and ask you to install cwm version x.x.x.x???

I'm running cwm 3 running ext4.
Rom manager works on the phone; but anytime it needs to go into cwm it fails.
It'll hang at the sammy logo. Pulling the battery and powering the phone up normally does the same.
However..doing the three button recovery boot it attempts to load cwm and fails then gives me the Triangle with an Exclamation point inside it..along with the green android.

so how do you get into recovery? also is it 3.0.0.5 or 3.0.0.6?

shabbypenguin said:
so how do you get into recovery? also is it 3.0.0.5 or 3.0.0.6?
Click to expand...
Click to collapse
3.0.0.6
I'm unable to get into recovery through the manager it self. Once I do the three finger salute..it attempts to load and fails; I pull battery and just hold the power button and it loads into cwm.

ok so sounds like 3.0.0.6 is sorta working but we just need to be able to get into recovery normally now....
3.0.0.5 is confirmed to not be working at all

I would love this... had premium on my hero, but sadly I cannot use it on my epic.
Sent from my Samsung-SPH-D700 using Tapatalk

shabbypenguin said:
ok so sounds like 3.0.0.6 is sorta working but we just need to be able to get into recovery normally now....
3.0.0.5 is confirmed to not be working at all
Click to expand...
Click to collapse
Seems to me like it's just a redirector issue; but I've yet to dig into this too deeply so I could be wrong.
It seems to work fine..it just has issues loading directly into cwm.

Hey peeps hopefully someone here can help with almost similar problem.
I used one click root with cwm recovery 2.5.5 in both 2.1 DI18 and EB13. The recovery installed just fine on both.
When I download Rom manager from clockworkmod it doesnt detect that the recovery is installed. I cant do anything without installing the recovery according to ROM manager.
BUT it is installed! Why doesnt it detect it??
How can I get the rom manager to see that I do have clockworkmod recovery 2.5.5 installed?
Or is it not possible yet? I too am a suckered premium owner.

ErlyD said:
Hey peeps hopefully someone here can help with almost similar problem.
I used one click root with cwm recovery 2.5.5 in both 2.1 DI18 and EB13. The recovery installed just fine on both.
When I download Rom manager from clockworkmod it doesnt detect that the recovery is installed. I cant do anything without installing the recovery according to ROM manager.
BUT it is installed! Why doesnt it detect it??
How can I get the rom manager to see that I do have clockworkmod recovery 2.5.5 installed?
Or is it not possible yet? I too am a suckered premium owner.
Click to expand...
Click to collapse
I don't think that ROM Manager can detect recoveries on the phones partitions. I believe it downloads and installs recovery to the sd card.

I some how managed to get an older recovery installed 2.5.1 But still get "an error occured while downloading your recovery." when I click any option and select samsung epic from the prompted list. In an attempt to install the recovery.
If it doesn't install to the fixed partitions how does it install the recovery to boot from? I thought thats where it had to be? That would mean the current recovery I have is in the SD card? then a simple edit of a file would allow it to be detected?

ErlyD said:
I some how managed to get an older recovery installed 2.5.1 But still get "an error occured while downloading your recovery." when I click any option and select samsung epic from the prompted list. In an attempt to install the recovery.
If it doesn't install to the fixed partitions how does it install the recovery to boot from? I thought thats where it had to be? That would mean the current recovery I have is in the SD card? then a simple edit of a file would allow it to be detected?
Click to expand...
Click to collapse
I believe ROM Manager uses the stock recovery to redirect to a zip file on the sd. If the redirector isn't set up right it won't work. The One-Clicks we use to install CWM install it to fixed partition.

I do see that the ACS team is on board with this, hope to see more support soon. On my buddies Fastinate there is quite a bit to work with in Rom Manager, it is a very cool option.
Thanks to all the Dev's
Sent from DEEZ

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

[Recovery] Clockworkmod 5.8.4.3

Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf

mine, just in case!

Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?

KarateExplosion6 said:
Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?
Click to expand...
Click to collapse
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?

KarateExplosion6 said:
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?
Click to expand...
Click to collapse
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Shouldn't matter to my brother. He doesn't even use an SD card!!

KarateExplosion6 said:
Shouldn't matter to my brother. He doesn't even use an SD card!!
Click to expand...
Click to collapse
x_X before I switched I used cm5 (unofficial) on Eris, it was good.. gingerbread is ok on it.. but ics on a better phone is a lot better
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf
Click to expand...
Click to collapse
How does the tool work? I want to get this to work on my htc hero gsm

jordfaz said:
How does the tool work? I want to get this to work on my htc hero gsm
Click to expand...
Click to collapse
what u do is u go to the site and insert a recovery ( even stock ) for ur device and it builds it for ur based on cwm.. fortunately ( or unforunately, if u wanted to do it urself ) there was already one done for the hero =] .... yes that means i looked through a good amount of them just to see what people were building x.x

swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
Click to expand...
Click to collapse
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.

doogald said:
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.
Click to expand...
Click to collapse
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Sent from my Galaxy Nexus using Tapatalk 2

swordrune10 said:
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Click to expand...
Click to collapse
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.

doogald said:
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.
Click to expand...
Click to collapse
Yeah, that's how I always thought was the safest way to do it--running CWM from ROM Manager.

Yep, been using ROM Manager, and CWM through update.zip via Amon RA for a year and a half now without any issues. I don't think I'd ever be tempted to flash CWM over Amon RA; I'd rather have the best of both worlds without wondering if I'm taking any additional risk.

well.. I understand everyone's opinion and its cool.. I tried working on making a recovery.zip that just restarted the recovery not overwrite it, but it just wouldn't do it =/
Sent from my Galaxy Nexus using Tapatalk 2