Database Info

HTC One X Flash and SDcard issue

Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason

zad2k2 said:
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
Click to expand...
Click to collapse
1. Wrong section, things like this should be in Q&A
2. Did you flash the CWM recovery with working ADB? If so you should be able to push the rom to your sdcard from recovery (someone correct me if I'm wrong about that).

RUU back to stock?
Sent from my HTC One X using XDA

Enter Fastboot re flash a recovery that has ADB working either teamwins or the CWM that has working ADB. Then push the rom to the sd card through ADB in recovery.

My apologies for posting in the wrong area...Thank you for the quick responses. I reflashed the current CWM, no luck. I flashed the recovery from Teamwin and things are looking up. I was able to look at the sdcard in recovery and I was able to push the ROM to the sdcard via ADB. However, when I try to install the zip, it gives the error again "can't mount sdcard" failed....hmmm Any other ideas or thoughts??
Thank You
Jason

I just wanted to say thank you to those who helped. All the time wasted, I never relocked before trying to flash RUU!!

made same mistake
...everything was too cool to be true,
rooted my HOX with
One Click HTC One X Root by kennethpenn (Win/Mac/Linux) (Recommended)
then
Auto Deodex/Debloat AT&T One X by kennethpenn
then let my HOX relax for a week, but past weekend after install CWM with
How To: Install CWM Recovery on HTC One X (AT&T)
Filed under Development, Guides by Kenneth Pennington
i was not sure about wether to install ROM
CleanROM DE 2.1 -★| Sense / AOSP Blend | Smooth! | Refreshing! |★-
or
CleanROM 2.4.5 SE -★| Landscape! | EQS! | APM! | Clean! |
i download both and then restart in recovery then i did
install zip from sdcard, but instead of do it over CleanROM 2.4.5, I did it with CleanROM DE 2.1
after reboot i realize that i screw it big time since CleanROM DE 2.1 comes without boot.img
so now when i start my HOX just reboot by itself after 5sec, the only thing i am able to do is start on recovery and when i tried to install all over again thru install zip from sdcard i just get
"E: Cant mount /sdcard/"
I ran AT&T RUU_Evita_UL_Cingular_US-1.83.502.exe and RUU 1.73 but it cant detect my HOX
help!!!

I found this for you. Give it a try. It was not my work just googled.
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30%
[edit] Try this first
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
In command prompt window opened in your platform-tools folder type:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash

[Q] Semi-bricked tf300t

I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)

same thing just happened to me. Im going to download another version of CM and try that. It might just be that.

DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...

http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.

OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2

Glad you got it!

nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.

DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?

1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.

nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.

This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.

I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.

[Q] New Rom

I have just successfully unlocked my bootloader and rooted my AT&T HTC One X. My first time doing this. What I would like is a Jelly Bean Rom to flash and where to find step by step instructions on how to get it up and running. I just cant seem to find it anywhere out there. I'm very new to this and I just want to get this done properly. I did the bootloader unlock and root through TWRP all in one tool kit. I'm assuming I would flash a Rom from the same program? I also would like to have as much a "vanilla" Jelly Bean ROm as possible and one that is stable and fully functional. If anyone can direct me it would greatly be appreciated. Thanks in advance !!

jmlape said:
I have just successfully unlocked my bootloader and rooted my AT&T HTC One X. My first time doing this. What I would like is a Jelly Bean Rom to flash and where to find step by step instructions on how to get it up and running. I just cant seem to find it anywhere out there. I'm very new to this and I just want to get this done properly. I did the bootloader unlock and root through TWRP all in one tool kit. I'm assuming I would flash a Rom from the same program? I also would like to have as much a "vanilla" Jelly Bean ROm as possible and one that is stable and fully functional. If anyone can direct me it would greatly be appreciated. Thanks in advance !!
Click to expand...
Click to collapse
i'll make it simple
1) install TWRP custom recovery from here: http://forum.xda-developers.com/showthread.php?t=1677447
2) download rom and gapps to your computer and transfer it to your phone
3) *make a backup in case anything goes wrong*
4) flash boot.img (extract it from rom file) and use this to do it: http://forum.xda-developers.com/showthread.php?t=1962428
5) reboot into recovery (boot into bootloader, then reboot into recovery)
6) full wipe (cache, davlik, factory, etc)
7) go to install and find the .zip file of the rom and flash it, be patient it may take a while
8) flash gapps
9) reboot system and u'll be done be patient for this one too, first boot always takes a while
hope this helped

