Enter CM4DX recovery from brick? - Droid X General

Just wondering if this is possible. I'd like to be able to fix my phone without the need for a pc to Sbf from. Or maybe a tablet app to Sbf?

zehkaiser said:
Just wondering if this is possible. I'd like to be able to fix my phone without the need for a pc to Sbf from. Or maybe a tablet app to Sbf?
Click to expand...
Click to collapse
have you tried entering stock recovery and wiping data several times?
i havent seen anyone mention a method that works for getting into cwr.

Well, I'm just worried one day I'll botch an install and have to SBF. It would be nice to have a method of entering recovery to flash the SBF like zip or a nandroid. Maybe a 3 second window before cm starts you could hit your volume button or something.

The Liberty rom has a safe feature that is supposed to have to phone boot into cwr every reboot, but it seems to rarely ever work right.
Luckily when i got in a bootloop last week I kept pulling the battery and sd card to see if it would boot into cwr and to my surprise after several attempts it did. Thank the lord

You're running Liberty? I'm concerned with Cyanogenmod. It bypasses the normal stuff. I can't boot into CWM without selecting Reboot->Recovery from the menu. Bootstrap can't be used.

Related

Booting into clockwork recovery

I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!
Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?
To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed
Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!

No recovery mode/Phone with Explanation mark

Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App

[Q] Emergency. HELP!

I was adding a new custom ROM to my Droid 2 because I wasn't happy with the Epic ROM so I went with the VZW 2.4.5 Clean ROM, I wanted to add the kangerade blue theme to it but accidently installed the wrong version of it over my ROM and now my phone is in a constant boot loop. sometimes it stays at the droid eye for a while and then load into the lock screen but will go right back into the boot sequence.
When it does boot into the lock screen there is not enough time for me to get into the bootstrapper app to boot into recovery mode.
are there any other ways to get into recovery mode? I've searched high and low on this forum and others as well.
I want my droid back =[
Have you tried to pull the battery and then put it back in. Everytime I do that, I end up at recovery thing.
yup, i've pull the battery many times. i've got it into the android recovery screen but when I to the data/cache format it just brings me to the green android starting screen and goes back into the boot loop, what's weird is that the theme is still applied to the phone
yaooitsbrett said:
yup, i've pull the battery many times. i've got it into the android recovery screen but when I to the data/cache format it just brings me to the green android starting screen and goes back into the boot loop, what's weird is that the theme is still applied to the phone
Click to expand...
Click to collapse
Hmmm. Kind of a roundabout process, but did you make a backup. I'd just restore it to a backup and then go from there.
i can't get into the clockwork recovery, just the stock android recovery. are there any backdoors that i could use with adb?
Try taking the battery out during the boot animation a few times, if that doesn't get you to clockwork recovery you've probably lost your recovery. I've noticed that I sometimes (or always?) Lose clockwork when installing a Rom. If that is the case you may have to sbf unless you can get adb to work from the lockscreen.
Sent from my DROID2 using XDA App
pulptastic said:
Try taking the battery out during the boot animation a few times, if that doesn't get you to clockwork recovery you've probably lost your recovery. I've noticed that I sometimes (or always?) Lose clockwork when installing a Rom. If that is the case you may have to sbf unless you can get adb to work from the lockscreen.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
how would I go about doing an sbf? could you point me in the right direction?
On this forum three posts down is a guide. Follow the guide exactly, except you will have to put your phone in bootloader mode since it will not turn on and stay on. Do do this, hold the up button on the dpad when you turn it on.
It works, i just did it yesterday. First time ive ever had to flash SBF, and i did ALOT of roms and modding on my D1. The bootstrap is nice but not as nice as a full bootloader.
Sent from my DROID2 using XDA App
cool. i think i found the guide. it says backup my sd card to my computer..this doesn't delete everything on the sd card does it?
(not a huge concern since having a working phone is better than losing all my stuff on my memory card)
okay. I tried doing what the tutorial said and I got an error on my bootloader that says
"Critical Error: DEA1"
EDIT:
Well it looks like it was just a simple "I need to update my rsd lite program"
I was using the 4.5 and I read that 4.9 was out so I gave updating RSDLITE a shot and boom, the phone is reflashing as we speak
My sd card is intact... untouched from what I can tell. I had no apps2sd though (with 8 gigs on board why would I?)
Sent from my DROID2 using XDA App
Where is the RSD Lite 4.9? All I come across is 4.7.
Sent from my DROID2 using XDA App
Terri M said:
Where is the RSD Lite 4.9? All I come across is 4.7.
Click to expand...
Click to collapse
Google "RSDLite 4.9" it should be in one of the first results..I found mine in a forum
http://droid2files.com/tools/RSD Lite 4.9.zip
This is RSD Lite 4.9.

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

[Q] MyTouch 4g: Multiple problems... PLEASE help.

Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.
have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.
mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.
Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???
glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!
yeah I would send that back
Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App

Categories

Resources