[Q] Unbrick my HTC Evo 3D - HTC EVO 3D

I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash

---

gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hey man the phone isn't bricked if you have a pulsating dim red power light, alot of people came across the problem of actually killing batteries trying to brick their phones. If its pulsating just leave it charging on the wall socked for a while bit if it is a very very dim constant red light it is bricked and you would have to use a compatible computer that takes the drivers for your phone. Read through the thread you linked and search for your issue, it is a common one
****'ll Buff Out

---

gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~

---

closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Thanks, it's just dead as can be. I did eventually get it recognized by linux on the live cd and it successfully went through it's routine to get to hboot 1.40. The next step should be to install RUU 1.13. It's a KDDI phone. I used this
RUU_Shooter_K_S_KDDI_JP_1.11.970.2_Radio_1.02.00.0906_NV_1.39_01C_release_246058_signed.exe
for initially bricking it. I extracted the ROM first. That part went smoothly . I think I did everything right and i'm where i should be now but it just doesn't do anything... nothing. I did try to mess with emmc_recover but no luck yet. When I do the RUU I just keep getting "error 170 usb connection error." I've tried uninstalling/re-installing/different versions of HTC drivers. I keep messing with it for a bit and hopefully something gives! Oh and battery, no battery, I can't get anything. If I could get it recognized on the PC I think I'd have a shot! Thanks again,
gjash

---

runcool said:
The evo3d was designed for americans. We don't support the Japan people do to over population of your race. Also if you used your head you'd notice that the computer you're using likely is in the crappy Japan language no one uses. Therefore, you need to try another computer and it'll work. We can't support every computer out there. The Drivers won't work for every type of computer on the planet.
To make this racist reply short, it's your computer. you gotta try another computer. Try using an older system. I'll have to open it up to figure out which drivers they put in there, but I know for a fact it won't work on my computer. I'd have to use it on another as well.
They should put that in the instructions. hmmm But after trying another computer, get back with us.
ps again, you said you "tried it on other computers" model numbers of those and what language are they in? It does make a difference. But I'm glad you speak english or I'd just laugh. I'm really mean today. so sorry. hahaha. Let me know if I'm right.
ps again. remember drivers drivers and drivers. drivers only work with certain types of hardware.
edit, you said linux machine, BUT DID YOU EVEN INSTALL the drivers on it? lmao!?
Click to expand...
Click to collapse
Your a complete douche bag! Its people like you that drag society down! If I met you in person I would ***** SLAP you so hard it would not be funny!
The last I checked we all bleed red.
@op I am glad you got it worked out unfortunately I can not help because I have no idea who your carrier is. What I do know is if you update to ruu 2.17.651.5 you will be back on Hboot 1.5 but with S-off.
Sorry that is all the info I can give you.

---

@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk

---

mpgrimm2 said:
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash

---

