Related
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0
Ok, so I tired to dabble in custom roms and I got burnt!!!
First things first,
HTC One X+ (International)
Version Main: 1.17.708.1
CID: HTC_622
S-On
HBOOT: 1.35.0000
Radio: 3.1204.168.32
I'm trying to RUU the device back to the stock and then never tinker again!
Can someone please step me through this, all the links I'm finding are dead or the RUU doesn't run.
Many thanks =)
Get hasoons20000 one x+ toolkit it has a link for ruu
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
CJMilsey said:
Gave this a shot, I cannot find the appropriate RUU for my device.
****...
Click to expand...
Click to collapse
What country did you buy it from and what is your CID?
I bought it online (from Asia) The CID is 622 as above.
Addicted2xda said:
What country did you buy it from and what is your CID?
Click to expand...
Click to collapse
Bump
CJMilsey said:
Bump
Click to expand...
Click to collapse
Refer to the posting rules. You should not bump a thread within 24 hours...
You can download the RUU (ENRC2B) from this :
http://forum.xda-developers.com/showthread.php?t=2094118
you need to relock your bootloader before running the RUU
http://www.androidfiles.org/ruu/get...Radio_3.1204.168.32_release_299722_signed.exe
I'm sorry, I must have missed that one :/
I Tried this before but the RUU used didn't work, but I'll try to re-download and go from there.
(RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed.exe)
Will it be a problem that my phone is 1.17.708.1 and that this is 1.17.707.1 (0.0.001 lower)?
Also, do I need to flash the stock recovery. And If so where would I go about getting it?
You will only have to relock the bootloader again and then (while in fastboot) run the RUU. Remember that you will lose everything on the device.
To relock the bootloader use Hansoon's toolkit. It has all the commands build in for easy use.
"Wrong CID" I'm not sure why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
CJMilsey said:
"Wrong CID" I'm not why this is wrong. 662 came back from fastboot getvar cid, and does indeed correspond to Hong Kong.
What would you advise from here dear sir?
Click to expand...
Click to collapse
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
Are you sure it's a generic HK CID? And not an operator locked one? Maybe you need the RUU from a particular operator.....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I looked up the CID and it's just for HK, the phone came unlock so I doubt it needs a locked RUU. But hey, I've been wrong before.
Is there any reason the phone would not accept the correct RUU?
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Thanks
Addicted2xda said:
Okk,
This might seem a bit weird but I had the same issue with my Intl HOX+ and I have given it to hTC and they asked me to shell out aroun 18K to change the motherboard! (Which of course we all know is not required since this is a software issue).
So here is what I did:
1. I relocked the boot loader (I hope you have the unlock_code.bin with you, else get it from hTCDev)
2. Of course it started giving relocked security warning.
3. Again unlocked the boot loader and voila - it booted straight in to Elegancia!
This essentiially happens because unlocking the bootloader formats all the partitions except system and boot (I guess, because my media files were gone...).
See if this gets you through.
But DO IT AT YOUR OWN RISK!
I am talking about International HOX+, I do not know if ATT works in a different way.
Click to expand...
Click to collapse
I had a small bootloader problem and was just surfing this section.I used your method of relocking and again unlocking and my problem was solved.I found it obligatery for me to thank you.
---------- Post added at 10:30 AM ---------- Previous post was at 10:21 AM ----------
CJMilsey said:
Unfortunately that hasn't worked and I'm still stuck with the stall during boot :/
I think my best bet will the RUU, but I just can't get one that will work.
Do you know a ROM that I could side-load onto my device and just use it with that?
Click to expand...
Click to collapse
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
faandrabi said:
I have unbricked mine by efforts of two long days and nights from about same problem. Provide the details and I will try to help you out,
1. can you boot to recovery.
2. If yes.which recovery you use.
3. what were you doing when this happened.
Click to expand...
Click to collapse
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
flash twrp through fasboot as only twrp provides side load option.
when twrp is flashed ,boot to recovery.side load incertcoin rom through hasoons toolkit.
don't worry about 707 or 708 etc.Mine was 707.1 but i am using incertcoin which is 401.3
after falshing incertcoin if it is again in boot loop then
use this command from adb
adb shell
wipe data
and reboot
you will be done.
CJMilsey said:
1. No recovery works, and by mistake I performed a full erase with TWRP (don't ask me how, I honestly don't know why I did this) so despite all that they don't even exist anymore.
3. I flashed to Boot File as I couldn't get CM10.1 (Lior's HOX+ plug) to install and considered that my solve it. (I was wrong)
From this stuff I'm pretty sure it's broke, but I can get to the boot loader and recovery. Though I ran the appropriate (so I thought) RUU and it didn't work due to CID which stumped me.
Click to expand...
Click to collapse
I hope you are on TWRP 2.5? If not update it...
And then use adb sideload
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
rmuruga said:
Hi,
I have the exact same problem.. I can get to TWRP recovery and HBOOT and my PC only detects the phone if its in recovery.
my CID is HTC__001.
I am trying to find a working RUU to run..
I tried this one: RUU_ENRC2B_U_JB_45_hTC_Asia_TW_1.14.709.17_Radio_3.1204.167.31_release_291089_signed.exe
(But that didn't work)
Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
download incertcoin rom from hox+ android development & hasoon toolkit v2.4
boot in recovery
connect to pc
run onex+.exe and side load the rom
after it is done flash boot.img inside rom through fasboot command
and you will be done
Full disclosure, this isn't my phone and I'm helping a coworker who did some things. The phone was originally purchased without service as she was switching from AT&T to T-mobile and didn't have it setup yet.
Incident: The phone was unlocked and rooted when last night she used a "toolkit" (I have no idea which one and she said she deleted the folder with everything), then locked it with the toolkit and used the fastboot oem unlock to get back in. When the stock rom was installed again the screen wouldn't work and I was able to navigate with a OTG mouse connected. All of the custom roms work fine as far as the screen goes but the stock one is like it's missing a driver. The other issue here is the SIM card doesn't pickup a network, I verified the Access Point is setup correctly and tried with both the LTE (fast) setup and regular. It's entirely possible that the radio was hosed to start with and we didn't find out until the sim card was purchased on Monday. At this point I'd just like to get it back to FULL stock and see if she can do anything with the Warranty (not sure if this is really possible yet). So, on to things I've tried.
1. Display Issue on Stock, I read this could be a kernel issue and attempted to flash several Stockish roms from here. Also the kernel from mugetsu666. That kernel a long with the other 3-4 stock roms from page 1. Nothing resolved.
2. No Signal. While going through the stock and custom roms all I really need is the signal to work. The PA install had the wrong APN settings and I updated them with the Defaults. No change, so I moved on to radios, maybe that's it. Flashed all the radios from here and a couple other random ones from the individual rom I was using. Nothing.
3. Ok, at this point I just want back to stock. This phone is toast and I'm tired of dealing with it for the day. Found the t-mobile ruu file here and attempted to run it as admin on a windows 7 and 8 machines. The bootloader was locked before attempting this and I tried in fastboot or just the phone being on. All I get is error 170 which is the usb connection issue. Fastboot does recognize my device so the RUU should pickup, now i'm really stuck.
Needless to say it's hasn't been a productive day at work. Any assistance is greatly appreciated. THANKS!!
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
joselv456 said:
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
This one?. The link is dead. Can I use another supercid by at or M7?
Thanks for the help. I'm really a Samsung user so this is new
C Murder said:
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
Click to expand...
Click to collapse
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Sooooo, I think there is more wrong here than a simple RUU update. I noticed under the *** UNLOCKED *** that the model is M7_UL, which i'm finding is a Europe model. I'm toast.. warm buttery toast i think.
Side note: Don't offer to help coworkers if you haven't worked on a phone like this before.
I have m7ul which was originally a t-mobile device when I got it used. I flashed the GE ruu no problem. You should be ok with that device.
Sent from my HTC One using Tapatalk 4
kronikwisdom said:
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Click to expand...
Click to collapse
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
C Murder said:
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
Click to expand...
Click to collapse
Yes, I've tried the tmobile RUU from these forums.
I've just made things worse now it seems because I updated the CID back to "T-MOB010" and now the recovery image won't stick. Seems like I'm missing something else from the boot.img but I've tried to flash the original firmware.zip on these forums. So tired of this thing.
Monday and I'm still at this. After relocking my boot loader per the request of the owner I'm unable to unlock it now. Requested a new code and that didn't change anything. The command to unlock from fastboot completes and writes successfully but the screen doesn't popup on my phone to accept the unlock.
Fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 kb)... <--- not sure if that's correct, the file is actually 256b but maybe it's under 1 so it doesn't show.
OKAY [ 0.150s ]
writing 'unlocktoken'...
OKAY [ 0.010s ]
finished. total time: 0.160s
this phone is going further down hill.
last ditch effort and I ran the RUU from Tmobile on an old XP machine, worked. back to stock.. not sure what to say but i'm tired of looking.. haha
I don't know why she needed to do all that soff in the first place ... This device doesn't require soff to flash roms or even soff to flash tmobile roms on the att m7 or vise versa
It's a lot like nexus model the boot.img flashes In roms soff is usually needed to do that on other htc devices not the One
Simple carrier unlock and Bootloader unlock with recovery is all you need to flash any Rom onto any m7 besides sprint and vzw
Soff and supercid doesnt seem like it was necessary in her case
HTC is touchy stuff takes reading 10 times over before attempting anything...
If we had a samsung Odin method we would be golden ..
Glad it's fixed
Sent from my HTC One using xda app-developers app
Hi everyone, here is my last attempt to save my desire x.
First : i’m not completely a newbee, i’m use to the devlopment with android i’m owing a TF700 and xperia mini pro, both rooted and running under custom rom.
My problem : This summer my phone used to switched off and on again, once per day. One day, it switched off and i couldn’t start it again (stuck on HTC logo). I did the first operation which came in my mind « factory reset by the bootlader » , same problem !
My second problem, i bought the phone in India were i was studying, HTC France explained me that i should return to the shop where i bought the phone to fix it up…..hahahahaa !
I gave up, now i want fix it by myself
How my phone is actually
HBOOT : 1.24
Access to the bootloader possible
Fastboot command works
Rooted with WIndroid
Why not flashing ?
I tried…First, i rooted sucessfully my phone, installed a ICS recovery but no a single one is working, can’t wipe any cache, ect…and the zip installation failed with CWM, TWRP, Philz….
I get these messages for all recoveries :
- Can’t mount eMMC
- Can’t mount cache
Any attempt to mount the eMMC and the cache is a fail, though the Ext-sd card can be mounted.
I tried the RUU (asia) , I relocked the bootloader with windroid, the RUU failed, it sent the files, and failed at the « signature update », the code error is 155.
Everything which is cited is what i did today, I did many other operations this summer but i couldn’t precisely describe it, i just know that i did a lot, and i’m today without any other solution….thus here is my post !
Thanks for your answers !
hugiz said:
Hi everyone, here is my last attempt to save my desire x.
First : i’m not completely a newbee, i’m use to the devlopment with android i’m owing a TF700 and xperia mini pro, both rooted and running under custom rom.
My problem : This summer my phone used to switched off and on again, once per day. One day, it switched off and i couldn’t start it again (stuck on HTC logo). I did the first operation which came in my mind « factory reset by the bootlader » , same problem !
My second problem, i bought the phone in India were i was studying, HTC France explained me that i should return to the shop where i bought the phone to fix it up…..hahahahaa !
I gave up, now i want fix it by myself
How my phone is actually
HBOOT : 1.24
Access to the bootloader possible
Fastboot command works
Rooted with WIndroid
Why not flashing ?
I tried…First, i rooted sucessfully my phone, installed a ICS recovery but no a single one is working, can’t wipe any cache, ect…and the zip installation failed with CWM, TWRP, Philz….
I get these messages for all recoveries :
- Can’t mount eMMC
- Can’t mount cache
Any attempt to mount the eMMC and the cache is a fail, though the Ext-sd card can be mounted.
I tried the RUU (asia) , I relocked the bootloader with windroid, the RUU failed, it sent the files, and failed at the « signature update », the code error is 155.
Everything which is cited is what i did today, I did many other operations this summer but i couldn’t precisely describe it, i just know that i did a lot, and i’m today without any other solution….thus here is my post !
Thanks for your answers !
Click to expand...
Click to collapse
Have you tried to wipe cache in fastboot? Use the command: ''fastboot erase cache''
Try to flash a Hboot 1.24 recovery after that and factory reset the phone. Then flash the rom of your choice (for 1.24 hboot of course)
So, I used the clear cache tool of the WinDroid, i flashed the TWRP 2.5.0.0 recovery for ICS, reset the phone, the same, can't clear any cache !
hugiz said:
So, I used the clear cache tool of the WinDroid, i flashed the TWRP 2.5.0.0 recovery for ICS, reset the phone, the same, can't clear any cache !
Click to expand...
Click to collapse
Don't use any tool, just do the command yourself
You sure you have hboot 1.24? For me, this looks like the typical hboot mismatch...
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
You sure you have hboot 1.24? For me, this looks like the typical hboot mismatch...
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wait you got a point, can you show us your bootloader screen @hugiz
ok I did the command directly in cmd, it works, i flashed the recovery...same
hugiz said:
ok I did the command directly in cmd, it works, i flashed the recovery...same
Click to expand...
Click to collapse
Show me a pic of your bootloader/fastboot screen
Here is the screen of the BL !
Here is the Fastboot one...same
hugiz said:
Here is the screen of the BL !
Click to expand...
Click to collapse
Now that's interesting... i didn't know that there were different partition layouts in hboot 1.21 as well. But then at least the RUU should work...
Which CID do you have? You are sure your CID is compatible with the RUU?
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
hugiz said:
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
Click to expand...
Click to collapse
Relock your bootloader and run the ruu in the bootloader mode (not the fastboot mode)
GtrCraft said:
Relock your bootloader and run the ruu in the bootloader mode (not the fastboot mode)
Click to expand...
Click to collapse
I need an explication here, I did relock the BL ( how can i check if it's really relock ?), so, I should launch the program of the RUU while i'm in the HBOOT USB window and no the FASTBOOT USB one, right ?
hugiz said:
I need an explication here, I did relock the BL ( how can i check if it's really relock ?), so, I should launch the program of the RUU while i'm in the HBOOT USB window and no the FASTBOOT USB one, right ?
Click to expand...
Click to collapse
At the top of the bootloader screen the purple text is showing if it's locked, unlocked or relocked.
I see at the pics you send the bootloader is unlocked so do this:
1. Go to fastboot mode and do this command: ''fastboot oem lock''
2. It will restart after that but as you said it will be stuck at the htc logo so go back to the bootloader.
3. If it says RELOCKED at the top of the screen you are good to go
4. Go into bootloader/hboot mode
5. Connect the phone to the PC and run the RUU again
GtrCraft said:
At the top of the bootloader screen the purple text is showing if it's locked, unlocked or relocked.
I see at the pics you send the bootloader is unlocked so do this:
1. Go to fastboot mode and do this command: ''fastboot oem lock''
2. It will restart after that but as you said it will be stuck at the htc logo so go back to the bootloader.
3. If it says RELOCKED at the top of the screen you are good to go
4. Go into bootloader/hboot mode
5. Connect the phone to the PC and run the RUU again
Click to expand...
Click to collapse
so, i tried 3 times, i get :
(bootloader) lock sucessfully...
FAILED ( status read failes (no such file or directory))
finished. total time 1.027s
reboot, stuck logo....
hugiz said:
so, i tried 3 times, i get :
(bootloader) lock sucessfully...
FAILED ( status read failes (no such file or directory))
finished. total time 1.027s
reboot, stuck logo....
Click to expand...
Click to collapse
Then send it to a htc repaire center or use it as a paperweight
hugiz said:
cid: HTC__038
i took the RUU asia of this link http://www.androidruu.com/?developer=Proto
I guess it's the right one, because when i called htc the guy noticed immediatly that i bought it there !
Ya, indeed this phone is interesting, if we can't fixe it up, i give to xda for science purpose ! :laugh::laugh::laugh:
By the way, the RUU detect the phone and its version,1.18.XXXX but can't restore it !
Click to expand...
Click to collapse
I know the problem why the RUU is not working. Your software version is 1.18.XXXX but RUU software version is 1.14.XXXX. As you can't downgrade your phone with RUU, that won't work.
Take a look at that: http://forum.xda-developers.com/showthread.php?t=2210619&highlight=nandroid
You'll find a restorable nand backup there, which first part is incomplete, so you need to flash the second file as well like explained in the thread. Good luck!
Ok that's look interesting, i followed the step perfectly ,i put on my SD card the files of this folder
- https://drive.google.com/folderview?id=0Bytqvf8J9vnabkhxVWJJMk45dFU&usp=sharing from this link http://forum.xda-developers.com/showpost.php?p=40541546&postcount=102 which match with my CID.
I put the file as indicated in theses folders TWRP/BACKUPS/SERIALNO/2013-03-28--11-51-07
Once in twrp i can mount the sd card put nothing appear in the available backups but i can see the files in the integrated file explorer of TWRP....
You need to replace SERIALNO with the actual Serial number of your phone. If you don't know how to do that, you can do a little trick: Just do a nand backup of your current configuration, the folder with your Serial Number should then be created. After that, paste the files from the link to that folder. Also, do not forget do flash the additional file needed for CID HTC_038 to be completely stock.
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
mhnx said:
Hello my friend, the reason you can't load the pg86img is because you have unlocked bootloader. The fastboot commands could help us a lot, did you follow the controlbear instructions in the correct order? I think there is a way through windows with exe files I don't remember well because I did S-OFF 3years+ before. If you want we can try together some time. If you want for start we can flash 4ext recovery and a custom rom so your phone can boot.
Click to expand...
Click to collapse
Hi there, I didn't know with having the bootloader unlocked that it would cause any issues, but there you go!
Yeah, if there's a guide to flashing the 4EXT Recovery and a custom rom that would be great!
I have a fair idea of how to do it, but don't want to try anything without having someone of greater knowledge point me in the right direction
Thanks!
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
skylirizm said:
Just an update, I did come across a thread to flash 4EXT Recovery onto my Evo 3D.
Put Recovery.img into my platform-tools folder, used the fastboot command, it said sending and OK.
Selected recovery and still boot loops. No idea where to go from here now
Click to expand...
Click to collapse
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
mhnx said:
Sorry for being late, I had some problems with my internet connection. Can you boot into recovery? Power button + Vol- and choose recovery, if you can boot tell me first which version you have and second what type of rom you want to have.
Click to expand...
Click to collapse
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
skylirizm said:
Hey there,
That's OK, I don't mind the wait, it's all good!
I can boot into Fastboot, but when I choose recovery/factory reset etc, it shows the HTC Logo and then goes into a bootloop.
As for the ROM, I want to get the original GB ROM for it because when I updated it to the latest ICS that's when the camera and touch started to get weird, whereas beforehand it was fine.
So thinking, if I go back down to GB Stock, that it should be all fine again, but I am not too sure on that one.
Thanks!
Click to expand...
Click to collapse
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
mhnx said:
Well, we have to downgrade the hboot version first. Did you do the wire trick procedure right? You can download a pg86img and flash it first to fix the bootloops. First lock the bootloader. When you finish this report here. I have to sleep it's late here and I work early. I'll send you tomorrow. See you.
Click to expand...
Click to collapse
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
skylirizm said:
Ok, the technician I took the phone to supposedly did the wire trick for S-OFF, but, it's still S-ON.
I have downloaded a lot of stock PG86IMG files before posting on here and none work, they scan when in bootloader and then nothing after that.
But that would be because I haven't locked the bootloader. So in saying this, I lock the bootloader following steps on many forum posts on here, then flash a .zip file that's correct and then it should all work?
I'll wait for your response, thanks!
Click to expand...
Click to collapse
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
mhnx said:
I do not think that the wire trick procedure was correct because you are still s on. Lock the bootloader and try to load the zip.
Click to expand...
Click to collapse
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
skylirizm said:
Hey, so I tried a P86IMG.zip from this thread here - http://forum.xda-developers.com/showthread.php?t=2274635
I couldn't find another one and with that I get an error "Main Version Fail" or "Main Version Check Fail".
I then tried RUU and RUU in zip format.
RUU comes back with wrong bootloader error. (I couldn't find an RUU that matched my radio version so I went with the nearest one)
RUU Zip comes back through fastboot with "remote 43 main version check fail"
Also I tried to do the Wire Trick and got stuck at the "ADB and Fastboot not found" even though the files are there and the phone is connected.
So still a little bit...stuck :\
Also relocked bootloader it just says relocked now.
If you need any other additional info I can send screenshots of what it's at.
Thanks!
Click to expand...
Click to collapse
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
mhnx said:
Did you try flashing the zip after the locking? You are doing the wire trick procedure on live linux cd?
Click to expand...
Click to collapse
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
skylirizm said:
Yes, tried flashing the zip after locking. Live CD is being used also. I will try again later. Thanks!
Click to expand...
Click to collapse
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
Oh that would be extremely helpful, I can use Linux, but prefer my Windows PC as it has all the files and it's just easier.
Thanks so much!
mhnx said:
If you want we can do the procedure together some time. Keep in mind that you have to unlock again. We can search for the windows version too.
Click to expand...
Click to collapse
donkeykong1 said:
I have windows version of wire trick procedure. If you need it, I'll gladly share it via PM
Click to expand...
Click to collapse
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
skylirizm said:
So update -
DK sent me the windows version of ControlBear via PM - thank you.
Have an unlocked bootloader.
I tried ControlBear, and because I can not boot into the OS, I start it at Fastboot USB, it reboots, then says "Connecting to Device", then "Testing ADB connection" then "Press Enter To Exit" and that's it, can't do anything else from there, and it gets stuck in the boot loop that it still has.
Tried again to google for methods for HBOOT 1.53, and am trying some of those methods, but it's not looking good at all.
I haven't even got to the stage where it asks me to do any sort of wire trick.
Also my battery in the EVO 3D has died so am using a battery out of a HTC MyTouch 4G with help from electrical tape :\
So now, any suggestions? I am trying to flash another RUU that's stock for my Radio (Well, it's close enough - RUUs are both 11.25.3504.06, mine is 11.25.3504.16)
EDIT: Tried all RUUs with relocked bootloader and comes back with bootloader error (ERROR 140). So, no idea.
Also it's scanning for PG86DIAG.img files on the SD Card - that's not normal is it.
Do you think we should give up on it, it's probably hard bricked and dead now
I think it's literally hard bricked and no way to bring it back from the dead.
As per my original post, all the details for the phone are there. And it sucks that I can't find a correct RUU for my phone (As it was Telstra AU - latest update of ICS)
AHH I don't know.
Click to expand...
Click to collapse
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
skylirizm said:
Hey there, thanks for the help again, unfortunately, still didn't work.
I unlocked the bootloader again. Then tried to flash what you said, it said "writing" then "successful". I pulled the battery and tried to boot into recovery and just loops
Click to expand...
Click to collapse
Try doing:
fastboot erase recovery
fastboot flash recovery "recovery".img
fastboot format system
fastboot format boot
And if it still doesn't let me send you a boot.img in some minutes to try flashing it.
EDIT: And something last, you can still do the controlbear trick while not in OS, its easy if you wanna try let me know.
skylirizm said:
Hey all,
I have this HTC EVO 3D that just, refuses to co-operate with me.
Story goes -
Got it on ICS and everything was working fine on it. I looked for updates available and it found a 28MB update that I installed and once the phone rebooted with the update, the camera fails to start and the touch screen just starts going crazy and opening everything, whereas before it fine.
So, I attempted to try and get it back to Gingerbread.
And googled and googled and googled.
Reason why I have opened a new thread is cause it's sort of everything going weird with it.
Of course, trying RUU files and trying to flash RUU in zip failed so on so forth.
I had unlocked the Bootloader and S-ON is on at this point. Also had CWM recovery installed and was able to boot into that.
With this in place, I read up on the wire trick and thought, yeah it seems a bit hard, I'll take it to a phone repair shop, where they had the phone for 2 weeks and told me that it was S-OFF and back to stock.
Since they had it and I got it back, it's now stuck in a boot loop and I can not get into any recovery etc (With the original SD Card in it). Can get to Bootloader and fastboot though.
Spent the last 3 hours with about 20 tabs in Chrome opened on how to exactly go from here and I am stuck.
Got a Linux Laptop here and tried to ControlBear and it comes up with ADB and Fastboot not found (Directory points to it being in tmp..no idea)
TL;DR
HTC Evo 3D (Australian Variant, was running ICS Telstra OEM)
Unlocked Bootloader
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio - 11.25.3504.16 M
Boot Loops, No Recovery, Fastboot commands work on windows.
So just wondering, where do I go from here. I don't know if the device is completely bricked now or if it can be saved.
(I tried a number of zip files on the SD Card (PG86IMG.zip) and nothing due to having S-ON.
Hoping someone can provide a procedure or point me in the right direction.
As reference, I used this thread mostly before it was taken to the Repair Shop and got stuffed.
Any help is appreciated.
Thanks so much.
Click to expand...
Click to collapse
i have same problem plz give me GB rom link and flash method
---------- Post added at 07:56 AM ---------- Previous post was at 07:42 AM ----------
mhnx said:
First of all you should be unlocked now with 1.53 hboot. Download from here the latest 4ext recovery (4EXT_Recovery_Touch_v1.0.0.6_RC3)
It's in my mega account don't worry about malicious software I downloaded it 5 minutes before doing this post. If you don't have unlocked your bootloader do it with the tokens HTC sent you in your email. Flash this recovery from fastboot (fastboot flash recovery "recoveryname".img). After that remove the battery and re-enter fastboot mode (Vol down+power button) and choose recovery. If you manage to boot into recovery from there tell me to send you a link for a rom to flash. I don't believe its a hard brick.
Click to expand...
Click to collapse
plz help my htc evo 3d is bootloop no go to any recovery mode i flash all recovery
BOOTLOADER-UNLOCK
HBOOT-1.53.0007
RADIO-11.25.3504.06.M
i flash many ruu.exe but this
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3
flash seccussfully without any error but no booting only htc logo plz help