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).
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 cannot upgrade to a newer version of Clockworkmod recovery !
I have tried everything, fastboot flash returns failed signature verification, rom manger also cannot update to a newer version.
Also tried Unrevoked but it fails.
the phone is rooted and I have flashed several ROMs in the past without any problem.
Any idea?
Fastboot flash doesn't return verification failed error.
You need to be s-off to change recover using fastboot. Before you do anything, read some tutorials, you need to differentiate among most basic terms.
Sent from my HTC Desire using Tapatalk
erklat said:
Fastboot flash doesn't return verification failed error.
Click to expand...
Click to collapse
It can do if you try to fastboot flash connected in hboot or are s-on
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I get this error from fastboot
< waiting for device >
sending 'recovery' (3256 KB)... OKAY [ 0.468s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.952s
I have tried to flash clockworkmod 5 and also tried the touch version, but with no luck.
Maybe the S-OFF is messed up, but only if rom manager did something wrong, because last time when I have upgraded the recovery it was from ROM Manager.
Fail on my part...
That seems like there is no device tho. My money is on broken drivers. There is a guide how to do in development so search for it as it works 100%.
unrevoked connects to phone, sends the file to phone then at the end it fails.
I have tried revolutionary for S-OFF the program connects to phone then displays the phone serial number, asks for the key then after I enter the key, the connection is lost.
So I really don't know what to do anymore, and I need a newer recovery since the one which I have does not have options to partition the SD Card and ICS is eating a lot of memory without SDExt.
The phone is ok, it's not broken, I flash every 2-3 days a newer ICS ROM and it works.
why dont you try a different recovery.i have been using ext4 recovery for a while and imo it is way better than cwm....
I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7
evolution_x said:
I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7
Click to expand...
Click to collapse
Because all you are doing is a fake flash. You need to flash it from fastboot in order to stick.
Ditch the Rom manager. That pos app is guilty of more usb bricks than most of us can count.
And how can I flash it from HBOOT ?
evolution_x said:
And how can I flash it from HBOOT ?
Click to expand...
Click to collapse
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.
erklat said:
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.
Click to expand...
Click to collapse
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?
KitkatKlub said:
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?
Click to expand...
Click to collapse
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.
stankyou said:
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.
Click to expand...
Click to collapse
Hey thanks sthankyou.
This is what i get on fastboot:
sending recovery...
OKAY
writing recovery
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.054s
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
I have also tried this flashing using the terminal, Which I found in the Q&A's but i get several error messages, and then finally:
"error writing recovery: No space left on device"
So I uninstalled a couple of apps (freeing some 10mb+) but still the same issue.
As you are not s-off you can't flash recovery, get s-off and flash any you like
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
KitkatKlub said:
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
Click to expand...
Click to collapse
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
KitkatKlub said:
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
Click to expand...
Click to collapse
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk
erklat said:
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!
KitkatKlub said:
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!
Click to expand...
Click to collapse
theresa way to downgrade. check resources on my guide.
i had the same problem. s-off solved everything.
i had problems with s-off. i had ISC 4.0.3. and i couldn't get it to s-off and i installed some stable rom. cant remember which one, but i'm sure it was on of stable ones. and then tried to s-off again and it was over in few minutes.
and then i flashed recovery with adb
Hey guys....
So my Droid Inc got bricked. A evil brick though. Funny thing is it got bricked before i ever rooted or messed with it in anyway. It just bootloops forever. Ive tried
1. RUU
2. PB...IMG....Many of them
They flash successfully, but same bootloop.
So i took it a step further
1. HTC Dev Unlocked (idk if their unlocking can be considered as legit, but anyway...) from fastboot (only way to unlock bootloader from fastboot i guess, or else i would of tried unrevoked...)
2. Then flashed clockwork from fastboot.
3. Wiped absolutely everything multiple times from recovery
4. Flashed CM7 in recovery....same bootloop
another step further
1. Put recovery.img in adb folder and and tried to "fastboot boot recovery.img" and flash CM7 like that (because If im not wrong htc dev unlock restricts kernel flashing but this circumvents it, or does it...)
2. After yet another bootloop, tried fixing permissions, reflashing CM7 again, then fixing permissions again
Nothing . Sometimes ittl bootloop the CM7 boot animation, sometimes ittl get stuck at HTC Incredible screen forever. Tried another stock rom also...
Any ideas lolll?
Ruu
Fastboot flash recovery
Flash su binary thru recovery
See if you can boot.
If you can boot download and install busybox
Wipe and flash a rom
I think the issue may be your not installing su before flashing a rom, or will it not boot on stock either? Idk just throwin stuff out there. Sounds like you have done everything right so far
cmlusco said:
Ruu
Fastboot flash recovery
Flash su binary thru recovery
See if you can boot.
If you can boot download and install busybox
Wipe and flash a rom
I think the issue may be your not installing su before flashing a rom, or will it not boot on stock either? Idk just throwin stuff out there. Sounds like you have done everything right so far
Click to expand...
Click to collapse
hmm. To be honest I doubt ittl work but I'll try it soon. I'll write results...
EDIT:nope....
Sent from my GSM Galaxy Nexus using XDA Premium!
Is there an SD card in the phone? You know, in case you were just storing everything on the internal storage.
Anyway, I think some ROMs interact with the SD card on bootup, and that can cause some issues. Try reformatting the card and see if it makes a difference.
Just a shot in the dark here but its a distinct possibility you're not bricked at all but you have a hardware failure.I had this same issue on not one but two separate Incredibles and come to find out it was simple hardware failure.I went so crazy trying to figure it out after I thought I had bricked the second one that I paid a family friend who is actually an engineer for htc to look at them.I shipped them to him and after a few days the answer came through.Hardware failure.I thought one maybe but two hardware failures?And it was.Processor failed on both of em.
Sent from my SCH-I500 using xda premium
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
I tried installing a custom rom today and I think I messed up really bad, because my phone does not get pass the boot screen and I cannot enter the recovery setting. I think I messed up after entering
fastboot flash boot boot.img
in the command prompt and restarting because I forgot to put the rom zip on my phone. Since then I could not get pass the boot screen and even tried running a backup using CWM, but it didn't help. I then managed to mount my phone and put the rom onto it and installed it, but again it didn't help.
Now my phone can only enter the bootloader, I select hboot and fastboot, but nothing else works. Everytime I select recovery or factory reset I get the htc boot screen and it gets stuck. Does anyone have any solutions?
Thanks
did u backup your phone rom???
if you did u can go to recovery and restore it
and never try to change rom again trust me in that
otherwise i can't help bcuz i did the same mistake
I did make a backup, but like I said I can't enter recovery anymore, so I can't load the backup.
Thanks for trying to help anyway though.
fastboot erase cache
Often fixes recovery problems.
BenPope said:
fastboot erase cache
Often fixes recovery problems.
Click to expand...
Click to collapse
Still not working, thanks anyway.
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
BlueSingA said:
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
Click to expand...
Click to collapse
I have hboot 1.39.0000 and I was trying to install the latest cyanogenmod cm-10-20130106-NIGHTLY-endeavoru.
Yeah I realized this after I restarted and did it get the zip onto the phone. I think I installed it, but the phone is still stuck on the boot screen
UPDATE: Okay I've managed to install CWM recovery, so I think I'm making progress
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
BlueSingA said:
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
Click to expand...
Click to collapse
Yeah CWM didn't load up, but I got it working again. Well it seems I'm back to getting the rom to install and being stuck at the boot screen again, so maybe I just need to use a different rom. Thanks for the help though
Okay, I've tried installing a few roms, but unfortunately I'm still on the boot screen, I can sometimes even reach the cyanogenmod boot screen, but get stuck there. I've read that this might be kernel issue, does anyone have any ideas?
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are a goddamn hero! Thanks, this solved everything.
No problem!
Sent from my EndeavorU using xda app-developers app