Thank You
utkaar099 said:
i'll make it simple
1) install TWRP custom recovery from here: http://forum.xda-developers.com/showthread.php?t=1677447
2) download rom and gapps to your computer and transfer it to your phone
3) *make a backup in case anything goes wrong*
4) flash boot.img (extract it from rom file) and use this to do it: http://forum.xda-developers.com/showthread.php?t=1962428
5) reboot into recovery (boot into bootloader, then reboot into recovery)
6) full wipe (cache, davlik, factory, etc)
7) go to install and find the .zip file of the rom and flash it, be patient it may take a while
8) flash gapps
9) reboot system and u'll be done be patient for this one too, first boot always takes a while
hope this helped
Click to expand...
Click to collapse
I really appreciate your response. Don't I have TWRP already from when I unlocked bootloader and rooted? Next question.... what ROM and where do I download it from? Do I download to PC or phone? Sorry for all the questions but I dont want to mess up my phone. Hope you can help me....Thanks again

Download goo.im install TWRP via goo.im or from fastboot. Test to see if get into the recovery. If so you can flash away. Follow instruction from the video that twrp puts out or from the how to thread. I'm running AOKP now for nearly a week and so far so good. Just be sure to start by backing up your phone with twrp or the other pimp apps available. Watch Video or follow directions on twrp thread for your device. Goo. im is darn noon friendly. Here's a screenshot of an example screen
Sent with Swagger

jmlape said:
I really appreciate your response. Don't I have TWRP already from when I unlocked bootloader and rooted? Next question.... what ROM and where do I download it from? Do I download to PC or phone? Sorry for all the questions but I dont want to mess up my phone. Hope you can help me....Thanks again
Click to expand...
Click to collapse
once the bootloader is unlocked, then you are able to install the recovery. you can check if you have it already, but its likely that you dont.
its fine if you download from your phone, but for starters it is much simpler to download from the computer and transfer to the phone
and for what ROM to flash, since you want a jb rom i'd recommend starting with a stable rom, so that would mean you should stay way with roms with the "unofficial, beta, alpha",etc labels. also CM10 is in a pretty unstable state too, so stay away from that
i wouldn't necessarily recommend a jb rom for starters, but it seems to me that you'd like one so i would start with nocturnal'd dirty rom. its stable, smooth, and has some really nice tweaks

jmlape said:
I really appreciate your response. Don't I have TWRP already from when I unlocked bootloader and rooted? Next question.... what ROM and where do I download it from? Do I download to PC or phone? Sorry for all the questions but I dont want to mess up my phone. Hope you can help me....Thanks again
Click to expand...
Click to collapse
You can download ROMs via goo.im on your phone like CM10, AOKP.. just read up a bit and get it right. The other poster's response is right on the money. Follow those links and you are good to go.
Sent with Swagger

No offense to any other devs, but I agree dirty rom is pretty solid and polished with a very active dev. As for installing, download rom and dirty gapps. Also head to play store and download flash image GUI...
1. Open flashgui app. Browse to dirty rom and select. OK it by following instructions and don't worry about the WiFi bit. (Its just a disclaimer). It'll automatically flash just the kernel.
1. Once successful, immediately boot into recovery. Wipe cache, wipe dalvick, factory reset, wipe system. Press back button, hit install. Find your dirty rom. Swipe to flash it. Once successful, immediately flash dirty gapps.
2. Reboot system. (First boot takes a little longer)
3. Swim in the butter!
Sent from my fast as f*#@ OneXL codenamed: Dirty Girl

I'm downloading that ROM right now for a test drive...ending thread highjack mmmm now.
Sent with Swagger

[Q] Problems with MD5 file trying to flash CD10 rom

