Database Info

[Q] trouble with my htc one x rogers

hello, ive got this rogers htc one x that is stuck in a bootloader loop, anyway heres my info i really need help with this:
C:\adb>fastboot getvar all
(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.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW307580
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(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: 1.031s
C:\adb>
actually its stuck in qhusb_dload

How did it get in this state?
Can you not get to bootloader?

slickwidnick said:
hello, ive got this rogers htc one x that is stuck in a bootloader loop, anyway heres my info i really need help with this:
C:\adb>fastboot getvar all
(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.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW307580
(bootloader) imei: 32
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(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: 1.031s
C:\adb>
actually its stuck in qhusb_dload
Click to expand...
Click to collapse
well now ive managed to mess around and got aokp_evita-rohan-milestone6.4 rom loaded on my phone, but its stuck in a boot loop at the boot animation... ahhh, this is frustrating.....

How did you get it out of QHSUSB_DLOAD mode? You're s-on so you probably just need to flash the boot.img from the ROM zip via fastboot to get it to boot.
Sent from my Evita

timmaaa said:
How did you get it out of QHSUSB_DLOAD mode? You're s-on so you probably just need to flash the boot.img from the ROM zip via fastboot to get it to boot.
Sent from my Evita
Click to expand...
Click to collapse
just tried flashing the boot.img from the rom twice to make sure and it still bootloops at the boot animation...
and for how i ended up getting it off of qhusb_dload, i just downloaded all of what i could find for the rogers htc on x and tried flashing this, flashing that, and i dont really know exactly what it was that kicked it out of that mode...
im still confused as to why it wont boot after flashing the boot.img from the rom..

While "flashing this and that" has gotten you out of trouble this time I wouldn't suggest doing that again in the future, it was likely a huge fluke and flashing random things is a pretty bad idea. What ROM are you trying to flash?
Sent from my Evita

timmaaa said:
While "flashing this and that" has gotten you out of trouble this time I wouldn't suggest doing that again in the future, it was likely a huge fluke and flashing random things is a pretty bad idea. What ROM are you trying to flash?
Sent from my Evita
Click to expand...
Click to collapse
well originally i was trying to flash i think it was eragon and i got as far as flashing boot.img and then the rom wouldnt flash. now i have aokp_evita-rohan-milestone6.4 rom loaded but it bootloops.
should i try to flash another rom and keep trying till i find one that will startup?

What is eragon? If that's a ROM you've flashed a ROM that isn't for this device, no such ROM exists for the Evita (HTC One XL / AT&T One X). You're lucky you didn't brick your phone. Have a look through our development sections which you'll find here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Don't ever download ROMs from anywhere except within those two development sections or you're on a dangerous road to phone bricking land. Find a ROM you think you'll like, read the OP, make sure you meet any requirements it lists prior to flashing, and flash it.
PS. You should really remove your IMEI number from your first post, and the other post where you quoted it. Don't ever post your IMEI publicly.
Sent from my Evita

[Q] Made a mistake with firmware, now ROMs won't boot

My HTC One S is stuck in a bootloop. I'm very new to this stuff.
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I can currently start the bootloader, which states S-ON, TAMPERED and UNLOCKED.
I can install recoveries. Right now I have TWRP, and I think it works the way it should.
Tried installing a stock ROM, tried CM11 (which is what I started with) and CM10.2.
I updated the firmware which is what I think caused the issue.
Between every attempt, I cleared cache and dalvik before and after each ROM flash, then rebooted.
Every ROM puts me into a bootloop.
Please help me.

Ricaz said:
My HTC One S is stuck in a bootloop. I'm very new to this stuff.
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I can currently start the bootloader, which states S-ON, TAMPERED and UNLOCKED.
I can install recoveries. Right now I have TWRP, and I think it works the way it should.
Tried installing a stock ROM, tried CM11 (which is what I started with) and CM10.2.
I updated the firmware which is what I think caused the issue.
Between every attempt, I cleared cache and dalvik before and after each ROM flash, then rebooted.
Every ROM puts me into a bootloop.
Please help me.
Click to expand...
Click to collapse
Easy fix your going to have to flash a boot.img from the rom
You have to do this because your S-on if you were S off you would not need to flash the boot img yourself
follow the instructions here http://forum.xda-developers.com/showthread.php?t=1604677

dave1970 said:
Easy fix your going to have to flash a boot.img from the rom
You have to do this because your S-on if you were S off you would not need to flash the boot img yourself
follow the instructions here http://forum.xda-developers.com/showthread.php?t=1604677
Click to expand...
Click to collapse
I don't have access to a PC with Windows on it, unfortunately. Can't I do it without the All-in-One tool?

Ricaz said:
I don't have access to a PC with Windows on it, unfortunately. Can't I do it without the All-in-One tool?
Click to expand...
Click to collapse
I have only installed through a PC using this toolkit but the links have been removed anyway to download it.
There are other tools but I have not used them I'm sorry

A little update:
First, recovery stopped having control over the SD card somehow. Right now I can't even boot into recovery anymore.
I think I need to run RUU, but I don't know which one. I have downloaded this one off androidruu.com:
Code:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
because it matches my radio version, but I don't know about the rest. Currently in the process of installing Windows 7 on a virtual machine so I can run this thing (why the hell is it a .exe file?!).
Does anyone know which one would work for me?

[Q] Phone will not boot into recovery/ bootloops

This morning when I woke up my phone began to bootloop without anything but me turning on the screen. At first it would happen every few minutes but it has progressed to happening whenever it isnt in bootloader.
So far I have tried flashing a new rom, but then the phone began to bootloop in the middle of recovery, which is something Ive never had to deal with before. From there I figured the problem is further down and I tried to flash a new recovery to no success. now to where I am,
I can flash a recovery, but when entering it it takes me back to bootloader. The odd thing is, if I let it boot normally, after a few boot loops, the phone will boot rom with safemode to a half broken rom that will bootloop after a minute. I tried flashing stock boot and recovery but that didnt work either. Finally ive been flashing new firmware and boot imgs with it making no difference. What else can i try?
tl;dr recovery wont boot, stuck in bootloader, wat do?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43FSF01988
(bootloader) imei: 990004996433284
(bootloader) imei2: Not Support
(bootloader) meid: 99000499643328
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.019s

Sukhol said:
This morning when I woke up my phone began to bootloop without anything but me turning on the screen. At first it would happen every few minutes but it has progressed to happening whenever it isnt in bootloader.
So far I have tried flashing a new rom, but then the phone began to bootloop in the middle of recovery, which is something Ive never had to deal with before. From there I figured the problem is further down and I tried to flash a new recovery to no success. now to where I am,
I can flash a recovery, but when entering it it takes me back to bootloader. The odd thing is, if I let it boot normally, after a few boot loops, the phone will boot rom with safemode to a half broken rom that will bootloop after a minute. I tried flashing stock boot and recovery but that didnt work either. Finally ive been flashing new firmware and boot imgs with it making no difference. What else can i try?
tl;dr recovery wont boot, stuck in bootloader, wat do?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43FSF01988
(bootloader) imei: 990004996433284
(bootloader) imei2: Not Support
(bootloader) meid: 99000499643328
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.019s
Click to expand...
Click to collapse
When your phone boots up and before it reboots... Does it appear to get network signal at all?
Have you tried one of my ruu yet?

dottat said:
When your phone boots up and before it reboots... Does it appear to get network signal at all?
Have you tried one of my ruu yet?
Click to expand...
Click to collapse
Thanks for the quick reply
Yes, it seemed to have connected to the network, in the few seconds i have, i went to settings and it was.
i tried the files from http://forum.xda-developers.com/showthread.php?t=2723159 if that matters,
I tried to use your auto ex for the ruu but it would not work ill try it manually in a little bit
UPDATE: Flashing the RUU seems to have solved my problem, i could boot into recovery and there werent any bootloops. Thanks for the suggestion, I was running out of ideas

Rare bird: Stock Tmobile ROM 3.14.531.19

Hi all.
I have a completely stock never-been-modified HTC One S that has started freezing on boot.
No, I never tried to root it, unlock the bootloader, or any other stuff.
I would like to get my data off it, but because I never rooted it, I can't extract said data using ADB (unless you know a trick that I don't).
My options seem to have come down to flashing something to get it to boot... ROM, kernel, radio, what do you think?
- I can get into Fastboot, Bootloader, Recovery, etc.
- I can ADB to the phone while it is boot-stuck (so probably not the kernel?).
I want to get my info off of it and if I can make it boot all the way in, that's an added bonus.
To that end, have you ever seen a 3.14.531.19 ROM that wasn't wrapped up in an RUU? I was willing to try RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2 but it says that it'll wipe all my info.
Here's my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.531.19
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW404294
(bootloader) imei: 359902041072822
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3920mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
What say you?

If your phone is bootloader locked, S-ON with original recovery, you're out of luck... The complete boot sequence is secured and if you try to unlock, all data will be wiped off.
The only first step to get to your data would be to root without unlocking the phone, but I can't see how to do that if you can't start the OS.
One thing you can try is to get to the HTC recovery and wipe cache (I think this is possible).

Thanks for the reply.
I have already wiped the cache (forgot to mention that in the OP, sorry) and it didn't make a difference.
It sounds like what I was expecting to hear: My data are beyond recovery... Which is a bummer.
Anyone else have anything to add?
Some miracle cure, maybe?
I'm going to hold off on my attempt to unlock the bootloader another few days in case someone has a suggestion to offer.

A final bump in the hope that someone might have a solution.
Thanks!

HTC ONE MINI, NO OS, no ADB, Bootloader Unlocked, TWRP and fastboot works...

Hello,
I will try to explain what happened, although I am not sure... I tried to root my phone so I can do a data recovery as I lost all data... at this stage phone still rooted fine, no contacts, no sms, no nothing... it looked like a factory reset.
1. I used htcdev to unlock bootloader
2. I flashed recovery-clockwork-touch-6.0.3.6-m4.img to try and load the superuser.zip to root my phone... I tried several zips, but none of them rooted it... I had to use adb through: cmd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>, at this stage phone still booted normally and no problems... so I used adb push to install zips to root it... none of them worked...
3. I realized that it might be the clockwork recovery that is the problem, so I decided to change the recovery to TWRP... and this when something went wrong as the phone wouldn't reboot into normal mode anymore, only bootloader... I though giving it a factory reset would solve the issue, so I did... nothing happened...
4. I managed to flash twrp-2.8.7.0-m4.img recovery and discovered that there is no OS and basically apart from the bootloader theres nothing else on the phone...
I understand that I need to do a RUU flash, however I cannot find the one I need. I followed this thread, however I cannot seem to find the RUU that I need
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
I also tried fastboot flash zip sense6_firmware.zip, it cannot do it... gives me a fail error...
and now I am stuck as adb doesnt work to push files from either the unlock folder, nor the htc sync one or C:\Program Files (x86)\Android\android-sdk\platform-tools>
This is my first root attempt (maybe I shouldn't do one and won't in the future ) as you can see, but maybe I am just missing something very obvious and easy...
I'd like to get the original soft back on the phone but even if its still stored on it, I don't know how to get to it and make it work...
Phone details
astboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.28.40e.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
If you can, please help me!

I have exact same problem! please help

Alpha1BA said:
I have exact same problem! please help
Click to expand...
Click to collapse
hello, what version are you running?

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.28.40e.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4317mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Alpha1BA said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: 1.28.40e.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4317mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Looks like we have the same version... Honestly, I spent so much time on trying to S-off it and fix it, I think I'll just give up... I found a UK based service that does it for £20... not sure it's worth the time and effort to fix it ourselves... if you're UK based, msg me and I'll give you the details if you're interested!

Hi there, if you unlock the boot loader you will wipe all data from your phone. You confirmed that with the swipe to agree unlock. Recover your data might be difficult but you can give it a try even from Recovery itself.
The easiest way to get your phone back to work is the appropriate RUU for it, but with unlocked boot loader and TWRP booted you can try to put the ROM via USB on the Phone. Flash it via TWRP and since you where S-ON you need to flash the boot.img for your chosen ROM manually the same way you did it for recovery (fastboot flash boot boot.img). If your boot.img does not do well with your ROM you will get into a boot loop. hope this helps.