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.
Related
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.
downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.
ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.
I'm running the stable cm10 and I have cwm recovery installed. I was thinking about installing TWRP Recovery because I have hboot 1.14 and I read somewhere that it's easier to flash the fast boot when updating the rom using TWRP. Anyway, I can install it directly through GooManager, but it seems far too easy. Can I really just have GooManager install it for me and that's it?
Yup, it really is that easy
And is it accurate that TWRP makes it easier to flash fast boot files when updating your rom? Coming from Samsung devices, I was a little iffy with having to flash the fast boot files with adb and I actually temporarily bricked my device.
Also, once I update to TWRP through GooManager, that's it, cwm is replaced with TWRP? I feel like I'm missing something.
Also, thanks for answering.
You're not missing anything, it really is that easy.
And when using twrp for hboot > 1.09 you need to use HTC dumlock (it's part of twrp) to flash boot in recovery. Maybe try using flash img GUI, its available in the play store and is all over the cm10 threads.
Also, why flash boot with adb over fastboot? Fast boot seems easier. Or maybe I'm just used to it
Sent from my HTC One S using xda premium
First noted this is first time installing a custom rom. Long time lurker, first time problem!
HTC One S from Bell (Canada) Rooted/unlocked. CWM for Recovery.
Installed the from Zip in CWM. Cleared everything, went and flashed with fastboot for the boot. Everything looked good. Went back into CWM and cleared cache again.
Went to boot, hanging at htc screen but has the additional red text as well.
What did I miss ?
Thanks for any help or insight into this issue.
Is your phone s-off ... If not thm install 4ext recovery n flash the rom by enabling smart flash in 4ext recovery... Search for 4ext recovery n how to flash rom with s on ull b done
If I hve helped you press the thanks button ...
sent from HTC sensation
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Goatshocker said:
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Click to expand...
Click to collapse
Thanks so much, It worked. I was starting to stress out. Re-did the flash and BAM music happened. Just sitting at the HTC One screen now. I assume that takes a couple minutes.
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
AKToronto said:
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
Click to expand...
Click to collapse
Yeah im going to be switching over to TWRP. Sounds like its allot better to work with. I know with cwm you can't even mount usb storage, so you end up pushing files on using adb.
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!
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.