yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Drive you? I don't even know where you live!

Seriously though, from what I've seen it's not complete yet and still has some bugs they are working on. Plus it will require custom built files for each device and that tool is still a work in progress. Right now it's geared towards testing to see IF it will work, so I wouldn't recommend it yet as it might do more harm than good. As soon as it's in a working state someone will post about it.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] mik93250:
Ok I understand ;)

(Sorry for my very bad english! :( )
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
Read previous pages. I've posted about riffbox. It does have HOX Evita supoort
[AT&T, Rogers HTC One X, Telstra One XL] bioan:
I've read the entire thread and didn't find any info. I would appreciate if you could point it out. Thank you!
[AT&T, Rogers HTC One X, Telstra One XL] newtlex:
Waiting with hopefully
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
Might be in the s off thread.
[AT&T, Rogers HTC One X, Telstra One XL] choumi:
Soul Shadow anything in progress ? Is it the case of no news good news my phone is in a deep coma for 2 months now! :(
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
No offense, but remind me what happened to your phone? I've had countless people ask for help, I can't remember who had what problem.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] shonuff1221:
step 3

ok ima a dumbass i guess when it comes to this but i really want to learn but in step 3 when it says to spam $ ls /dev/sd*...is there a special command im possed to put bc my /dev/sd never gets as long as yours does when u said u should go from seeing this to that...just keeps the same like 6 names...plus from the beginning there was something about hex and CID..where r the instructions on how to do that if that step is needed...thanks
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
First of all, what happened and what are you trying to do? There are many causes for a brick, the instructions in the op may not apply to your situation.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
Thanks for all the help but can you please explain wt exactly is keeping us from unbricking our phones.I mean wt is the problem,wt can be the solution,wt is the goal.I have gone through all your posts and other threads too,I tried the tool by darksprite too.

also wts the status on getting a device specific hex file so that we can work with qpst.

sorry if I am totally wrong.I have read ur thread but that is beyond my understanding.

anyways I will wait for you i would really love to see my phone come back to life again.

Also if you were to ask wt happened to my phone,I actually messed up with the partitions by flashing bakp4 file of mmcblk0p5 into mmcblk0p4

Thanks
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
After all your posts in many, many different threads, yes, I do remember what happened to your phone.

We have the hex file that we need. The problem now is that qpst get's stuck waiting for a response from the phone. So to complete the process we've been forced to develop out own program to replace qpst. The tool posted by darkspr1te was the first attempt to test if it would work. It does work, but that tool is incomplete.

And that's where we are so far. We both have jobs and our own personal responsibilities that must come first. This limits the time we have to work on ANYTHING phone related. I wish I could snap my fingers and magically fix everyone's phone, but unfortunately it just isn't that easy. We will succeed, but as I've said from the start, I have no idea how long it will take.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] saketh91:
hey bro thanks for replying.don't mistake me,I just asked you wts going with the phone,that's it.Ofcourse personal life is more important.take your own time.I have been waiting for one month and will wait till i recover my phone.

I understand now the issue with qpst.will the updated version qpst help with problem(i hope so)?.anyways thanks again for your reply and you are really helping everyone.

thanks
[AT&T, Rogers HTC One X, Telstra One XL] mittenman:
Waiting patiently as well. Appreciate the level of nerdery you guys put up to help us dummies out. I flashed a tegra ROM after I drank too much wine. Of course I had the 2.2 hboot. Recently picked up an Optimus G, but I'd love to get my hox up & running again. Once again, much appreciated.

Sent from my LG-E970
[AT&T, Rogers HTC One X, Telstra One XL] choumi:
Yes sure Soul Shadow I got bricked when I first have installed rom manager and flashed it then I unistalled it when I read it causes trouble then I flashed JellyBam rom and did it normal way (wiped cache, system, dalvik, data system) after reboot it stayed stuck a while at the animated image and boom!!! I was root with french sfr rom - Then I had to go through this thread and followed successfully the procedure and tried so many things without success I mean the unbrick-evita using ubuntu and linux as well and now after too many attempts always the same results no partitions showing when I spam the ls/dev/sd* - the last thing I did was opening the the phone then you told me I should told you before (not sure if it was you) this was to see if I could get a led light or the QHSUSB-DLOAD driver to install but no success again!

