Database Info

Cant boot into recovery...HTC screen only

I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!

From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast

E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?

http://forum.xda-developers.com/showthread.php?t=1754018

gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?

rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?

rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1

veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast

E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...

Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app

c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:

Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app

veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?

rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!

veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?

http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!

Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.

Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.

slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.

im getting the same error and im using the recovery ending on evita

[Q] [A700] bootloader unlocked, but nathing happens with fastboot flash

I unlocked the bootloader by doing:
Code:
# adb reboot-bootloader
// wait for it to reboot
# fastboot oem unlock
// follow the on-screen instruction to unlock the bootloader by pressing vol-up then vol-down
# fastboot reboot-bootloader
and now it boots with "Bootloader vICS-MR1-a055314(UnlockMode): Starting Fastboot USB download protocol" on the top left corner.
but then I try to flash recovery downloaded from this thread by issuing:
Code:
# fastboot flash recovery recovery-a700-6015.img
sending 'recovery' (5006 KB)...
OKAY [ 1.985s]
writing 'recovery'...
OKAY [ 2.601s]
finished. total time: 4.586s
// the screen flickers (going to pure black with backlight and come back in ~0.1 sec).
# fastboot reboot
# adb wait-for-device
# adb reboot recovery
but it's still the stock recovery (with an android with belly opened in the middle).
I tried all images (6.0.1.5, 6.0.1.4, 6.0.1.1 update 1) in that thread but none of them works.
I also tried to boot the recovery image (works on my HTC Desire) directly by doing:
Code:
# fastboot boot recovery-a700-6015.img
but the screen just flickers once and nothing else happens.
I tried to unlock the device again by issuing "fastboot oem unlock" once more, but it says the device is already unlocked.
I also tried another USB cable but didn't help.
What am I doing wrong (or missing)?
=== UPDATE: 2012/11/14 ===
this problem is solved by the OTA update "Acer_AV051_A700_RV19RC01_TWN_GEN1 (Acer_AV051_A700_1.054.00_TWN_GEN1)".
the bootloader is vJB-653b3d3 now.
I think it's just a problem with certain version of the bootloader.
so you may want to either upgrade or downgrade your ROM version and try again.
btw, sorry for my bad English, I'm not a native speaker.

Same Problem here, did you get a solution already?
or anyone else?

Are you using the a700 USB drivers from the HTC support site, this did help me a while back, I had similar issues.

No I use the one from Acer of course. But I will give it a try. I pray that it works. Lol
hmm, don´t find anything that sounds like what I need.. Can you give me a link? would be grateful
Sent from my LT18i using xda app-developers app

I'm on Linux so there's no vendor drivers required.
I received a OTA yesterday, and the bootloader is now vJB-653b3d3.
the unlocking process worked on this version without no problem.
It might just be a random failure I guess......

oxide32 said:
Are you using the a700 USB drivers from the HTC support site, this did help me a while back, I had similar issues.
Click to expand...
Click to collapse
i believe this is an Acer tablet but not HTC.......

Yes it is : -)
Sent from my LT18i using xda app-developers app
---------- Post added at 05:24 AM ---------- Previous post was at 05:16 AM ----------
Sounds good, can you give it to me please?
Sent from my LT18i using xda app-developers app

Sorry I meant acer, having a bad typing day.

Lol OK. No problem. I have this driver, yes but didn't help so far...
Sent from my LT18i using xda app-developers app

Problem Solved.
My Solution was to flash the Recovery into boot-section by typing "Fastboot flash boot recovery.img"
So i was able to get into Recovery and install a FR_Rom
Special Thx to meier2009 from the german Forum Android-Hilfe.de

that would be a weird method.
you can't flash recovery partition but okay with boot partition?

Yes, Don´t know why, but this works for me...
any other methods failed.
don´t matter, i´m Happy again

[Q] Stuck in loop, can't boot recovery or normal. Please, help me. :(

