Is Htc 1.6 recovery needed to run cyanogens 4.25 rom, i am currently using the newest RA recovery
HTC Recovery isn't the same recovery we've all come to know and love, it's a system image, optionally you can get the system image and use fastboot to flash it, it's needed to install all cyanogenmod's since 4.1.99 or something like that, you'll still keep your RA recovery
just to clarify. you don't need it if your upgrading from 4.1.99 or above. As jack said, htc recovery is just basically a rom (not really but think of it like that)
Related
Hi guys. I don't really know what happened here. I've flashed a few different versions of Cyanogen's builds onto my MT3G without any problems. Today I flashed the official 1.6 dev build of Donut before doing Cyanogen's 4.2.3.1 flash. Well, the 1.6 seemed to go smoothly, but after the reboot, the recovery would no longer load. It's now giving me a picture of the phone with an exclamation point when I try to load the recovery.
How can I fix this? Anyone? Please?
taken from cyanogens website site instructions.
If you boot the 1.6 image it will install the HTC stock recovery. Booting back to recovery will show the /!\[] symbol. THIS IS NOT LOSING ROOT. You can still flash update.zip files from this recovery. Also, you can still flash a nicer (CM-1.4) recovery with fastboot, or flash_image inside the CM install once you get it installed.
thats what sounds like happen to me
How do I do anything though? I don't have the ability to do anything, it just sits there on that screen.
<edit> Also, I can't re-flash the recovery. I've tried, but it gives me the error:
Flash FAILED: The command could not be run
After figuring out how to install ADB and trying to fix it via that, it appears that I have somehow lost root. It's giving me Permission Denied or remote device not allow when I try to flash or use fastboot.
Got it fixed. Took me forever, but I made a goldcard and flashed with the stock ROM. Now I'm good to go again after installing CM recovery 1.4.
Hi guys, my phone currently running Amon_RA 1.6.2 and CyanogenMOD 5.0.5. Now I want to upgrade to Amon RA 1.7.0 and CyanogenMod 5.0.5.1. I know how to upgrade the ROM and I can use the updater to do that, but do I upgrade the recovery image first? and how do I upgrade the recovery image?
Thanks
No you do not have to update the recovery image first and
fastboot flash recovery [path leading up to recovery image]/[name of recovery image].img
i.e.
fastboot flash recovery C:/recovery.img
Thanks I just figured it out, and realized it was a dump question to ask...
Hi,
I've owned and ROM'd two Android phones, but not a G1 and wanted to help out a friend to get her stock 1.6 G1 to CM5. We ran into problems which led me to not want to continue before they are sorted out. I looked for answers to this but couldn't find any, so please don't flame me if I overlooked any. I tried to go by the instructions in the CM wiki.
This is what we did:
- We installed ClockWorkMod Recovery through the ROM Manager app
- We rebooted into that recovery and via adb flashed AmonRA recovery
- we rebooted into the AmonRA recovery which worked (I *think* just regularly holding Home while powering on)
- we flashed the appropriate radio update for her US TMo G1
- the documentation said "phone will reboot during update". I think it did, but it seemed stuck on "formatting cache" in recovery.
- when holding Home on reboot after that, it did from there on NOT reboot into the custom recovery
- instead, it rebooted into what looks like "bootloader" mode on my Moto Milestone, a screen with a phone and an exclamation point. We could get into stock recovery with Alt-L, but I don't think that is what we wanted.
At this point, it seemed to not reliably boot into custom recovery, so I didn't want to continue the process. I assume I could have gone down the same of flashing a custom recovery, but I wasn't sure what would happen with/after installation of the DangerSPL if booting into recovery wouldn't work.
So - is the "booting into bootloader instead of recovery" a known issue? Am I too much of a noob on the G1 and did totally miss something? Could or should we proceed to the DangerSPL / CM5 installation with this going on?
Any help would be much appreciated!
W0nk0
Flashing a new recovery from CM5 or CM6 is not working well. Try flashing the recovery image / radio image / ... from fastboot and you should be fine.
Edit: I did not read well the first time. Now I notice, that you are still on stock SPL, sorry. But re-reading well I've got a question: Are you sure you flashed already successfully a new recovery? For me it seems you are still on a plain stock G1.
Sent from my Htcclay's Superfly G1 using XDA App
Thanks a lot for your help!
We _were_ on a custom recovery twice, after flashing it from ROM manager (Clockworkmod then) and on the AmonRA recovery after that. As the recoveries clearly had non-stock things like nandroid I'm quite positive.
The problem seems to be that they didn't "stick" - we flashed the radio ROM upgrade from Amonra recovery, but after a reboot with Home pressed landed in the exclamation point screen again (which seems to indicate stock recovery as you can get to that with Alt-L from there).
If fastboot is indeed the way to go, where do I get the drivers for the windows/pc side of it? The noob guide I found had no help there :/.
Thanks again,
W0nk0
Sent from my Dell Streak using Tapatalk
Few things;
1) if you have the OEM system image, then, indeed, the recovery will be overwritten by the OEM recovery image upon reboot into the system.
2) You say that you've written a RADIO image.... ***WHAT*** radio image did you write? You should have written a radio with a version number that starts with a "2".
3) Have you written a new SPL? The SPL you should write is 1.33.2003. DO NOT install deathSPL, no matter how many RETARDS suggest it. There is ABSOLUTELY NO USE in it. 1.33.2003 is SAFE to install (unlike 1.33.2005), and the ONLY benefit of 1.33.2005 has been GREATLY EXCEEDED, making that "benefit" entirely pointless.
Note that with the stock SPL (0.95.0000), there IS NO FASTBOOT. 1.33.2003 has a very strong fastboot capable of writing ALL partitions, including the radio image. Fastboot is the safest way to write the radio and SPL, but prior to installing an SPL with a strong fastboot mode, obviously you can't use this feature.
Steps:
1) Reinstall custom recovery,
2) reboot into recovery and write 1.33.2003 SPL.
3) DO NOT let it boot into regular system prior to installing 1.33.2003 SPL, or it will overwrite that custom recovery.
4) After installing the good SPL, it would still overwrite the custom recovery by booting into the regular system, but by this time, you will have FASTBOOT, so it doesn't matter.
5) Now do what you want... but once you have a 2.x radio and 1.33.2003, do NOT write any other radio or SPL, and for F SAKES DO NOT RUN ANY NBH FILES EVER NO MATTER WHAT!!!
Is it posible to flash from fastboot the stock t-mobile g1 rom onto an ebi1 Rogers htc dream? I have recently switched from ebi1 to ebi0... meaning i switched my radios.. So now that my phone is technicaly a g1, would that be possible?
Thanks
Its possible to do many things.. particuarly with fastboot.. but I'd advise not the true stock G1 rom .. and point at the nearly identical but less locked down stock adp1 rom. And advise to keep 1.33.2003 or 1.33.2005 if one of those are installed.
At http://developer.htc.com/
1) download the system image (signed-dream_devphone_userdebug-img-14721 )
2) unzip the zip file on your computer
2) make sure you have a 2.22.* radio less than 2.22.27.08 (2.22.19.26I is the one this rom shipped with)
3) run 'fastboot erase system -w'
4) using the files in that zip run 'fastboot flash boot boot.img' and 'fastboot flash system system.img'
5) boot the phone, you will be on the official google rom
Since we kept the eng spl you can always use that to install a recovery for backing up or installing another rom even if a stock recovery gets installed over your current one.
(Now getting that rom to work on the 2708+ kernel with my old builds kernel takes a bit more work..)
..
That said.. I'd really look at my port of the t-mobile MT3G ota for froyo.. and pref the 2708+ radio+spl (but it can work without) .. if you are avoiding ezGingerbread.. that is just as fast but some of the newer verions of gapps like maps do take a toll I admit.. There are ways around this but not quite out of box.
ezterry said:
Its possible to do many things.. particuarly with fastboot.. but I'd advise not the true stock G1 rom .. and point at the nearly identical but less locked down stock adp1 rom. And advise to keep 1.33.2003 or 1.33.2005 if one of those are installed.
At http://developer.htc.com/
1) download the system image (signed-dream_devphone_userdebug-img-14721 )
2) unzip the zip file on your computer
2) make sure you have a 2.22.* radio less than 2.22.27.08 (2.22.19.26I is the one this rom shipped with)
3) run 'fastboot erase system -w'
4) using the files in that zip run 'fastboot flash boot boot.img' and 'fastboot flash system system.img'
5) boot the phone, you will be on the official google rom
Since we kept the eng spl you can always use that to install a recovery for backing up or installing another rom even if a stock recovery gets installed over your current one.
(Now getting that rom to work on the 2708+ kernel with my old builds kernel takes a bit more work..)
..
That said.. I'd really look at my port of the t-mobile MT3G ota for froyo.. and pref the 2708+ radio+spl (but it can work without) .. if you are avoiding ezGingerbread.. that is just as fast but some of the newer verions of gapps like maps do take a toll I admit.. There are ways around this but not quite out of box.
Click to expand...
Click to collapse
Will the official google rom unroot my phone?
Following the ethos of "because I can" I decided to port Amon_Ra to the Legend. Well, "port" might be a bit strong. I used the android kitchen to pull apart Amon Ra for the HTC Hero and ClockworkMOD for the Legend, then copied the relevant files from Ra to CWM and merged them. On that note, ROM Manager probably won't work with Ra. (What I think it will do is fakeflash CWM over Ra, so if you reboot to recovery using ROM Manager you'll get CWM, and if you reboot to recovery using the extended power menu in CM you'll get Ra)
Everything seems to work OK, but don't count on it. Like I said, this was done because I can and for a laugh. Backup with CWM before you try and be sure to have a copy of CWM to hand if you want to go back.
You NEED S-OFF to use this (Alpharev HBOOT) as it's flashed using fastboot. So, enjoy!
To flash:
1. Turn your phone off
2. Turn it on with the back button held down
3. Plug your phone into your PC
4. flash using fastboot
Code:
fasboot flash recovery Amon_Ra-1.7.0.1.img
DOWNLOAD: http://www.mediafire.com/file/j0o63jc4kua1a6x/Amon_Ra-1.7.0.1.img
Amon_Ra is actually pretty cool, there's a lot of stuff you can do via ADB (plug the phone in, type adb shell [enter] then utility [enter]). Main problem: the zips you flash NEED to be signed for Amon_Ra to flash them.
Other recoveries
To aid in recovering your recovery maybe, who knows?
CWM 5.X.X.X: http://forum.xda-developers.com/showthread.php?t=1244371
CWM 2.5.0.1: http://www.mediafire.com/file/l3c3kacbp8w0phm/CWM-2.5.0.1.img
CWM 3.X.X.X: http://forum.xda-developers.com/showthread.php?t=893248
Someone's been busy.