I don't know what hboot i was I remember i did an update but not for jellybean it wasn't out yet! Do you think i'm out of luck or still have to wait for something as any tool in progress or any other procedure to follow or simply stop thinking of any solution! I wish it is the case of a progress of course. Thank you for your attention and replies and everything you are contributing in Soul Shadow
[AT&T, Rogers HTC One X, Telstra One XL] :
I don't mean to be rude, but these "waiting patiently" posts and the "how long?" Posts are counterproductive.. they are just burying information, please stop.
[AT&T, Rogers HTC One X, Telstra One XL] TrustAugustus:
Want to say thanks for this continuing development. I overestimated my flashing skills and didn't properly read the thread...and the subsequent warnings..lol. But your development project gives me hope. Is there anyway to donate to you or your group?:D:D

Edit "PayPal does not currently support Donation Payments from buyers in JP. We apologize for any inconvenience this may cause." Ill figure a\out another way to get you guys a drink!
[AT&T, Rogers HTC One X, Telstra One XL] :
https://www.dropbox.com/s/1wp1a1wfn8mv074/disassembly.mp4

https://www.dropbox.com/s/we8alxze16fd9wf/downloadmode.mp4

We weren't really missing a window or id'ing them manually, we used the watch command which will immediately alert us of any new devices.

If hboot was corrupt this would be a different story. Don't rule anything out yet. We just need to find a different way to reveal the partitions
[AT&T, Rogers HTC One X, Telstra One XL] :
got the links.. and I don't know about a Riff Box, maybe a soldering gun, if we wanted to do our own jtag

https://www.dropbox.com/s/1wp1a1wfn8mv074/disassembly.mp4

https://www.dropbox.com/s/we8alxze16fd9wf/downloadmode.mp4
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
right. sorry for my improper terms haha. I probably should have noted this from the sessions, but when did the 1-2s window open up?

what I meant was, can we write something that will know precisely when linux sees the partitions (before going into download mode) and just starts attempting to write to whatever shows up. Like, even if it writes to the wrong partitions, it shouldn't make things worse right? and then you might get lucky and hit p4. Sorry if I'm still not getting it. lol

edit: i understand that when we were trying to write it would reset and just keep trying to write, looking for a new window. but I'm referring it the moment (ref: discussion on dead battery) when that first time it showed up. it didn't seem to pop up again after that. seems like we'd need to nail it first try, then wait until the device is dead again.

and no, I don't think the riffbox has hox support. but if someone knows how to fundamentally use it, they could still make it work. from what I quoted earlier, it seems like this guy was suggesting setting up an hox device from scratch. If he succeeded, he'd probably get a few dozen phones shipped to him at least lol. I believe once you get it figured out, it's only like a ten minute thing. it's just the figuring out part that is hard.
[AT&T, Rogers HTC One X, Telstra One XL] :
If you saw towards the end when we did watch -n.1 lsusb after we kept resetting the phone it would pop up as Qualcomm, Inc. for 2 seconds, disappear and then reappear as Qualcomm *something* QHSUSB_DLOAD

we can't write to it because it's not *there*
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
oh ok. I follow you now. I hope my discussion at least resembles being helpful haha, I know I'm way behind on understanding it all. but I want to, dammit!
[AT&T, Rogers HTC One X, Telstra One XL] lucentworld:
Oh that is a kind of Jtag toolkit...

And for the second video, it is an QPST way of fixing? I can not be used for the 2.20 right?
[AT&T, Rogers HTC One X, Telstra One XL] :
No, it just puts it into QHSUSB_DLOAD mode, kind of like how it is now. Useless and not writable
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
quick update on jtag

don't lose hope, my friends. I've been in contact with a few people and it seems the only holdup with jtag is that the pinout on the motherboard isn't known yet. msm8960 is supported by both riffbox and ort-jtag (probably the two most popular jtag adapters for phone work). as soon as the jtag techs can sort out which pins to connect the adapter to on our motherboard, the flashing process is already known. I don't know if the solution will come in days, a week or month, etc. but hang on to your bricks. we might find a 100% soft unbrick in the meantime, but your phone isn't going to be garbage. there will always be a last-resort repair.

