yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
---------- Post added at 05:24 PM ---------- Previous post was at 04:47 PM ----------

@absolutely grim

hi,you know me right?i am the guy who flashed p5 file in mmcblk0p5 into mmcblk0p4.i tried a lot to find a soln for it by searching different threads but still no go.i am right now not staying in US and so i cant claim for the warranty .so i am helpless.i tried whole instructions in jet thread and even in ur thread but nothing comes up to be working.

even ls /dev/sd* is not showing up any change.i tried thishttp://unlimited.io./qhsusbdload.htm too but no go.i came to know that you are working with some guys on 2.20 who bricked their phones.initially i have successfully downgraded my hboot to 1.09 and installed an 1.73 ruu over it,rooted it and now bricked my phone.so i hope the job will be easy as i am on older hboot.can you please help me
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
The fix is to manually dd the correct data back to the emmc through the disk at the correct address (ie: /dev/sdx instead of /dev/sdx4). I calculated this address already. However, before we were able to confirm the location and then write the data, your phone stopped enumerating the partitions. Meaning we currently have no way to access the phone to read or write.

I did not have time yesterday to write out step by step instructions. Hopefully I can do that during work today. Of course they will do nothing unless your phone starts to connect in qdl mode again and enumerate it's partitions.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
thanks for replying.is there any way other than putting the phone in qdl mode to enumerate the partitions
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
No. Once it's bricked that is currently the only way. We are working to develop another way, but it's uncertain if that will ever be possible.

I wish I had better news, for you and 2 other people currently in the same situation. It's extremely frustrating to know that the phone works but there is nothing we can do.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
what can be the reason for the phone to behave like that. is it the same for everyone or only for me?.whatever may be the case.i thought only i did that(flashing p5 file from mmcblk0p5 to mmcblk0p4),and so its the case with me alone.but i came to know that this is the case for guys who took 2.20 ota update.

i have full faith on you guys that you might bring a soln for this.but anyway thanks for wt u have done.mind posting instructions bcause may be the phone shows up its partitions or if it never does by this way then you know wt to do.

thank you very much
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Each phone was bricked by different reasons. However, once bricked there are only 3 possible outcomes:

1) qhsusb_dload (aka qdl) mode.

This is the result of an error that occurs AFTER the hardware initialization. The phone is functional, but can not run hboot. This state allows read access and limited write access to the emmc flash over usb. This is what we are able to use to recover or "unbrick"

2) ehostdl. Emergency host download, this feature is built directly in to the processor. As the name suggests, this is a last resort. This is the result of a software failure to initialize the hardware or failure to load software needed to control hardware (aka firmware). It will load a special file in to memory which will then enable qdl mode. This can not be used without a processor specific file that is created by the manufacturer along with the other firmware. We do not have access to this file.

3) total brick. This is almost exclusively due to hardware failure. Nothing can be done except physically repair of broken components.

Most bricks for this phone result in #1. If we can identify the cause then we can usually fix the problem.

Some bricks, often caused by bad ruu, ota, or mismatched firmware flashes result in #2.

Since you over wrote your extended partition table, your phone can't load all the firmware and results in #2. I suspect your phone never was in qdl mode, but instead the /dev/sdb1, /dev/sdb2 and /dev/sdb3 were probably your thumb drive.

Note:

These explanations are overly simplified, but should help most people understand the different "bricks" without getting in to more technical details (which I can provide if anyone wants)

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
so what do you suggest me either to give my phone to htc(which i cant do right now) for service or wait for you guys to find a soln for this problem

ah btw i got ubuntu 12.04 desktop i386 version installed in my pc.now i tried your instructions again.this time it showed little bit different results from the past.it showed two lines extra(defenitely not sdb1 or sdb2 or anything like that).i will post as soon as i finish writing my semster exam.

anyway thanks for the help
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
If you can wait a day, tomorrow I can look at getting on team viewer and doing it for you? Or maybe understand what's going on a little better.
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
ofcourse i will wait.i just lost hope that i can never recover my phone.but you gave me little hope.btw wt abt team viewer.i understand it as a chatting application via lan or wlan(sorry for my noobness).
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Unless your phone begins to enumerate the partitions, there isn't anything that can be done.

I've heard of team viewer, but not sure how it works. Although it sounds like you would need your linux computer to connect to the internet. I'd be interested in learning more about it.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
yeah i understand that my phone needs to enumerate its partitions to recover,but what i am asking is ,is it ever possible like this or do i need to do more to get it done.i mean i met all the requirements like having ubuntu 12.04,following your instructions,having usb 2.0 port as in everything.

so wt i am asking is will there be a soln in the future or is it just impossible.

sorry for asking you so many questions,but i just cannot digest that i am not able to use my phone.
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
In your situation, we are totally dependent on the phone. Those requirements are so we can work with the phone, but only if it enters that state. We have no magical way to make it cooperate.

