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
Related
Hi all,
I'm trying to help a friend update his Sensation to bruce2728's CM10 beta. I started from scratch on an updated-to-4.0.3 device with this phone and have done a fair amount of research. So far, I have done the following:
1.) Unlocked my boot loader via HTCDev
2.) flashed a custom recovery via fastboot - it's CWM-based 6.0.0.0. I can boot into recovery and back up the ROM and restore it
3.) Rooted with the CWM-flashable SuperSU 0.9.6 and verified root.
4.) used the JuopunutBear method to enable S-OFF. This is verified by booting to the boot loader, it says S-OFF and hboot version 1.27.1111
5.) Flashed a custom ROM
And #4 is where I run into problem.s I started with the CM10 beta mentioned above. It seems to install OK, and then I install G-apps, wipe data/cache, and reboot. I get to an htc logo and then it goes black and boots into recovery automatically. Tried wiping /system along with another wipe of data/cache and same result.
Thinking I had a bad download, I re-downloaded. Same results
Well maybe his Sensation is screwy, I wonder, so I grab the official CM9.1 release. Exact same procedure, exact same results.
So now I'm wondering, what can I do? Right now it's back to running the stock but rooted ROM. So it's not the end of the world. Just trying to figure out what I did wrong or what I can do to fix it. Should I get the official 5.0.2.0 or touch 5.8.0.9? I see both of those on the ClockworkMod ROM manager website, and I own ROM Manager Premium, so I can do all that if need be. Thanks in advance.
You might want to try 4ext recovery it is probably the most used recovery for the sensation. Then wipe every thing except sd . Then flash the ROM then gapps. But make sure you have a working nandroid first.
Sent from my HTC Sensation using xda app-developers app
I do have a working Nandroid. I'll check into 4EXT, as well. Thanks for the assist.
Will you think less of me if I pay $2.82 for the automated installer? :lol:
No, I'm not going that route, just wondering.
edit 10:01pm Central - that did it. Booted into bruce2728's CM10 beta. Sweet!
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!
For some reason, I decided to delete my backups, and now when I tried flashing to the newest PACman, it failed. Then, when the phone tried to boot, it wouldn't pass the first HTC screen. Then I tried to wipe just about everything to make the flash work using my recovery (TWRP), and it still won't work. I can get to bootloader, recovery, etc. I've been trying to just use fastboot to push a ROM onto their. I'm really just an average joe that likes to play with his phone, and I had my method of dowloading a rom, then using recovery to flash it, so fastboot is a little over my head. I'm currently downloading a RUU, but I don't know what I need or what I don't need. I thought I almost pushed a ROM using fastboot to my device, but then it said FAILED <remote: not allowed>. My computer doesn't recognize when I mount the sd card. Any help would be appreciated, and if it is using fastboot, please be step by step. Thank you.
Which TWRP version do you have?
foeti said:
Which TWRP version do you have?
Click to expand...
Click to collapse
v2.1.7
I had the same problem when i was using twrp, i switched to Clockworkmod and then the rom flashed properly
Sent from my One S using xda premium
So, if I understand you can't flash kernel, and phone won't boot. And you can't do this with ADB.
When I'm not wrong, my suggestion is -download sense-rom, in development sectons is ..i.e. sense-zen rom, or any other sense, and install this as a usualy, then install buletproof kernel from Flar.Hi made it with aroma installer, and you don't need fastboot or "flash img" app. Just install it and you phone should booted fine.
But, when I'm in misunderstood, excusme, and give me some more info.
Hi im a bit confused I used hansoons tool kit and unlocked bootloader.
I try to flash a CM rom/kernel but i keep failing and just leaves me stuck at splash screen forcing me to use the recovery.
not sure if im doing it right but i place a folder with the zip in it go to CWM and use the zip file option there.
am i doing something?
also is it normal that after having boot loader it takes more memory?
ok i got it working.
using http://forum.xda-developers.com/showthread.php?t=1912582
not sure if thats a good one but seems up to date.
now im installing gapps "well flashing it through recovery"
any other steps im missing?
Your phone was never bricked if you were able to just reboot into bootloader...also what toolkit are you using and are you S-ON or S-OFF?
Never used a toolkit to root anything before, but I'm under the impression it just unlocks your bootloader and then flashes a recovery for you
The next step would be to download ROM of choice (+any gapps or mods wanted) and but them on sdcard
Now boot to your recovery, wipe all, flash ROM, flash any gapps or whatever
Then if its not a stock based ROM (which is most only 3 or so old stock optimized ROMs) then you need to boot back to your bootloader and flash the kernel through fastboot
Unzip the ROM, find boot.img
Open cmd/terminal in the location of the boot.img
Then type
fastboot flash boot boot.img
fastboot reboot
Now all should work
Sent from my Nexus 4 using Tapatalk 2
yup got it working thanks guys. figured it on my own a bit before.
but im running into a new problem Gapps keeps giving me the unexpected close error "i think i flashed the wrong gapps for my phone"
can i just flash the right gapps to fix it? and where can i find a source for the correct one
Hansoons toolkit,and im pretty sure its S-on is what people state when using that way,,,
also seems liek i screwed up people say dont update it after installing the rom/kernel that i linked "scv's project"
but i updated how can i undo this? do i just reflash again same kernel and zip?
If the gapps aren't specified in the op of your ROMs thread then see what version android your using and Google search
Goo inside me gapps
Then download the appropriate version and flash it in recovery. You may need to do a full wipe and then flash ROM gapps and kernel again
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
If the gapps aren't specified in the op of your ROMs thread then see what version android your using and Google search
Goo inside me gapps
Then download the appropriate version and flash it in recovery. You may need to do a full wipe and then flash ROM gapps and kernel again
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
so i got gapps working
im curious how i can do a fresh wipe of rom and kernel i downloaded a update i wasnt suppose to that reverts it do i just redo the process i did when i first flashed it?
also is there a way to get teh genius button option working again when flashing?