Related
Hi guys, fist post here, hopefully not a noobish one.
anyway.... I want to know why it is so important to install ClockworkMod? I mean, stock recovery isn't enough to work with, or fastboot for flashing, and "cat" or "bb" commands for dumping and system backups?.
That's it, Thanks for your help!!.
I didn't even check out the stock recovery, flashed CWM out of habit.
Usually the primary reason is so that you can flash "unsigned" zip updates to the phone, but I understand from some posts here that the stock recovery lets you do that.
Other big reasons are ability to make nandroid back ups and some extra features like mounting partitions while in recovery. I don't think the stock lets you do that.
distortedloop said:
Usually the primary reason is so that you can flash "unsigned" zip updates to the phone
Click to expand...
Click to collapse
I'm trying to update the framework-res.apk with an unsigned zip, I having no problem, but there is no change too.
I tried to apply a UOT Kitchen update, and its not working too.
Any tip?
NVMENOR said:
Hi guys, fist post here, hopefully not a noobish one.
anyway.... I want to know why it is so important to install ClockworkMod? I mean, stock recovery isn't enough to work with, or fastboot for flashing, and "cat" or "bb" commands for dumping and system backups?.
That's it, Thanks for your help!!.
Click to expand...
Click to collapse
CW has lots of extra features and options, that the stock recovery does not offer
many of which features are crucial to save your phone on those Crap Happens! moments
the brilliance of clockwork recovery is it lets you basically update to most any ROM just like an OTA update, from anywhere you are. sure, you can also just download any ROM thru the browser, but using clockwork along with ROM manager is the brilliance of it all...
Clockwork Recovery removes the need for renaming all of your flashable zips to update.zip every time. Enough said.
I think I found the perfect balance:
Code:
fastboot boot recovery-clockwork-X.X.X.X-crespo.img
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.
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
plmiller0905 said:
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1954060
http://forum.xda-developers.com/showthread.php?t=1955303
plmiller0905 said:
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
Click to expand...
Click to collapse
as mentioned in other threads.. if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it
To clarify, flashing the boot image from fastboot is only necessary if you are on hboot 1.14 b(coming from AT&T firmware 2.20). Previous hboot versions, the kernel is flashed automatically when you flash the ROM.
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.