Is it possible to have both TWRP and CWM installed at the same time and switch between the two? I have noticed that some roms prefer to be flashed with TWRP and then the other way CWM. If this is possible is there a choice when going to recovery or is there a default .
You can only have one recovery installed
Sent from my HTC One X using Tapatalk 2
If you're on a 2.3 TWRP you should be able to handle any ROM without issue I'd say. Avoid 2.4 for now until they iron out the bugs.
leesumm said:
Is it possible to have both TWRP and CWM installed at the same time and switch between the two? I have noticed that some roms prefer to be flashed with TWRP and then the other way CWM. If this is possible is there a choice when going to recovery or is there a default .
Click to expand...
Click to collapse
Recovery is a partition, and there's only one of them. Whatever you flash there replaces what was there before.
Dual boot is possible with s-off, but only for running two different roms. I don't believe there's any way to have two recovery partitions without some sort of custom bootloader, and since hboot is not open source, you'd need to code one from scratch. You're welcome to give it a shot.
Related
I have cwm currently but I see threads saying to flash things such as radios and kernels through twrp. And I saw someone say that not to flash the new eu ota radio update through cwm. So I'm just wondering which recovery is better to use and why you wouldn't be able to flash a zip through cwm vs twrp. And is it easy to go back and forth between recoveries. Thanks.
Sent from my HTC One S using xda app-developers app
TWRP is for those who can't or do not want to use fastboot to flash the boot.img as it does it automatically, but only on hboot 1.09 and below I believe. TWRP has a feature called HTC dumlock which flashes the boot on higher hboots. It also has a GUI as opposed to just text and takes advantage of the touchscreen. I personally like CWM better (the lack of a GUI makes it feel more "hacker-like ) but until we get S-OFF, TWRP will be what I use because of the ability to flash ROMs without fastboot.
andrewt328 said:
I have cwm currently but I see threads saying to flash things such as radios and kernels through twrp. And I saw someone say that not to flash the new eu ota radio update through cwm. So I'm just wondering which recovery is better to use and why you wouldn't be able to flash a zip through cwm vs twrp. And is it easy to go back and forth between recoveries. Thanks.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Most people say that the twrp recovery is better in some ways than in cwm, well that I know of in twrp when flashing a Rom if your hboot is below 1.14 then you don't need to flash the boot.img via fastboot, although I'm pretty sure it doesn't work all the time but it has for me so far. As of now, cwm can flash roms/ certain zips, it just won't flash the boot.img for you like twrp does and it isn't hard to go back and forth between recoveries isn't that complicated, just download an app called goomanager for the twrp recovery and I think its called Rom manager for cwm and just ho to install recovery in romanager and install openrecovery script on goomanager and it does the rest for you, but you can't have both recoveries on one phone, they will over write each other if you do tend to switch back and forth, well hopefully I helped you clear up some confusion and if I did just hit the thanks button, and if you wanna know more just ask
Sent from my One S
leohdz148 said:
Most people say that the twrp recovery is better in some ways than in cwm, well that I know of in twrp when flashing a Rom if your hboot is below 1.14 then you don't need to flash the boot.img via fastboot, although I'm pretty sure it doesn't work all the time but it has for me so far. As of now, cwm can flash roms/ certain zips, it just won't flash the boot.img for you like twrp does and it isn't hard to go back and forth between recoveries isn't that complicated, just download an app called goomanager for the twrp recovery and I think its called Rom manager for cwm and just ho to install recovery in romanager and install openrecovery script on goomanager and it does the rest for you, but you can't have both recoveries on one phone, they will over write each other if you do tend to switch back and forth, well hopefully I helped you clear up some confusion and if I did just hit the thanks button, and if you wanna know more just ask
Sent from my One S
Click to expand...
Click to collapse
ok this explains alot, thanks. im on hboot 1.09, and i just flashed viper rom yesterday using cwm. i did it as they said...flashed the rom then the boot image using the pc. so if i was on twrp then i wouldnt have had to flash the boot image after (so i could cut out the use of a pc?)? i could just flash the rom and boot it up and it works?
Im just trying to get used to this phone, cuz i came form the nexus s and for that all you do is flash the rom with cwm and it all worked, but this phone is way better, much faster and stable
thanks
Kamilr97 said:
TWRP is for those who can't or do not want to use fastboot to flash the boot.img as it does it automatically, but only on hboot 1.09 and below I believe. TWRP has a feature called HTC dumlock which flashes the boot on higher hboots. It also has a GUI as opposed to just text and takes advantage of the touchscreen. I personally like CWM better (the lack of a GUI makes it feel more "hacker-like ) but until we get S-OFF, TWRP will be what I use because of the ability to flash ROMs without fastboot.
Click to expand...
Click to collapse
There is a touch version of CWM... it works very well
http://www.clockworkmod.com/rommanager
andrewt328 said:
ok this explains alot, thanks. im on hboot 1.09, and i just flashed viper rom yesterday using cwm. i did it as they said...flashed the rom then the boot image using the pc. so if i was on twrp then i wouldnt have had to flash the boot image after (so i could cut out the use of a pc?)? i could just flash the rom and boot it up and it works?
Im just trying to get used to this phone, cuz i came form the nexus s and for that all you do is flash the rom with cwm and it all worked, but this phone is way better, much faster and stable
thanks
Click to expand...
Click to collapse
On most ROMs, you are correct. On Viper, this didn't work for me and I still had to fastboot.
andrewt328 said:
ok this explains alot, thanks. im on hboot 1.09, and i just flashed viper rom yesterday using cwm. i did it as they said...flashed the rom then the boot image using the pc. so if i was on twrp then i wouldnt have had to flash the boot image after (so i could cut out the use of a pc?)? i could just flash the rom and boot it up and it works?
Im just trying to get used to this phone, cuz i came form the nexus s and for that all you do is flash the rom with cwm and it all worked, but this phone is way better, much faster and stable
thanks
Click to expand...
Click to collapse
Save yourself some future headaches and switch to TWRP. The One S isn't really supported by clockwork, there was one build for it when the phone was first released and that's it. TWRP has active development and can do things that CWM can't.
It's easy to try another recovery or move between them, it's almost the very same as flashing a boot.img with fastboot. If you want to try a recovery without installing it do this and it will boot right into it:
fastboot boot recovery.img
One important thing to consider when changing recovery is that your backups made in one recovery won't work in the other, eg CWM nandroids won't work in TWRP and vv. So make a new backup first thing
WCCobra said:
There is a touch version of CWM... it works very well
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
But it still doesn't flash the boot.img
Kamilr97 said:
But it still doesn't flash the boot.img
Click to expand...
Click to collapse
Well, no... but it does have a touch interface which is a bit easier to use for those who prefer CWM.
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
Yes there is a sense kernel and one for non-sense roms (aosp)
Usually the dev will have a kernel link posted on their page
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
redpoint73 said:
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
Click to expand...
Click to collapse
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file. So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
If you can point me to a how-to on this, I'd appreciate it - I hate filling boards with asinine questions.
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
viper doesn't require you to flash the boot image, it does it for your.
For cm10 or liquidsmooth you need to, an easy way is using Flash GUI. its available on the market and xda. you don't need to hook up to a computer to flash boot image, makes things much easier and faster.
originalseven said:
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
Click to expand...
Click to collapse
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
originalseven said:
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file.
Click to expand...
Click to collapse
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
originalseven said:
So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
Click to expand...
Click to collapse
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Awesome - thank you so much. Cleared that up completely.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
originalseven said:
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
Click to expand...
Click to collapse
flashimagegui is perfectly supported. got support awhile back. [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Hey,
Can I change custom recoveries as if I was flashing them for the first time? Do I need any special care with it? I've flashed CWM, but it isn't the touch version, and this is way nicer to use.
Diogomsb said:
Hey,
Can I change custom recoveries as if I was flashing them for the first time? Do I need any special care with it? I've flashed CWM, but it isn't the touch version, and this is way nicer to use.
Click to expand...
Click to collapse
Yup. Just fastboot or mfastboot flash (whichever one you used) the new recovery and it will overwrite the one you have now. Some recoveries even come in a flashable form so you can flash the zip from your current recovery just like you would any other zip (ie SuperSU).
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Preston2291 said:
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Click to expand...
Click to collapse
Most kernels r flashed in recovery.
Tigerstown said:
Most kernels r flashed in recovery.
Click to expand...
Click to collapse
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Preston2291 said:
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Click to expand...
Click to collapse
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Tigerstown said:
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Click to expand...
Click to collapse
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick because I can't write to the system with a new rom
Preston2291 said:
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick
Click to expand...
Click to collapse
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Tigerstown said:
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Click to expand...
Click to collapse
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Preston2291 said:
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Click to expand...
Click to collapse
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Tigerstown said:
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Click to expand...
Click to collapse
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Preston2291 said:
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Click to expand...
Click to collapse
You should be able to just flash pretty much any sense based rom and have what you want. Write protection is removed in all of them, or, at least in all the ones I've tried.
That said, if you've already flashed a kernel that has write protection removed, you should be able to check it by just copying any file to the system folder. A text file, picture, anything. Then reboot the phone and check to see if the file you copied to the system folder is still there. If so, you're good to go. If not, write protection is still being enforced.
I rooted and installed the (dual recovery? i believe its called) so that i wouldn't need to unlock bootloader and lose DRM keys.
My main question is why do we need this dual recovery which essentially installs 2 custom recoveries?
Some ROMS specify flashing using Philz however i have always used TWRP and have my backups using this etc.
What is the difference and why should i use Philz instead of TWRP?
What are the benefits of each?
rm83855 said:
I rooted and installed the (dual recovery?...
What are the benefits of each?
Click to expand...
Click to collapse
Both do the same job. It's just a matter of user preference really. Philz can come in handy if you are flashing a massive stock based rom which TWRP might not be able to handle, due to it's size. However, Philz development has ceased, while TWRP continues.
Sent from my D6653