Related
My HTC One S is stuck in QHSUSB_DLOAD. I tried to bring it out of it using Unlimite.io's solution for One V, though it finished successfully One S didn't come out of this mode. Is it completely dead and should be sent to company or is it still un-brickable?
Does it boot into HBOOT after running the tool?
Sent from pixels to more pixels
Nothing happens.Just blank screen and charging led which remains orange forever.
same here man.. didnt work with one v unbricker either ...
This is not going to help you (sorry), but maybe provide some insight for everyone..
Do you know how you got into this state?
I've seen reports from others deleting large files from their sdcard partition.
Do you remember what you did right before it died?
Thanks,
-Jobo
Your HBOOT might have become corrupted. This happened to people with a Sensation after writing S-ON flag from S-OFF for warranty purposes. A re-flash of your bootloader would be good. But since you can't get into the bootloader, this is quite hard. Have you tried following the Sensation unbricking guide, using a different, One S HBOOT?
Sent from pixels to more pixels
Same problem here after flashing the new OTA...
Any solutions
Same threat here:
http://forum.xda-developers.com/showthread.php?t=2064202
We tried almost anything to get it out of dload, nothing seems to work.
I made a new threat here to collect all info about this issue.
Vauix said:
Same threat here:
http://forum.xda-developers.com/showthread.php?t=2064202
We tried almost anything to get it out of dload, nothing seems to work.
I made a new threat here to collect all info about this issue.
Click to expand...
Click to collapse
Does it mean that we to reflash the bootloader? Mine cant go to HBoot nor Bootloader.
Sent from my GT-S6500D using XDA Free mobile app
MPRG8260.hex
I was looking for firmware files of devices using the same msm8260 and found hex programming block in FLY IQ285 rom.
I know a lot of people are looking for this file.
carbonat87 said:
I was looking for firmware files of devices using the same msm8260 and found hex programming block in FLY IQ285 rom.
I know a lot of people are looking for this file.
Click to expand...
Click to collapse
Im guessing, even with the file you provided, no one i gonna take a look at it, i mean everyone here probably had an upgrqde from the One S surely after this issue even myself.
Sent from AssForMini
carbonat87 said:
I was looking for firmware files of devices using the same msm8260 and found hex programming block in FLY IQ285 rom.
I know a lot of people are looking for this file.
Click to expand...
Click to collapse
Hi, do you happen to have 8260_msimage.mbn
Anyone ?
thank you
Unbricking HTC One S C2 [S3]
Hello my friends. Newly I faced with the same problem. Phone did not react and was defined as QHUSB_DLOAD.
I solved a problem thanks to a topic http://forum.xda-developers.com/showthread.php?t=1522351
Instead "pyrV.VV.nb0" I put file hboot.nb0 which took from a RUU firmware for my device. Also you can find it in firmware.zip
RUU roms: http://androidruu.com/?developer=VilleC2
And how get hboot.nb0 there: http://forum.xda-developers.com/showthread.php?t=2534428. Good luck!
AxNx666 said:
Hello my friends. Newly I faced with the same problem. Phone did not react and was defined as QHUSB_DLOAD.
I solved a problem thanks to a topic http://forum.xda-developers.com/showthread.php?t=1522351
Instead "pyrV.VV.nb0" I put file hboot.nb0 which took from a RUU firmware for my device. Also you can find it in firmware.zip
RUU roms: http://androidruu.com/?developer=VilleC2
And how get hboot.nb0 there: http://forum.xda-developers.com/showthread.php?t=2534428. Good luck!
Click to expand...
Click to collapse
i will try this thanks
currently i got two htc one s (c2) bricked both detected only as qhsusb_dload in windows
just out of the blue..one when it died on battery and the other one when it hangs and i try to restart it by holding the power button
few years ago this happened once to one of them but i fixed it 'accidentally' by following the instruction at unlimited,io (i dont know what i was doing that time)
i will give this a try and report back
okay so as many of you know I ruined my phone and i said i was going to send it to jtag repair. as much as i want that to happen i dont have the funds at the moment to do so. what i did was call AT&T and then told them that i had a problem when updating to jelly bean, theyre sending me a new phone and so heres my question! is there any hope what so ever to recover my memory? i went to go see "In Flames" and i really would like to get my pictures and videos before i send it in, in 4-6 days. any ideas? and please, be nice to me on this one, i made a stupid mistake. but now i can learn from it. :/
I don't believe there's any way to do it short of jtag.
When you're in QHUSB_DLOAD mode, what that means is that the CPU can't find instructions on how to boot up, in this case, hboot. Either it's corrupted or the partition map is unreadable so it can't find it. That means it has no way to read the onboard memory because it has no OS to work with. It's like trying to start your PC without a bios in place--nothing happens.
Hi Elivis, you responded awhile back on my thread here: http://forum.xda-developers.com/showthread.php?t=2187491
I tried everything that was suggested by you and others with no luck, my question is am I having the same problem as the OP?
iElvis said:
I don't believe there's any way to do it short of jtag.
When you're in QHUSB_DLOAD mode, what that means is that the CPU can't find instructions on how to boot up, in this case, hboot. Either it's corrupted or the partition map is unreadable so it can't find it. That means it has no way to read the onboard memory because it has no OS to work with. It's like trying to start your PC without a bios in place--nothing happens.
Click to expand...
Click to collapse
Thank you... That's what I thought :/ okay well it was worth a shot asking
Sent from my HTC Inspire 4G using xda app-developers app
Okkoto said:
Hi Elivis, you responded awhile back on my thread here: http://forum.xda-developers.com/showthread.php?t=2187491
I tried everything that was suggested by you and others with no luck, my question is am I having the same problem as the OP?
Click to expand...
Click to collapse
No. He has a corrupted hboot, most likely. It can happen when your phone dies in the middle of a firmware update, which seems to be what happens during an OTA with SuperCID.
You have some strange connection error that's preventing your computer from communicating with your phone.
My simple mind is wondering why if hboot is corrupt can you just not run the jet tool then go through the unbricking process
Sent from my One X using Xparent Green Tapatalk 2
twisteddroid said:
My simple mind is wondering why if hboot is corrupt can you just not run the jet tool then go through the unbricking process
Sent from my One X using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Well look at it this way , computer can't read anything on phn, its like some1 who speaks English trying to read a mixed up word puzzle in Chinese. Maybe try hooking up with linnux but It still may not wrk
Sent from my HTC One X using xda premium
twisteddroid said:
My simple mind is wondering why if hboot is corrupt can you just not run the jet tool then go through the unbricking process
Click to expand...
Click to collapse
He's on the 2.20 base. There is no unbricking tool for that.
iElvis said:
He's on the 2.20 base. There is no unbricking tool for that.
Click to expand...
Click to collapse
I'm on 2.20 and used unbrick method to unbrick mine after running jet. A week before s-off I was pissed cause I almost had a paperweight when I could have waited one more week lol
Sent from my One X using Xparent Green Tapatalk 2
I have a htc x AT & T one that will not start, I have looked in several forums and have not found the solution, I need help?
1. When the phone is connected to the mains or red light.
2. At precionar the power button for several seguntos the buttons below gives no flash and no response.
3. When I connect the phone to a PC with Windows only recognizes QHSUSB_DLOAD no response from phone.
This happened after installing RUU 3.18.502.6.
have any solution for my case?
This has happened to a few people. Were you rooted with SuperCID? It's not clear what the cause is, but your phone is bricked.
It's possible the jet tool might be able to unbrick it. There is also a service called jtag that will cost around $75.
You sir, are screwed. QHSUSB_DLOAD means the phone is most likely bricked.
Did you have SuperCID? You should have read this: http://forum.xda-developers.com/showthread.php?t=2181929
You can try the unbrick evita thread. You'll need a Linux boot disk. If you can't pull up the emmc partitions then you're SOL. Which is most likely the case but doesn't hurt to check right?
If you manage to restore your phone be sure to s-off before trying to ruu again.
Sent from my HTC One X using xda app-developers app
Please help me!
Hi, im only 14 years old, from argentina. I bricked my phone a month ago by flashing ICJ into HTC One X evita, and i spent like 160 dollars to repair it by jtag as here in argentina the jtag service did not work. Today i was also updating to RUU 3.18.502.6 through the RUU downloaded from HTC site and as it finished a message appeared saying it completed succesfully. But when i tried to boot it it wont turn on nor charge, and my PC detected as QHUSB_DLOAD my heart freezed as they are the same symptoms as last time. I would like to know please any solution to this, and also, will jtag service work this time or this case is like the one that happened to me before. Please any answer would be great. Thank You!
Nicobesso said:
Hi, im only 14 years old, from argentina. I bricked my phone a month ago by flashing ICJ into HTC One X evita, and i spent like 160 dollars to repair it by jtag as here in argentina the jtag service did not work. Today i was also updating to RUU 3.18.502.6 through the RUU downloaded from HTC site and as it finished a message appeared saying it completed succesfully. But when i tried to boot it it wont turn on nor charge, and my PC detected as QHUSB_DLOAD my heart freezed as they are the same symptoms as last time. I would like to know please any solution to this, and also, will jtag service work this time or this case is like the one that happened to me before. Please any answer would be great. Thank You!
Click to expand...
Click to collapse
This site works for some of the bricks... Didn't work for mine...
http://unlimited.io/qhsusbdload.htm
I tried this method but it did not work ... I'm still looking for a solution.
FarBeyond said:
This site works for some of the bricks... Didn't work for mine...
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
Maybe you, and others,need to learn to read again... Sorry to be rude, but that website clearly states at the top, "THIS METHOD WILL NOT WORK FOR DEVICES BRICKED BY FLASHING ROMS OR ANY OTHER SOURCE".
Also, PblClear.zip wipes the primary bootloader partition. Not the greatest idea...
Sent from my HTC One X using xda premium
Ok
Myrder said:
Maybe you, and others,need to learn to read again... Sorry to be rude, but that website clearly states at the top, "THIS METHOD WILL NOT WORK FOR DEVICES BRICKED BY FLASHING ROMS OR ANY OTHER SOURCE".
Also, PblClear.zip wipes the primary bootloader partition. Not the greatest idea...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes i know, but as there is a lot of people like you with experience, maybe someone can help me.
http://forum.xda-developers.com/showthread.php?p=39545425
This is a discussion we were having about installing QHSUSB_DLOAD drivers and repairing them via usb.Might have useful links on it for you to do some investigation.
Sent from my HTC One X using xda premium
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
salissimo said:
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
Click to expand...
Click to collapse
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
exad said:
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Click to expand...
Click to collapse
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
i guess i deserve it
thanks
iElvis said:
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
Click to expand...
Click to collapse
Charge it overnight and see if it turns on at all afterwards.
Sent from my One X using xda app-developers app
Delete.
Sent from my HTC One X using xda premium
salissimo said:
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
Click to expand...
Click to collapse
There's bit of etiquette involved. If the thread is "mature" in the sense that the OP's issue has been resolved, or multiple discussion threads have evolved, then popping in with a related question is fine. It's just not polite to pop in on the second page of someone else's query when people are still trying to help him, unless you have the identical problem.
salissimo said:
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
Click to expand...
Click to collapse
It's possible, but sounds unlikely. I don't think that just changing some setting would stop it from at least powering on. ROM Manager would have had to overwrite something critical that would prevent the CPU from even finding hboot. Had you merely messed up some boot setting, you should still be able to get the boot screen, which would then start looping.
Plug your phone into your PC and see what pops up in Device Manager. I expect you'll get QHUSB_DLOAD, which means you're bricked.
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
salissimo said:
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
Click to expand...
Click to collapse
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
I've never used that unbrick tool but I'm assuming you would need to be able to get to the bootloader to get it to work. Correct me if I'm wrong.
Sent from my HTC One X using xda app-developers app
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
exad said:
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
Click to expand...
Click to collapse
salissimo said:
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
Click to expand...
Click to collapse
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
exad said:
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
Click to expand...
Click to collapse
salissimo said:
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
Click to expand...
Click to collapse
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
If you got it from AT&T, contact them and ask for bit. Whenever they activate a phone, we store it in the system and keeps track of what phone the customer is using.
Sent from my Carbon-ize Evita using xda-developers app
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
exad said:
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
Click to expand...
Click to collapse
do you think mz phone is still under warranty considering it was tampered, and i cracked it open?
thanks!
salissimo said:
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
Click to expand...
Click to collapse
I doubt AT&T can tell you unlocked it. They'll assume it's a power issue like Telus did for me. HTC may or may not warrant it. Mixed results from xda members
Sent from my One X using xda app-developers app
It should be in the EFS nv_data.bin. folder.
Sent from my HTC One X using xda premium
Hello,
I had a few issues with my HTC One XL, and decided to take the plunge and factory restore my phone. There was nothing that I could think of that I wanted other than my photos, so I backed up all my photos to my PC, and got to restoring it.
Once it was done I realised that I had notes I wish to keep. These notes were quite important to me. Is there any way to get these notes back? My phone is not rooted and on Android 4.2.2. This wouldn't be such a hassle if my phone wasn't running in MTP when I plug it into my computer.
Any help is appreciated,
Thank you.
P.S I'm new when it comes to phone terminology so excuse any silly questions, or if I don't understand what you're saying.
P.P.S Sorry if this is in the wrong forum, I'm 90% sure it's not. I have been up all night trying to figure this out and this is my last hope.
There are data recovery programs available for Windows that might be able to recover your data, but if you've written to the sd card since the wipe those chances are slimmer.
Sent from my Evita
timmaaa said:
There are data recovery programs available for Windows that might be able to recover your data, but if you've written to the sd card since the wipe those chances are slimmer.
Sent from my Evita
Click to expand...
Click to collapse
I have tried around 4 or 5 recovery programs. They are unable to continue as they require the device to be in USB mass storage mode. My phone won't do that because it constantly goes through MTP.
I have not written ANYTHING to the SD card since.
The only way I can think of to get it to mount in usb mass storage mode is through a custom recovery, for which you'd need an unlocked bootloader.
Sent from my Evita
timmaaa said:
The only way I can think of to get it to mount in usb mass storage mode is through a custom recovery, for which you'd need an unlocked bootloader.
Sent from my Evita
Click to expand...
Click to collapse
With an unlocked bootloader, that deletes absolutely everything, doesn't it?
It deleted texts/call logs etc but it left all my photos and music alone.
Sent from my Evita
timmaaa said:
It deleted texts/call logs etc but it left all my photos and music alone.
Sent from my Evita
Click to expand...
Click to collapse
Anyway I could back up the deleted note files? Or something?
Should I just do it and hope to God it doesn't rid of it haha?
I'd at least try it. Look at it this way, if you don't try your data is gone, if you try and it fails your data is still gone but at last you have a chance at restoring it.
Sent from my Evita
timmaaa said:
I'd at least try it. Look at it this way, if you don't try your data is gone, if you try and it fails your data is still gone but at last you have a chance at restoring it.
Sent from my Evita
Click to expand...
Click to collapse
Good advice, just rooted it seeing how it goes.
Blaizen88 said:
Good advice, just rooted it seeing how it goes.
Click to expand...
Click to collapse
Well now my phone won't turn on at all, it is doing something as the computer is saying that it's picking up a USB but can not recognise it.
Screen is black.
What were you doing directly before this happened? Is the device registering on the PC as anything? Perhaps QHSUSB_DLOAD? I certainly hope not.
Sent from my Evita
timmaaa said:
What were you doing directly before this happened? Is the device registering on the PC as anything? Perhaps QHSUSB_DLOAD? I certainly hope not.
Sent from my Evita
Click to expand...
Click to collapse
Don't say that to me. I'm pretty sure I just read QHSUSB_DLOAD in the Device Installing thing on Windows.... I'll double check if I can.
Oh dear, QHSUSB_DLOAD means a brick. What had you done/attempted beforehand?
Sent from my Evita
Yep, just double checked and it's QHSUSB_DLOAD.
I was on what I believe is the last step of rooting it. Unlocked the bootloader and flashed a custom recovery. Just went to enter recovery the last time and it didn't turn back on.
Which recovery did you flash? What's the exact filename?
Sent from my Evita
Knowing me it's problem wrong, I tried to do as much research as I could...
openrecovery-twrp-2.6.3.0-endeavoru.img
It did boot after I flashed it though.
(Sorry if it takes a while to reply, I have to wait 5 minutes between them due to being a newcomer)
Oh no. That's a recovery for the HTC One X. The Endeavoru part of the filename means HTC One X (it's the codename). The codename for the HTC One XL is Evita. There's a slight chance you can recover it by trying the Evita Unbricking thread, to be honest most attempts fail at the enumerating partitions step but it's worth a shot. Sorry I don't have a link but if you Google Evita Unbricking it should come up, it has WIP in the title somewhere. It requires a Linux OS, a virtual Linux setup should do the trick. If that doesn't work you'll need to get a jtag repair done (about $60 USD).
Sent from my Evita
timmaaa said:
Oh no. That's a recovery for the HTC One X. The Endeavoru part of the filename means HTC One X (it's the codename). The codename for the HTC One XL is Evita. There's a slight chance you can recover it by trying the Evita Unbricking thread, to be honest most attempts fail at the enumerating partitions step but it's worth a shot. Sorry I don't have a link but if you Google Evita Unbricking it should come up, it has WIP in the title somewhere. It requires a Linux OS, a virtual Linux setup should do the trick. If that doesn't work you'll need to get a jtag repair done (about $60 USD).
Sent from my Evita
Click to expand...
Click to collapse
Well I guess there's where I dropped the ball. haha.
Thank you for all your help, I'll try the first method and if all else fails I might just let go of the phone...
Hoping for the best.
If you don't want to have it repaired, you can sell it for parts (screen, speakers etc) and at least recoup a little bit a cash out of it.
Sent from my Evita
The fix semi worked. It's now rebooting constantly at the HTC white screen.