Database Users

why stuck on modaco??

hello all, i recently installed clockwork3.0 to try out the cm7 rom and did so. afer that i wanted to go back to cm6 but decided to try out a custom baked modaco in between. I went no problems to the modaco vision rom and then tried to go back to the cm6 and thats where i ran into the problem. It seems as if though all i can flash and boot now is the modaco vision and desire roms. i try enomther and cm and after the flash and reboot im always stuck at the HTC boot screen which i know shouldnt be there and cant format boot in cwork3.0 without failure error. Even a nandroid back to cm6 wont work. Im assuming this has something to do with the modaco rom writing some apps to /system during install. If anyone can point out my error or explain why this could happen it would be greatly appreciated. Thanke, veritasaequita

You need to flash back to the old ClockworkMod Recovery using fastboot? You have done that haven't you? CWM Recovery 3 is only for 2.3 roms atm afaik.

Cool, thanks for the input bro. Yes I sure have. I did see in the dev forum a thread titled install cw3.0 easily from phone. Is it possible to go back to the old cw by way of using the phone also? Once again thanks for your help
Sent from my HTC Vision using XDA App

oh yeah, indeed you have hit upon something. Try installing ROM manager via the Market,... then use that to re-install the old recovery.
But if that fails,... then yes, you SHOULD be able to use a Terminal Emulator to flash without using fastboot commands.

