Database Info

[Q] Boot loop, can boot to twrp/fastboot, but cant flash any roms.

Okay so heres the deal. Bought a new evita from a dealer. Dont remember/have what the stock software was, but it was booting with an att rom and all the bloatware. I downloaded the all in one eztoolkit and unlocked the bootloader successfully. Heres my problem, I can get into fastboot and twrp, but all of my flashes fail regardless of what rom I flash. I tried cm 10.2, 10.4, and 11 beta and they all failed. Then I tried to revert using both att ruus I could find, including the 2.20 and 3.18 updates directly from att. Both of them reboot to the ruu loader and appear to be working, but fail citing the incorrect software version. I assume its because I manually changed the recovery and flashed boot.img files from each of the roms I tried to flash, but I am not certain. Heres is the getvar information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW304126
(bootloader) imei: 359691042468010
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3897mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can this be solved by flashing the correct rom, and if so can you direct me to it? Otherwise, how can I fix this?
Thank you.

edit: flashed cm 10.0.0 and related gapps after manually flashing the boot.img and I got it to boot.
Going to try to s-off so I can be done with all this garbage.
edit: Got it booting, got s-off. Still on 10.0.0 with root and s-off. Not sure where to go from here unless anyone can give me further direction. I'd prefer to have the latest cyanogen etc, but I am ok with this if I cant go any further.
Thanks all !

Where are you downloading your ROMs? You mentioned earlier that you flashed cm10.4 but there is no such ROM for this device. You need to be careful about where you get your ROMs, flashing a ROM that isn't intended for this device can easily result in a brick.
Your ROM flashes were failing because your firmware is too old, it does state pretty clearly in the install instructions on the cm threads that you need to update your firmware via the 3.18 RUU. So you need to download the 3.18 RUU and run that which will update your firmware. Here's a very useful thread which details how to run an RUU.
After you've done that you'll need to flash TWRP again. If you want to flash the latest cm, which is cm11, you need to install the modified version of TWRP 2.6.3.0 recovery which can be found in our Original Android Development section. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter TWRP and flash your ROM + gapps. Because you're new here I'd suggest you click the Everything Evita link in my signature and bookmark it, it contains links to basically everything for our phone. You should also click the other links in my signature and read those threads, you'll find them very helpful. Here's a few important links for you too:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
One XL Q&A
http://forum.xda-developers.com/forumdisplay.php?f=1572
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Make sure you only ever download ROMs from the development sections I've linked there, many people make the mistake of wandering into the HTC One X forum and flashing those ROMs, many of those people bricked their phone. That might seem confusing but you don't have the HTC One X (Endeavoru), you have the HTC One XL / at&t One X (Evita). If you have any further questions just ask either here or in my q&a thread (link in my signature).
Sent from my Evita

[Q] unable to flash ruu via .exe or fastboot

ive been trying to resolve this for two days in an attempt to avoid having to post this thread
sooo here we go-
the phone is k2plc_cl. in a haste/ not caring/ thinking i could maybe get the data working fashion, i flashed viper to my oneSV.
unable to get any signal, i tried relocking my bootloader, and flashing the latest ruu.exe- it sat on sending everytime
so i unlocked my bootloader and tried flashing via fastboot.
recovery and boot flash, radio gives me the remote not allowed like the bootloaders locked.
im not 100% sure on what to do right now actually...
i have the OTA_K2PLC_CL_JB_45_S_Cricket_US_2.04.1050.2-1.03.1050.7_release_321361523g7wih6zk058h5.zip
this needs flashed through stock recovery or fastboot?
fastboot gives me data too long, so i think recovery
but
i flash recovery img. in fastboot, it says OK, and reboots and hangs on the white htc screen
c:\android\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.12.00.1029
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: k2_plc_cl
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8012000
(bootloader) cidnum: CRICK001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3763mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any help will be GREATLY appreciated!:good:

Remove your imei & serial, not needed in public.
You need to downgrade hboot first, if you wanna flash the Ruu.
As you are S-off, i would give the last firmware.zip a try. Maybe this solves the issue.
http://fotadl.htc.com/OTA_K2PLC_CL_....04.1050.5_release_343402dpsh8ror12wwdww2.zip
Download the OTA, inside you'll find a firmware.zip. Extract it from the OTA file and rename it to PL80IMG.zip.
Copy to external sdcard, boot into bootloader, wait for scanning the files and confirm to flash with vol+ button. Wait until its finished, can take some minutes.
Reboot and see if your problem is gone.
Some sidenotes: Make a backup before in recovery. And after flashing the firmware you will have stock recovery, so in case you will need TWRP, flash it with fastboot.