the pinout hangup is a roadblock, just as getting into emmc mode through usb, but it is the kind of roadblock that appears as if it certainly does have a solution around the corner.
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Who's working on this exactly?
[AT&T, Rogers HTC One X, Telstra One XL] :
I think some local guy 30 minutes away from him
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
yeah, it's someone with a jtag repair shop a half hour away. he makes money on the side doing it, so I'm assuming it's in his interest as well to actually solve the problem. I'm hoping he'll be generous enough to share the pinout with the community when he's figured it out. I've offered him my phone to experiment with, and a 50% tip if he shares the pinout with the community. Just waiting to hear back from him.

In my initial correspondance, he actually suggested I try everything that grim and yarimapirate have suggested so far, so it seems he's not *all about* making money, otherwise he would have just told me to bring it in and charge me for the repair. that's just me being optimistic maybe.

Note: this guy says no dice. too busy I've also contacted another guy in my area with a jtag and he said he'll also try to figure it out as well.

And lastly funkym0nk3y is working on the pinout for jewel. not sure exactly how much that will help us, but it could be beneficial.

if we want to try some more soft-solutions, my phone has been sitting for a couple days now without charge...not sure if the battery is dead yet, but I'll be available this weekend. feel free to txt me if interested, grim.
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
Have him s-off you while he's in there.
[AT&T, Rogers HTC One X, Telstra One XL] :
I'm actually hoping this guy will share the procedure.. I'd jtag for s-off.

Can't say the same for anyone else in the s-off thread
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
I'll certainly ask! I hope all this isn't just pie-in-the-sky and the guy is serious about doing this.
[AT&T, Rogers HTC One X, Telstra One XL] :
Try and make note of exactly what he does..

We possibly have a few more ideas, but this of course, would be a last resort fix. :fingers-crossed:
[AT&T, Rogers HTC One X, Telstra One XL] lucentworld:
Yeah,if the worst result come we can use JTAG as a last resort.

And...Do you have any new ideas grim?
[AT&T, Rogers HTC One X, Telstra One XL] :
I do.. But I don't want to reveal them yet.. I'd like to test them beforehand.

I will need to keep collaborating with Pirate and 18th before we decide to test.
[AT&T, Rogers HTC One X, Telstra One XL] =JKT=:
FYI Disassembling my phone enough to access the battery is seriously not a big deal for me, if we want to do anything without a battery.
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
I got to thinking last night, wish I could say it was a good thing, but the x factor exploit spoofs the CID. Is there any way you could spoof code from an RUU? Just a thought. Most of this is way over my head but, I'm trying to learn so I might be of some help on projects in the future.
[AT&T, Rogers HTC One X, Telstra One XL] :
RUU's are signed, if you change even 1 bit of information, the signature breaks and your phone won't take the RUU
[AT&T, Rogers HTC One X, Telstra One XL] 954wrecker:
You just copy and pasted it from a thread you started 6 months ago, why hijack this thread?

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] radjan:
Hey guys,

So, another one bites the dust. I was able to downgrade to 1.09, follow all the steps, but since I used no IMEI it had no signal at all. Didn`t realize it soon enough, so I tried to flash a RUU (1.81). It worked, went through all the steps but afterwards it bricked my phone.

I've read the whole topic and I guess I am in the 2nd category, since my computer identifies there`s something connected, but as much as I try it never shows the partitions. I won't claim for help cos I know you guys are already working on it as much as you can.

But, since my device is from Australia and I'm in Brazil, I have no hope of exchanging it at all. So, my device is yours to do any tests you find useful.

I'm regularly online, have teamviewer set up on ubuntu (12.10 x32).

