Hey guys !
I tried AmonRA recovery a few days ago but I prefer Clockworkmod so I'd like to revert back to it (2.5.0.7 version). I made a few searchs and everyone says to use fastboot for that (fastboot flash recovery). So I installed the last AndroidSDK, ran fastboot command for flashing recovery BUT it says
Code:
FAILED (remote: signature verify fail)
So I'm asking : what did i miss ? I heard about SPL, what is that ?
I also tried the method of this link : http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/ but it says the cmd is not known.
Thanks !
shinodoigt said:
Hey guys !
I tried AmonRA recovery a few days ago but I prefer Clockworkmod so I'd like to revert back to it (2.5.0.7 version). I made a few searchs and everyone says to use fastboot for that (fastboot flash recovery). So I installed the last AndroidSDK, ran fastboot command for flashing recovery BUT it says
Code:
FAILED (remote: signature verify fail)
So I'm asking : what did i miss ? I heard about SPL, what is that ?
I also tried the method of this link : http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/ but it says the cmd is not known.
Thanks !
Click to expand...
Click to collapse
You can only use fastboot flash recovery if you have an "s-off" SPL (alpharev.shadowchild.nl), otherwise you have to use unrEVOked (http://unrevoked.com/#desire)
Yea, I just S-Offed my desire, it worked well. But I have tried to use unrevoked several times to revert back to clockwork from AmonRA, it failed every time on Windows & MacOS.
have you tried downloading Rom manager from Market and flash clockwork from there?
I tried yes but It didnt change anything to the recovery. Now i'm s-off, fastboot flash recovery worked, so I guess I'm done here, thanks for your help !
shinodoigt said:
I tried yes but It didnt change anything to the recovery. Now i'm s-off, fastboot flash recovery worked, so I guess I'm done here, thanks for your help !
Click to expand...
Click to collapse
Glad you got it sorted!
Hi all,
I'm sort of new to this. I've been using clockworkmod recover for a while now. Mostly to back up and restore. I want to try to load the stable CM7 rom or maybe some other rom that supports A2sd+ but I saw that at least CM7 recommends a newer version of ClockworkMod Recovery.
Right now I have 2.5.0.9. It's also the one that shows up in Rom Manager.
But I've seen here and other forums that people are now unto 3.0.0.5 and even beyond (I saw 3.0.2.4 on the CM forum)
So my question is what is the latest version of ClorkworkMod for the CDMA desire and how do I get it?
I saw an article on addictivetips.com that suggested renaming the new version to the name of the old one (2.5.0.9) and placing in in the Rom Manager folder on the SD and then flashing from Rom Manager thus fulling it into flashing a newer version.
Some, forums have guides on how to do that using adb and yet others have it as a zip file that can be flashed from the hboot.
Whats the best and I guest simplest way to get the new version.
Did you actually run into trouble with your current CWM trying to setup CM7?
The wiki states no problem using the version you currently have - 2.5.0.9.
If you do want to upgrade, you should follow this post.
foalsrock said:
If you do want to upgrade, you should follow this post.
Click to expand...
Click to collapse
Yep. thats exactly the forum I was referring to when I mentioned 3.0.2.4
Although I was not able to flash it using the PB99IMG.zip. Probably should ask there about that.
I did flash CM7 but,
here is what's weird: I tried the method where you fool the rom manager into flashing a newer recover outlined here.
Got the 3.0.2.4, but then when I went back into the Rom manager and hit reboot into recovery, it boots me into 2.5.0.9.
If I just press the power button, select reboot, and reboot into recovery I get 3.0.2.4. It's like I have two recovery images loaded.
I wiped the phone restored my nandroid backup of the stock rom I get 2.5.09.
Wipe again, as always everything data, cache, and dalvik. Load CM7 again. And the same thing two recoveries depending on how I reboot into it.
P.S.
1. Happy Passover, חג שמח.
2. forgot to say: if I power down and boot into Hboot with vol down + power and then go into recovery I get into 3.0.2.4
Do you happen to have your phone S-OFF?
If so, a simple solution might be to flash the 3.0.2.4 recovery .img file using "fastboot flash recovery xxx.img" @ hboot.
But you shouldn't S-OFF just for this as I'm not sure it'll actually resolve what you're experiencing.
It's a pretty odd situation and I think I better not give you advice which could potentially worsen it.
I'd seek help in the thread linked in the CM forums or hope that someone else might notice this post.
חג שמח! =)
foalsrock said:
Do you happen to have your phone S-OFF?
If so, a simple solution might be to flash the 3.0.2.4 recovery .img file using "fastboot flash recovery xxx.img" @ hboot.
Click to expand...
Click to collapse
I do have S-OFF, how would I flash this in Hboot?
Zhenya13 said:
I do have S-OFF, how would I flash this in Hboot?
Click to expand...
Click to collapse
This is assuming you have the Android SDK all set up on your computer (if not, read through the wiki).
Boot into the bootloader, type "fastboot devices". If you see your device listed - continue flashing by typing "fastboot flash recovery <filename>.img"
foalsrock said:
This is assuming you have the Android SDK all set up on your computer (if not, read through the wiki).
Boot into the bootloader, type "fastboot devices". If you see your device listed - continue flashing by typing "fastboot flash recovery <filename>.img"
Click to expand...
Click to collapse
Where should I put the img file? just to the root of the SD card?
תודה רבה
You should have the recovery .img file on your pc when flashing via fastboot
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).
Hi all
DHD 2.35 GB
3.13.351.4
Used HTC hboot unlock
Used ace tool to root and flash cwm
So phone is hboot unlock rooted and have cwm.
Tried using hack kit to s-off but when it pushes the PD98IMG phone re boots into cwm.
Tried manually booting to hboot and it loads the PD98IMG but after loading says failed or wrong version.
Read somewhere that hack kit has to have locked hboot to work so tried the ace tool to re-lock hboot and that fails.
When it says phone will restart it restarts to cwm
Tried flashing a few roms as is using cwm (cm10.1, slimbean, viper)
cwm says the roms installed but either phone boots as normal stock 2.35 or hangs at htc screen
Luckily i did a full cwm backup so easy to restore if it doesnt boot.
IS THERE A METHOD OF FLASHING ROMS THAT DOESN'T NEED S-OFF?
IS THERE ANOTHER METHOD TO S-OFF
Any help greatly appreciated
Stu
stuuk said:
Hi all
DHD 2.35 GB
3.13.351.4
Used HTC hboot unlock
Used ace tool to root and flash cwm
So phone is hboot unlock rooted and have cwm.
Tried using hack kit to s-off but when it pushes the PD98IMG phone re boots into cwm.
Tried manually booting to hboot and it loads the PD98IMG but after loading says failed or wrong version.
Read somewhere that hack kit has to have locked hboot to work so tried the ace tool to re-lock hboot and that fails.
When it says phone will restart it restarts to cwm
Tried flashing a few roms as is using cwm (cm10.1, slimbean, viper)
cwm says the roms installed but either phone boots as normal stock 2.35 or hangs at htc screen
Luckily i did a full cwm backup so easy to restore if it doesnt boot.
IS THERE A METHOD OF FLASHING ROMS THAT DOESN'T NEED S-OFF?
IS THERE ANOTHER METHOD TO S-OFF
Any help greatly appreciated
Stu
Click to expand...
Click to collapse
It does not boot because you need to flash the custom rom boot.img in fastboot after flashing the rom in CWM.
Ok so this is what I did
In CWM factory reset, wipe cash, wipe dalviQ, wipe battery stats
CWM installed zip from card
chose cm-10.1-20130311-UNOFFICIAL-ace.zip
This completed in a couple of minutes no errors
back in hboot / fastboot
flashed boot.img from cm-10.1.... zip but get sig verify fail......
fastboot flash boot boot.img
sending boot 3824k
okay
writing boot
(bootloader) signature checking.....
FAILED (remote: signature verify fail)
finished
What an i doing wrong?
Cheers
Stu
You need to re-unlock your bootloader. And AAHK is retired and the server hosting the files it needs has been pulled.
bananagranola said:
You need to re-unlock your bootloader. And AAHK is retired and the server hosting the files it needs has been pulled.
Click to expand...
Click to collapse
hboot already shows as unlocked
i never relocked it
In 1st post you're mentioning "either boots to 2.3.5"....in the 2nd again missing system and data wipe.
Not 100% but I guess you at least need radio s-off for flashing ROMs.
If I were you, I'd rather not try.
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
iopetja said:
In 1st post you're mentioning "either boots to 2.3.5"....in the 2nd again missing system and data wipe.
Not 100% but I guess you at least need radio s-off for flashing ROMs.
If I were you, I'd rather not try.
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
Click to expand...
Click to collapse
This is false. You can flash ROMs with S-On if you have an unlocked bootloader.
My mistake.
Stuuk, "the Bible" says: "the other way of gaining root is flashing custom ROM after unlocking bootloader."
http://forum.xda-developers.com/showthread.php?t=2168500
So, did you wipe the system and data after nandroid backup, and before flashing custom ROM?
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
Bananagronola was right
Even though hboot showed as unlocked it didnt act like it was.
I ran the htdev unlocker again then I was able to fastboot flash recovery 4ext (over cwm)
In the same session i was also able to fastboot flash a boot.img (which was failing previously)
So booted into 4ext recovery and flashed cm-10.1-20130311-UNOFFICIAL-ace and gapps again after wiping everything.
For good measure I fastboot flashed the boot.img again and hey presto everything works!!!
Well i say everything works however for some reason the touch screen seems a little unresponsive in this rom.
But now I know the procedure I'll be trying a few more roms.
Thanks for all the help
Stu
Running CWM 3.x.x from DHD release
Downloaded CWM 5.8.1.5 zip and 'flash' using install zip util on 3.x but when I went back into recovery it was still 3.x
Didn't realise it was 3.x so I wiped then full wiped etc, then realised 3.x so ran 5.x install again
Decided to reboot to make sure 5.x had installed BUT I hadn't yet flashed a ROM on!
Stuck at HTC screen, have a broken 'DOWN' button so I can't boot into recovery and I can't get into Android and reboot to recovery for obvious reason
Please please can someone help? I just need to get back into recovery to flash.
If it helps, I'm on OS X but I have access to Windows and iirc Ubuntu
Danke
Adb reboot recovery...i dont think you bricked...why dont you use 4ext
Sent from my Inspire 4G using xda premium
So to clarify. You tried to flash the CWM5 recovery.zip from CWM3 recovery, but it failed? You could try to fastboot flash the recovery.img from your computer. Also, are you S-On or S-Off?
To reboot into recovery connect to computer and from cmd type "adb reboot bootloader."
bananagranola said:
So to clarify. You tried to flash the CWM5 recovery.zip from CWM3 recovery, but it failed? You could try to fastboot flash the recovery.img from your computer. Also, are you S-On or S-Off?
To reboot into recovery connect to computer and from cmd type "adb reboot bootloader."
Click to expand...
Click to collapse
My volume down button is broken so I can't access anything on the device. Yes I tried to flash 5 from 3 and it failed.
I'm fairly sure I'm s off. When I rooted etc I used the phone only method so I didn't need adb. Will I need to download anything?
Juilliard said:
My volume down button is broken so I can't access anything on the device. Yes I tried to flash 5 from 3 and it failed.
I'm fairly sure I'm s off. When I rooted etc I used the phone only method so I didn't need adb. Will I need to download anything?
Click to expand...
Click to collapse
Take a look at your bootloader info. If it show 'ace pvt __ s-off, means that it is s-off.
Fail in flashing rom sometimes hinting that there is something wrong with hardware. Unfortunately our hardware expert is no longer here.
Sent from my Desire HD