yashsingh1/xdaforums huggingface dataset:
[RAZR HD Q&A, Help & Troubleshooting] recDNA:
My maxx hd is in the vzw kickstand case which is pretty thin. Anyone know a good horizontal belt pouch big enough for it to fit without squeezing it in?
[Off-topic] Rhizo:
Hi,

I’d like to share some awesome and inspiring Zerolution content with you.This competition is currently taking place in South Africa.

Basically it is based on personal resolutions and the person in first place with votes and points could win R 100 000 towards their project. Please lets help this guy he seems the type of person that causes the changes that we see and want to see in the world today.

See what it is and don’t forget to vote! PLEASE SHARE THIS FROM THE LINK BELOW VIA FACEBOOK, TWITTER AND EMAIL. SHARE AS MANY TIMEs AS POSSIBLE!! The more you share the more points this guy gets.

Mod edit: Link removed.

This is an awsome project. Lets help this guy win!

Kind regards

Rhizo
[Off-topic] predatOr:
Its XDA developers... Don't post such spams:mad:
[Off-topic] Archer:
Feel free to post it on your own Facebook, Twitter and via email, but please don't post it here.

Thread closed.
[Sprint HTC EVO 4G LTE] dexter93:
We are proud to announce that the EVO 4G LTE is now fully supported by the HTC Unbrick Project!

Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported.
​
[Sprint HTC EVO 4G LTE] dexter93:
Prerequisites

the appropriate package for the device

the latest RUU for your device

a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device

a usb cable

some basic linux experience

patience

DISCLAIMER:

We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.

Instructions

​

Boot the linux box and download the appropriate package for the device.

Extract the package in the home directory

Open up a terminal

Remove microSD card and connect the device using the USB cable.

Detect the device using the script provided. Type this in the terminal

sudo ./brickdetect.sh

You should get something like sdX. We are interested on that "X"

Hexdump the hboot to check the version

sudo ./emmc_recover --device /dev/sdX12 --hexdump 00000000:00000060

Replace the "X" with the letter the script gave you

Follow the on-screen instructions from emmc_recover

The output should be like this:

00000000 05 00 00 00 03 00 00 00 00 00 00 00 00 00 20 80 |.............. .|
00000010 d8 fc 0f 00 d8 fb 0f 00 d8 fb 2f 80 00 01 00 00 |........../.....|
00000020 d8 fc 2f 80 00 00 00 00 12 00 00 ea 31 2e 31 35 |../.........[B]1.15[/B]|
00000030 2e 32 32 32 32 00 00 00 38 39 36 30 20 53 50 4c |.2222...8960 SPL|
00000040 00 00 00 00 00 f0 20 e3 53 48 49 50 00 00 00 00 |...... .SHIP....|
00000050 00 f0 20 e3 00 f0 20 e3 48 42 4f 4f 54 2d 38 39 |.. ... .HBOOT-89|
00000060 36 30 00 00 00 f0 20 e3 64 69 72 74 79 2d 33 63 |60.... .dirty-3c|

This is the typical hex of a hboot. We are interested to check if that is the hboot partition and if it is, to get to know the version. In this case it is 1.15

If in the above step you failed to identify the hboot, unplug all devices connected to that pc, reboot and try again

Unplug the device

Check again it is the right version, because if you do a mistake here, you won't be able to go back

Flash the hboot on the device. Replace "V.VV" with hboot version (eg. 1.12, 1.15, 1.19) and "X" with the one you got from the detect script. Plug the device in ONLY when asked to

sudo ./emmc_recover --flash jewelV.VV.nb0 --device /dev/sdX12 --chunksize 24576 --backupafter hboot_f.nb0

Follow the on-screen instructions from emmc_recover and wait until the process is finished

Unplug the device, put microSD card in and power on

Congratulations, the device is unbricked.

FLASH THE RUU IMMEDIATELY AFTER RECOVERING!! The device will be unstable after the recovery if you don't flash it.
[Sprint HTC EVO 4G LTE] dexter93:
Notes on the procedure:

​

We recommend using a Ubuntu 12.04(or higher) liveCD

USB3 ports do not work properly. Please plug the device in a USB2 port

Downloads

For HTC EVO 4G LTE(Jewel)

32bit version MD5: 94615b3ec8eebdb16f078d6389cf6d0b

64bit version MD5: 05be37af94fcb2298920d1950ed017e1

​
[Sprint HTC EVO 4G LTE] ssojyeti2:
Awesome!

also first...:D
[Sprint HTC EVO 4G LTE] P.Mobile:
2# :) thanks for this!!
[Sprint HTC EVO 4G LTE] scottspa74:
For real?