By copying p5 on to p4 you totally erased the extended partition table. The only way we can fix it is with access to the emmc flash drive. We only have access if the phone makes it available.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
well may be i am very unlucky i could not recover my phone eventually.but do you mind posting how the output should be(exactly) when the phone enumerates its partitions and also the instructions.please may be i will not give up for now atleast
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
I'll pm you tonight with details
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
If course. I have about 75% of the instructions typed up, I just need some time to finish and double check to make sure they are correct.

Is the battery on the HOX removable? If it is, take it out, wait about a minute, put it back in, then plug the phone in to the wall charger for a couple hours. You will not see the light come on, but it will charge.

Then wait till someone is helping you before trying to connect to the computer.

It's probably a long shot, but sometimes this will force the phone to completely reboot in to qdl mode.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] :
not 'removable' but you can take apart the phone and disconnect the battery
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Ok, just like my evo lte.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
no it cant be removed and also its difficult for me to disassemble it.but i have read this somewhere that we just trim the usb cable and connect to it 6 100k ohms resistors connect the usb to phone so that will force the phone to be in qdl mode.

and also i have one more doubt,when i run this cmd watch -n.1 lsusb,ubuntu shows it up as qualcomm,inc gobi modem(qdl mode).doesn't that mean phone is in qdl mode?anyway i am waiting for ur reply and i will try if i can take out the battery

---------- Post added at 01:44 PM ---------- Previous post was at 01:07 PM ----------

thank you very much.i will try installing it

---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------

yeah now i have taken apart the phone cover but now i have seen that removing the battery in htc one x is a pain in the ass.we need to remove the car docker first,then motherboard and then the battery.after we do this reassembling it perfectly is almost impossible and is very painfull.atleast is there a way to empty the battery without actually removing it
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Don't try disassembling it, you'd risk breaking something which could never be fixed.

As for the USB cable thing... I don't know. Never heard of it.

As for draining the battery, you probably just have to let it sit for a few days.

Unfortunately, the description in lsusb is just a generic description for that device id. I recently learned that Qualcomm uses that same device id for a few different types of connections. Which makes it not only confusing, but also difficult to identify which type of connection was established. Again, we don't get to choose this, the phone will decide based upon it's programming and whatever errors it might encounter. That's why we check dmesg to get more detailed information.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
oh GOD help me.if i was in US i would have given it to at&t for replacement but now don't know wt to do.anyway thanks for all the help and interest on me.
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
For those with unrecoverably bricked devices, new developments may soon change that. Some testing will need to be done, but a full recovery *might* be possible.

Please be patient.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
thanksssss!!!!

thanks a ton soul shadow i am patiently waiting to recover my phone
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
You will be one of the first to know when it's ready. With the holidays this week I'm not sure exactly how long it will take. I will contact you directly when the time comes.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
thank you very much waiting for ur reply
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
qpst

@soul shadow

by any chance i can use qpst for doing something?just letting you know,because i have heard that we can restore emmc partitions using stock image(correct me if i am wrong)
[AT&T, Rogers HTC One X, Telstra One XL] xboxlugo94:
Thanks!

You guys are the AT&T One XL's saviors, MAny thanks for all your hard work. Some of us One XL owners with 2.20 are waiting patiently, again thanks!!:good::laugh:
[AT&T, Rogers HTC One X, Telstra One XL] beaven:
Hi. I am on hboot 2.14.0000 after a bad OTA update from Telstra.

I can still get to bootloader, but touchscreen in TWRP doesn't work.

Phone doesnt boot bast initial HTC screen. I tried jet, but it doesn't 'brick' the device so I can downgrade, it still boots to bootloader rather than qualcomm download mode. read all the pages in this thread and the jet thread and have now run out of ideas. I thinnk I should be fine if I could get a hold of the 3.17.xxxxx RUU for my phone, but the newest RUU out there is 1.89.

Any ideas?

Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
if u can still access bootloader then you can relock the bootloader and ruu to ur stock rom
[AT&T, Rogers HTC One X, Telstra One XL] beaven:
Thanks, this is part of my problem. There is no RUU out for my software version. I tried 1.89, but it fails. Getvar output below.

version: 0.5

version-bootloader: 2.14.0000

version-baseband: 0.23a.32.09.29

version-cpld: None

version-microp: None

version-main:

version-misc: PVT SHIP S-ON

serialno: HT2A9W303102

imei: 359691041684351

product: evita

platform: HBOOT-8960

modelid: PJ8312000

cidnum: 11111111

battery-status: good

battery-voltage: 4193mV

partition-layout: Generic

security: on

build-mode: SHIP

boot-mode: FASTBOOT

commitno-bootloader: dirty-97c9a06e