old.splatterhand said:
Remove your imei & serial, not needed in public.
You need to downgrade hboot first, if you wanna flash the Ruu.
As you are S-off, i would give the last firmware.zip a try. Maybe this solves the issue.
http://fotadl.htc.com/OTA_K2PLC_CL_....04.1050.5_release_343402dpsh8ror12wwdww2.zip
Download the OTA, inside you'll find a firmware.zip. Extract it from the OTA file and rename it to PL80IMG.zip.
Copy to external sdcard, boot into bootloader, wait for scanning the files and confirm to flash with vol+ button. Wait until its finished, can take some minutes.
Reboot and see if your problem is gone.
Some sidenotes: Make a backup before in recovery. And after flashing the firmware you will have stock recovery, so in case you will need TWRP, flash it with fastboot.
Click to expand...
Click to collapse
flashing the pl80img brought the phone back on, but its still on the viper rom.
so, im going to downgrade hboot, and try to flash the ruu.
thanks for the advice too!
update- i got it back to normal! thanks
i downgraded by renaming the firmware zip to pl80img, put it on my sdcard, and let the bootloader take it from there.
then i installed cwm and flashed the zip that you made from the cricket backup.
geez ive been stuck on this for 2 days hahaha

ok this phone is confusing me sooo freaking bad
so i see that you need to make sure your bootloader is equal(?) or lower than that of which your updating to..
im at 4.1.2, hboot 1.01.000, and software version 2.04.1050.3 trying to update to 2.04.1050.5
and it fails with an 'error in zip file'
i have stock recovery, unrooted, unlocked and s-off.
ive read i do not need to relock to update right?
im trying to just update to 4.2.2 right on the phone but im def at a road block haha

I thought you want to run the RUU to get back stock?

old.splatterhand said:
I thought you want to run the RUU to get back stock?
Click to expand...
Click to collapse
Yes after finally getting the ruu to work! I had to relock, flash newest firmware zip from your list, unlock, download and flash ota then ruu worked. in between I was trying to just flash the ota zip and recovery would abort no matter what
But
Man Im happy to be back on 422 hahaha
And thanks a lot for being there to help everyone out btw :good:
This process finally makes sense to me haha :cyclops:

Stock AT&T XL won't boot after factory reset

I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.

He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)

Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img

I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon

Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?

Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.

I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.

Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon

Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.

Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382

[Q] Rogers HTC One X help with customer recovery issue...

Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?

If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong

nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.

13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved

Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?

audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.

I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!

HTC One S Reboot Loop

Hello,
I recently dropped my HTC One S into a glass of water. It kept on working so I thought I'd got away with it, but then a few hours later it rebooted and now won't boot beyond the white "HTC" screen before rebooting again. I've tried drying it out but it's still doing it.
The phone had not been modded or rooted before, I just used the stock HTC OS which came with it. I can get to the bootloader screen and have tried various things to get it working but nothing seems to have worked. I've anyone can point me in the right direction (or tell me I've no chance) I'd be very grateful. I've done the following:
Tried the stock recovery, gave the same reboot loop.
Tried the "clear storage" and "factory reset" options, same reboot loop.
Connected with USB Fastboot - seems fine and I can see the device from my laptop
Unlocked the bootloader - I now have *** UNLOCKED *** at the top of the screen
Flashed a custom recovery (I've tried CWM and TWRP, various versions) - seemed fine and Fastboot suggested that the flash had worked, but when I try to load it I get the same reboot loop. The only difference is that I now have some red text on the HTC screen when starting recovery: "This build is for development purpose only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
I'm at a loss as to what to try or where to look now. I saw one post which suggested that the stock ROM may be detecting the invalid recovery and trying to overwrite it, and others that suggest using an RUU to get the phone back to original state, but I can't seem to see one which matches the info I get from "fastboot getvar all". My thinking is that if the recovery doesn't even work then something is wrong with the phone itself, but is there a way I can tell what the phone is doing or any logs I can see? As Fastboot doesn't have access to files in storage I can't tell if there's anything there.
The phone's info (from fastboot getvar all) is below, and if anyone can suggest anything I'd be very grateful.
Thanks,
James
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.13.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.771.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24SW409116
(bootloader) imei: 359901047356445
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-26dff973
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

From what you describe, it surely sounds like a HW fault. Reflashing will not fix it. You can always try (in the unlikely case that the flash memory was somehow rewritten), but as you already have tried it, it means your phone is most probably bricked. Sorry.
Some expert may want to confirm my conclusion.
As a last resort, I would take the phone apart, and leave it like that for a day or two, to make sure any remaining moisture has a change to evaporate - and then re-assemble. It is possible that some of it could be shorting an address line or something? More likely something is corroded beyond repair.
EDIT: It may be possible that the hboot was damaged / rewritten but the flash memory is still intact. That may be fixable, but quite difficult. It means purposedly "bricking" the device further and manually registering device nodes in Linux and directly writing into them.... I think I saw a guide somewhere. This will not be easy for the average user, and there only a slim chance it will actually work.

Thanks. That's pretty much what I thought but thought I'd ask in case someone had any bright ideas. I've already ordered a new phone which should get here tomorrow, so I don't really want to spend hours trying to get it working when it's probably bricked anyway.