Ok, I can boot into Hboot, but when I choose recovery, I get stuck in a loop on the logo with the red disclaimer.(yes I cleared cache) I tried installing a rom and after that I cannot boot into ANYTHING. Just a loop. Hboot 1.14 I just want a working rom at this point. Stock is fine. But I am totally at a loss right now. Am I screwed? Thank you for your time.
I tried CM, Stock Recover, TWRP.....
HTC One X ATT
Rooted
Bricked?

Try to reflash the recovery and try again. Do you have the Evita or endeavor?
Sent from my Carbon-ize Evita using xda-developers app

Need to be more specific, but try this and for future reference
Are you unlocked? Did you fastboot flash boot boot.img (always do this when on hboot 1.14 or higher)?
Give me all the info you can about your phone. Recovery version, rom that was flashed, but failed, what did you do when flashing the rom step by step?
This should be fixable by ruuing heres a link on the basic directions
http://onexroot.com/one-x-unroot/how-to-unrootunbrick-att-one-x/
I think you can't use 2.20, you probably need a later ruu. Hope this works, but don't do this until after you have provided more info
---------- Post added at 01:28 AM ---------- Previous post was at 01:19 AM ----------
And I or someone better than me at this has given you the OK to.

Tried all of the fastboot methods
I have tried reflashing multiple times, multiple versions of TWRP. was trying to follow this youtube vid ((HD) Samsung Galaxy SIII (S3) Touchwiz for HTC One X - Cursed4Eva)
I only got to install the gapps file from the vid, then it failed to flash anything else.
**tampered**
**unlocked**

Grab version 2.3.3.0. It works just fine for me. Also when you get into recovery you need to flash the ROM and then flash the boot image.
Also if you can, open up fast boot and type "fastboot OEM getvars" and paste the results. It could be getvar if the previous does not work.
Sent from my Carbon-ize Evita using xda-developers app

wtf
Herc08 said:
Grab version 2.3.3.0. It works just fine for me. Also when you get into recovery you need to flash the ROM and then flash the boot image.
Also if you can, open up fast boot and type "fastboot OEM getvars" and paste the results. It could be getvar if the previous does not work.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Fastboot just displays the menu when I type that... 2048
now it says info[ERR] command error !!!
now that I see it... that tutorial I followed was for endevor.. does that mean I am fcked?
2.3 = failed

joeytortorici said:
Fastboot just displays the menu when I type that... 2048
now it says info[ERR] command error !!!
now that I see it... that tutorial I followed was for endevor.. does that mean I am fcked?
Click to expand...
Click to collapse
download twrp 2.3.3.1 or under.
Fastboot flash recovery nameofrecoverzip.zip
fastboot erase cache
Boot to recovery flash roms for evita, extract the boot.img from the rom and flash that. fastboot flash boot boot.img
Good luck.

been there.
exad said:
download twrp 2.3.3.1 or under.
Fastboot flash recovery nameofrecoverzip.zip
fastboot erase cache
Boot to recovery flash roms for evita, extract the boot.img from the rom and flash that. fastboot flash boot boot.img
Good luck.
Click to expand...
Click to collapse
What is a rom that I can use? confirmed for vita.
I can't even get into recovery.

joeytortorici said:
What is a rom that I can use? confirmed for vita.
I can't even get into recovery.
Click to expand...
Click to collapse
omg, get an iphone.
Any rom in the AT&T one xl sections. Evita is the phone we have, endeavor is the quad core one x, cross flashing has a high chance of bricking your device. Have you done any reading before risking your expensive piece of equipment?

...
exad said:
omg, get an iphone.
Any rom in the AT&T one xl sections. Evita is the phone we have, endeavor is the quad core one x, cross flashing has a high chance of bricking your device. Have you done any reading before risking your expensive piece of equipment?
Click to expand...
Click to collapse
Dude, I'm not an idiot. I am pretty tech savy. especially with linux. But i dont know what I did here... if I can get into hboot does that mean it's not bricked?