Thanks. Mass.

hurled from my AOKP'd Evo LTE. Enjoy.
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Is this going to help people that have bricked when downgrading firmware? It'd be awesome if we can find a way to do that . . .
[Sprint HTC EVO 4G LTE] EVOuser94:
I hope to see an all in one downgrader/ unbricker someday. Ik its not being worked on for windows but even a basic live cd with just the nesacities in it :)
[Sprint HTC EVO 4G LTE] rearview:
I find myself in great need of something like this it seems. Is there an ETA of when this is up?
[Sprint HTC EVO 4G LTE] pre2epic4g:
i have a bricked EvoLTE if ya'll need it. just PM me
[Sprint HTC EVO 4G LTE] Granite1:
Agreed, if that can be figured out, a lot of perma bricks could be salvaged. Very interested to see where this goes. :)
[Sprint HTC EVO 4G LTE] SouL Shadow:
Are you looking to get it working again or just get rid of it?

-SLS-
[Sprint HTC EVO 4G LTE] scottspa74:
Awesome!! Thank you. So this is different than the unbrick method at the unlimited.io lazy panda site?
[Sprint HTC EVO 4G LTE] dexter93:
this method supports other types of bricks( as listed in the OP)

the lazypanda unbricker is specific for bricks caused by lazypanda
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Looks like I could've used this on my first bricked LTE (if I still had it). Nice work!
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
So, I may have bricked my device with no returning but I figured I'd ask.

Was trying to get s-off and the process got hung up. Rebooted and now I get no response. Tried to use RacunHunter but apparently all I get is Bus 002 Device 042: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) in Ubuntu.

Is there anyway to revert this or what should I do?
[Sprint HTC EVO 4G LTE] DNarsingh:
Go to the DirtyRacun IRC, they are very helpful with fixing these types of issues.
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
I tried but one guy swears I have to send it in. I bought it off Craigslist and have it on Boost Mobile so I don't think that's really an option. I've done a ton of searching and it seems like it might be possible to unbrick it but I have no idea. So I came here in hopes someone can help me.
[Sprint HTC EVO 4G LTE] scottspa74:
You might check the stickies for a thread by yarrimapirate or macguyver. Those guys were doing a lot of bricking and unbricking to get s-off and seem really knowledgeable and helpful. I'm not saying dexters tool won't work, I'm not familiar with it.

Best of luck.
[Sprint HTC EVO 4G LTE] SouL Shadow:
It should be recoverable.

I would try the irc channel for dirtyracun again. It sounds like the exact scenario they created a recovery tool for.

However, if they are unable to help, you can pm me and I can try to help. Please try their recovery tool first though, as it's most likely the solution you'll need.

-SLS-
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
Had another guy over there try and help me through Teamviewer and he said the same thing. It will list my device but list it as Qualcomm, Inc. Gobi Wireless Modem (QDL mode) which apparently is the problem. Everytime I try to run any of the tools it won't detect the device. I think it has something to do with the emmc memory.

I'm out of options and I'm on the phone with HTC. Not sure if they'll fix it or what so any help would be greatly appreciated.
[Sprint HTC EVO 4G LTE] scottspa74:
I believe it's supposed to show QDL for the tool to work. But that Gobi inc stuff I've never heard of. Maybe a result of being flashed to boost. IDK. PM soul_shadow.
[Sprint HTC EVO 4G LTE] SouL Shadow:
Unplug then plug your phone back in to the computer and Pm me with the output of:

lsusb

dmesg | tail -20

-SLS-
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
PM sent. Also going to provide more details as I was in a frenzy yesterday.

Got the phone a week ago today off Craigslist and flashed it to Boost Mobile. Rooted it but S-ON was still there. So went to use the DirtyRacun package and was doing great, followed the instructions to a T. Had the process running and it go to "Racun is in your refrigerator" and then it just hung there. Let it sit for a while but it wasn't going forward or doing anything so I rebooted the phone and it went back to ROM as usual. Rebooted to bootloader and nothing seemed to be doing anything. Went to reboot and that's when I got a black screen and nothing would work. Plugged it in and got the QHSUSB_DLOAD in the device manager.

Followed the instructions for the RacunHunter package to undo this but the script won't detect my phone no matter what I do. It's listed under USB devices as Qualcomm, Inc. Gobi Wireless Modem (QDL mode) but it won't detect it.

From what I've been reading, there's a script called gobi_loader which will load custom firmware so the phone can communicate with the computer. I've got it installed and found the Sprint firmware files I need but I haven't tried it yet because I don't want to make anything worse. Would this allow the script to detect my phone? Also, what would happen if I let it completely power down?

