Database Info

After I root...

So, I am going to do a lot more research prior to rooting, but I had a couple of general questions that I was wondering about, before I begin the steps leading up to rooting.
1) I presume the easiest way for me to root my Thunderbolt is the Revolutionary Root? This will take be through rooting and installing the CW recovery that I need, correct?
2) Right after I root, If I want to install roms/kernels? than I can just get Rom Manager from the android market?
3) Once I install Rom Manager, can I just flash a rom that is compatible with my Thunderbolt? Can I just flash a kernel that is compatible with the Rom?
I suppose where I get a lil lost is the flashing compatibility part. What kernels work with what roms, what roms I can flash... I have read a number of articles, so I suppose what I'm asking is...
Will the process more or less be: Revolutionary Root, Install Rom Manager from market, flash a rom (just the most popular one). Is the Kernel flashing piece important? Do I need to flash a different kernel? Is it easy to tell in Rom Manager which kernel/rom I can use?

Yes use revolutionary to root and install custom recovery (cwr). You can use ROM manager to download custom roms if you want, only roms for your device will show up. Or you can download custom roms from forums, this is the method I prefer.

Just use kernel that comes with the Rom for the time being some developers include a custom kernel and others make modifications to the HTC kernel itself. Kernels are seperated in development section having to do with sense and aosp that is the first way to seperate them. Second would be leak the kernel was based on such as imo test 3.8 was based on newest leak so it works for just about if not all newest sense roms. When in doubt fire up a question in the Rom thread itself and ask what kernels those people are using, find a Rom like BAMF or thunderstick or synergy where the developers or support staff are very active.
Also you will need to flash a new radio right after rooting if you are still using froyo, I am using newest leak but different phone work differently. Once you install the radio VIA Hboot. Reboot phone and remove zip file from root of SD card now place your Rom image on SD card and reboot to recovery and install your new Rom.
Sent from my Thunderbolt using XDA App

This is good info.. thanks.
Well, I am upgraded to Gingerbread as of VZW's last update and still unrooted and stock.
So, if I were to root (using revolutionary) and install Rom Manager... could I just install something like Cyanogenmod or BAMF right through Rom Manager?
What do you mean by kernel that comes with the Rom? The kernel that is listed to use with the Rom? Or do you mean if I flash BAMF or something popular, just leave whatever kernel I have as is?

Bwangster12 said:
This is good info.. thanks.
Well, I am upgraded to Gingerbread as of VZW's last update and still unrooted and stock.
So, if I were to root (using revolutionary) and install Rom Manager... could I just install something like Cyanogenmod or BAMF right through Rom Manager?
What do you mean by kernel that comes with the Rom? The kernel that is listed to use with the Rom? Or do you mean if I flash BAMF or something popular, just leave whatever kernel I have as is?
Click to expand...
Click to collapse
When you flash a rom it flashes the kernel too with whatever one the devs packed with it.
Sent from my HTC ThunderBolt using Tapatalk

Okay, clear enough.
So, for someone like myself, just use revolutionary root, install rom manager and play around a lil with flashing roms using rom manager for awhile. I understand that I can install roms from my SD card, but it sounds like at least initially installing roms right from rom manager would be the simplest. I can also not worry about installing a different kernel during this "honeymoon" phase. Just pick the latest version of whatever Rom I want and flash the rom?

After you root you need to install superuser so CWM can function. I have read that some people flash their CWM via hboot after s-off and then go right to recovery to flash the root gaining RUU, then enjoy your root.
Do not flash ROMs right from CWM reboot to recovery clear data/cache and under advanced davlik cache and then install Rom from install from SD and choose zip file and I always store mine in downloads since I download all my roms right to my phone and download md5 checker from market and always check the md5 if it does not match don't think its a mistake redownload and try again.
Sent from my Thunderbolt using XDA App

Agreed, it is better to install the ROM through recovery instead of installing through ROM manager as sometimes it doesn't work right.

Don't forget to use thank you for all you great answers.
Sent from my Thunderbolt using XDA App

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english

same problem here, help is needed!

A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM

Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?

I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.

But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?

Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device

Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...

Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.

@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers

Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!

Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

[Q] stock rom with s-off ? what i need to do?

hello and sorry for the same questions asked over the same issue...
its my first time and im afraid to brick my phone
anyway now im with custom rom and want to go back to stock to receive ota updates.
my phone is rooted and s-off i want to stay s-off with stock rom.
1. is it possible ?
2. will i need to wipe data before the flash?
3. backup needed ?
4. will i get ota updates with stock rom s-off?
5. the ruu is europe 1.47 do i need it to match to my software/radio/hboot?
my phone:
SAGA PVT SHIP S-off RL
HBOOT -0.98.0002
RADIO-3805.06.02.03_M
EMMC-boot

