So, I posted earlier about looking for a Stock Android 2e recovery image, to no avail.
I have pulled the recovery from a stock build and being that I don't have an EVO, I respectfully would like to ask a couple people to test this.
The goal is, that after flashing the zip via HBOOT, that entering recovery will yield the stock HTC Recovery that came with the phone. I believe this is necessary to have to successfully install ota updates from Sprint in the future.
Of course, your S-OFF will allow you to revert back to Clockwork or Amon_Ra.
It's attached at the bottom of the post. Appreciate the feedback.
I think it is possible to flash this recovery via fastboot. Take out the recovery.img and go into fastboot and simply use:
Code:
fastboot flash recovery recovery.img
Related
I'm a fan of using Hboot to flash basic things like recoveries and radios. This might help someone if you recently flashed the new 3.0.0.x recovery but can't flash any zips or format partitons manually and want to go back to the older recovery. Be sure to read this all the way if you are new to this or like reading my mindless dribble.
This will restore you to a stock Clockwork Mod Recovery 2.5.0.1. You will lose any firerat custom MTDs you may have in place.
If you are S-OFF, give this a try:
REMOVED
Rename to HERCIMG.zip, copy to root (top level) of your sdcard. Use Windows on your mounted SDcard drive, or use adb:
Code:
adb push HERCIMG-recovery.zip /sdcard/HERCIMG.zip
Reboot into hboot, either from the phone, or via adb:
Code:
adb reboot bootloader
You can also use vol-down + power key combo if your phone is turned off.
Make sure you are in Hboot (not fastboot). If not, read the screen on how to get there. If it says push 'action' for something, that means press your trackball.
Once in Hboot it should find your HERCIMG.zip and read it and say that a recovery is ready to flash. Press trackball (action) to accept, wait, and bam you are done. You can reboot the phone (read the screen!) or.....
Instead of rebooting, just go back home (send I think?) and look it will give you the option to boot into recovery. Saves a bit of time if you want to flash and go right into the recovery.
TIP: You can (possibly) replace recovery.img in the zip with ANY recovery. Just name it recovery.img and replace it with the one in the zip. Peek at android-info.txt if you want. Of course I have only tested clockwork. Also s0be has tested this HERCIMG-recovery.zip and it worked for him one day on IRC.
TIP: There are other ways to do this, this is just one option. ROM Manager from the market can reflash your recovery, as well as using flash_image via adb shell.
Please mirror if you can, I don't want my dropbox to get eaten alive!
Credit: Koush and friends for CWMR
someone, I forget, for the HERCIMG flashable stock RUU
aosp: for the test 3.0.0.4 recovery
Tested only on Sprint HTC Hero CDMA using S-OFF via the unrevoked method. HBoot version 1.47.
I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.
you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.
I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.
This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock
I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.
chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?
Like a complete prat, I have lost my boot and recovery img!!!
I was trying to get clockwork recovery as the recovery img and then accidentally did:
fastboot flash boot recovery.img
instead of
fastboot flash recovery recovery.img
I have found an unlocked bootloader from here (third one down) http://forum.xda-developers.com/showpost.php?p=9869067&postcount=38
I have saved this to the AndroidSDK\tools file as bootloader.img and tried the below whilst in fastboot mode:
fastboot flash boot bootloader.img
but the phone only reboots to the fastboot screen.
I now have no phone and I need it for work, can anyone help me, im desperate?
Thank you
Why not just flash cwm recovery then flash a ROM?
There's a sticky in this forum section with almost all full ROMs (stock Android, no need to flash cwm recovery for the signed ones, can use stock recovery) or head over to dev forums and look for a custom ROM you like (need cwm recovery).
Be sure to pick the right ROM for your device.
you don't need a bootloader! you need a boot.img! a kernel with ramdisk! ^^
Sent from my Nexus S using XDA Premium App
If the following command was executed successfully:
Code:
fastboot flash recovery recovery.img
Next step is to download a ROM of your choice and flash it via ClockWorkMod recovery and you're good.
FYI, the command
Code:
fastboot flash boot ...
does not flash your "bootloader". It is used to flash the kernel, which will already be included in the ROM you downloaded.
meso100 said:
...instead of
fastboot flash recovery recovery.img
I have saved this to the AndroidSDK\tools file as bootloader.img and tried the below whilst in fastboot mode:
...but the phone only reboots to the fastboot screen.
Click to expand...
Click to collapse
No problem. Flash your recovery using the correct command (above).
If you have access to fastboot, use your volume keys as up and down, and navigate to the "Recovery" option. When your phone boots into recovery, you can mount your USB and copy a ROM to your device.
Then go back, do a factory/data wipe, and flash the zip you copied. This should restore your phone.
Recovery images:
http://forum.xda-developers.com/showthread.php?t=988686
ROMS:
http://forum.xda-developers.com/showpost.php?p=13556812&postcount=2
Thank you all for your replies and help and apologies for the late delay.
I have been away for a few days and with your help and a bit of playing about I managed to sort out the problem. I was probably a bit hasty to ask for help but actually felt that I had bricked my phone!
This happened because I was following two different fastboot flash guides on the net...lesson being just keep to one!
Also, when I lost cwm I didnt know how to get it back...but again you can only learn from your mistakes and I did.
I managed to get cmw reinstalled and cm7 flashed.
Now I am running the latest MIUI and it is pretty good.
Thanks all for your help, see you the next time I panic!
meso100 said:
Thank you all for your replies and help and apologies for the late delay.
I have been away for a few days and with your help and a bit of playing about I managed to sort out the problem. I was probably a bit hasty to ask for help but actually felt that I had bricked my phone!
This happened because I was following two different fastboot flash guides on the net...lesson being just keep to one!
Also, when I lost cwm I didnt know how to get it back...but again you can only learn from your mistakes and I did.
I managed to get cmw reinstalled and cm7 flashed.
Now I am running the latest MIUI and it is pretty good.
Thanks all for your help, see you the next time I panic!
Click to expand...
Click to collapse
Thanks for using your brain and figuring it out. Congrats on getting it up and running.
Sent from my PC36100 using XDA Premium App
Hi there. I'm new to rooting but I've done a considerable amount of reading before this and I have a question.
I'm rooting using a guide (can't post link due to new user restrictions) on another forum, and before doing this I realized that I wouldn't be able to receive OTA updates using the one of the two custom recovery options (CWM or TWRP 2) that the root method specifies. Is it possible to restore the stock recovery to receive OTA updates and keep my root? And how would I go about doing this for the HTC One S?
Thank you!
you just need to flash the stock recovery and relock your boot loader.
This isn't hard to do in fastboot
fastboot flash recovery recovery.img (change the name of the recovery.img file to make it easier than typing something like recovery_signed_ville.img or whatever)
fastboot oem lock
I have the s4 variety of htc one s and I've used this stock recovery. it's the second download not the first.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
or you can use the all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1604677
select 'your own recovery' and click flash recovery button. It will bring up a window to browse to where the recovery you want to flash is.
you can lock or unlock bootloader with it by putting your unlock_code.bin file in the data folder of the toolkit.
I mistakenly flashed twrp as an update in flashify, after that both startup and recovery mode shows "Invalid boot image". I managed to fix the startup by flashing the compatible boot.img for my phone, while recovery mode is still like that. I can now open my phone but after that I can't turn on my wifi and hotspot and the camera is not turning on too. I tried to restore factory thought it might fix it but it directed me to "Invalid boot image" again. I really need some help right now. Someone know how to fix it?
Asus Zenfone Go ZB551KL
Aharu said:
I mistakenly flashed twrp as an update in flashify, after that both startup and recovery mode shows "Invalid boot image"...
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/asus-zenfone-go
With that stated...
I believe that you should be able to obtain some member guidance within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3282861
https://forum.xda-developers.com/showthread.php?t=3460995
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I GOT!
Comrade, I had the same problem, and at the expense of a lot of sweat, blood and tears, I got a IMG.
Here is the recovery.img of the ZB551KL, Enjoy
Code:
mediafire.com/file/tetjmun58gxm6mv/recovery.img
Code:
fastboot flash recovery recovery.img
lethemooca said:
I GOT!
Comrade, I had the same problem, and at the expense of a lot of sweat, blood and tears, I got a IMG.
Here is the recovery.img of the ZB551KL, Enjoy
Code:
mediafire.com/file/tetjmun58gxm6mv/recovery.img
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh wow, I forgot about checking this post because I replaced this phone quickly after that. I have 0% knowledge about flashing the time I posted this. Well, I just fixed it right now by doing EXACTLY that.
Quick recap what I did back then:
Thought of flashing TWRP recovery but I have no idea about adb, fastboot and stuff. Only used Kingroot and Flashify. My very first flash was a mess. Used twrp.img as an update which almost broke my system completely, revived the system by flashing stock boot.img but wifi, hotspot and camera doesn't work and recovery is missing. My dumbass back then tried adb, used
Code:
fastboot flash recovery
to flash boot.img IIRC (facepalm). That's when I thought the phone is now bricked and can't be fixed.
Now years passed I learned all about adb, I tried everything I can think of, installing root apps like kingroot or kingoroot so that I could flash again but failed, looked for a solution to unlock bootloader (oem unlock is missing) but only method that works is to downgrade firmware which is also a no because I don't have recovery.
Found a firmware with recovery.img but thought you couldn't even flash stock recovery through fastboot because bootloader is locked but I just did it because that's the last hope I got and IT WORKED. Figured fastboot recovery flashing is fine as long as it's the stock one. Recovery is back, flashed the latest firmware, phone system is now back to normal.