gjash said:
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
Click to expand...
Click to collapse
After downgrading/flashing Hboot 1.40, the goal of the RUU is to install an earlier fully working Stock Rom (S-On still) that came with the same Hboot 1.40 that is pushed to the phone with the downgrade tool/process. Hopefully you can find an early KDDI ruu with Hboot 1.40 for this part. This allows you to run " http://Revolutionary.io 's rooting/S-Off tool to gain "S-Off" and install a custom Recovery like Revolutionary CWM Recovery 4.0.1.4 (or 4Ext Recovery).
From there (make a nandroid backup) you can update the firmware/radio if needed (make sure hboot 1.50 isn't included) and flash a current rooted rom (stock or custom) that matches your radio/baseband as appropriate. Maybe there is a current rooted stock KDDI RUU (PG86IMG.zip) without the hboot 1.50 or someone (like Mr.Esp, freeza, or xhausx) can help you pull the stock rom apart for this step.
You can also flash the SuperUser zip (app & binary) from custom recovery to gain root on a currently installed stock rom once you have S-Off.
That's my LIMITED understanding, but I'm not 100% sure about your situation overseas since I thought all foreign carriers outside the U.S. used GSM devices.

---

closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash

---

Can't really do anything at the moment. I can't flash RUU 1.13 and I can't get it to be recognized on USB so I could use ADB and try pushing something to it. I have no idea! This is a learning thing at this point. I did root my Asus transformer before though! Thanks for any help!
gjash

---

gjash said:
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Click to expand...
Click to collapse
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
closeone said:
But take the RUU .EXE that you upgraded your phone with already and grab the ROM out of there.
To get to your temp directory: press the Windows key and R on your keyboard at the same time. Type in this exactly: %temp%
Rename the rom.zip to PG86IMG.zip and put it on your SD card.
Click to expand...
Click to collapse

---

I haven't made any progress. I'm assuming I need to use emmc_recover to overwrite the boot partition and maybe the misc partition. So can someone help me figure out identifying the partition, how I can get linux to recognize the device so I have a chance to recover? Also, at this point I settle for anything working, any Hboot, whatever... It would be nice if I could post in the original thread, hmmmm. moderator, can you help there?
thanks,
gjash

---

Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.

---

mpgrimm2 said:
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
Click to expand...
Click to collapse
You are right... both KDDI 1.09 and 1.11 have Hboot 1.50. I guess the trying Sprint 1.13 wouldn't be an option? That's the question and I can't really find out as the KDDI ones and the Sprint ones don't work because I always get USB 170 connection errors. So kinda stuck, but greatly appreciate the help!
gjash

---

mpgrimm2 said:
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
Click to expand...
Click to collapse
I will start looking there... I was thinking that the KDDI Evo 3d is CDMA and it would have the same partition layout. I'd like to determine that and go from there. Can someone explain the sprint evo 3d partition layout? thanks!
gjash

---

I'm willing to mess with this phone so if any developers have something I can do, please let me know. Otherwise, I just try to get back to stock.
I extracted original hboot from latest KDDI RUU and renamed it hboot.img and then executed 'downgrade'
I got this error:
Waiting for device...
Found the Correct Device!
Writing image file!
dd: opening `/dev/sdf34': Permission denied
FAILED!!
Any ideas? Thanks!
gjash

---

I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.

---

mpgrimm2 said:
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
Click to expand...
Click to collapse
Getting closer I think... I just needed to do a sudo ./downgrade and it flashed fine. Now I have a red light on which is more than I had before. I will go to windows now and try to flash the KDDI RUU. thanks for the help.
gjash

---

Update:
I'm back up where I started. I used Unknownforce's hboot downgrade but renamed the original hboot from the KDDI RUU to hboot.img, according to Unknownforce's direction (thanks!). After I did that, the phone just booted up normally. I thought I would have to flash the RUU but wasn't necessary. I think with some changes this whole exploit could work with the japanese cdma version of the Evo 3D. If anyone can outline what I'd need to do, it might be fun. especially that I already ordered another phone, but I won't actually need it.
gjash

---

Does your device happen to be the KDDI ISW12HT?
(I assume it is from what you've said)
Do you know the exact model you have?
The current CDMA models that I'm aware of are the:
X515c: CDMA800, CDMA1900, ESMR800, WiMAX 2.5-2.7GHz (the sprint one)
X515d: CDMA800, CDMA1900 (I forget)
X515e: CDMA900, CDMA2100 (the HTC rider)
The ISW12HT is listed as having CDMA800, CDMA2100, which arnt any of those 3.
Do you happen to know what submodel you have? I have no idea how to check as I've never touched one.
I'm wondering if it's the X515b or a yet unknown one (by unknown I mean with regards to the model number)
I've already listed all the common and less-common models on the wiki: HTC Evo 3D - XDA wiki.
But I have no idea what the ISW12HT's model is, and a fair amount of googling turns up little.
If you could poke around your device/box/manual and find it I'd appreciate it