I have an ATT HTC One X 2.20 Hboot 1.14 using twrp 2.4.1 and have been trying to install roms but continue to have an issue with the MD5 file. I have followed the instructions about flashing the boot.img of CM10 but it seems no matter what I do, it can't find the MD5 and says it is skipping MD5. I know just enough not to get out of a bootloop but I am quite new to this. The one odd thing I see is when I go to mount my phone in order to copy the CM10 zip file into the phone, the options I get are different than others I see online: Mount System (unchecked), Mount Data,(unchecked), Unmount Cache (checked), Unmount SD Card (checked). Any help would be awesome.

quick update; same problem
SWell, going through some of other posts and videos, I tried using goo manager to download the CM 10 zip file. But Im still stuck on boot loop. And it still says that the MD5 file was not found. I used the onexroot.com tutorial to root my phone and have superuser and twrp. Not sure what else to try. Ideas on other stable JB roms I could try? Thanks again.

In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?

force check
redpoint73 said:
In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?
Click to expand...
Click to collapse
I'm pretty sure I do. I have always left it unchecked. Should I check it and try again?

I've always left it unchecked (no MD5 check). If its a bad download, all that will happen is the phone will get stuck on boot, anyway.
I'd go into TWRP, and see if its checked or not. And if so, uncheck and try to flash again.

Update: No Luck
I just tried wiping system, factory reset, and cache, flashing the cm10 boot.img and then installing the CM10 zip file and checking the force MD5 and then the entire process and unchecking the force MD5 and with both attempts I get right back to the same issue. All I can say is that I'm so thankful that I created a backup in twrp. I've restored my phone at least 20 times today, haha. Learning is definitely a process. Ill take any more ideas.

Download the ROM again, may just be a bad download.

Will try
I will try to download the rom again from the CM website. If I were to try another rom (viper xl), the process should be the same correct? Thanks for the help.

alemcc said:
If I were to try another rom (viper xl), the process should be the same correct?
Click to expand...
Click to collapse
Put the ROM on your SD.
Boot into hboot, go into TWRP
In TWRP, factory reset, wipe cache, wipe Dalvik
Install ROM
Reboot
ViperXL should flash boot.img in AROMA, although its not foolproof. If the phone doesn't boot (may take about 5 min first time), then flash boot.img using fastboot.
For most ROMs, you will need to flash boot.img manually. ViperXL is one of the few exceptions (also CleanROM 5.1, I think).

Still no luck
I just tried aokp JB 4.1 with no luck. I do everything I've been told or that I have read on these forums (copy zip to SD, flash boot image, install rom...) but i continue to get the same problem: MD5 not found, skipping MD5 and so on. If anyone has any ideas I'll be happy to give any other info needed. At this point I have a rooted phone but cannot install roms. Argh!

He's not the only one. I'm on viper 3.2.3 but when trying to flash any Rom based off of AOSP or anything similar I bootloop. Yes I flash the boot.img then the Rom to no avail . I started a thread in this department called weird problem if the OP would like to take a look there.
Sent from my HTC One X using xda app-developers app

I'm new to all this, but I don't understand why certain people have this issue but most don't. Aren't all att one x phones pretty much the same?

Same thing i'm wondering
Sent from my HTC One X using xda app-developers app

you dont check any md5 checking for custom roms in twrp
you only rom i know of that you will have a md5 without anything selected is evervolv 4.2 i found a fix where you copy the CERT.SF from evervolv 4.1 to evervolv 4.2 and it will install and boot.
also always remember to "fastboot flash boot boot.img" if you are on hboot 1.14 or newer. if you going changing from sense to aosp always do full wipes no matter what. never factory reset in bootloader.

Yes I've done this countless times as I was on jellybam before going to jokers sense 4+ Rom then viper . I know the processes but something is wrong.
Sent from my HTC One X using xda app-developers app

alemcc said:
I used the onexroot.com tutorial to root my phone and have superuser and twrp.
Click to expand...
Click to collapse
I hate websites like that one. They just ripoff content from XDA, repackage it, and give little or no credit to the actual developer or XDA.
Stupid question, your bootloader is unlocked, right? In bootloader, it says UNLOCKED?
It must, for you to have TWRP. But it doesn't hurt to cover all the possibilities.

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!