joeytortorici said:
Dude, I'm not an idiot. I am pretty tech savy. especially with linux. But i dont know what I did here... if I can get into hboot does that mean it's not bricked?
Click to expand...
Click to collapse
If you're familiar with linux, consider the stickies in this forum man pages and READ.
If your phone can make it to hboot, it's not bricked.

exad said:
If you're familiar with linux, consider the stickies in this forum man pages and READ.
If your phone can make it to hboot, it's not bricked.
Click to expand...
Click to collapse
. I HAVE READ. I joined this forum to get help. My situation is unique. I have tried everything. I just can not boot into recovery or normal os. kind of a bid deal.
I cant even use fastboot oem getvar
I get an error.

I disagree.
Download recovery check md5
Fastboot flash recovery recovery.img
Fastboot erase cache
Make sure the recovery you're downloading is for the right phone too. One xl aka Evita.
Sent from my One X using xda app-developers app

sdfsdfsdfsd
exad said:
I disagree.
Download recovery check md5
Fastboot flash recovery recovery.img
Fastboot erase cache
Make sure the recovery you're downloading is for the right phone too. One xl aka Evita.
Sent from my One X using xda app-developers app[/QUOTE
Literally done that 10 times now
Click to expand...
Click to collapse

joeytortorici said:
. I HAVE READ. I joined this forum to get help. My situation is unique. I have tried everything. I just can not boot into recovery or normal os. kind of a bid deal.
I cant even use fastboot oem getvar
I get an error.
Click to expand...
Click to collapse
First of all you should have done more research before flashing stuff on your phone. Youre lucky your phone is still alive after flashing that international rom buddy.
Second the command fastboot oem getvar is incomplete. THats why you are getting the error. Getvar must be followed by something like fastboot oem getvar cid.
So one more time.
First make sure you have plenty of battery
1 Boot into hboot.
2Select fastboot and press the power button.
3 Open fastboot in command prompt and and type "fastboot devices"
4 If it shows a serial number it is recognizing your phone. If not try different cables and ports
5 IF recognized type "fastboot flash recovery ( navigate back to your fastboot folder and drag the recovery.img into the command window. The recovery.img MUST be in the same folder as the fastboot program!!)"
6 Press enter.
7 Type "fastboot erase cache"
8 Type "fastboot reboot recovery"
If this doesn't work you have another problem. I would suggest running a ruu if your're not super cid. To check super cid boot back into fastboot mode and type "fastboot oem getvar cid" If it shows "11111111" you have super cid and cant run a ruu. If not you can run a ruu.
If the steps above did work and your're now in recovery. Then.
1 Wipe everything. Cache/dalvik cache/system/android secure/ and sdcard.
2 Mount sdcard and transfer your rom to your sd card. MAKE SURE THE ROM IS FOR THE DUAL CORE ONE XL EVITA model. For now just stick with a sense rom. If you want a suggestion I suggest you use this one for now. http://forum.xda-developers.com/showthread.php?t=2181891
3 Once transfered. Safetly unmount sdcard and flash the rom.
4 Select reboot bootloader in recovery.
5 Once in hboot select bootloader.
6 Open the rom you just flashed and copy the boot.img that is in the root of the zip to the folder where you have fastboot.
7 Type "fastboot devices" to see if the pc recognizes the phone.
8 If you see a serial number the pc recognizes your phone.
9 Type "fastboot flash boot (go back to explorer and drag the boot.img from the fastboot folder to the command window."
10 Hit enter
11 Press the vol down button and navigate to power off.
12 Hit the power button.
13 Once phone is completely off press and hold the power button till the phone comes on.
14 If it still boot loops a ruu is your only option.

fmlll
Installed HTC Sync, RUU up and running. Thanks guys. Sorry for so noob. nearly trolling.

One XL no onger recognizes unlock.bin from HTC DEV

Good day everyone.
I relocked and installed stock RUU (4.0.3) on my Evita since I had that failing zip install though TWRP. It worked fine but when I tried to manually install the latest RUU (Android 4.1) it failed. Now I decided to unlock it again and start to flash custom ROMs, problem started.
1.) After flashing boot, recovery and custom rom (tried it with CM 10.1 and JellyBam), it would go only up to the boot image (HTC) and stay on there forever. Cleared everything that I could clear on the recovery and cleared fastboot cache.
What I did, relocked it again and tried running the stock RUU (through the computer) and shows error and won't complete.
2.) Now, phone no longer recognizes the Unlock_code.bin from HTC dev. I tried manually flashing it in fastboot and as well as using the All-in-one-tool for Evita, it would somehow show that it went through on both but looking at my phone, it stays: Relocked. Tried it with at least three unlock bin files to no avail.
3.) Other than that, turning the phone off and back on would go straight to bootloader. When I select Recovery, it would go back straight to fastboot mode. Tried to flash recoveries again, and would get this:
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.5.0.0-evita.img
sending 'recovery' (7992 KB)... OKAY [ 2.140s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.871s
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.2.0-evita.img
sending 'recovery' (7460 KB)... OKAY [ 1.692s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.370s
Now I'm stuck with a phone with no OS. Please help. I appreciate your time.
Here's my phone info.
AT&T HTC One X
S-ON
HBOOT - 2.14.0000

Getting a new code only requires fast boot. So just get a new unlock code.....
*edit*
Sorry I misread. This happened to me. Just simulate a battery pull by pressing and holding power and try again. Keep doing that over and over. Eventually, it will work.
Took me about 10-15 tries once.
Sent from my One X using xda app-developers app

Also try to lock the phone even if it tells you it is already locked.
fastboot oem lock
Do that prior to attempting the unlock after full power cycle. Sometimes that gets the device back on track, dont worry too much this issue is not exactly new and after a bit of dicking around the phone will unlock again.

Thanks for your responses!
Yeah, it did. After a number times requesting for unlock bins and re locking, finally it was unlocked.
Now I now have problem #1 from OP. It actually goes to HTC boot screen, stays there for a couple of seconds then reboot. It's been doing that in a loop. Flashed three different ROMs and three different versions of TWRP and phone still does the same thing.
Found my mainver to be 3.18 which I suspect have been changed when I attempted to run the 4.1 RUU (this was before I tried to unlock the bootloader). Downloaded the said RUU from two different sites just to be sure. None of those have worked.
So I found a thread here in XDA saying that this could be the reason why I couldn't boot any of these ROMs.
Any thoughts/help would be greatly appreciated.

Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app

You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita

Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app

exad said:
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
timmaaa said:
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Click to expand...
Click to collapse
twistedddx said:
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
It's actually my fourth device. Did flash boot.img all the time. That's why it's kind of frustrating.

Any thoughts about damaged eMMC? Just hypothetical.
I don't know if it was a brick but I had an issue before where this HOXL didn't boot up after flashing a wrong kernel. Didn't even light up when plugged to power and had to re-flash the eMMC block using that WIP method. It went back to life.
Might need to try that again. Would that be possible? Still have to download live ubuntu, though. The one I used before got corrupted.
What I did so far:
-relock
-unlock
-erased fastboot cache
-flashed boot.img ( from the custom ROMs that I've tried )
-flashed twrp ( 3 versions )
-wiped every wipe option i could see
I already have tested at least 6 ROMs on this device with no issue with TWRP.
I had ViperXL installed before this happened. I wiped everything out and tried to flash the ATT Android 4.1 RUU and everything got screwed.
edit: i typed the capcha on the title box. lol

You're still s-on right?
Sent from my One X using xda app-developers app

exad said:
You're still s-on right?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.

EjWilkes0121 said:
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
Click to expand...
Click to collapse
Get twrp running 2.3.3.1 and flash any sense Rom then s-off
Sent from my HTC One XL using xda premium

I'm going to try again once I get home from work.
Thanks for all your responses guys.

Done it all.
Relocked, intalled RUU - fail.
Unlocked, wiped everything, installed ROM, erased fastboot cache, flashed boot.img, erased fastboot cache - bootloop.
Tried using CWM and same thig happes - bootloops after flashing rom and boot.img
However, I just noticed something.
Whenever I get to flash a zip through recovery, process seems to just complete in no time. I have flashed multiple ROMs and one could really see progress shown on progress bar on both recovery flashing( CM10.1, JellyBam ) and through Aroma installer( CleanROM, ViperXL ).
When this problem started, entire process would initiate, pauses for few seconds then it completes. Can't see the progress bar move across.
I might be going out of topic here but I'm desperate in having this fixed.
Your thoughts and ideas means a lot.

Are there any roms you can boot?? How are you downloading the files? On a pc? Did the md5 match. Maybe the usb wire has a defect and screws the file upon transfer. Your have a really strange issue. I'll flash out of boredom and never had that happen, Even with roms that do nothing more than boot.
And your running twrp 2.3.3.1???
Sent from my HTC One XL using xda premium

I think the recovery is most likely at fault here.
Make sure it's twrp 2.3.3.1: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Use a USB 2.0 port just to be safe.
check md5 omg so important!
Code:
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.3.3.1-evita.img
fastboot erase cache
fastboot reboot bootloader
Select recovery
Check the md5 of the sense rom you downloaded
Extract boot.img from rom.
Transfer the rom zip to the phone.
wipe cache, dalvik, system and factory reset in recovery
install sense rom
reboot to bootloader
Code:
fastboot flash boot boot.img
fastboot reboot
Do all that and then tell me what happens.

Back to life!
A huge thanks to you guys! Big time! :victory:
It could be the recovery that screwed it up. Been trying TWRP 2.5 and TWRP 2.2 most of the time. I gave TWRP 2.6 a shot and that made a successful install. I flash ViperXL 3.2.7 + ElementalX 6.7 and phone's back to life!
One thing i noticed. After I S-Off'ed, phone's kind of jerky using normal use. One noticeable thing is the lock screen that doesn't respond after waking, takes 1-2 sec to respond when swiping the lock ring. Big prob for me, battery stuck at 77% even when charged or used heavily. Random reboots also happen. Maybe have to read the entire FacePalm S-Off thread this week. LoL. For now, back to S-On, phone works perfect.
Again, thanks so much for your help guys! Won't be missing any Thank button that you got. :laugh:

I found current sense roms work better with latest firmware so s-off ruu to 3.18 and then see how things run.
Sent from my HTC One X using xda app-developers app

Shield tablet wont boot beyond fastboot menu :'(

I hope you guys can help me, i have been wandering around blogs forums to find a fix to this issue but to no avail. I got my replacement tablet about a few month ago. I decide to keep the old one and install custom rom on it. The old one is still usable now, but the replacement tablet is dead to me. One day i restart the repl tablet and it just stucked at the fastboot menu. When i choose to go into recovery mode. Nothing happened except a blink of message said that cold linux booting failed. So i try to unlock bootloader to flash it using adb command. Now it wont let me unlock boot loader giving me an error same as the guy here ( i cant paste an outside link here, google : Shield Tablet (LTE) won't boot beyond fastboot, fastboot OEM)
Ps : sorry for bad english im from Malaysia and also im tech newbie

flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.

DreadApex said:
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
Click to expand...
Click to collapse
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter

RaybenBB said:
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
Click to expand...
Click to collapse
Hi,
The "fastboot oem unlock" command don't work?

Elpatii said:
Hi,
The "fastboot oem unlock" command don't work?
Click to expand...
Click to collapse
Nope, also cant detect device using adb devices command. Tried same command in the other shield tablet, work just fine. Its not driver problem.
Tried fastboot oem unlock, and somehow it ask me on the shield to unlock or not, choose unlock and this error occured
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 3.736s

Maybe that you can flash the stock image from NVIDIA (https://developer.nvidia.com/shield-open-source)

Elpatii said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse

RaybenBB said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
I think that's the best solution for now!