[Q] EVO 3D stuck on splash screen reboot - read many Q&A - HTC EVO 3D

Greetings!
I've inherited a EVO 3D that has issues. I'm new at this, but had 3 other old HTCs. I read a lot that i could for the last 12 hours in various forums and made a few mistakes/discoveries. I tried a few but i think i am stuck and i couldnt see anything else that can help so here i am. groveling for help. My first post too!
The 3D when turned on shows the HTC with white background splash screen for maybe 30-45 secs and blanks out. then reboots again ad nauseaum. In short, the phone cant boot to Android.
when plugged into the usb, seems to heat up under the camera area but not the battery, it actually drained the battery (or so i think ) because i was able to boot it before, and after i left it plugged in for an hour, it was hot and will not charge (red light blinks) i found out later voltage was below 3.0v used my old raphael to charge the batt (that works) so i can continue working on the 3D.
- i found the hboot power+vol down and was able to get into fastboot usb.
- was able to unlock using htc method
- tried loading cwm 4.0.1.4 - says success but wont enter recovery mode - just same splash screen
- tried loading cwm 5 (latest) says success but wont enter recovery mode - same as above
- found out about the RUU method. flashed back stock recovery and locked again and using the PC86IMG.zip method in hboot and a sd card. new 2.08.651.3 stock RUU was loaded successfully. but alas, still stuck in reboot/splash page.
edit: i noticed it "bypassed" one of the TP. not sure what that meant. when i was installing the stock RUU.
i dont know about the S-on or off, cant see it from hboot. can i?
i dont know if this has been rooted but the previous owner said no. it was still locked until i unlocked it.
so now, when i try recovery or factory reset, it immediately reboots and show splash screen only ad nauseaum. ( i waited as much as 5 reboots )
Help please? let me know if u have any questions.
Thank You!
CK

U should use the latest cwm not the touch one.an push it via fastboot read up on it on website below
www.rootofallevo.com
Sent from my PG86100 using XDA App

Go get flash image gui from the market. Put your recovery of choice on your SD card and flash it via flash image gui. Hboot 1.5 recovery partition is marked as "read only" hence the s-on, which can be seen in bootloader. The way around it is to fastboot into your device and flash zips that way or flash kernels and recoveries via flash image gui app.

Thanks Jwolf1,
I did try both CWM 4 and latest CWM 5 that is 3D specific. but it just reboots immediately and cycles over and over again and wont go into recovery. But! I may be missing a step or two. I havent found a post yet or a faq where there are more detailed steps to do this. maybe you can point me to one thats EVO 3D specific?
I tried the link but unfortunately, all it shows is the domain name is for sale.
CK

Thanks Jabawockee,
would i be able to use Flash image gui even if i cant get get the phone to boot aside from getting into hboot? if its possible, please let me know where i can find the instructions so i can read up.
CK

Oops that was on my part wrong link here's the right onewww.therootofallevo.com
Sent from my PG86100 using XDA App

Thanks jwolf1
I went to the site but i dont see anything that could help my case.
do you have other suggestions?
it seems that everyone expects recovery to fire up after a fastboot boot or a pc836img.zip boot from sdcard. i just cant seem to get to that page
I was observing that everytime i run a fastboot flash recovery something, i see it being loaded, but i dont see it being "written" (the progress bar on the right hand side is just a blip. no color) but when i try a recovery.img that is with the stock rom i have. i do see color in the progress bar when writing. not sure if that means anything.
I'm trying to find out if i can wipe cache and dalvik without going into recovery (since i cant boot the phone properly) but so far, all indications is ... no.
also, is there a way to peek inside the phone to see if the partitions are corrupted?
Thank You.
Ck

Is ur phone unlocked becuase if not this could be a problem if its locked
Sent from my PG86100 using XDA App

OP: You have my big thanks for trying to find an answer by yourself BEFORE you ask for it. A simple rule that n00bs are constantly failing to comprehend.
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk

Hi Jwolf1,
yes, I unlocked my phone with the HTC method.
CK

Thanks Terepan,
still hoping to figure this out...
CK

new info...
I think i may have found the issue...
while trying over and over again, i notice i wasnt getting consistent responses to a certain command. in particular,
fastboot getvar all
on most cases, i get the following response on the cmd line
getvar:all FAILED (Status read failed (Too many links))
but once in a while i get
(bootloader) version : 0.5
(bootloader) version-bootloader: 1.50.0000
(bootloader) version-baseband: 0.97.10.0808
.
.
.
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
So i think the problem is, when i try writing to recovery, the message may say OKAY. but i am not sure that its being written in.
when i try a "fastboot erase recovery"
i always get "FAILED (Status read failed (Too many links)) "
another problem could be that the boot-mode is FASTBOOT
Is this the same as the one that we are suppose to turn off in the settings?
if yes, since i cant get in the phone settings. how do i turn it off?
if no, then it doesnt matter?
and is the security: on an issue? maybe why i cant erase recovery or load recovery ? i do noticed a difference in the screen on the phone when i load a "signed" recovery vs CWM and TWRP.
Anyone? help?
Thanks.
CK