Thanks in advance!
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Ok, Bad News time :(

After further investigation and some help from other developers, it appears our miracle (the mprg8960.hex) is NOT loading on MSM8960 based phones (including this one). Without the help of that file, we are once again limited to only repairing devices which connect and enumerate their partitions.

If your phone is connecting to your computer as a Qualcomm Gobi (QDL) device with vid/pid 05c6:9008 and NOT showing it's partitions (/dev/sda1 - /dev/sda36) then there is nothing that can be done at this time.

Myself and other developers will continue to explore other possible ways to fix these devices, but as of right now there is nothing that can be done.

My apologies to everyone who has been waiting patiently. Unfortunately we can only work with what Qualcomm and HTC have incorporated into the design and manufacturing of these devices. While they are essentially unbrickable by design, the means to a software based recovery has been disallowed. JTAG appears to be the only currently available method to unbrick these devices.
[AT&T, Rogers HTC One X, Telstra One XL] HTConeXnoob:
I can only go as far as step 9 and then it just gets hang, holding down the power button for 10 secs just causes the device listed in the other terminal to flash but not disappear.

help???
[AT&T, Rogers HTC One X, Telstra One XL] :
Can't fix it. Sorry, you were probably running the 2.20 software (1.14 hboot) if that's the case, there is no fix at this time
[AT&T, Rogers HTC One X, Telstra One XL] choumi:
Thank you for all the time consuming and effort spent in this particular model device Soul Shadow and the other developers the positive thing here is that I personally learned a lot of things I didn't know before using ubuntu for instance was a new experience to me and probably for others so it's all positive as we are to blame in not being careful in flashing roms and in this device was the most complicated operation in finding a solution to recover the hboot system and finally everyone will understand that this should be a lesson never to happen again and pay more attention. In the end of this I think now we have to send our phones for repair as it appears to be the only way as you said so I would be thankful if you can give us any contact as address or phone number or email to send the phone for repair because in my case there is no repair centre here in north africa I will have to take this other orientation to look atound for any centre around morroco tunisia or of course Europe because it is the nearest area to us here. Kindest regards
[AT&T, Rogers HTC One X, Telstra One XL] HTConeXnoob:
whats the "JTAG" method? will it work? sorry I'm a noob :(
[AT&T, Rogers HTC One X, Telstra One XL] mrjayviper:
I'm on Hboot 2.14.x. I suppose I cannot use this to downgrade the hboot? thanks! :)
[AT&T, Rogers HTC One X, Telstra One XL] motox16:
Hey i Got a windows 7 computer and i dont really get this can anyone help me ?​
[AT&T, Rogers HTC One X, Telstra One XL] Myrder:
Let's not quote the entire op. Please delete it.

As for this process, its for unbricking your phone.. in certain circumstances. You can also downgrade your hboot with it. You need Linux/Ubuntu to do so..
[AT&T, Rogers HTC One X, Telstra One XL] itzkrlos:
It was my first time with and android phone and I bricked my htc one x evita on 2.20, so, there is no way, by now, to fix it.

Which box can do the "JTAG" for this model?

I'm noob with all of this, if you can give me some instructions I will appreciate it.

Thanks.:cowboy:
[AT&T, Rogers HTC One X, Telstra One XL] mik93250:
http://mobiletechvideos.mybigcommerce.com/htc-one-x-jtag-brick-repair/

They just finish to repair my phone and they shipped it, now I'm waiting for it :)

They are famous on internet
[AT&T, Rogers HTC One X, Telstra One XL] bradspace:
Mobiletechvideos.net

I used these guys as soon as they announced unbricking for the AT&T One X. I think because I was an early adopter, they were still working out the bugs with the process, but they were very responsive and worked diligently to get it taken care of. When I got it back the second time, it appears to be working like new with one exception. I can no longer flash any ROM"s on the device. I have tried 3 or 4 and they all end up at a boot loop. When check MD5 sum is enabled, every ROM fails. I haven't had time to troubleshoot this yet, but I suspect it may be a fairly easy fix. All in all, I am happy with the cost and the work done by these guys and would recommend.
[AT&T, Rogers HTC One X, Telstra One XL] WTFunk:
Uncheck signature verification when flashing roms.
[AT&T, Rogers HTC One X, Telstra One XL] jac0b:
BIG THANKS TO mirGantrophy & yarrimapirate. YOU FIXED MY PHONE. :good:
[AT&T, Rogers HTC One X, Telstra One XL] mrjayviper:
can you please explain which circumstances are those? I want to get out 2.14.... :/

thanks!
[AT&T, Rogers HTC One X, Telstra One XL] cgukevin:
Thank you so much! I brought my bricked device back to life with your method. Great post!

---------- Post added at 02:41 PM ---------- Previous post was at 02:19 PM ----------

Btw, I did not even finish all the steps to unbrick my phone. In the middle of step 9 after a bunch of data writing, the "Qualcomm. Inc. Gobi Wireless Modem (QDL mode)" became "HTC............" in the first terminal window. I had not realized my phone was successfully unbricked at the first time, and I tried to hold the power button for about 10 seconds to let the process continue. After a few attempts failed, I found that the charging light was back on! I could boot it to bootloader and recovery!

P.S. I bricked it during hboot downgradation.
[AT&T, Rogers HTC One X, Telstra One XL] Kole_Ackerson:
You know you could've swapped the hboot in the unbrick with the downgradable one and you would've recovered with a 1.09 hboot
[AT&T, Rogers HTC One X, Telstra One XL] :
Same process.. Attempt at your own risk though. I can neither confirm nor deny if it will work or not.
[AT&T, Rogers HTC One X, Telstra One XL] priddyma:
The JET tool wasn't working for my device for some reason. It detected the phone, and tried to switch modes but it seemed like my PC wasn't executing the code fast enough.

The manual method with emmc_recover worked perfect. Now hboot downgraded.
[AT&T, Rogers HTC One X, Telstra One XL] SouL Shadow:
Jet isn't perfect. It was originally developed for Jewel, which is a single carrier (sprint) version of the one x. While it also works on the various qualcomm based one x/xl phones, there appear to be timing issues between the slightly different one x/xl hardware. Coupled with the different speeds of people's computers and the buggy nature of the linux usb 3.0 driver's backward compatibility, it introduces a timing complexity that isn't easy to handle in a single solution. That is why the manual method sometimes works when Jet does not.

-SLS-
[AT&T, Rogers HTC One X, Telstra One XL] EjWilkes0121:
Hi Guys,

Learned a lot from your posts. Thanks to your efforts in providing us ways to get our phones workin. :)

