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!
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.
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.
Hello, recently i've just rooted my htc one s, s4. I stalled for a bit and had the 4.0.4 update already, so currently I have root access with the stock firmware. I'm looking through the rom list and the viper One s room caught my eye. So my question is, are there any prerequisite requirements before i flash this rom. Sorry for such a ridiculous question, but i havn't flashed a rom since the G1 and I remember having to flash certain kernels for certain roms. I still haven't messed with the kernel yet so that's stock too.
_________________________________________________________
My One S is s4 t-mobile, TWRP recovery, obtained root access with the All in One Toolkit v3.0 by hasoon2000. firmware is stock update 4.0.4 and everything else is just stock. so all i did was root
Just follow the instructions in the Viper Thread.
Since you have it rooted (and I assume a working recovery) you should already have all tools needed (fastboot etc).
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
rugmankc said:
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
Click to expand...
Click to collapse
Thanks! i went ahead and flashed viper rom and after reading a bit i noticed that i had hboot .14 so it broke my wifi . I'm still currently searching info and came across that i need linux to downgrade, which i don't have . do you know any other method? or roms beside trickdroid 7 that support the hboot version and allow wifi?
On .14 the items I mentioned will apply on all roms
Not sure on wifi, i use mostly cm roms atm
Im on Hboot .14, and wifi works fine for me on viperS
there is a wifi partition zip floating around for wifi issues. didn't pay much attn to it as i have no issues--maybe a search, or someone will post it
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
thrgk said:
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
Click to expand...
Click to collapse
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
cntryby429 said:
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
Click to expand...
Click to collapse
Thanks for all the info. So if I am on 4.4.3 and want to flash a 4.4.2 rom just flash the 4.4.2 firmware just to be safe before flashing the 4.4.2 rom?
Also where are the kernels located ? Are they carrier dependent as I didn't see any yet browsing but didn't look hard either.
So I can do flash boot through flashify and be ok? Now all roms and kernels are flashed through twrp tho right ?
EDIT: actually fastboot can flash rom and kernels so no real need for custom recovery other then for convenience?
Btw do you have a kernel recommendation for aosp, sense, ? I already saw your recommendation for sense above.
Thanks !!
Sent from my SM-N900V using XDA Free mobile app
I have a feeling that it's simply not necessary to downgrade your firmware in order to run a 4.4.2 rom but you should find a more reputable source than myself. I'm just trying to answer these easy questions to save time for the guys who really know what they're doing. Once you do start flashing things, always make sure 1) they are for your device (and carrier, unless unified for all carriers) and 2) the md5 of the downloaded file matches that provided by the hosting website or the OP.
I'm not a fan of flashing utilities simply because I've heard of instances where they don't work correctly. For example, I keep hearing how the TWRP manager app flashes TWRP to the system partition on Verizon devices and sends the phone into a sort of recovery loop. I would suggest gaining knowledge about the fastboot flash command "fastboot flash <partition name> <filename.extension>" and how to enter and flash within RUU mode.
My experience is that ROMS and kernels are easiest flashed through a custom recovery especially when the developer packages it with an Aroma installer script.
A few Sense/GPE custom kernels exist for verizon. There's MassStashed and Checkm8 (no longer maintained?) for 4.4.2 roms. Also, for 4.4.3 roms I only know of the EliteLunar kernel which isn't on XDA although you can find a few links to it in the forums if you search. Last I knew, there weren't any AOSP kernels which work with verizon but that might not be true anymore. The general HTC One m8 forum may have some kernels which aren't represented in the verizon-specific forum. Just make sure and find out if they're compatible with verizon devices. I'm pretty happy with sense so I haven't wondered off to AOSP like I usually do.
so do you recommend to use flashify or no?
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
Its the easiest way
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
I'm not saying you shouldn't use flashify, it's awfully convenient. Just make sure you're using it for the convenience and not because you don't know how to accomplish the same tasks in recovery/fastboot.
I was running CM 12.1 on my N5 and wanted to give stock 6.0 a try so I flashed the factory image using the meathod in this article.
'androiding.how/marshmallow-rom-nexus-5-recovery-flashable/'
Have no problems and everything seems to be normal. However, I did want root access so I was going to follow the method described in that article which mentioned using fastboot to load a new boot.img. All I had to do was boot into TWRP flash the hellscore Kernel, then flash Superuser SU2.46.
However all the threads on this forum suggest that rooting marshmallow should not be this easy and requires a new boot.img ect......Am I missing something?
Ridley78 said:
I was running CM 12.1 on my N5 and wanted to give stock 6.0 a try so I flashed the factory image using the meathod in this article.
'androiding.how/marshmallow-rom-nexus-5-recovery-flashable/'
Have no problems and everything seems to be normal. However, I did want root access so I was going to follow the method described in that article which mentioned using fastboot to load a new boot.img. All I had to do was boot into TWRP flash the hellscore Kernel, then flash Superuser SU2.46.
However all the threads on this forum suggest that rooting marshmallow should not be this easy and requires a new boot.img ect......Am I missing something?
Click to expand...
Click to collapse
The thing is, u need a kernel built for M that allows root access, something like HellsGod, the kernel that is packaged with XtraSmooth. I'm on the Nexus 6 running M and this is what did to achieve root access, I flashed XtraSmooth ROM thru twrp, downloaded 6.0, extracted the system, bootloader, and radio from the factory image and flashed them using fastboot, then I booted back into twrp and flashed SuperSU v2.50, u don't wanna use 2.46, it will bootloop, now I'm on M, rooted and loving it
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:44 AM ---------- Previous post was at 10:38 AM ----------
And it's always been that easy to root Nexus devices, that's what they're for, is primarily a developers phone, so they make it easy cut devs
Sent from my Nexus 6 using Tapatalk
Thanks for the input, however I am still unsure why you need to use fastboot to load the bootloader and radio? I downloaded the zip files and used TWRP and it worked with no issues? and I did not get stuck in a boot loop using SU2.46?
I guess I am wondering if the update I flashed from the posted article was infact a full version of Marshmallow or just the preview since I did not need to use fastboot, and SU2.46 worked fine? at this point I am under the assumtion I did not go back to full stock 6.0 when I flashed the update.
The kernel you flashed (also known as a boot.img) was modified to allow root. It is no more complicated than that. If you didn't have a nice twrp zip file to flash (hell's kernel) you could have used fastboot to flash the kernel(boot.img) instead. Also, because you used a rom that was packaged as nice twrp flashable zip file you didn't have to use fastboot to flash the bootloader and radio, etc...it was in that rom zip file. You can use 7-zip or winrar to browse it and you can see all the files that zip flashed for you if you want.
This is why a lot of times after a new version of android drops the Q&A gets loaded with people asking for a stock flashable zip of the roms. It's just an easy way to upgrade without having to use fastboot which seems to be difficult for a lot of people to grasp.
Marshmallow cannot be rooted without a modified kernel right now so maybe that's what people mean by it"s "hard" to root marshmallow? Who knows. I thought it was easy peasy lemon squeezy.
Awesome. That is kinda what I thought but I just wasn't sure. it seemed too easy. I know enough to follow steps with out bricking my phone, and how to get out of a bootloop, but some of the finer details are still greek to me. I appretiate your input.:good:
Evo_Shift said:
The kernel you flashed (also known as a boot.img) was modified to allow root. It is no more complicated than that. If you didn't have a nice twrp zip file to flash (hell's kernel) you could have used fastboot to flash the kernel(boot.img) instead. Also, because you used a rom that was packaged as nice twrp flashable zip file you didn't have to use fastboot to flash the bootloader and radio, etc...it was in that rom zip file. You can use 7-zip or winrar to browse it and you can see all the files that zip flashed for you if you want.
This is why a lot of times after a new version of android drops the Q&A gets loaded with people asking for a stock flashable zip of the roms. It's just an easy way to upgrade without having to use fastboot which seems to be difficult for a lot of people to grasp.
Marshmallow cannot be rooted without a modified kernel right now so maybe that's what people mean by it"s "hard" to root marshmallow? Who knows. I thought it was easy peasy lemon squeezy.
Click to expand...
Click to collapse
I looked at that site you linked and it is possible you are still using the old radio and bootloader. It seems they had separate zip files for those things. The old ones might work with marshmallow though, I am not sure. You can go into your settings and look to see if the radio you have is up to date. Did you flash both of those zips or just the rom? The current one is baseband version M8974A-2.0.50.2.27. If yours is older you could flash that bootloader/radio zip file they have on that site. However, if your phone is working properly and you get good signal and everything there is not really any need. (I honestly can't remember if the bootloader and radio files can be included in flashable rom zips since I always update that stuff using fastboot, lol. Now that I think of it I don't think radios are typically included when people develop roms. I am trying to think back to when I flashed cyanogenmod like over a year ago... Either way it seems you get the idea of what to do.)