[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

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

[Q] rooted EVO, but cant flash most roms =(

so i went to install the newest infected rom with sense 3.0 and was very excited about it. repartitioned my card with RA, wiped, and installed and got boot loops upon sense startup. tried a dozen combinations of superwiping, cache/dalvik wipe, double flashing, fix uid, etc but no luck.
i then decided to try the BOS kingdom rom and get the same problem, boot loops as soon as sense loads. maybe i wasnt destined to install sense 3.0 roms.
ok, so i decide to try KingsROM shift4g blakk rom. its a sense 2.x rom so it should be ok, right? nope! boot loops as soon as sense loads up.
at this point, i suspect its my sd card. i use a 1gb without any repartitioning and try KingsROM again. still same problem. the only roms i can actually get flashed are the latest Fresh and Warm 2.2.
i think the problem may be my phone and not the sd card or rom.
details:
003 with nova panel, S-OFF with unrevoked forever
HBOOT 2.10.0001
RADIO 2.15.00.11.19
i have tried RA 2.3 and CW 2.5.0.7 (the newer version doesnt support some sort of scripting so i use an older version). i also superwipe 2-3x before EVERY flash and sometimes wipe cache/dalvik AFTER a flash.
does anyone have any suggestions on what i should do or try? any input is appreciated and i thank you all in advance.

Those roms all use the same kernel, try flashing the rom then netarchys latest kernel, youll lose cam but I can almost guarantee it will boot.
Sent from my PC36100 using Tapatalk

RileyGrant said:
Those roms all use the same kernel, try flashing the rom then netarchys latest kernel, youll lose cam but I can almost guarantee it will boot.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
wow that certainly stinks since i use the camera a lot. i will definitely try it for the sake of trying. i wonder why it wouldnt be able to handle a kernel especially if its a stock htc one iirc.

superwiped 3x, flashed rom, flashed netarchy kernel, then did cache/dalvik wipe with same results =(

http://www.stupidgifs.com/images/full/75.gif
any other suggestions?

nevermind, I failed to properly read the post.

jesuspgt said:
nevermind, I failed to properly read the post.
Click to expand...
Click to collapse
it happens. it means you need more coffee

Can't flash radio, can't fix GPS

So I've got this problem which is driving me nuts...
My GPS isn't working so I need to reflash the 19 radio and then the latest radio again.
I have CWM 4.x so I need to temporarily flash CWM 2.5.0.7 from within ROM manager.
After I do this I can flash the 19 radio (no errors here, everything looks fine) but after rebooting I see that I'm still with the latest (20) radio.
So basically flashing radios doesn't work so I can't fix my GPS...
What can I do? I really need my GPS working...
Any help is very appreciated, thanks a lot!
Sent from my HTC Wildfire using XDA App

U have to downgrade ROM manager to 2.5v
Sent from my HTC Wildfire using Tapatalk

Yeah I know and that's what I've done. I used ROM manager to temporarily go back to CWM 2.5.0.7 and indeed I don't get any error when flashing the radio but at the next reboot I can see that the new radio hasn't actually been installed...
You mean I should go back to CWM 2.5.0.7 with unrevocked?
Thanks!
EDIT: I just realized you said to downgrade ROM manager and not CWM... how do I do that?
Sent from my HTC Wildfire using XDA App

How are you flashing the radio? Its possible to do it in hboot
sent from my android powered. tank using xda premium B-)

radio is to be generally flashed through cwm. But before that may I know which rom you are using ?

.xxx. said:
radio is to be generally flashed through cwm. But before that may I know which rom you are using ?
Click to expand...
Click to collapse
Indeed but if you have the file as an image you can take a HTC rom update.zip with all the stuff in it. Delete everything aside from the txt file, add the new radio if the one it came with is not the one you want then zipup and rename pc49img.zip boot to bootloader and it should do the rest
sent from my android powered. tank using xda premium B-)

I would surely agree to this.

Thanks guys for your help.
Do you care to elaborate on how to flash the radio via HBOOT?
I have the radio.zip file, I guess I can't simply rename it to PC49IMG.zip and put it on the root of the SD card, right? What do I need to do?
Step-by-step instructions are very welcome! ;D
Thanks!
EDIT: I use CyanogenMod 7.1.0.1 if that matters. Also: Revolutionary S-OFF | HBOOT 6.01.1002 | CWM 4.0.1.4

I hope you know how to go into recovery.
In recovery goto install from sd card. Then goto choose from sd card. Choose the required radio zip file and follow the instructions.

and to do it from hbooot. first download a ruu that has the radio that you want. then follow this giude to get out the rom.zip http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
after you get the rom.zip delete or remove all of the files aside from the radio and the android-info-txt file. rip up these files into a zip(make sure there not in a folder) and rename the zip pc49img.zip
then boot into hboot and allow it to do its business.
bear in mind the usual disclamers apply
you do it on your own head
good luck

Have you tried flashing a sense Rom, turning on gps and going outside to get a good fix on Google maps then without changing any settings reboot to recovery and restore a cm7 nandroid backup or flash a fresh install of cm7, the first time it happened to me I flashed the radio to fix it but the second time I lost gps on cm7 flashing a sense Rom fixed it.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
Have you tried flashing a sense Rom, turning on gps and going outside to get a good fix on Google maps then without changing any settings reboot to recovery and restore a cm7 nandroid backup or flash a fresh install of cm7, the first time it happened to me I flashed the radio to fix it but the second time I lost gps on cm7 flashing a sense Rom fixed it.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
No I haven't tried this yet, what sense rom should I use?
Thanks!
Sent from my HTC Wildfire using XDA App

rent0n said:
No I haven't tried this yet, what sense rom should I use?
Thanks!
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Use rempuzzle and then do the steps as mentioned by Scratch..

Yeah even my gps wasnt working on nightly 256. i did the steps mentioned by scratch (rempuzzle) and now back to #256 with gps working.
remember do not switch off ur gps once u get a fix on sense rom.

i don't know why all this hastle for a minor problem like this. wipe everyrhing, installing another rom so that GPS works then wiping again to flash cm7? i hope you still didn't do this because i have this problem so often and the slolution is simple... ANDROID FLASHER! it takes you less than one minute to flash a radio. or anything (boot animations.....) and it works always. mail me if u have questions.

hamdimo said:
i don't know why all this hastle for a minor problem like this. wipe everyrhing, installing another rom so that GPS works then wiping again to flash cm7? i hope you still didn't do this because i have this problem so often and the slolution is simple... ANDROID FLASHER! it takes you less than one minute to flash a radio. or anything (boot animations.....) and it works always. mail me if u have questions.
Click to expand...
Click to collapse
Just want to say, that I also had trouble flashing radio to fix GPS and when I found Android Flasher, I fixed the radio in very short time!
So I can also recommend trying Android Flasher. Very simple!

Thanks guys I solved by flashing Rempuzzle rom, enabling GPS and restoring CM7. Worked like a charm!