My phone just got bricked hours ago after I tried flashing Siyah vSync Kernel.

It was running JellyBam 4.1 and got no issues at all. It was just my curiosity to try a different kernel.

Is it something that I could fix using the manual method? I'm going to give it a shot once I get home from work.

I just thought I bricked my phone in a different way. Haha! Thanks in advance!

AT&T HTC One X running JellyBam 4.1 <- currently bricked
[AT&T, Rogers HTC One X, Telstra One XL] Kole_Ackerson:
I have never heard of that kernel. Were you in the international forum or am I just blonde?

sent from my envenomed HTC One XL running ViperXL 3.2.1
[AT&T, Rogers HTC One X, Telstra One XL] EjWilkes0121:
Nope, I got the AT&T Version. Got it from eBay. ^.^

Well, guess what? It's up and running like it hasn't bricked. Lotsa thanks to ya'll!

I got interested with the Siyah Kernel when I saw some posts from JellyBam forums that it's got better battery performance.

Flashed it, and boom!! Expensive paperweight showed up.

Do you flash custom kernels as well? I got 3.0.57-g9268db3

AT&T HTC One X running JellyBam 4.1
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
I don't get a "success!" notification after the flashing is done on step 9. In fact, it looks to me as if it's freezing on:

Writing 15616 bytes to offset 0x000FC000

Waiting mode-switch

Device changed mode

Detected mode-switch

After that another empty command line just shows up. Either that's how it's supposed to be or I'm doing something wrong, though I am following the steps to the letter...

EDIT: Also after those steps when it comes down to restoring the original mmcblk0p4

Ready to write 1024 bytes

Resetting device

Cannot reset device

Reset command sent

Waiting device /dev/sdb19.......

Found device!

Writing 1024 bytes to offset 0x00000000

Waiting mode-switch

Device changed mode

Detected mode-switch

Notorio@ubuntu:~/unbrick_evita$

Notice again no "success!" notification here either, just another empty command prompt after the mode switch is detected :(

EDIT 2: Ok, I'm going to completely re-do everything from downloading all the files again to following every letter again. Hopefully the 10th time is the charm :p (I've got to be missing a step so this is a bread crumb run)
[AT&T, Rogers HTC One X, Telstra One XL] beaups:
You sudo first?
[AT&T, Rogers HTC One X, Telstra One XL] Notorio:
Yeah. Doing it this time I'm having trouble finding the device number. I'll keep messing with it until I get it right. I've done it before, I think my mind is just getting burned out by the repetition so I'm missing steps...

EDIT: Not sure what I did but now I can't even get past step 3. Ugh this is so frustrating...

---------- Post added at 03:34 PM ---------- Previous post was at 03:03 PM ----------

Ok so it seems the problem is that I can't get out of QDL mode. Any suggestions?