Database Users

Can't Restart my CM MT3G?

I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.

Probably because you have a lot of apps?
If not, reflash it.

tmc_adio07 said:
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Click to expand...
Click to collapse
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom

mt3g said:
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
Click to expand...
Click to collapse
Thanks for help man, right now I'm running dwang's rom 100% perfect w/ no issues at all. it can reboot and everything just fine. I'm just a little worried on going back and trying to flash cyanogens.
When I installed it, I first did the root process, downloading the .apk file and going through all that part smooth, then I downloaded and flashed the Cyanogen Recovery 1.4, and from there I downloaded the two files (DRC83_base and the latest cyan's rom, i forgot the version #) and applied update from SD, first doing DRC83 and right after doing the rom itself, without rebooting the phone. It loads up A-OK and I can installl the apps and go about my business, but once I need to restart my phone, it just never turns back on. I'm puzzled completely...I even did the whole unroot and reroot thing and STILL i'm not having any luck.

K I got confused in there some where did you flash a cyan rom at all in there I read that you flashed the drc83 zip file but sounds like you just flashed that and booted the phone lol... never tried that but.... any way it seems like you are doing everything correct onlything I could suggest is make sure you have the correct htc base image, and make sure you wipe and repair everything!!!!! and also try a differant download of cyanogen as you might have gotten a bad one or something I have never had any issues with a cyanogen rom except maybe a FC back on 4.0xx or something

兄弟，估计你刷成砖了。同情ing。。

[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] Help to Uninstall ver. 2.3.3

I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0

The problem is that there isn't a known process for rooting Gingerbread (except for installing a pre-rooted ROM)
SBF back to stock, and then you should be able to root, install clockworkmod, and then reinstall Liberty.
pcwebiz said:
I had the Liberty 1.5 ROM on my Droid Rooted with Rom Manager Clock Work recovery and everything was fine until..
I found a file on the web called Monster_D2_2.3.2_4.5.153 I used Clock Work recovery and installed it.
Now my phone says I have Android Version 2.3.3 Build Number STAB
Kernal Version: 2.6.32.9-gd72dc5da20523
It's running fine but I have lost ClockWork Recovery. I can not root the phone after trying several different methods. I can not install anything on it with its stock recovery without getting a signiture failure in the stock recovery and worst of all I can not uninstall it or overwrite it with anything I have loaded on the SD card.
I would be happy to remove this build and re-install Liberty.
I would be even more happy If I could just get this rooted and have my clockwork recovery back.
can anyone help me by pointing me to a thread or link that can help?
Thanks SO much
Gingerbread Dead :0
Click to expand...
Click to collapse

Yup, SBF is the way to go.
SBF Guide:
http://forum.xda-developers.com/showthread.php?t=770224 (be sure to use RSDlite 4.9)
SBF Download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
If you made a backup of liberty before you installed 2.3.3, after you root and put clockwork on, you should be able to just restore it.
It's always good to do as much research as you can before trying anything like that.

I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.

pcwebiz said:
I installed VRZ_A955_2.3.20_1FF_01.sbf
Then I was able to root the phone and use my root applications. The device is very slow and too sketchy to complete anyone task so it was a failure.
Now with your advice I should get back on the right track. Thank You very much for the response. I thought for a moment I might have to drop my phone on the pavement and go to phoneclaim dot com. But you cant learn anything taking the easy way out. lol I'll post the outcome.
Click to expand...
Click to collapse
Yup, as long as you can get the phone into bootloader mode, the phone isn't bricked.
Hope everything works out!
Sent from my Liberated DROID 2

I've had that performance problem after SBF'ing as well. I think I cleared data and rebooted a couple times to address the issue...

Complete Recovery!
Thank You SO much!

I began having a black screen.after a few weeks on gingerbread so I decided to sbf back to froyo but it failed now my phone gives the MOTO logo and goes directly to a black screen. I can't get it into flash mode even with holding the arrow up key. I'm out of ideas here so I'm really hoping to find a way to get this working again without being worried that its truly bricked. Any help would be greatly appreciative.

Have you been able to boot into anything else, such as the stock recovery?

[Q] Can't get into hboot or clockwork?

Search function is down but I did go through a few pages of threads looking for what was going on and no luck but I apologize if this has been solved somewhere else.
First off I would rate my rooting know-how as beginner to intermediate. I've jailbroken/unlocked multiple iPhones awhile back and have rooted/flashed roms on a cliq, mts, my3g, and this mt4g before.
I recently returned my current mt4g back to stock rom and unrooted. I do not think I turned s back on but I should have double checked before.
I currently have root and flashed clockwork and am trying to flash CM7 (I had ran it before on this phone as well). I have an issue right now where I cannot get into clockwork recovery as it will just sit at the mytouch logo forever and if I try and volume up and power into recovery all I get is 3 vibrations and a flashing amber light.
I can boot into the stock (but rooted) rom.
Any ideas? I feel like my recovery is broken or something but this goes beyond what I know. Any help would be great and any information you need I'll be happy to provide.
myTouch 4G, rooted, s (probably) off, stock rom, clockwork says i'm on 3.0.2.4

After reading that, I'm not fully convinced you actually have root and S-OFF. If you're sure you do, download ROM Manager from the Market and use that to install a fresh copy of CWM recovery. Also make sure the "fast boot" option is turned off somewhere under Settings. At that point, there should be nothing preventing you from getting into recovery if you have perm root.

I've got ROM Manager and it has SU permissions and I have the latest recovery flashed but I am still stuck on mytouch logo or the 3 vibrations/amber light when I try to get to recovery. If I reboot there is still no problem getting SU in terminal emulator or ROM manager or anything.
Fast boot is off as well. Thanks for the help so far.
Any ideas?

I don't often boot into recovery manually since most custom ROMs have an enhanced reboot menu with a recovery option, but if memory serves, I believe the key press combination is actually Power + Volume Down, not up like you mentioned in your OP. Give that a try.

Man I am really crazy. Here I am a tmo rep and also a novice modder and I'm hitting power + volume up.
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Thanks for the fresh set of eyes!

breakaway87 said:
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Click to expand...
Click to collapse
After flashing CM7, the phone hangs at the myTouch screen when attempting the first boot?

From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.

breakaway87 said:
From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.
Click to expand...
Click to collapse
What if you select the "boot into recovery" option in ROM Manager? Does the phone reboot into CWM recovery? (you should see the main CWM menu in orange text)

Boot into recovery takes me to MT4G logo and hangs.

breakaway87 said:
Boot into recovery takes me to MT4G logo and hangs.
Click to expand...
Click to collapse
So you don't have a good installation of CWM. Open ROM Manager again and re-flash a fresh recovery. I think there's an option to wipe your existing recovery beforehand, so if you see that, select it. You need to get a working recovery image before you can do much else.

Deleted current recovery and I confirm my model again and it takes a total of 5 seconds. Trying to reboot into recovery again after and I still hang at MT4G.
I hate it when you know something you need to do but you've been working on it so long you can't come up with new ideas.
Thanks again for the help.

Sorry multipost since it didn't register on my computer the first time for some reason

Yeah sorry man, I've never heard of a situation where CWM stubbornly refuses to install. If you have the engineering bootloader, you could manually flash it that way, but that's my only other idea.

Alright well thanks for all the help man, I'll dig around and pick up tomorrow.

I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help

breakaway87 said:
I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help
Click to expand...
Click to collapse
Sure, glad you figured it out.