hbootpreupdate: 11

gencheckpt: 0
[AT&T, Rogers HTC One X, Telstra One XL] disturbedDRAGON666:
I got bricked with the Telstra OTA as well, except proper bricked. No flashing lights, no light on charge. Phone shows up in Linux but partitions don't show up, so no jet or emmc_recover. Was on hboot 1.4 /2.20 so won't hold my breath but hoping the above possible solution can get me going again.

Edit: should add it wasn't the update itself that bricked me, one of my daughters tried to turn it on while it was in ruu mode.
[AT&T, Rogers HTC One X, Telstra One XL] :
Wow. She reset the phone while it was flashing? That's painful.
[AT&T, Rogers HTC One X, Telstra One XL] Zoide_:
My phone was working fine some days ago, and it entered an unusuable state (can't turn on or charge) after my car charger went crazy: http://xdaforums.com/showthread.php?t=2058486

I managed to see Qualcomm, Inc. on my lsusb, but not Gobi Modem (QDL mode). Also, I didn't see anything in /dev/sd* since I didn't read properly that I was supposed to spam ls /dev/sd* repeatedly. So I pressed the power button to try again.

But now the system can't accept the phone as a USB device:

[ 571.528343] usb 2-1.4: >new high-speed USB device number 14 using ehci_hcd

[ 576.603470] usb 2-1.4: >device descriptor read/64, error -71

[ 581.782594] usb 2-1.4: >device descriptor read/64, error -71

[ 581.958429] usb 2-1.4: >new high-speed USB device number 15 using ehci_hcd

[ 587.033726] usb 2-1.4: >device descriptor read/64, error -71

[ 592.212831] usb 2-1.4: >device descriptor read/64, error -71

[ 592.388664] usb 2-1.4: >new high-speed USB device number 16 using ehci_hcd

[ 597.795429] usb 2-1.4: >device not accepting address 16, error -71

[ 597.867477] usb 2-1.4: >new high-speed USB device number 17 using ehci_hcd

[ 603.274274] usb 2-1.4: >device not accepting address 17, error -71

[ 603.274495] hub 2-1:1.0: >unable to enumerate USB device on port

I've tried holding down the power button for 10 seconds again, but keep getting the same problem. Any ideas? Thanks
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
i have seen you in another thread.you screwed ur mobile with some faulty car charger right?did you remove ur battery.did u dare to do that.i was affraid if i wd break something or atleast its difficult to assemble it again.anyways hope you will recover urs and mine soon.
[AT&T, Rogers HTC One X, Telstra One XL] beaven:
I just managed to restore my phone! :laugh: I found the generic RUU for Asia (RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed) and ran that against my phone in a last ditch effort. I had already been to Telstra and the engineer saw the **Tampered** flag in bootloader and said I could only bring it in on the 2nd Jan to be sent of for repair. So came home and tried this. It wen't into that special booloader mode with HTC displayed on the screen. Took like 15 minutes but then the device came back! :good:

So frikkin' stoked. Now, to see if I can get back to CM10 with HBOOT at 2.14.0000. I highly doubt it though.
[AT&T, Rogers HTC One X, Telstra One XL] raffles.angus@gmail.com:
I'm in the same boat as you but I get CID error flashing the abovementioned rom....how did you do it
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
you have to lock the bootloader with this cmd "fastboot oem lock" while being in fastboot mode and then run the ruu.

---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------

wait for soul shadow or absolutely grim to come up with a new solution for this.
[AT&T, Rogers HTC One X, Telstra One XL] raffles.angus@gmail.com:
thanks but have oem locked it....the cid is the customerid does not match telstra
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
the cmd will lock the bootloader irrespective of which carrier it is.you just have to restart the phone so that it says relocked or locked.but if it still stays unlocked or tampered,then try locking it again by running the cmd.it should get locked then.but remember the ruu which you are running should match with your carrier.if it is from asia then it won't work.but if you are interested in flashing that jb update,then there is a rooted rom(both odex and de-odex) in the development section.flash it using twrp.
[AT&T, Rogers HTC One X, Telstra One XL] choumi:
I got bricked with two weeks ago after flashing a Jellybam rom on my evita I wanted to get ridd of the sfr french operator apps my device rooted and TWRP recovery installed after rebooting the phone the animated logo was stuck there for long then I rebooted to recovery to install the google apps package for the same rom when rebooted it went dead no led light no charging no usb device recognized but the QHSUB_DLOAD shown! since then I've read all the threads related I tried the procedures from the first page I succeded in getting the ls /dev/sd* showing all partitions I followed the insttructions to the last line it strated changing or loading hex numbers or something like that for about 15 minutes at the end it was done saying successful but I still don't understand that my device is always off! then I read some about the jeweltoolkit/evita and followed the instructions on ubuntu and kept stuck on waking device for long trying to unplug replug the usb cable for many times or press and hold 10 seconds all that for several times it didn't work ! then the reason why the device isn't shown is because of this weird driver QHUSB_DLOAD I searched on google and found a zip file on unlimited IO website named PblClear.zip and followed the instruction using ubuntu there again I did it to the end but the thing is that it's so fast in timing I got as last line "QDL rest" but I'm not sure what that means! I did that repeatedly but my device seems to be dead weirdly!!! I had a bricked htc one s before but could find a solution and got it back to life this evita is really complicated in systems I guess is too different I really appreciate your help and I'm impatiently looking for Grim back to solve our phones. Thanks for all contributing in such an emmergency what would it be if you were not there! just lost! I'm keeping following every page here and I hope something will make come up with a final formula soon. Thanks :good:
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
you still can get ur phone show up the partitions when you spam ls/dev/sd*?if yes then you can recover your phone.follow the beginning of this thread and you should be using ubuntu for recovering your phone.
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
If you were able to unbrick your One S, you're able to unbrick your One X ATT... They are both Evita devices. And PBlclear.zip is more than likely a primary bootloader clearing tool... Meaning your primary bootloader is gone if you were able to successfully use that .zip. if not, and ls/dev/SD* still shows all of your partitions, you're able to recover your device. Hopefully you didn't use pblclear. zip successfully. I cringed for you when I saw that. If you used that properly, your phone is more than likely gone. Thanks to write protected bootloader partitions...
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
thank god you replied.any chance of you knowing how to use qpst to recover our device?.i have got the required files but i have seen in s-off section that they get an error(missing cache) while using it.soul shadow said he is working on it but no reply from him as he might be enjoying his holidays.thanks
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Pblclear does not wipe anything. It simply resets the device clearing any prior error codes.

The primary boot loader (pbl) is in a read only memory (rom) chip on the board. It can not be erased.

-SLS-

---------- Post added at 10:59 AM ---------- Previous post was at 10:52 AM ----------

The error is "missing cookie". We tracked it down, it means the device is not in the pbl's ehostdl (emergency host download), therefore it never even tries to send the hex. Using the hex also requires additional files which we must build for the device. Please try to be patient. We are learning and figuring this out as we go. Yes the holiday did reduce my free time, but I've been quiet on here because I'm using that time to develop a solution.

-SLS-

---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------

Also, to those trying to recover their phones: all currently available tools ONLY perform a specific task.

Jet downgrades hboot. It is not written to be a recovery tool.

Anything from team unlimited is written ONLY to recover from an error caused by running their programs.

Everything available so far targets very specific problems, which are DIFFERENT from what everyone here is currently experiencing. That is why those other tools have not been effective.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] Zoide_:
So there's no solution for seeing "Qualcomm, Inc." on lsusb with no partitions showing up on ls /dev/sd*? Any chance the partitions do show up but it's so fast I didn't notice? For how long do they stay in /dev?