Is it correct to.say you have a Sprint Cdma 651.3 hboot 1.50 based Evo3D?
When u enter hboot/bootloader you should see either "s-on" or "s-off" near the top and either "locked, unlocked, or relocked".
I had a problem with that Ruu.zip file Mr.Esp posted, maybe a bad download. Find another link (i did) or.run the 651.5 based Ruu for the updated radio (i did).
Note: you have to relock before running the Ruu.
See this:
http://forum.sdx-developers.com/index.php?topic=18852.0
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12)
I don't know if.it will help you or not but I had some issues getting certain recovery files loaded & booting to them afterwards to flash files from. I have the details & step by step scenarios of what I did that may help if you are overlooking a step. See the ROM/recovery issues thread in my signature.
Here (posts 1 & 10th ) :
http://forum.xda-developers.com/showthread.php?t=1450466
[Solved]Hboot 1.5 Rom/Recovery install issues (fastboot/FlashimageGui/RomMgr) 2-4-12
It sounds like the kernel/boot.img may not be correctly loaded after a ROM flash, but I'm not sure.
Sent from my "up all night, sleep all day" Evo3D!

mpgrimm2,
Thanks for the help! Thanks for inspiration!
i ended up inadvertantly fixing the damn thing. it was a hardware issue but i dont know which one.
I got fed up of 4-5 nights of not sleeping and got myself another "broken" evo 3d.
It had a broken digitizer so i was going to perform the swap. as i disassembled the first 3vo. i had the mainboard out and i figure, why not test it? hooked it up to the usb and hand held a batter and lo and behold i saw "normal" recognition pattern by the pc!
I slowly assembled it again, testing it at each and every connection to see if everything is still the same or maybe some other component may be causing the issue, and i finally have a whole 3vo working! booting! now i can even fastboot boot cwm ! damn! no more boot loops!
i am not sure if its was me pressing on the mainboard and maybe a chip got a connection back or maybe just one of the cable has a loose connection but now its fully functional again. (i'm thinking more of the former than the latter)
reason why is because of the heating issue it has. i wont be surprised if the issue comes back or if others has the same issues.
so for others with the same symptoms, try disassembling it and pressing down on the part where it heats up. one of those with the heat shields (using only finger and thumb!) good luck!
CK

My evo 3d is exactly the same problem. I have disassembled and reassembled it, also pressed down the part with heat shields, but no lucky to me:-(

xdapyro said:
I think i may have found the issue...
while trying over and over again, i notice i wasnt getting consistent responses to a certain command. in particular,
fastboot getvar all
on most cases, i get the following response on the cmd line
getvar:all FAILED (Status read failed (Too many links))
but once in a while i get
(bootloader) version : 0.5
(bootloader) version-bootloader: 1.50.0000
(bootloader) version-baseband: 0.97.10.0808
.
.
.
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
So i think the problem is, when i try writing to recovery, the message may say OKAY. but i am not sure that its being written in.
when i try a "fastboot erase recovery"
i always get "FAILED (Status read failed (Too many links)) "
another problem could be that the boot-mode is FASTBOOT
Is this the same as the one that we are suppose to turn off in the settings?
if yes, since i cant get in the phone settings. how do i turn it off?
if no, then it doesnt matter?
and is the security: on an issue? maybe why i cant erase recovery or load recovery ? i do noticed a difference in the screen on the phone when i load a "signed" recovery vs CWM and TWRP.
Anyone? help?
Thanks.
CK
Click to expand...
Click to collapse
I never have erased a recovery I have flashed over the old one... Seems to overwrite that part the recovery is stored...
Haven't had any issues doing it this way...

Subaochen,
Try plugging the mainboard while disassembled, just mainboard and battery. thats how i found out mine works. then you can slowly reassemble step by step. if yours doesnt connect normally during that time, check the board over. if you can identify which part overheats then you know where to press...
Good Luck!
CK

reaper24,
I have tried "fastboot flash recovery any.img" multiple times without success, until i disassembled it and then, everything was just normal. could also be a dirty connection for me. altho when i run the RUU, it "seems" to work properly since i was able to upgrade to latest stock ROM.
I do have S-ON so i guess i would never be able to erase recovery nor boot.
hopefully everyone have the patience to troubleshoot their unit. i had to learn patience with mine.
boot loops are really the discouraging to say to least.
Sincerely,
CK

xdapyro said:
Subaochen,
Try plugging the mainboard while disassembled, just mainboard and battery. thats how i found out mine works. then you can slowly reassemble step by step. if yours doesnt connect normally during that time, check the board over. if you can identify which part overheats then you know where to press...
Good Luck!
CK
Click to expand...
Click to collapse
Thanks xdapro first!
I have tried again but not lucky:-(
Maybe my situation is not the hardware failure, just the wrong kernel or boot? When I accepted the OTA while the phone was rooted and after have a full reboot, the phone just stuck at the htc splash screen and boot loop.
I guest that, when I accepted OTA, the bootloader was updated to Hboot 1.5. But because the phone is rooted, kernel or boot partition is not updated by OTA, so the security signature is not the same between the new bootloader and the old kernel, so the boot loop.
I have tried RUU and all custom recoveries I can find, all failed, the recovery seemed installed ok, but can not boot into recovery. Also, I have tried fastboot boot recovery.img, just directly boot into the HTC splash screen and boot loop.
Anyone can give any hints? thanks a lot in advance!

Just a heads up, you have to "relock" the phone before flashing the Stock RUU's.
From "fastboot USB" Type: fastboot oem lock
It will erase the recovery in the process. I have had bad ruu downloads before. If the exe doesn't work, get the zip version.

Related

Just got a Droid Eris Free(bricked)

I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App

[Q] Bricked Flyer with CWM, charged but cannot recover GB

Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks

[Q] Help - unable to return to stock, but need to because of broken touchscreen.

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

[Q] bricked droid HTC One X+ - boot screen loop

so I bricked my device. it boot loops at the htc screen. several hours later or repair attempts and I still am back to where I started. Initially was able to load elegencia, but when the wifi was not responding I tried to load another ROM and everything has just gone downhill from there.
on my boot screen I see
***UNLOCKED***
EVITARE_UL PVT SHIP S-ON RL
HBOOT1.32.0000
CPLD-None
MICROP-None
RADIO-SSD: 1.09.55.17
EMMC-bootmode: disabled
CPU-bootmode: disabled
HW-Secure boot: enabled
modem type : mdm9215m
I dont really want to re-trace all my steps as I have tried many things to get this back up and running. I may have put the wrong ROM on as I got confused thinking this was a HTC OneXL. I think I want to put venom on here and leave it be. As of now I can no longer see the oneX+as a removable hard drive when i plug it into my pc. windows reports missing hardware ID once and a while. I have recovery as an option when I boot to hboot, but I cannot figure out how to load a boot able image from there. my backups got deleted. When I check my hardware with adb I cannot see it, but my pc detects a device being plugged in. I can flash to the device. So I think I also deleted my hardware ID trying to put in 11111111 superCID. not sure what else I can add. Any help would be appreciated.
sorry if this type of thing has been played out, I just dont want to follow another guide that gets me nothing or makes things worse.
Well, if it makes you feel any better, as long as it boots it's probably not "bricked". Since you can still flash.. can you not just reflash recovery, wipe it all, and flash stock?
hastings101 said:
Well, if it makes you feel any better, as long as it boots it's probably not "bricked". Since you can still flash.. can you not just reflash recovery, wipe it all, and flash stock?
Click to expand...
Click to collapse
it does. thanks. I am kind of nervous to do anything else without specific instruction or guidance. Where can I find a stock rom? what command sequence should I use in flash boot to get it back to normal? I know I can force ROM onto the unit with adb but adb isn't seeing my unit while fastboot is. so how do I get the rom onto my phone?
U changed the Rom with another one thin it's looping ?
Maybe it's the kernel !!
Boot into bootloader and flash a new kernal that support ur new Rom .. don't forget boot.omg
Sent from my HTC One X+ using Tapatalk 4
I did more than change the rom. I tried several things to recover the device and may have made things worse. The last rom I tried to upload, was probably not for my unit. for whatever reason I convinced myself that the reason I was having issues was because I had an htc oneXL and not a htc OneX+, and that may have compounded issues. I also tried to flash superCID to 11111111 and I was never able to do it, and at around that point my unit dissapeared as a removeable storage in windows. SO I am unsure how to put roms on the phone now. adb does not seem to see my unit.
I tried running the android phone ROM update utility but am getting a Error 155: unknown error, when I run it.
I dl'ed and ran the two top most ones here http://www.androidruu.com/index.php?developer=EvitaRE . the update went pretty far but never completed due to the first saying it was incorrect version and the second the Error 155. One thing that is different now, is I re-updated my drivers using Hasoons HTC OneX+ all in one toolkit and I can now see a drive in windows when I boot into recovery. The removable storage drive in windows tell me to insert a disk when I click on it, though. Before I could see 59 gigs of storage, it now has 0 bytes.
I think I am ok for now. I was able to get viperxl+ 2.0 to load via side loader on my second attempt. I rebooted and no more loop. still cannot see my storage in windows when plugged in via usb. but running is running. thanks for your suggestions.
drioddead said:
I think I am ok for now. I was able to get viperxl+ 2.0 to load via side loader on my second attempt. I rebooted and no more loop. still cannot see my storage in windows when plugged in via usb. but running is running. thanks for your suggestions.
Click to expand...
Click to collapse
don't try to change the [CID] u cant do it on OneX+ because (S-ON) and no way to make it off ( as i know )
try flashing stock RUU after re-lock ur Bootloader and thin u will get the OTA update its awesome
+1 to flashing a stock RUU, in theory, this should fix any issue you're having. Once back to stock and 100% working you can start flashing other ROMs.
REMEMBER: AT&T and the International phones ARE different and require matching ROMs. ie if you have ATT phone, make sure you flash an ATT ROM/kernel

HTC EVO 3D - Long Story - Trying to get back to GB with issues (Details in thread)

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

Categories

Resources