My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
xs11e said:
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
Click to expand...
Click to collapse
What google apps are you looking for, 99% of them can be found online and installed. Have you tried the online Android market (it can send downloads directly to your device) https://market.android.com/
You might be able use visionary to temp root the device, that will get you started
Bupahs said:
What google apps are you looking for, 99% of them can be found online and installed. Have you tried the online Android market (it can send downloads directly to your device) https://market.android.com/
You might be able use visionary to temp root the device, that will get you started
Click to expand...
Click to collapse
Online market won't install because I've flashed my HD2 to Android so it keeps saying that everything is already installed.
Visionary won't temp root, nothing will, don't know why? Do you know just how many rooting proceedures there are on the WWW? I've tried each that I've found 3 or more times with no luck.
I'm going to try to see if the online market will allow me to install Root Explorer, that may help me some....
It won't. There seems no way to change phones???
xs11e said:
My phone isn't a brick but it might as well be, I flashed a CM7 build but didn't much like it so I never bothered to add the Google Apps, instead, I did a restore to my original MyTouch 4G backup but.... it didn't work, got a flashing screen, etc. so back to the CM7 build, now I can't run ROM Manager, it goes to the red triangle symbol, I can't run ADB, it won't find my phone, I can't root, it just keeps saying S=ON! Since I didn't add the Google Apps and can't now, I can't use the phone!
Am I out a MyTouch 4g? Is there anything that'll fix it?
Click to expand...
Click to collapse
When you tried to restore, did you flash the recovery back to version 2.x? You need a 2.x recovery (use 2.5.1.2) to flash CM6, stock, and other Froyo roms. This should let you restore back to stock. Supposedly clockworkmod 3.0.0.6 can flash back and forth between Froyo and Gingerbread roms, but I haven't tried it yet.
Thanks but whatever version of Clockworkmod I have is what I have since the critter won't allow anything to be changed???
I can't get into Clockworkmod so I think changing versions won't help but I can't change so it's sort of moot at this point. The phone will do either one of these things:
1. Boot normally into the partial CM7 build which isn't usable as explained elsewhere.
2. It'll do the hold Vol Dn and hit power boot but then it won't do anything, the only option that works is normal boot and then I'm right back into CM7.
3. I can select "restore" or boot normally and select ROM Manager and hit boot into recovery and it'll reboot to the error screen, red triangle with ! sign on it.
That is the stock Recovery (which doesn't do anything but display the lovely triangle).
If Rom Manager is running in your broken CM7 system, you could re-flash Clockwork Recovery.
You can also flash a Clockwork Recovery image using adb or Fastboot.
xs11e said:
Thanks but whatever version of Clockworkmod I have is what I have since the critter won't allow anything to be changed???
I can't get into Clockworkmod so I think changing versions won't help but I can't change so it's sort of moot at this point. The phone will do either one of these things:
1. Boot normally into the partial CM7 build which isn't usable as explained elsewhere.
2. It'll do the hold Vol Dn and hit power boot but then it won't do anything, the only option that works is normal boot and then I'm right back into CM7.
3. I can select "restore" or boot normally and select ROM Manager and hit boot into recovery and it'll reboot to the error screen, red triangle with ! sign on it.
Click to expand...
Click to collapse
As mentioned the red triangle is the stock recovery. Not sure how you flashed CM7 with the stock recovery but for some reason it sounds like that is all you have on your phone. FYI...If you hold the vol up and power button at the red triangle screen it should boot you into the stock recovery.
A couple of things that caught my eye. You say that your phone now says s=on. did it used to say s=off? When you say you went back to CM7 after trying to flash your backup, what steps did you take to try and go back? Was your backup made thru Rom Manager? Did you try to use Rom Manager to restore your backup?
First thing I would try is a full wipe and factory reset from the stock recovery if you can get there. You need to try and get CM7 to load correctly. If you can do that then you should be able to flash a new recovery. You dont need s=off to flash roms but you do need root.
Do you still have root acces? Ie: can you use SuperUser? Try a few root apps and see if they as for su permission.
jggimi said:
That is the stock Recovery (which doesn't do anything but display the lovely triangle).
If Rom Manager is running in your broken CM7 system, you could re-flash Clockwork Recovery.
You can also flash a Clockwork Recovery image using adb or Fastboot.
Click to expand...
Click to collapse
Thanks, ROM manager is running but re-flashing Clockwork Recovery doesn't help anything, it completes successfully but any attempt to do anything with it gets me to the red triangle.
I wish I could flash a recovery image using ADB or Fastboot, neither will function.
TrueBlue_Drew said:
As mentioned the red triangle is the stock recovery. Not sure how you flashed CM7 with the stock recovery but for some reason it sounds like that is all you have on your phone. FYI...If you hold the vol up and power button at the red triangle screen it should boot you into the stock recovery.
Click to expand...
Click to collapse
Correct, that's all that's there or at least all I can access so far. Vol up + pwr does boot me into stock recovery but that doesn't help.... <sigh>
A couple of things that caught my eye. You say that your phone now says s=on. did it used to say s=off? When you say you went back to CM7 after trying to flash your backup, what steps did you take to try and go back? Was your backup made thru Rom Manager? Did you try to use Rom Manager to restore your backup?
Click to expand...
Click to collapse
Yes, I did have S=off to flash. Steps trying to go back were none, really, after the restore failed the phone wouldn't do anything as detailed in my posts. The backup was made through Rom Manager and that's what I used to try the restore.
First thing I would try is a full wipe and factory reset from the stock recovery if you can get there. You need to try and get CM7 to load correctly. If you can do that then you should be able to flash a new recovery. You dont need s=off to flash roms but you do need root.
Do you still have root acces? Ie: can you use SuperUser? Try a few root apps and see if they as for su permission.
Click to expand...
Click to collapse
Wiped and factory reset several times with no change in the problem. I'd love to get CM7 to load correctly but since I didn't originally load the GAPPS it's pretty useless, no gmail, no contacts or calendar, no Android market (which means all that's on the phone is all I can get, the online market won't work as mentioned in a previous post.) I cannot flash a new recovery, that's what I've been trying to do for several days now.
I do have root access, I can use SuperUser but it doesn't seem to do anything. Attempts to re-root have failed.
i feel ya bro, the reason I am asking these questions is to try and figure out what you have tried and not tried. CM7 isnt useless if you can get it to load. Just because you dont have the gapps installed, that shouldnt do anything but make you not have the market and google apps. Do you have adb set up and will it recognize your device? The biggest question is why would it have turned s=on and why wouldnt rom manager be able to flash a new recovery. Rom manager has a problem making/flashing backups using 3.0.0.X recoveries so that is where this problem started I think. Thats why I am trying to get you a clean working CM7. Does it give you a error when trying to install recovery through rom manager? Have you tried going to applications/manage applications/all/Rom Manager and clearing the data?
If you have su access you might also be able to flash a new recovery via terminal emulator.
Thanks, I appreciate the help and sympathy! I've fixed it in a very unorthodox way, it involved going to T-Mobile's website, changing phone to Blackberry 9700, moving SIM to 9700 and switching data plan to Blackberry.
Dang, that's a little screen....
The reason I'm maybe not giving you all the information you need is that I have very bad arthritis in my hands and I try to type as little as possible, I'm sorry if I'm not being clear but don't hesitate to ask if you need more info.
Not having the gmail means no sync, can't import contacts or calendar, no apps means what I have on the phone is ALL I HAVE, I can't get anything else. That's why I say it's unusable.
ADB does not recognize the device.
Installing recovery through Rom manager results in red triangle.
I did clear Rom manager data as you suggested but it didn't help.
How could I flash recover through terminal emulator, I do have that and can access it and typing SU does give me the # prompt so that's helpful maybe? I'd need step by step directions because I'm very unfamiliar with using terminal emulator, I've only used it to follow directions given in the rooting instructions.
xs11e said:
Thanks, I appreciate the help and sympathy! I've fixed it in a very unorthodox way, it involved going to T-Mobile's website, changing phone to Blackberry 9700, moving SIM to 9700 and switching data plan to Blackberry.
Dang, that's a little screen....
The reason I'm maybe not giving you all the information you need is that I have very bad arthritis in my hands and I try to type as little as possible, I'm sorry if I'm not being clear but don't hesitate to ask if you need more info.
Not having the gmail means no sync, can't import contacts or calendar, no apps means what I have on the phone is ALL I HAVE, I can't get anything else. That's why I say it's unusable.
ADB does not recognize the device.
Installing recovery through Rom manager results in red triangle.
I did clear Rom manager data as you suggested but it didn't help.
How could I flash recover through terminal emulator, I do have that and can access it and typing SU does give me the # prompt so that's helpful maybe? I'd need step by step directions because I'm very unfamiliar with using terminal emulator, I've only used it to follow directions given in the rooting instructions.
Click to expand...
Click to collapse
to flash a recovery image via terminal emulator if you are on cm7 is:
Type "su" and then enter the code below after putting the recovery on your sd card. Make sure you name it recovery.img
Code:
flash_image recovery /sdcard/[COLOR=black]recovery.img[/COLOR]
LMK if that works.
Thanks, I'm not sure what I expected but what happened is exactly nothing:
Put Recovery.img on card, booted up phone, started Terminal Emulator got:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/recovery.img
#
And that's it, nothing happened at all, just went back to the # prompt.
xs11e said:
Thanks, I'm not sure what I expected but what happened is exactly nothing:
Put Recovery.img on card, booted up phone, started Terminal Emulator got:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/recovery.img
#
And that's it, nothing happened at all, just went back to the # prompt.
Click to expand...
Click to collapse
As long as you named it recovery.img and not Recovery.img it should have worked. Try to boot into recovery by powering off your phone and then holding the vol but and power button at the same time. Then chose recovery. Or if you on CM7 just hold power button for a sec and then reboot and recovery.
LMK if that works.
I checked the name several times, booting into recovery just takes me to the red triangle, I've tried that many times before, nothing's changed.
I suspect it's a brick?
xs11e said:
I checked the name several times, booting into recovery just takes me to the red triangle, I've tried that many times before, nothing's changed.
I suspect it's a brick?
Click to expand...
Click to collapse
ok, I still dont believe its a brick. Are you running a rom at all? I mean does it boot into CM7 even though you dont have Gapps? Or is it totaly stuck on bootloop all the time. I am going to send you a PM with my Gtalk. Add me if you want and maybe it will make it a little easier to communicate and help.
TrueBlue_Drew said:
ok, I still dont believe its a brick. Are you running a rom at all? I mean does it boot into CM7 even though you dont have Gapps? Or is it totaly stuck on bootloop all the time.
Click to expand...
Click to collapse
It boots right up in CM7, if I'd added the Gapps at the beginning I'd just be running it happily I think? I'd be able to sync and get needed apps from the market, etc. etc.
I am going to send you a PM with my Gtalk. Add me if you want and maybe it will make it a little easier to communicate and help.
Click to expand...
Click to collapse
Thanks, I'd really prefer to do it this way. Why? Because I'm really sick of messing with it and I hate to spend much time working on it now, I've resigned myself to having a very costly paperweight! Using the thread here allows me to check in once or twice a day when the urge strikes, besides, I really don't IM, never have, never could figure it out. I don't text either, it's blocked at T-Mo's website and on my phones as well. I'm not really a technophobe but I'm 99.2 % one.....
That's fine. I was just trying to maybe make it a little easier in ya.
If you can install a .apk I can send you the market and a few things. We can try to get a few things going that way if you want. If we can get the market going you can get gmail and every thing else from there. will attach the market and tell you how to install if you want
Sent from my HTC Glacier
If he's still s=on, he's not going to be able to flash recovery. You need to get s=off.
Grab the .apk for Visionary. Grab gfree. Grab an apk for a terminal emulator if you don't have one. Put them all on your sdcard, boot into CM7, and follow the instructions for the gfree method here:
http://forum.xda-developers.com/showthread.php?t=858996
If you don't have a file manager to get to them, you could try SMS'ing the download links to the phone and installing through the browser for the .apk's.
TrueBlue_Drew said:
That's fine. I was just trying to maybe make it a little easier in ya.
If you can install a .apk I can send you the market and a few things. We can try to get a few things going that way if you want. If we can get the market going you can get gmail and every thing else from there. will attach the market and tell you how to install if you want
Sent from my HTC Glacier
Click to expand...
Click to collapse
I can't install an APK. I got all the Google apps and put them on the SD card, if I click on one I get "couldn't parse the file" what ever that means?
Actuall, it did install the Market apk but it won't open.....
Related
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
Can't remove clockwork mod after factory reset complete with .340 back. I have tried everything. I have read that I could remove 2 files in root exployer but am lost as to how to complete. Phone never been flashed. Just rooted with clockword Mod and rooted with Z4root. Please Help
Not too sure why you want to remove it. If you want to get rid of root and clockwork then use the SBF.
Sent from my DROIDX using XDA App
I still have a hard time understanding how people really think that doing a factory reset magically flashes the stock OS back. All it does it erase user data and apps. Use the root explorer method or sbf.
I have unrooted and have factory .340 but can't get rid of boot to clockwork mod. I have read sbf will not remove it, so I havent done it. i never flashed a rom, was just curious and wanted to learn. Just need help getting rid of clockwork mod at boot. I thought this was a place for help not downgrading people
mikeyt114 said:
I have unrooted and have factory .340 but can't get rid of boot to clockwork mod. I have read sbf will not remove it, so I havent done it. i never flashed a rom, was just curious and wanted to learn. Just need help getting rid of clockwork mod at boot. I thought this was a place for help not downgrading people
Click to expand...
Click to collapse
This is the place for learning however there is a little doing on your part.
You want to learn but yet you wish to delete a primary tool to flash a Rom.
Your statements are contradictory in meaning.
Now with that said.
check out this site also for flashing info and Rom's
http://www.mydroidworld.com/forums/droid-x-discussion/
You are heading in the correct direction don't get discouraged there's a lot to learn.
kdkinc said:
This is the place for learning however there is a little doing on your part.
You want to learn but yet you wish to delete a primary tool to flash a Rom.
Your statements are contradictory in meaning.
Now with that said.
check out this site also for flashing info and Rom's
http://www.mydroidworld.com/forums/droid-x-discussion/
You are heading in the correct direction don't get discouraged there's a lot to learn.
Click to expand...
Click to collapse
so I am banned from xda? I made a statment that is the way I felt and I dont know who you are but you must be a boss of somesort, don really know the chain of command, and I get a message from you I guess because I said he was degrading. In your read this first, your statmemt is to help noob's and be kind. If you will show me a kind word in his reply I will appoligize to him at once. So I guess I just need to know if you have banned me or what for just trying to get help.
After you SBF, do a factory reset using Motorola's recovery. When the phone boots back up, you will be unrooted and without Clockwork.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
Thank you, could I be stupid as to ask for a link on how to do the SBF you are talking about. Sorry, I am just so comfused right now. I would really appreceiate as i have been make to look like a total idoit already. Thanks if you want to. no problem if not. Mike
There are no stupid questions.
Here is the guide I followed to SBF my phone. http://www.droidforums.net/forum/droid-x-hacks/68222-unbricking-your-droid-x.html. Depending on which OTA version your phone is on, you may need to track down the 2.3.15 Full SBF, or if on a newer version, you will need to get the 2.13.32 Full SBF and the 2.13.40 System-Only SBF. 2.13.40 is the latest OTA from Verizon.
After you follow the steps outlined about, your phone will have a mish-mash of Official OTA and whatever custom ROM you may have had. Power the phone off, and then hold the Home key while powering it back on. Release Power, but keep holding Home until you see a screen with a folder icon with a "!". Release Home, press Search, and then select Factory Reset. Once it completes, reboot the phone. The first boot will take 5-7 minutes of staring at the animated Motorola splash, and you will have a complete, non-rooted, stock ROM without Clockwork.
Hope this helps.
NotATreoFan said:
There are no stupid questions.
Here is the guide I followed to SBF my phone. http://www.droidforums.net/forum/droid-x-hacks/68222-unbricking-your-droid-x.html. Depending on which OTA version your phone is on, you may need to track down the 2.3.15 Full SBF, or if on a newer version, you will need to get the 2.13.32 Full SBF and the 2.13.40 System-Only SBF. 2.13.40 is the latest OTA from Verizon.
After you follow the steps outlined about, your phone will have a mish-mash of Official OTA and whatever custom ROM you may have had. Power the phone off, and then hold the Home key while powering it back on. Release Power, but keep holding Home until you see a screen with a folder icon with a "!". Release Home, press Search, and then select Factory Reset. Once it completes, reboot the phone. The first boot will take 5-7 minutes of staring at the animated Motorola splash, and you will have a complete, non-rooted, stock ROM without Clockwork.
Hope this helps.
Click to expand...
Click to collapse
the problem he is having is that he DID the sbf completely and thats all and EVERY time he reboots it first boots into clockworkmod recovery without installing clockworkmod recovery
Well....you're in a pickle...wish I had the 2.3.340 sbf...I'll take 5 copies when it's out
Sent from my DROIDX using XDA App
Funnyface19 said:
the problem he is having is that he DID the sbf completely and thats all and EVERY time he reboots it first boots into clockworkmod recovery without installing clockworkmod recovery
Click to expand...
Click to collapse
If the SBF completes successfully, a factory reset from the Motorola recovery menu (can only be accessed using the key combo I mentioned earlier) will completely remove Clockwork. If Clockwork still boots, the restore was not done correctly.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
I did it today its fine
Sent from my DROIDX using XDA App
For anyone who might want to remove the bootstrap recovery, outside of having to reload an SBF, the instructions below are what I used to remove Clockwork from my DX. (I was tired of it always booting into Clockwork when I powered my device off and on. I found this in another forum, which references a couple of other forums below.
Removing Bootstrap Recovery:
Removal from an Androidforums post:
UNINSTALL the Recovery APK (Droid X Bootstrapper) in Settings, Applications
Reboot
Run "adb shell"
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
or
1. Reroot
2. Get root explorer in the market
3. Uninstall the bootstrap app
4. Go into root explorer to system/bin
5. In top right corner tap r/w
6. Delete the file called hijack
7. Delete logwrapper
8. Rename logwrapper.bin to just logwrapper
9. Reboot and it should be gone.
(thanks to Droidforums member Hostility6)
The commands can be used with terminal emulator do all the commands except for the first command. (Run adb shell)
are you turning your phone on while holding volume down ...if so that is why its booting into clockwork mod...but in all fairness you were contradicting yourself.... and I am a noob as well and having issues with the clockwork 3.0 but I have given up because i cant downgrade without errors and there are no answers on these forums about its solution so i will wait it out... uninstall clockwork will also not get you stock and I cant understand why the phone is booting into clockwork recovery and not the OS.. or did I misread and misunderstand your original question...
Ok, I know I am a noob to android phones and to this forum, but I already spent many hours online researching the problem and didn't find anything that helped.
So, here's what happened:
I got my MyTouch 4G about 2 weeks ago unlocked. I wanted to get rid of a lot of the garbage that came with it, so I followed the steps and successfully rooted it and then removed several of the preinstalled apps with Titanium backup. So far, no noticeable problems.
Then I wasn't happy with how quickly my battery was draining, so I installed Advanced Task Killer, and set it to automatically kill certain apps periodically.
A few days later when I was trying to add a widget to the desktop, I got the familiar to some message "Sorry, com.htc.launcher has stopped working". Everything else was still working fine on the phone. I researched the problem and the first proposed solution to clear the data for the process from Settings/Applications, did not help. The second proposed solution was to do a factory reset. So, I rebooted with volume down + power pressed together and chose factory reset.
After 4-5 min, I got into the welcome screen where I did the initial setup. After this was complete, the phone checked off that everything was setup correctly (apps, widgets, etc). Then it started loading the desktop and the message "loading..." appeared. This is where it froze.
Basically, I can't get past the "loading..." message on the home screen, no desktop ever loads, and I have access to nothing other than the camera key.
I let it stay for hours to see if it will eventuall load, but nothing happened. I also rebooted and tried factory reset many times and it always get stuck at the same point. I tried all of the above with and without a SIM card, with and without a memory card - basically I exhausted all possible combinations but I always get the same frozen "loading..." screen.
Has anyone experienced this problem? I feel helpless rebooting or reseting the phone from the phone itself because it always get stuck. Is there a way to factory reset from a computer?
Thank you so much if you can help me with any advice and Happy New Year!
Vess
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
esincho said:
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
Click to expand...
Click to collapse
Hi, thank you for your message. I think you are correct about deleting the launcher and factory reset not fixing it.
But I don't know how to do "nandroid backup, flash iced glacier rom". Could you point me to instructions on that? Sorry, I'm really new to android phones.
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
esincho said:
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
Click to expand...
Click to collapse
I did what you suggested but from what I understand to flash a rom I need to be able to boot into Recovery mode, which I can't do either. Every time I choose Recovery I get the "!" screen and I'm stuck. Am I doing something wrong?
Thank you.
vess22 said:
so I followed the steps and successfully rooted it
Click to expand...
Click to collapse
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
shlongwoodian said:
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
Click to expand...
Click to collapse
No sir, I didn't do any of the above unfortunately. From what I understand had I done that, I wouldn't have a problem booting into Recovery mode, correct?
I believe you might still be able to get to what you need via adb. That's not my specialty though, even though I can mash out a few commands and comprehend what I'm doing. It would be remiss of me to guide you any further, but I don't think all hope is lost for you. Search the forums for 'adb' and 'recovery' and let's also see who replies back with some better advice.
Find the raw .img of cw recovery then adb flash_recovery /location/of/recovery.img
If that doesn't work you'll need to use fastboot assuming you updated to eng spl.
Sent from my HTC Glacier using XDA App
sounds like your boot.img is borked.... try flashing one of the many available kernels (make sure it will work with your rom first... if you haven't flashed a rom or flashed a sense based rom then use an HTC kernel if you're running CM or MIUI use a CM based kernel) and then when you get it running read this and understand why task killers are bad FAQ: You shouldn't be using a task killer with Android
Yes, I'm starting to realize that now my only option is to do flash recovery through adb. So, I've spent all night last night trying to understand what adb is. I installed and updated the sdk, but my adb shell doesn't see my phone as a listed device, so I'm stuck at this point. And yes, I read probably 5 tutorials on installing various usb drivers/ modifying sdk ini files/etc to make your computer recognize the phone as an adb device. I tried everything that was suggested but no luck so far.
I've spent nearly 30 hours so far since this whole disaster started and although I haven't made much progress, I've learned quite a few things.
And, no, I won't mess with Advanced Task Killer or Titanium Backup any more, just give me my phone back and working
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
ESKIMOn00b said:
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
vess22 said:
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
Click to expand...
Click to collapse
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Phateless said:
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Click to expand...
Click to collapse
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
vess22 said:
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
Click to expand...
Click to collapse
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Phateless said:
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Click to expand...
Click to collapse
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
vess22 said:
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
Click to expand...
Click to collapse
You make an appealing case for Iced Glacier.
Stock tends to be the most stable and reliable, plus you get OTA updates. Other than that, not much reason. I can tell you from recent experience that my phone gets a gps lock much quicker with stock than with cm6, but I'll do further testing to see if that's really the case.
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
GLACIER PVT SHIP S-ON
HBOOT 0.86.0000
MICROP-0429
RADIO 26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Click to expand...
Click to collapse
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
sending 'recovery' (8701 KB)... OKAY [471.891s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 473.125s
Click to expand...
Click to collapse
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
RedDonkey said:
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
Click to expand...
Click to collapse
The instructions above only pertain to a rooted phone. Your phone is not rooted and you dont have eng bootloader. Without superuser access you cant even flash recovery like you were trying. A factory reset didnt fix your problem?
Side note, im an opponent of doing the whole temp rooting only thing cause if you screw something up you dont have access to tools to fix anything, your just screwed if something happens like this.
I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!
Try reflashing your recovery image.
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/
Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
ok thanks, i'll try it when I get back home
jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.
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.