@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.

foX2delta said:
@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.
Click to expand...
Click to collapse
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped

thanks
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!

yonigo870 said:
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!
Click to expand...
Click to collapse
here is a few guides to help with that question i don't know anything about rom manager sorry i use 4ext touch recovery
Custom ROMS:
Custom roms can be found in this thread: http://forum.xda-developers.com/show....php?t=1146601 or head to the development section.
(Most of these ROMs are pre-rooted, which means that you don't need to root your phone after flashing one of the custom ROM.)
How To: Flash Custom ROMs using Recovery (Method 1)
(You can use your default recovery from Revolutionary tool but I recommend using 4EXTRecovery)
1. Copy your custom ROM "zip" file to your SD card (Root directory).
2. Turn off your phone.
3. Turn on your phone by holding the power button and the volume down button together.
4. Once you see the white screen, choose "Recovery"
5. Make a full wipe/format and clear all cache.
6. Choose "install from sdcard/zip file" and then choose your Custom ROM zip file from your SD card to flash your Custom ROM.
Optional: If you want to use 4EXTRecovery, just flash it like you are flashing your custom ROM(Step 6). Just do it before you flash your new ROM.
How To: Flash Custom ROMs using ROM Manager (Method 2)
(This method might be easier for flashing ROM updates or add-ons)
1. Go to ROM Manager (You can install this software from the Android Market.)
2. If you want to use 4EXTRecovery, please follow steps below, and if you're not using 4EXTRecovery, please skip to step 6)
3. Press your phone's option's button and choose Manual Flash Override.
4. Press OK and choose your phone model.
5. Choose ClockworkMod 3.x (After these steps, your ROM Manager won't ask you to flash new recovery again when flashing new a ROM)
6. Reboot into Recovery and make a full wipe/format and clear all cache then reboot.
7. Now, from your ROM Manager, choose Install ROM from SD Card.
Note: Flashing ROMs can be vary, some custom ROMs may require you to flash some of their own file first. Eg, The LBC Mod ROM requires you to flash "WIPE zip file" before flashing the ROM. Read their instructions carefully to know more.
NOTE: I am not responsible for any faulty or bricked devices after S-OFF or flashing new ROMs. Do it at your own risk.
How To: Flash a ROM in a "Perfect" Way (Method 3 - Recommended)
A great guide from vampire36 for people who encounter the following problems:
1. The ROM you flashed gets stuck on HTC screen (bootloop) while the same ROM works right for others
2. You get the same kernel and radio yet you find your cell to have more battery drain than others
3. Finally some strange force closes and restarts but works perfect for others
So this is basically one of the most perfect way to flash a custom ROM and is a way to help people who face such issues.
Please head to : http://forum.xda-developers.com/show....php?t=1257731 to see full instructions and discussions.

Blush91 said:
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped
Click to expand...
Click to collapse
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root afterwards and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!

Saipro said:
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!
Click to expand...
Click to collapse
yes i've flashed many roms also and have never encountered a boot-loop the only time i got a boot-loop was when i flashed the wrong RUU in the past 48 hours i've changed roms about 20 times

flashing pre rooted stock rom
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager

yonigo870 said:
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager
Click to expand...
Click to collapse
Loooool don't worry that's what's xda is for were all here to help
Sent from my HTC Desire S using XDA

no wifi
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
the phone updates himself ??? i see it updates programs from the market without me doing anything
* do i need to reboot the phone after flashing rom ??? and how ?

yonigo870 said:
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
Click to expand...
Click to collapse
I don't know much about titanium I use app extractor try this ROM http://db.tt/Wnl7ZrKa
App extractor restores your apps contacts wifi settings SMS from your nandroid(backup)
Sent from my HTC Desire S using XDA

many thanks for the help !!!!
do i need to reboot after flashing ?

Yeah reboot I hope you made a full wipe before flashing sorry should have told you earlier
Sent from my HTC Desire S using XDA

yeah i did full wipe
after flashing rom the phone made updates from the market by himself, and now im restoring via titanium and seems like everything is ok...
after that titanium asked me to reboot, and so i did.
again thanks a lot for the support and for the help !!!!!!!!

problem !!! the rosie utility stopped unexpectedly...
htc widgets (like clock and weather) not working after restoring with titanium!
maybe its since the backup was on sense 2.1 and now its 3.0
how can make the htc widgets work ???

reboot back into recovery and fix permissions i dont know if you can do that in titanium

solved !!!
all was needed is to clear data from the htc sense

Boot Image?

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!

Can someone answer these couple newbi questions for me

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.