Hope this gives more insight into my problem. Any ideas/comments would be greatly appreciated!
[Sprint HTC EVO 4G LTE] SouL Shadow:
I looked at it. Your situation is similar to someone else I tried to help. The phone appears in qdl mode but it doesn't come up as a usb block device and enumerate the partitions. However it is establishing a usbtty0 device, which didn't happen for the other person. I have an idea to try. I'm also interested in this gobi-loader you found. I've been meaning to explore the gobi sources, but haven't had time yet.

I'll pm you so we can trouble shoot this without clogging up this thread. Although I'll be honest, getting your phone working again will depend on us discovering a new way to fix it. Hopefully we can succeed and add to the unbricking capabilities for this phone.

-SLS-
[Sprint HTC EVO 4G LTE] scottspa74:
^^^^^^ would love to know how this goes.
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
Well, after a ton of reading and trying everything I've come across I've still had no luck. As far as I can tell, I think the emmc memory was flashed and there's nothing on the phone. From my understand there is currently no way to recover from this and leaves me the options to send it in or get a new one.

When I contacted HTC, they claimed since I bought off Craigslist it voided the warranty and I would be charged $140 to 'fix' it. Is this true? I told them I was taking an OTA update and it just happened. They said they'd look at it and decide if I was to be charged or not, and if I didn't want to pay they'd ship it back for free. Being I paid $230 for the phone, I can't see myself paying $140 to unbrick it.

In the midst of all this, I came across this website and was wondering if anyone has ever used them, what they think, etc.

http://mobiletechvideos.mybigcommerce.com/htc-evo-4g-lte-jtag-brick-repair/

As a last resort I'm going to let the phone completely die and start it back up. Although I doubt it will change anything it's worth a try. If that doesn't work, what direction should I go from here in terms of having it repaired?

PS: I am not happy with what that dirty racun did in my refrigerator :confused:
[Sprint HTC EVO 4G LTE] SouL Shadow:
Hmmm, never seen that site before. Might be an option. Until we can get the needed .hex file jtag may be the only option. Of course I would check the company out to make sure they are in fact legit before sending them your phone.

-SLS-
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Well I just tried this, because my device is now a brick after trying to update to the 2.13 RUU via fastboot. Not sure why it bricked, honestly. So I'm trying this, since I'm not sure what else to do.

It's telling me where my bricked device is detected, but it's stuck on waiting for the device.
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
From what I read, if it gets hung then hold the power button for 10 seconds and see it will continue.
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Trust me, that I've tried.
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
Can you run adb or fastboot?

Yours sounds like it can be recovered if it's being detected by the scripts. Not sure what's causing it to hang.
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Device is bricked, so no adb or fastboot.
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
When you say your phone is detected, do you mean by Linux or brickdetect.sh? Basically, if you can get your phone to show it's partitions, then you should be able to recover from it. If not, then you're in the same position I'm in unfortunately. :(
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Talking about brickdetect.

lsusb reports:

