Been on the Samsung side of the street for the past four years so if it wasn't named after a accient Viking God then I'm lost However just a couple questions if I may: I am unlocked, rooted, recovery installed, & TA backed up however not real sure how the whole boot image flash works, does this need to be done everytime I go to flash a ROM? Also do I have to reflash recovery everytime I flash a ROM? just remember reading that somewhere, been trying to read all I can
nickfar2000 said:
Been on the Samsung side of the street for the past four years so if it wasn't named after a accient Viking God then I'm lost However just a couple questions if I may: I am unlocked, rooted, recovery installed, & TA backed up however not real sure how the whole boot image flash works, does this need to be done everytime I go to flash a ROM? Also do I have to reflash recovery everytime I flash a ROM? just remember reading that somewhere, been trying to read all I can
Click to expand...
Click to collapse
You only need to flash a boot image once to get the recovery going if you have a locked bootloader then this will have to be done, if it is unlocked as you have said then you do not need to do this again. The recovery should stay how it is. Some kernels that you can flash have twrp and usually cwm included, when you flash it you'll have access to both.
Cool, welcome!
The recovery is included in the kernel (boot.img), so it's automatically updated/flashed every time you install a ROM zip through recovery. The very first time you install a CM/AOSP/etc ROM, you may have to first flash the boot image through fastboot, like you said, to get a recovery compatible with the ROM. I think you only have to do this when going from stock based recovery to AOSP based recovery.
Oops, got beaten.
theinspector said:
You only need to flash a boot image once to get the recovery going if you have a locked bootloader then this will have to be done, if it is unlocked as you have said then you do not need to do this again. The recovery should stay how it is. Some kernels that you can flash have twrp and usually cwm included, when you flash it you'll have access to both.
Click to expand...
Click to collapse
Not quite correct but close
You have installed recovery (dual by [NUT]?). most ROMs are completable with both twrp and cwm. Just flash the zip for the rom (after making a backup. choose the recovery that is in the ROM*). if this fails then you can flash the boot.img from the zip with adb/fastboot (fastboot flash boot <boot_img_name>). most ROMs only contain one recovery
* CM based normally have cwm. Slim, omni, candy all use twrp from memory
Okay thanks guys very much appreciated, so if I'm understanding you correctly then I don't need to flash any "boot images" becuase I am already unlocked and on a non stock recovery(dual recovery by NUT) becuase the "boot image" is just the recovery? So since I already have nuts dual recovery then I should be good to
Enter TWRP
Nandroid, Wipe
Flash CM 11+Gapps
Reboot
???
If not correct please let me know, sorry just trying to make sure I'm understanding this correctly, and if not then my ass needs to go read some more ;+)
nickfar2000 said:
Okay thanks guys very much appreciated, so if I'm understanding you correctly then I don't need to flash any "boot images" becuase I am already unlocked and on a non stock recovery(dual recovery by NUT) becuase the "boot image" is just the recovery? So since I already have nuts dual recovery then I should be good to
Enter TWRP
Nandroid, Wipe
Flash CM 11+Gapps
Reboot
???
If not correct please let me know, sorry just trying to make sure I'm understanding this correctly, and if not then my ass needs to go read some more ;+)
Click to expand...
Click to collapse
boot.img is the kernel (and ramdisk etc) + recovery
If you are going to flash CM the do it from cwm as then the nandroid backup can be flashed from the recovery that cm uses. other than that you are about right (wipe both caches and /data, dont wipe /system. the ROM will take care of this)
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
I flashed twrp.img during unlock/root process. I have seen some mods/roms that say I should use CWR and not twrp to flash.
is it ok to install cwr even though I am running twrp already?
I fear conflicts like when I click reboot to recovery, wouldn't my device be confused which to use?
If you flash cwm it will replace twrp
Sent from my Droid DNA
jasonpascoe said:
I flashed twrp.img during unlock/root process. I have seen some mods/roms that say I should use CWR and not twrp to flash.
is it ok to install cwr even though I am running twrp already?
I fear conflicts like when I click reboot to recovery, wouldn't my device be confused which to use?
Click to expand...
Click to collapse
Go ahead and flash cwm youll be perfectly safe. the recovery.img's overwrite eachother so the phone will only boot to one or the other depending on what you have flashed most recently. TWRP has known errors, i've actually contacted the primary dev of twrp to resolve this but havent had time to follow up with him. Anyway CWM is much safer for now.
Don't forget that backups made with one recovery won't restore with a different recovery. So if you switch from TWRP to CWR, make a new backup
I would really like to see Amon Ra ported to the DNA. Anyone know how, or someone who could? It worked really nice on the Rezound.
Im tired of installing many ROM's and 2 different Recovery, some "cant open .zip" and having boot problems, and in other recovery, it can install roms, but other aslo cant open .zip, and also having boot problems,
Im really tired of reflashing stock ICS Fw then root, install Recovery again, after failing installing ROMs.. its too long to reflash, root, install recovery,, its waste my time and having headache after failing installing ROMs for almost a week
Is there any fast solution or what would you do after you fail installing ROMs and cant boot? even do you can enter recovery? what proper should do next? would you also reflash again stock ICS then root and install recovery?
or any other fast way solution..
Please help
Root and install recovery onto your device. Enter recovery and make a nandroid back up of your device. Flash your new rom and reboot the device. If you boot loop or the rom doesn't work or even if you just don't like it, enter recovery (may have to remove the battery to restart a boot cycle) and use your nandroid back up to restore your device.
Before flashing the new rom, you should make sure that the kernel is compatible with the one that is already on your device. If it isn't compatible, you will also want to flash the new kernel using fastboot/flashtool, and not recovery. Also make sure you have a back up of your rom's current kernel so you can flash the original kernel, if you decide to go backwards.
justmpm said:
Root and install recovery onto your device. Enter recovery and make a nandroid back up of your device. Flash your new rom and reboot the device. If you boot loop or the rom doesn't work or even if you just don't like it, enter recovery (may have to remove the battery to restart a boot cycle) and use your nandroid back up to restore your device.
Before flashing the new rom, you should make sure that the kernel is compatible with the one that is already on your device. If it isn't compatible, you will also want to flash the new kernel using fastboot/flashtool, and not recovery. Also make sure you have a back up of your rom's current kernel so you can flash the original kernel, if you decide to go backwards.
Click to expand...
Click to collapse
Thanks I think that what im looking for.. the Nandriod backup..
gota way to find that now and how to install
Thanks a lot!
Hmmm...the most easiest way it to unlock your bootloader first...then flash custom kernel...this can help you skip rooting and installing recovery again and again if something goes wrong cause all custom kernel is pre-rooted and got recovery by default....
next you need to find which custom roms you want to flash...some custom roms have their own kernel or flash any custom kernel that is compatible with the roms....
remember, custom kernel is important cause if you flash the wrong kernel, you might get bootloop after flashing the roms....
Pusak Gaoq said:
Hmmm...the most easiest way it to unlock your bootloader first...then flash custom kernel...this can help you skip rooting and installing recovery again and again if something goes wrong cause all custom kernel is pre-rooted and got recovery by default....
THANKS! I have a plan now to unlock my BL
thanks for that info
Click to expand...
Click to collapse
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
radici said:
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
Click to expand...
Click to collapse
Tell people who you fixed it FFS!
how did you fixed ?
radici said:
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
Click to expand...
Click to collapse
Please help , I'm having exactly the same issue.
OS is booting correctly, but I'm not able to enter in any recovery mode, neither in CWM or TWRP..: confused:
radici said:
FIXED, NM.
Click to expand...
Click to collapse
These forums become useless if the knowledge is not captured. It is awesome that you fixed it, but please let us know briefly HOW you fixed it!!
sparkdroid said:
These forums become useless if the knowledge is not captured. It is awesome that you fixed it, but please let us know briefly HOW you fixed it!!
Click to expand...
Click to collapse
Same issue here too' please share how you fixed it.
I was trying to switch my phone over to CWM from TWRP. I tried flashing using ROM manager but it was always rewritten. I decided to grab the .img file from the CWM site and flash it in terminal emulator like I had done with TWRP before. It seemed to flash but when i rebooted I got the message that the system software was not authorized. I thought the file I downloaded was loki but I guess not. Do I have to odin back to stock now or is there another method?
So I just realized it was being stupid and was stuck trying to boot recovery. I booted to download mode and selected cancel to force it out of this loop. Once it did this I was able to boot the system and restore a proper recovery.
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
thecaptain0220 said:
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
Click to expand...
Click to collapse
ROM manager does work...try flashing then reboot at least once before booting recovery...and if you are running a stock tw rom some will attemt to overwrite custom recovery...in newer cwm it will ask you if you want to disable recovery install...clicking yes will stop the process keeping custom cwm