Related
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?
sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo
Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help
erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X
encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?
Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what
Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?
oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!
whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.
HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App
I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App
Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App
Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!
I was attempting to install Cyanogen Mod 9 RC2 on my HTC G2 (Vision - Tmobile Branded) and before I did, I decided to flash a "new" recovery from clockwork. I broke my own rule and used Rom Manager and it seems like the recovery partition is now completely screwed up. Either that or my system is now read only.
I am able to access recovery, bootloader, and even the OS (can still make calls) but if I uninstall an application it will come back on the next boot up such as facebook or even the rom manager. I tried to load PC10IMG from the bootloader, but it only finishes the radio_v2 then it reboots and gets caught in a boot loop. If I go back to try again, it starts over as if no changes were made. Worse still, I've gone as far as to erase the recovery partition only to have it come right back.
I am still showing as S-OFF, but I can't seem to get any changes to stick and I'm not getting any error messages ever. Infact, clockworkmod seems all to eager to say "Install success" when I try to flash another rom or wipe cache & data. Has anyone else been experiencing this issue?
ROM: CM 7.1
Recovery: 5.0.2.7 CWM
I've been at this for a day now and I"m fed up with it, any insight would be a huge help.
ark3typ3 said:
I was attempting to install Cyanogen Mod 9 RC2 on my HTC G2 (Vision - Tmobile Branded) and before I did, I decided to flash a "new" recovery from clockwork. I broke my own rule and used Rom Manager and it seems like the recovery partition is now completely screwed up. Either that or my system is now read only.
I am able to access recovery, bootloader, and even the OS (can still make calls) but if I uninstall an application it will come back on the next boot up such as facebook or even the rom manager. I tried to load PC10IMG from the bootloader, but it only finishes the radio_v2 then it reboots and gets caught in a boot loop. If I go back to try again, it starts over as if no changes were made. Worse still, I've gone as far as to erase the recovery partition only to have it come right back.
I am still showing as S-OFF, but I can't seem to get any changes to stick and I'm not getting any error messages ever. Infact, clockworkmod seems all to eager to say "Install success" when I try to flash another rom or wipe cache & data. Has anyone else been experiencing this issue?
ROM: CM 7.1
Recovery: 5.0.2.7 CWM
I've been at this for a day now and I"m fed up with it, any insight would be a huge help.
Click to expand...
Click to collapse
I would try to reflash recovery thru adb then download fresh rom to install. Not sure if there is any other troubleshooting you could do 1st though.
better yet how about dropping clockwork for 4ext, in mine and many others experience it is far superior on our g2s. and if you insist on clockwork, try to stay away from rom manager. don't flash a pc10img either, if you do the wrong one and there is a radio error you can easily brick your phone (many people with soff seem to think this is a good idea but it can be a terrible one)
then reflash a new rom, if you like cm7 I suggest elitemod cm7, but the choice is yours
never heared of these specific problems with all my years in android but I'm sure you will be happy with the changes I suggested and unless I'm missing something this should also fix your problems
Sent from my HTC Vision using xda premium
demkantor said:
better yet how about dropping clockwork for 4ext, in mine and many others experience it is far superior on our g2s. and if you insist on clockwork, try to stay away from rom manager. don't flash a pc10img either, if you do the wrong one and there is a radio error you can easily brick your phone (many people with soff seem to think this is a good idea but it can be a terrible one)
then reflash a new rom, if you like cm7 I suggest elitemod cm7, but the choice is yours
never heared of these specific problems with all my years in android but I'm sure you will be happy with the changes I suggested and unless I'm missing something this should also fix your problems
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Well you can't exactly flash 4EXT without first having the app to download and install it for you.
But here is the zip file for 4EXT Touch Recovery 1.0.0.5 RC5 specifically for the G2/DZ, which can be renamed to PC10IMG.zip and placed on the SD card to be flashed via fast boot (it contains ONLY the recovery, it won't flash over hboot, radio or any of that).
http://xlu.be/g2/4EXT_Recovery_Touch_v1.0.0.5_RC5.zip
Code:
MD5 (4EXT_Recovery_Touch_v1.0.0.5_RC5.zip) = dfc5dc1e4aee18fdea6268345e3dad22
I never did find a place 'online' to download the recovery images direct, only thru the app was I ever able to download it to my Zip card. (PS: I recommend getting the paid version of the Recovery control from the Google Play market place to support the developer, it'll also let you set options like not backing up the caches).
not @ a comp right now but you can get the image and flash through fastboot, I did this to try it out free, liked it so much right away so I purchased the app through the market just to support the dev. but either way, its all prefrence
Sent from my HTC Vision using xda premium
I tried to flash the recovery img that kbeezie gave me both through PC10IMG.zip (verified MD5) and again through fastboot flash with just the straight img from inside the zip. Neither method worked and now I'm caught in a boot loop until I pull the battery. I've even gone as far as to erase the recovery, do you think formatting the recovery and then flashing again would yield better results?
ark3typ3 said:
I tried to flash the recovery img that kbeezie gave me both through PC10IMG.zip (verified MD5) and again through fastboot flash with just the straight img from inside the zip. Neither method worked and now I'm caught in a boot loop until I pull the battery. I've even gone as far as to erase the recovery, do you think formatting the recovery and then flashing again would yield better results?
Click to expand...
Click to collapse
A boot loop trying to boot normally? or trying to boot into recovery. If you haven't flashed a ROM yet, then naturally you would need to go into the Recovery to do so first.
Are you aware of how to get into Recovery?
PS: NEVER NEVER NEVER NEVER NEVER 'erase' the recovery, you should always have a recovery on there, if you can't get anything going with fast boot then you're probably going to be screwed. Furthermore how did you even 'erase' it ?
You should be able to simply flash the recovery, reboot, hold volume down + power to get into recovery, do a factory reset/wipe, and flash a new rom form SD card.
Play it safe and provide A LOT more information in your next reply.
1) What's your hboot info (the whole boot loader screen, including radio version).
2) What did you do exactly?
---------- Post added at 07:38 PM ---------- Previous post was at 07:29 PM ----------
By the way you might want to hop onto #G2Root on FreeNode IRC for some live assistance, you seem to be doing a lot of unnecessary and potentially bricking stuff with way you're just 'trying everything'.
kbeezie said:
A boot loop trying to boot normally? or trying to boot into recovery. If you haven't flashed a ROM yet, then naturally you would need to go into the Recovery to do so first.
Are you aware of how to get into Recovery?
PS: NEVER NEVER NEVER NEVER NEVER 'erase' the recovery, you should always have a recovery on there, if you can't get anything going with fast boot then you're probably going to be screwed. Furthermore how did you even 'erase' it ?
You should be able to simply flash the recovery, reboot, hold volume down + power to get into recovery, do a factory reset/wipe, and flash a new rom form SD card.
Play it safe and provide A LOT more information in your next reply.
1) What's your hboot info (the whole boot loader screen, including radio version).
2) What did you do exactly?
---------- Post added at 07:38 PM ---------- Previous post was at 07:29 PM ----------
By the way you might want to hop onto #G2Root on FreeNode IRC for some live assistance, you seem to be doing a lot of unnecessary and potentially bricking stuff with way you're just 'trying everything'.
Click to expand...
Click to collapse
A boot loop trying to boot into recovery. I can still pull out the battery for a few seconds and boot into normal.
----------------------------------------------------
HBOOT INFO
----------------------------------------------------
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.06.02.27_M
eMMC-boot
Aug 20 2010, 16:51:01
----------------------------------------------------
I should also mention that I've been doing this for a while, but this is the first time I haven't been able to just flash a new recovery or rom...it's vexing. I'm aware that what I'm doing is risky and I'm being careful to check steps and MD5s the whole way with a couple of chances taken where appropriate.
ark3typ3 said:
A boot loop trying to boot into recovery. I can still pull out the battery for a few seconds and boot into normal.
Click to expand...
Click to collapse
If you can boot into normal, and you are rooted then try installing a new recovery via either rom manager (if you want clockworkmod) or 4EXT recovery control (which I prefer, note my signature) then reboot into recovery.
Sent from my T-Mobile G2
kbeezie said:
If you can boot into normal, and you are rooted then try installing a new recovery via either rom manager (if you want clockworkmod) or 4EXT recovery control (which I prefer, note my signature) then reboot into recovery.
Sent from my T-Mobile G2
Click to expand...
Click to collapse
I would gladly do that, and believe me I've tried, but it's not working. If I go into Rom Manager and attempt to flash the clockwork recovery it will "succeed" and then do nothing, or it will fail but still act like it succeeded and provide me with a blank confirmation window with a yes button and a no button. 4EXT didn't work either though it definitely looked interesting....
ark3typ3 said:
I would gladly do that, and believe me I've tried, but it's not working. If I go into Rom Manager and attempt to flash the clockwork recovery it will "succeed" and then do nothing, or it will fail but still act like it succeeded and provide me with a blank confirmation window with a yes button and a no button. 4EXT didn't work either though it definitely looked interesting....
Click to expand...
Click to collapse
List out your exact phone specs and included software:
Phone Information
example:
T-Mobile (Carrier)
G2 (or in your case may be HTC Desire-Z)
HBoot information
Example of Mine:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Sep 8 2012,15:56:38
Rom
Examples:
Cyanogenmod 7
"Stock" (i.e.: same one phone came with), and if Stock what software version?
Methods
What exact methods were used to unlock/root/etc the phone?
Fastboot is the safest method for flashing recoveries (or radio or spls) how did you go about it with fastboot? When in fastboot mode type
fastboot devices
If you see yours continue
fastboot flash recovery recovery.img
fastboot reboot bootloader
Of course you have to point fastboot to the place the recovery image is, and either name it recovery.img or change the command
When you do this do you get an error or is all seemingly well until you try and boot into recovery?
Sent from my GT-I9100 using xda premium
demkantor said:
Fastboot is the safest method for flashing recoveries (or radio or spls) how did you go about it with fastboot? When in fastboot mode type
fastboot devices
If you see yours continue
fastboot flash recovery recovery.img
fastboot reboot bootloader
Of course you have to point fastboot to the place the recovery image is, and either name it recovery.img or change the command
When you do this do you get an error or is all seemingly well until you try and boot into recovery?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
All is seemingly well, it just won't allow any other recoveries but CWM. If I put CWM (5.0.2.7) on it gives me recovery back but when I try to flash a different rom it just stays at Cyanogen 7.1 (Even though it says it succeeded). Trying the 4EXT recovery got rid of CWM, but I can't boot it because it gets stuck in a boot loop until I pull the battery to clear the recovery flag.
I used the exact commands you described and it says it succeeds...
ark3typ3 said:
All is seemingly well, it just won't allow any other recoveries but CWM. If I put CWM (5.0.2.7) on it gives me recovery back but when I try to flash a different rom it just stays at Cyanogen 7.1 (Even though it says it succeeded). Trying the 4EXT recovery got rid of CWM, but I can't boot it because it gets stuck in a boot loop until I pull the battery to clear the recovery flag.
I used the exact commands you described and it says it succeeds...
Click to expand...
Click to collapse
Did you make sure to do a Factory Reset and Wipe (within the Recovery) before applying Cyanogenmod or a different recovery? (flashing a recovery without first wiping will of course sort of 'mix' up whatever you had on there plus new stuff, and as such would break it).
wiping from within recovery will not wipe recovery, the only way to "wipe" recovery is to erase recovery, which isn't a good idea. if you want to ever change recoveries just flash the new one over the old, there will not be a conflict.
as to your continued problem I suggest logging on to freenode #g2root, if there is a chance to fix your phone you'll have the best luck there as testing can be done in real time
Sent from my HTC Vision using xda premium
kbeezie said:
Did you make sure to do a Factory Reset and Wipe (within the Recovery) before applying Cyanogenmod or a different recovery? (flashing a recovery without first wiping will of course sort of 'mix' up whatever you had on there plus new stuff, and as such would break it).
Click to expand...
Click to collapse
Yes I did wipe, I also have tried CM7.2, CM9 RC1 (Build 2), and CM7.1 (current) and they all have the same result. They succeed installation, then they get stuck in a boot loop, then if I pull the battery, it boots up fine with all my settings as if I had never done any of it.
I'm looking for a brute force way to wipe the OS and start completely fresh without harming fastboot or recovery. I'm leaning towards it being a hardware issue, but the issue is a bit confusing because everything is succeeded and I'd have expected an error message of some kind...
demkantor said:
wiping from within recovery will not wipe recovery, the only way to "wipe" recovery is to erase recovery, which isn't a good idea. if you want to ever change recoveries just flash the new one over the old, there will not be a conflict.
as to your continued problem I suggest logging on to freenode #g2root, if there is a chance to fix your phone you'll have the best luck there as testing can be done in real time
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I have gone to the IRC...no answered me.
well of course people aren't always avalible to chat on freenode, try hopping on after work hours, of course this varries depends where you live. I find there are many people around about 6-11pm central time
as for wiping, the cleanest wipe is fastboot -w
your issue is very strange to me and I feel you have a curropt recovery, I would attempt flashing a new one but without your phone in front of me it is hard to troubleshoot these rare problems over xda
try freenode again, good luck!
Sent from my HTC Vision using xda premium
demkantor said:
well of course people aren't always avalible to chat on freenode, try hopping on after work hours, of course this varries depends where you live. I find there are many people around about 6-11pm central time
as for wiping, the cleanest wipe is fastboot -w
your issue is very strange to me and I feel you have a curropt recovery, I would attempt flashing a new one but without your phone in front of me it is hard to troubleshoot these rare problems over xda
try freenode again, good luck!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I agree, I'll try again later but this is the stuff I got when I ran fastboot -w
Code:
erasing 'userdata'...
OKAY [ 0.410s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.010s]
erasing 'cache'...
OKAY [ 0.229s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.009s]
finished. total time: 0.663s
Not sure if that's important, but the Can't determine partition type seems suspicious to me.
ark3typ3 said:
Not sure if that's important, but the Can't determine partition type seems suspicious to me.
Click to expand...
Click to collapse
Probably because when you wiped it previously, it was not "automatically formatted" as such has no partitions (or not formatted).
I've been happily running CM7 for the past year and yesterday while I was browsing the phone suddenly turned off and starts bootlooping, I then tried to get into recovery to flash one of my backups but I couldn't get into recovery anymore. I can get into the bootloader (vol down, back and power key) but if I select recovery from the menu it starts bootlooping again. I was hoping someone knows what's going on.
I used revolutionary to root the phone, had clockworkmod recovery installed (don't think it was the latest version, haven't updated it since I've installed it a year ago) and was running CM7.2 (latests stable version).
I also apologise in advance because you guys must be sick of people asking what to do with a 'bricked' phone but I'm still hoping someone can help me.
You have the explanation how it all works in my signature.
Just flash recovery.img via fastboot.
Sent from my HTC Desire using Flashes and Thunders
nlooooo said:
You have the explanation how it all works in my signature.
Just flash recovery.img via fastboot.
Sent from my HTC Desire using Flashes and Thunders
Click to expand...
Click to collapse
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.
the catfishman said:
Thanks for the post, I'm guessing you mean the third link? running the RUU? in that thread there is a link 'http://htcdev.com/' but that link is dead.. so I can't get it there but I will google around to see if it's somewhere else.
Click to expand...
Click to collapse
Not sure what link you said is dead, they all work. I meant on this one "Before Crying for Bricked Device - How Nexus One and HTC Work ".
All you need is recovery.img download it from here:
http://www.clockworkmod.com/rommanager/
and flash it via fastboot.
Both your ROM and recovery are bootlooping. But importantly your bootloader is fine and therefore you can easily recover. First get your recovery in order by flashing recovery from fastboot. Thereafter when you are able to get into recovery flash your ROM in the normal manner or restore your nandroid.
Thank you both! I flashed the recovery.img and could get into the recovery mode again! it's restoring my last back up as we speak, so hopefully it's working again.
If it all work go here:
www.4ext.net
and get rid of that buggy cwm recovery.
Well.. today it started bootlooping again in the same way as described in the first post and now the method I used yesterday to fix it doesn't work anymore. If I flash a new recovery.img now and subsequently try to go into the recovery mode it starts bootlooping again... so now I'm wondering if I should just flash the RUU via pc to at least get my phone working again... do you guys think that would work?
edit: can I even run the RUU in fastboot usb?
RUU is the solution if all else fails. But only use 2.3 Android RUU. And remember to downgrade hboot first.
Before you get into that I would try :-
- Flash a different recovery and try to get into recovery. But this time dont restore your nandroid. Flash a ROM afresh.
- Remove your sdcard and try to get into recovery. Wild guess !
- Also try formatting your system, sdext etc partitions as given in Bortaks thread.
I tried flashing a different recovery (amon ra) but that also didn't work, when I tried to get into recovery mode it got stuck on the HTC boot screen (with some weird extra lines through the image).
I will try to remove the sd card.
Another weird observation, the phone doesn't seem to be charging anymore, at least... the led doesn't turn on when it's plugged in.. it get's weirder and weirder.
like handy says full wipe, wipe/factory reset, wipe dalvik and format all partitions except sdcard then do a clean install of a different rom. restoring the nandroid, u could just be restoring the problem.
edit: just read ur post bout charging, looks like HW not rom or recovery problems
Sent from my HTC Desire
yeah but the weird thing is that this started this morning, I charged it last night (when all of this stuff was already happening).
Run 2.3 ruu as fast as you can, you're on a good way to hboot or radio brick.
:banghead: constuction material guaranteed...
Sent from my HTC Desire using Flashes and Thunders
Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.
the catfishman said:
Well.. the RUU worked, I'm back on sense (ugh).. but at least it's working again.
Click to expand...
Click to collapse
You can easily go s-off and root now just go here:
www.revolutionary.io
And the rest is history...
Sent from my HTC Desire using Flashes and Thunders
yeah, I will probably do that in a few weeks, I just moved to another country 2 days ago so I kinda need a functional phone these weeks... aand.. thanks for the help guys
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I know it's OneX forum, but maybe someone experienced this problem and devices are similar.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
EDIT:
A tried ADB sideload today, but after the file is sideloaded it can't be flashed - TWRP considers it corrupted and it vanishes after rebooting - AS EVERY CHANGE
I hope I didn't ruined my phone the first hour I got it, and XDA members could still help me. PLEASE
Tried flash a custom Rom..?
Sent from my HTC One X using xda app-developers app
Thanks for reply.
I did try, but I am unable to copy zip to device memory. Adb sideload didn't work either. File was copied but flash reported it as corrupted. I tried couple of times with few custom roms
7virage7 said:
Thanks for reply.
I did try, but I am unable to copy zip to device memory. Adb sideload didn't work either. File was copied but flash reported it as corrupted. I tried couple of times with few custom roms
Click to expand...
Click to collapse
and you can not mount usb in recovery..?
mmhh..as i read you are no beginner...so mmhhh...
if you can not flash original recovery and boot and than relock bootloader to flash firmware again...i also did not know
Alex-V said:
and you can not mount usb in recovery..?
mmhh..as i read you are no beginner...so mmhhh...
if you can not flash original recovery and boot and than relock bootloader to flash firmware again...i also did not know
Click to expand...
Click to collapse
TWRP for OneX+ does not allow to mount usb, or al least I can't find that option.
It seems it's kind of emmc chip failure, but unfortunatelly i can't relock bootloader so HTC warranty service probably wouldn't fix it
7virage7 said:
TWRP for OneX+ does not allow to mount usb, or al least I can't find that option.
It seems it's kind of emmc chip failure, but unfortunatelly i can't relock bootloader so HTC warranty service probably wouldn't fix it
Click to expand...
Click to collapse
And cwm..not tried or will not flash
Sent from my HTC One X using xda app-developers app
Alex-V said:
And cwm..not tried or will not flash
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I tried CWM from XDA (coz there is no official CWM for OneX+), it flashed (as reported by fastboot), but after reboot I still had my old TWRP.
7virage7 said:
I tried CWM from XDA (coz there is no official CWM for OneX+), it flashed (as reported by fastboot), but after reboot I still had my old TWRP.
Click to expand...
Click to collapse
It SOUNDS like your phone has gone read-only...I know it's happened to some people when flashing certain kernels, happened with one of Trip's a while back.
I have no idea what to do about it, if anything.
Tigerlight said:
It SOUNDS like your phone has gone read-only...I know it's happened to some people when flashing certain kernels, happened with one of Trip's a while back.
I have no idea what to do about it, if anything.
Click to expand...
Click to collapse
Yeah, thats exactly what happened. Nothing seems to affect it's state. My phone trully is Read-Only
7virage7 said:
Yeah, thats exactly what happened. Nothing seems to affect it's state. My phone trully is Read-Only
Click to expand...
Click to collapse
I'm pretty sure your only recourse is HTC for repair.