Alright I have a problem. I bought a used G2 which had already been rooted. I installed CM7 on it and it worked fine except for wi-fi (little did I know the awful path this was about to send me down). I thought this might be because I was using Recovery 2.5, so I switched to recovery 3.0 and flashed CM7 again, same problem. I found out you have to reboot the phone after your first boot to get wifi working a lot of time so that was my fault, I should have researched that more thoroughly from the beginning and I would have avoided this whole ordeal. Anyway after this I wanted to downgrade to Recovery 2.5 again because there are a lot of zips that can't be installed through recovery with 3.0. So I tried to do that and couldn't, I looked around and found that was probably because I didn't have eng s-off which I didn't, I had s-off but not engineering.
So I tried getting that working, this took forever because I couldn't figure out if I was supposed to use the OTA or preOTA.ko file. I discovered my phone was post OTA so I tried using that file and didn't receive the correct error message (Function not implemented), but instead some other error. After researching this and trying to find out why that could be or what exactly the OTA part of it does without a definitive answer I decided to go ahead and run the terminal command for eng s-off anyway feeling relatively safe. This succeeded and I was happy that I'd finally figured everything out! Wrong. I had eng s-off. Also I was able to downgrade the recovery again through terminal, however after doing this and trying to boot into recovery it would just stay at the white HTC symbol. Fine, maybe I can't downgrade to 2.5 after installing CM7. So I upgraded Recovery back to 3.0 and used it to install CM6.1.
After doing this I went into ROM manager and dropped myself back down to recovery 2.5.1.3. Now whenever I try to reboot into recovery I immediately get taken to fastboot. I've tried searching for any others having problems like this without success and I'm extremely frustrated. I tried using different versions of recovery 2.0, I tried updating to recovery 3.0 all without any success, still just boots into fastboot if I try to get into recovery. Please tell me someone knows what my issue could be and how I can fix it, meanwhile I'll continue trying to work it out and let you know if I do. Thankyou.
EDIT: It appears for whatever reason rom manager may actually not be flashing a recovery, if someone could post the 2.5.1.3 recovery.img that would be wonderful
I dont know if you have Andriod SDK set up and if you know how to use Fastboot, but since you have an ENG. Hboot you can use fastboot to flash a new recovery image onto your phone, you can download the CWM Recovery 3.0.0.5 .Img from HERE. Place the new recovery image into the same folder your Fastboot.exe file is and run this command:
Code:
fastboot flash recovery <name of recovery.img>
There is also a way to flash a new recovery using flash_image method from you phone, so you can download a new recovery from the link above and use this method to flash it.
2.5.1.3 recovery is obsolete, the new 3.0.0.5 recovery supports all roms 2.2. and 2.3.
joemm said:
I dont know if you have Andriod SDK set up and if you know how to use Fastboot, but since you have an ENG. Hboot you can use fastboot to flash a new recovery image onto your phone, you can download the CWM Recovery 3.0.0.5 .Img from HERE. Place the new recovery image into the same folder your Fastboot.exe file is and run this command:
Code:
fastboot flash recovery <name of recovery.img>
There is also a way to flash a new recovery using flash_image method from you phone, so you can download a new recovery from the link above and use this method to flash it.
2.5.1.3 recovery is obsolete, the new 3.0.0.5 recovery supports all roms 2.2. and 2.3.
Click to expand...
Click to collapse
Thanks, yes I know how to use fastboot, and I did install the 3.0.0.5 recovery earlier, the problem with recovery 3 is that a lot of older zips don't support it and I'd really like that functionality. Any idea on where I might be able to find the older recovery? Thanks in advance
I have a copy of the 2.5.1.3 recovery, I put it in my dropbox for you:
http://dl.dropbox.com/u/17831112/recovery.img
Heres a MD5 checksum for it:
0C9C47FC09460DB17EC4BDA5F4F97A12
Update for anyone else frustrated by this, I found a tool that will attempt to update your zip to the new edify format. I've tried it on a couple zips so far and it worked both times, they just added support for the G2. Here's the link
http://forum.xda-developers.com/showthread.php?t=903598
Related
Hi everyone. I'm having some problems with my Recovery which I can't seem to figure out:
I tried to mod my phone with CM6.1 the other day using ROM Manager. ROM downloaded and started to install, no problems. When it tried to boot up again, it got stuck in a loop at the CM loading screen. When I tried to reboot in to Clockword Mod Recovery, all I got was a picture of a phone with a triangle (can't remember which colour - think it was green). Eventually I realised that was a stock recovery and managed to get my phone restored to my backup but I can't seem to get my recovery to go to anything but the stock one. Rom Manager reports Clockwork Recovery reports ClockworkMod 2.5.0.7 installed and I've tried using Rom Manager, Android Commander and UnrEVOked to flash ClockworkMod and Amon-Ra and nothing works - I'm still at the built-in recovery.
Now, If I boot in to recovery, I get the red triangle and a message on screen stating "E:Can't open /cache/recovery/command".
If I do use the built-in recovery to flash ClockworkMod as an update.zip, ClockworkMod launches but when I reboot, it's gone again and I'm back to stock.
Any ideas?
Thank you!
"Android Commander and UnrEVOked to flash ClockworkMod and Amon-Ra and nothing works" make sure youre trying to flash a .img file
"Clockwork Recovery reports ClockworkMod 2.5.0.7 installed" that because the recovery (.zip) is saved on the SDCARD. When booting Recovery from ROM Manager, youre fake-flashing the file (.zip)
"If I do use the built-in recovery to flash ClockworkMod as an update.zip, ClockworkMod launches but when I reboot, it's gone again and I'm back to stock." thats fake-flashing
what HBOOT are you on??
EDIT: You should S-OFF your Desire "http://alpharev.nl/".
WARNING: When using S-OFF your flashing a custom HBOOT. If that goes wrong, it may brick your Desire. If you use S-OFF, then you can flash a permanent recovery using fastboot
Thanks Chris. Any idea why it would have reverted though? I used to have a permanent version of ClockworkMod until the other week
Edit: HBOOT just says 0.80.0000 and has 3 androids on skateboards
Sent from my HTC Desire using XDA App
Go back to stock, download the original ruu for you phone. After that try rooting again.
Rats - had a feeling that may be the answer. Think I'll be able to restore a backup?
Sent from my HTC Desire using XDA App
I fake-flash all the time. I once messed up a ROM's installation and got stuck because it messed up the recovery too.
The loop startup is probably caused by older cache from your previous ROM. Just boot up recovery again, clear cache and restore factory settings and then flash your CM again. Should do the trick.
Chris016 said:
what HBOOT are you on??
EDIT: You should S-OFF your Desire "http://alpharev.nl/".
WARNING: When using S-OFF your flashing a custom HBOOT. If that goes wrong, it may brick your Desire. If you use S-OFF, then you can flash a permanent recovery using fastboot
Click to expand...
Click to collapse
Flashed my HBOOT with AlphaRev - those guys are brilliant, coding that!
Thank you for your help!
Bingo!
Think I've nailed it now!
I used Fastboot Commander [v.1.0] to flash Amon-RA which took and stayed!
To confirm: I installed AlphaRev bootloader to S-OFF then Fastboot Commander to flash Amon-RA. Hopefully, I'll now be able to flash Clockwork Recovery again (as I use Rom Manager) and be back up and running!
Think I may skip CM6.1...
I am trying to update my clockwork mod through recovery, flash .zip, locate the updated zip and flash. It all seems ok with the version but when I boot in the phone and back in recovery it comes the old one. How can I solve this ? Thanks.
DiWizard said:
I am trying to update my clockwork mod through recovery, flash .zip, locate the updated zip and flash. It all seems ok with the version but when I boot in the phone and back in recovery it comes the old one. How can I solve this ? Thanks.
Click to expand...
Click to collapse
if you have s-off you can just flash the recovery image file from fastboot
Use unrevoked to flash it.
You're using fake-flash to run the latest one (or the crap ROM Manager) - as said either run unrEVOked again or, if S-OFF, flash it manually
I have succesfully root my girlfriends slide and gained s-off thru Aplha . but i tried to flash cwm 2.5 thru fastboot like an idiot thinking this was the proper way of permanently flashing new recovery and now cannot get into recovery neither factory with triangle or cwm. How do i fix this or will i have to unroot bascially and start over to get the recovery .img again? Also, who can help with permanently flashing cw recovery so that i do not have to use the update.zip method.?
poor2rican1 said:
I have succesfully root my girlfriends slide and gained s-off thru Aplha . but i tried to flash cwm 2.5 thru fastboot like an idiot thinking this was the proper way of permanently flashing new recovery and now cannot get into recovery neither factory with triangle or cwm. How do i fix this or will i have to unroot bascially and start over to get the recovery .img again? Also, who can help with permanently flashing cw recovery so that i do not have to use the update.zip method.?
Click to expand...
Click to collapse
Did you try to fastboot flash the update.zip? That's not good, you should've flashed the cw2.5 .img file. No, you don't have to reroot or res-off, but download the .img file for the latest clockwork recovery on koush's website, for our device. Then, on your computer, while in fastboot mode and plugged into usb, type
fastboot flash recovery filename.img
obviously replacing filename.img with the actual file name/location.
Hi all, I'm looking for a little help.
I have a GSM Desire that I rooted a while back with Unrevoked and selected a custom recovery image which at the time was AmonRa. I've been running LeeDroid for a while, updated a couple of revision of ROMs with no problem and have now moved onto CM7 RC2.
After looking in ROM Manager which I'd never used before, it tells me my current recovery is ClockworkMod 2.5.0.7 and if I click on reboot into recovery it reboots into ClockworkMod. However if I press the powere button and reboot into recovery I end up in AmonRa 1.7.0.1-R5.
So first is this expected as if not how do I resolve it?
Second, how can I go about reflashing to a later version of AmonRa? I've tried using Unrevoked again but it seems to stop at "Running root" after pushing the image and rebooting the phone.
Thanks in advance for any help.
Rom Manager has it's own fake flash recovery which just loads the recovery once, temporary recovery if you would like to call it that. The AmonRA that you have is a permanent recovery installed. That is why you get the two different recoveries.
As it stands, the only way to flash a permanent recovery image (the one you want to update) is to use fastboot or to use a utility. This requires S-Off.
Using unrevoked on an already rooted rom is a no go.
Hello everybody, first post, please take care .
Hey all,
i had an older version of twrp recovery, and tried to flash the new one from here:
https://eu.dl.twrp.me/dumpling/
i opened poweshell from adb folder as usual while device is on fastboot mode, and used the command: fastboot flash recovery twrp-3.3.1-0-dumpling.img
It said "wrting...finished" in powshelll, but when entered recovery - nada, black screen of death.
then i tried flashing older version of twrp in the same way - and still go the same outcome =\
I currenly dont have ROM as well - so practically the phone is uselss. please guys, i need you're help!
Flash stock recovery and stock FW via ADB. If that doesn't work, try one of the dozen recovery tools on this forum.
Tried to flash OrangeFox and BluSpark recoveries, same issue =\
im running out of ideas here guys =(
Just managed to install stock recovery, and downloaded latest 9.0.10 OTA from here:
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
used LAA on adb.exe, and ran "adb sideload OOS.zip" while OTA zip is inside adb folder.
gives me "cannot read" error in powershell.
can someone tell me WTF is going on? how tf its even possible????