Bus 001 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Look familiar? :(
[Sprint HTC EVO 4G LTE] SouL Shadow:
That's good, as long as dmesg shows your emmc partitions (which is what brickdetect check, btw)

-SLS-
[Sprint HTC EVO 4G LTE] dexter93:
Run ./emmc_recover -r and get a dmesg

Sent from the brick
[Sprint HTC EVO 4G LTE] Captain_Throwback:
brickdetect isn't seeing the device at all now, though the dmesg shows the device connecting and disconnecting,

[ 2242.413910] qcserial 1-1.1:1.0: device disconnected
[ 2432.714842] usb 1-1.2: new high-speed USB device number 16 using ehci_hcd
[ 2432.808522] qcserial 1-1.2:1.0: Qualcomm USB modem converter detected
[ 2432.808720] usb 1-1.2: Qualcomm USB modem converter now attached to ttyUSB0
[Sprint HTC EVO 4G LTE] dexter93:
It doesn't seem to get into disk mode. that's bad news.

Something must have been damaged while applying the RUU. That usually means hardware issues. Get in touch with HTC and RMA it
[Sprint HTC EVO 4G LTE] SouL Shadow:
Hey captain, just out of curiosity, when the phone connects, can you post the output of: ls -l /dev/ttyUSB0

Still trying to figure out what type of connection is being made. When it's showing a usb dev id of 05c6:f006 it's not a gobi or qdl device, but it is something. Myself and another person are digging around to try and figure it out. He also said he knows EhostDL also shows up with the same id as qdl (05c6:9008), so this is something else altogether...

-SLS-

---------- Post added at 05:14 PM ---------- Previous post was at 04:54 PM ----------

Btw, you are the 3rd person I've seen this week to experience these same symptoms. The phone first goes in to qdl mode, then after some time starts connecting/disconnecting repeatedly, showing up as 05c6:f006. All 3 ppl reached the same result in completely different ways. You most likely because of mismatched firmware, the 2nd because he dd'd partition 5 in to partition 4 (I don't know why he thought that would be a good idea), and the 3rd simply by plugging his phone in to a "cheap" car charger.

-SLS-
[Sprint HTC EVO 4G LTE] Captain_Throwback:
Output is:

crw-rw---- 1 root dialout 188, 0 Dec 19 17:37 /dev/ttyUSB0
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
Dexter, mind explaining what you mean by contacting HTC and RMA it? Being I'm in the same boat I'm trying to figure out what to do next.

Also Soul Shadow, mine has been doing the same thing. I kept messing with the gobi_loader and thought maybe it loaded the firmware but I wasn't sure.. Then in Windows it connects/disconnects several times a minute with the same ID. In Linux it does the same but not as requently it seems and will go between 05c6:f006 Qualcomm Inc. and 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode).

Still trying to let it die to see what a cold boot will do but it was pretty much fully charged when it all happened so I'm sure it will take a few days to fully die.
[Sprint HTC EVO 4G LTE] Captain_Throwback:
I went to Sprint today and they told me the device was dead and were going to replace it for me. Unfortunately I'm on a business account and I can't get it replaced that way, but you should have no problem getting Sprint to replace it.
[Sprint HTC EVO 4G LTE] SouL Shadow:
Ah, a business account. No wonder you're not afraid to brick. What's this, #3? #4?

-SLS-
[Sprint HTC EVO 4G LTE] Captain_Throwback:
I think officially, this is only my 2nd brick. My first LTE I returned in the first 30 days to Wal-Mart (because I found it cheaper). The second one I got replaced because I upgraded the HBOOT (trying to find a downgrading method) and was worried the 1.15 would never be S-OFFed, so I got it replaced in the 30-day timeframe. My 3rd one I bricked within 10 minutes of it's being charged trying to downgrade the bootloader on it, after hex-editing the 1.15 HBOOT to appear as 1.11 and trying to write the secure flag. And this one is number 4, now also a brick.

Unfortunately, I've used too many replacements on my account in the past year, so until early February, I believe, I'm going to be stuck using my OG until a year has passed since my 3rd replacement (those go back to some OG bricks - the LTE replacements I got weren't through my account because I bought the device outright from Amazon Wireless).

So in the meantime, if you guys figure out a way to unbrick me, my device will be sitting around waiting :rolleyes:.
[Sprint HTC EVO 4G LTE] SouL Shadow:
Of course we'll keep trying. My own goal is to create a program that can diagnose and restore any bricked Qualcomm phone that supports qhsusb_dload and ehostdl. Working on Jet is just step one for me. Of course it's gonna take some time to reach that goal. But with the knowledge and help of many other ppl here on XDA I'm sure it'll happen one day.

-SLS-
[Sprint HTC EVO 4G LTE] benny3:
And here i thought i was the brick master....lol. Im glad to someone else is in the running with me.
[Sprint HTC EVO 4G LTE] dexter93:
It appears like HTC has messed up a bit here with the bootloaders... stuff between that and other Qualcomm chip based devices are a bit different.

and btw, if 05c6:f006 is what I think it is, it shouldn't be much of a help. Any chance you've got a full dmesg of a device in that state as well as ehostdl?
[Sprint HTC EVO 4G LTE] SouL Shadow:
I believe captain posted a dmesg with the entirety of a f006 connection. I haven't dealt with ehostdl yet, but darkspr1te here on xda has successfully reflashed to a working state an msm8660 based phone using the mprg8660.hex. He might have dmesg output for ehostdl. He's the one who told me ehostdl device id is 05c6:9008.

-SLS-
[Sprint HTC EVO 4G LTE] SouL Shadow:
A little digging on google suggests that 05c6:f006 is the (3g?) Modem. Not helpful for unbricking, but worth exploring. I'm surprised that id isn't listed in the qcserial.c source file as a gobi device. I'm gonna have to dig through the gobi doc's a bit to see if anything interesting pops up.

-SLS-
[Sprint HTC EVO 4G LTE] scottspa74:
Wow. Again captain?! :confused::eek: and yeah, I also thought you were on brick 4. Ouch.
[Sprint HTC EVO 4G LTE] SouL Shadow:
In the future, please don't put something that huge in a post. Use pastebin and post a link or attach a text file to your post.

-SLS-
[Sprint HTC EVO 4G LTE] dexter93:
That, or at least use

tags

Sent from the brick
[Sprint HTC EVO 4G LTE] 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.

-SLS-
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
That sounds awesome! I just broke down and bought a Galaxy S2 off Craigslist for $150 to use for the time being. Hopefully there's a way to save our devices, they're really too nice to be laying around as paperweights :eek:
[Sprint HTC EVO 4G LTE] SouL Shadow:
Agreed. Give me some time to put everything together. I thought you might want to be my first tester? Might take a week or so depending on my free time.

-SLS-
[Sprint HTC EVO 4G LTE] dexter93:
That's something we'd all be interested in. I'd like to hear your ideas, if you don't mind. Good luck :)

Sent from the brick
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
Yeah, I don't mind helping/testing at all. I still have all the related files so it's no problem. That's why I went ahead and bought the S2 so that I could figure out what to do with the EVO.

On a side note, I do not like how Samsung's work, maybe because I'm so used to HTC devices. But I have to admit, one click root is awesome and painless :laugh::good:
[Sprint HTC EVO 4G LTE] Tripp-phpBB:
Any update on this? I really miss my EVO :crying:
[Sprint HTC EVO 4G LTE] SouL Shadow:
Working on it...

-SLS-
[Sprint HTC EVO 4G LTE] pspunderground:
Oh man, thank god I found this thread. I must have flashed a boot.img to the wrong block and now I'm stuck. Same as the Captain, Linux sees the phone but no disk mode. I'm thinking of taking it to Sprint and getting a replacement, but I wanted to at least see if it's possible to save what's on the internal storage.
[Sprint HTC EVO 4G LTE] SouL Shadow:
No. We're working on a way to restore the phone, but until we finish writing the programs that are needed there is no other way to access the emmc/internal sd. If you can live without your phone for a week or 2, then you might consider waiting. (NO GUARANTEE ON TIMEFRAMES) If you can't wait then a replacement will be much faster.

-SLS-
[Sprint HTC EVO 4G LTE] scottspa74:
Damn, PSP, another one? :(
[Sprint HTC EVO 4G LTE] pspunderground:
Fine with me, I'll see if I can pick up a GNex for the meantime.

Yeah. This one is totally screwed, and I don't want to take it to Sprint because it has some very "personal" stuff in the internal storage. Might pick up a GNex and test out this PA PIE thing.
[Sprint HTC EVO 4G LTE] StrummingLevi:
Help a noob out

I was switching from sinister's v6 rom to decks. I booted into twrp recovery and wiped cache, dalvik, factory reset, and system. Then I flashed decks zip and then gapps. I then used adb reboot-bootloader to get back to the bootloader. From there I used "fastboot flash boot deckboot.img" (I changed the boot.img name to deckboot.img).

this is the message I recieved:

c:\Android>fastboot flash boot deckboot.img

sending 'boot' (1976 KB)...

OKAY [ 0.370s]

writing 'boot'...

OKAY [ 0.690s]

finished. total time: 1.070s

then I tried to reboot through adb but got this

c:\Android>adb reboot

error: device not found

so used the phone keys to reboot the phone. Now my phone will not show anything but the very first splash screen, which I think means my phone is bricked (****). I've never had this happen before and am hoping this tool can fix my problem. I had h-boot 1.19, was htc unlocked, and had s-on. Any help would be GREATLY APPRECIATED.
[Sprint HTC EVO 4G LTE] SouL Shadow:
Your not bricked. Hold vol-down and power to reboot in to bootloader. Use fastboot to reflash boot. Also remember there is no adb in bootloader, so use fastboot to reboot. You probably had a bad boot (kernel) flash or you'll need to use a different kernel. Also, double check your download to make sure it isn't corrupted (check md5sum).

Talk to the ppl in the rom's thread. They might have some additional info.

-SLS-
[Sprint HTC EVO 4G LTE] EVOuser94:
Lol, I was just about to ask if that was technically even bricked! Thanks SLS
[Sprint HTC EVO 4G LTE] StrummingLevi:
Well that makes me feel a little better, but I tried using those two buttons to get to the bootloader and the phone won't turn on. Its weird because about two seconds after I let go of power and down the phone goes to the HTC dev unlocked splash screen. I tried this multiple times to make sure I was holding power and down long enough, and got the same result each time.
[Sprint HTC EVO 4G LTE] corcgaigh:
Hold power and volume down for like 15 seconds. Take your finger off the power button for 2 or 3 seconds and repress it while holding volume down all the time