Do notice that my phone didn't enter this state after flashing the wrong firmware or anything like that. It was as a result of using a faulty car charger.

Also, what's the right way to go back to the "Qualcomm, Inc." state once the phone starts getting rejected by the USB system? I've only managed to do so by some trial and error (and just plain letting the phone sit there).

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
thank you so much.you are the guy who is working so hard I know.i will definitely wait for you come up with a solution.just letting you know that I am little aware of qpst.take your own time buddy.we will wait for you.thanks again

---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------

the solution is that the phone should be qdl mode to show partitions.the solution has been worked out and wait for soulshadow to work on it.just be patient.hope that you can recover the phone
[AT&T, Rogers HTC One X, Telstra One XL] :
The problem here is we don't know what the car charger did.. could have fried something or wiped something somehow.
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
You are not alone. Others have had the same problem with car chargers.

As for getting the phone to go in to a particular state, it is complicated and not currently something we can control. The biggest challenges are that we can only observe through usb and there are 4 different states the phone can be in:

1) booted in to android

2) qhsusb_dload

3) ehostdl

4) gobi 3g modem

It's further complicated by the fact that qhsusb_dload can show up with OR without enumerating the emmc partitions.

These new phones are both easy to brick and nearly 100% recoverable. They are also much more complicated and lacking in publicly available documentation. Non-OEM recovery methods are only now beginning to be developed.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] Zoide_:
Could there be a way to get the data out with a JTAG or something like that? What I want most of all is to recover the photos in my phone's memory (I hadn't synced them to a computer or to a cloud service). Un-bricking the phone to full operational status would be nice, but not essential.

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
I don't know. JTAG is meant to be used for diagnostic purposes. While it can also be used to recover a phone, I'm not sure if it can access or even save anything currently existing in the emmc memory.

-SLS-