Related
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Hiya Buddy said:
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Click to expand...
Click to collapse
Well first off, Flash Image GUI is a great program, so I want to provided my biased opinion as the author!
Off the top of my head, I am really temped to say your currently rebooting issue could very well be software related and not hardware related.
Moving around system applications, "freezing" and "unfreezing", I personally don't view as the most reliable method.
I view returning the device as the last ditch effort and giving up because everything else has failed and the issue is most likely hardware related.
If you're interested in troubleshooting the issue further, running the RUU, should return the system partition and the kernel back to a completely stock state at which point the rebooting should stop.
If the rebooting stops, then you'll know the issue was trigger by something software related and not hardware related.
Many of the RUU files for the EVO 3D are located at http://www.goo-inside.me/shooter/ruu . The directions/guides are posted all over the place on how to properly process an RUU but they are really fairly simple and bring the device back to 100% stock state.
Hope that helps and good luck!
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
I tried the instructions provided by Twolazyg but I can't get the first step to work...
So, I hold power + volume down and select fastboot.
Connect to pc with usb cable.
Open up cmd.exe and type in:
cd Desktop\Evo3DTwrp
Then follow instructions.
I type in adb reboot bootloader and then nothing happens.
I get this message on my computer:
* daemon not running. starting it now *
* daemon started sucessfully *
error: device not found
What am I doing wrong???
All I wanna do is unroot so I can return this phone for a new one...
Nevermind people, figured it out lol
Was about to Rage Quit but it works.
Got the RUU working and no longer have superuser and bootloader says relocked
Will now try the update to 651.5 then contemplate a return...
You da man joeykrim! My problem has been resolved
Hiya Buddy said:
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
Click to expand...
Click to collapse
regarding "adb", this binary is kept inside the android-sdk directory and under the subdirectory platform-tools.
many times ppl extract the adb.exe and the accompanying .dll file, package these two up into their "one click" tools and distribute.
personally, i prefer to grab the official android-sdk from google and their associate adb.exe instead of using copies distributed by other users.
hopefully that helps clarify some of the details around adb!
Hiya Buddy said:
You da man joeykrim! My problem has been resolved
Click to expand...
Click to collapse
always good to hear. another evo 3d saved!
glad it worked out. if any guides/posts were specifically helpful to you, feel free to post back your solution in case anybody else comes across this thread with the same issue.
never stops amazing me how many ppl end up with the exact same issue and these posts can be helpful!
glad to hear the issue was resolved!
@joeykrim
Everything works, but back to rooting for me until Sprint gets their **** together with 651.5 update. I took my phone in for service today after unrooting and relocking the bootloader. I was curious as to why my 3g speeds hover around 100kbps when they're usually at 800-1000kbps. According to the tech, who was running a custom rom on his Epic 4G Touch, he told me the update contained a prl that was screwy and it caused speed issues. I can confirm this with the other two evo 3ds on my account that have never been rooted/modded because they're just as slow with loading up web pages and working with apps. It was prl 21083 that is just not working out with data speed.
On Speed Test, I would put up a screen shot but I'm currently working on rooting lol, the latency would always be around 800ms and the fastest speed I got was 121kbps. There are no outages in my area because I called CS yesterday to set up my appointment and they said the towers are working normally. So it seems the 651.5 update is adds a snappyness to the UI but instead of speeding up the internet, it makes for a rather unpleasant internet experience and makes one question their "truly unlimited data and premium data fee."
So I'm gonna put TWRP back on my phone and pick a new rom based on 651.3 because of the screwed up prl unless I can keep my 651.5 and change the prl.
@Hiya buddy
I have a Sprint evo 3d flashed to reliance (carrier in india). I was on a sense 3.5 rom. I heard about this update and i restored my nandroid of stock ROM. Then i relocked it and flashed RUU (2.08.651.3). And accepted the OTA. Everything is working fine for me. No PRL's / Settings changed. My phone still works on reliance........
I did the same thing, restoring my nandroid backup of OTA 651.3 and did the update. After update 3g speeds are atrocious on Sprint, as for the software the phone is a bit snappier and more fluid than before.
hboot 1.5 s-off. Is this a true s-off or whats the deal
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
sag04463 said:
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.5 s-off is not possible at the moment. Probably wouldn't be worth it to the devs at this point in time with ICS around the corner. That OTA update will most likely change the bootloader.
sent from America....F__k yeah!
@sag04463 Jabawockee is right, that doesn't seem possible. And your issue is a common problem with Hboot 1.5. You gotta get the Flashimage GUI from joeykrim or you could do it via fastboot and remember a few simple commands. That 4G/Wifi issue seems to only be problematic with Hboot 1.5 because HTC didn't fully unlock the bootloader or something (Experts, take it easy on me I'm not sure about this) and it doesn't allow for the installation of custom kernels.
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, I will try to give as much info as I can, please let me know if there is anything else I should provide. I really appreciate any help and advice as I've been pulling my hair out for the last 3 days, spending 10+ hours trying to get my Amaze back working.
Problem started a few days ago, phone shut off, when it powered back on it was stuck on the White HTC logo. That same day the phone died completely and would not power on at all, not even the amber light. Eventually the amber light would blink the but phone wouldn't charge. I fixed this first issue by jump starting the battery with a 9V battery, something someone suggested on a thread. Worked great to get the phone charging again... but that's it. So basically I have access to the HBOOT/Fastboot and EXT4 Recovery menu's, and there is no OS on the phone, I know for sure now because I wiped the system.
When I try (but fail) to install the RUU 1.41 exe, and it checks the phone, i comes back saying my "current" version on the phone is 2.14.661.2 even though there isn't any OS on there...
Bit more background info. I purchased this phone last year off someone, it was running 4.1.2 and the bootloader was unlocked. It *is S-ON though.
Whatever else this guy did, I'm not sure as this is what I can tell, however the CID pulls up as Telus001? which the guy did tell me it was a Telus phone.
So I'm trying to load the Telus stock rom and I've been getting nowhere and pulling my hair out. I'm 10hrs in and no further then I was. So first I downloaded the Telus RUU 1.41 exe from the stock rom but it gives an Error 43. I tried this with both the bootloader locked again, and unlocked. I then downloaded the OTA 2.14.661 zip from the stock roms, and renamed it to PH85IMG, stuck that on the Ext SD card. Problem is when it boots into the HBOOT it actually see's the file, loads it, then checks it, but then returns me to the main menu. I don't get promted to update. Now I've tried this too with the bootloader unlocked, and locked. So a third go, I extracted the Rom from the 1.41 RUU and made that PH85IMG, tossed it onto the SD card and again this time it actually went further but gave another error.
I have tried to Sideload the above Roms through recovery but they give error's.
In that All In One program there is an option to fix the Mainver error, however when I run that all I get is "Device not found". The phone IS loaded under device manager as HTC Phone as I had installed the drivers. I've tried to google this fix but I can't get anywhere.
Everyone has said on forums that sticking a PH85IMG.zip file on an Ex SD and having it boot into the HBOOT menu will rebuild the phone, but I'm out of idea's how to get there because it loads the rom's, checks them, and then boots me back to the menu. There is only 2 Rom's I can find for Telus, and that's the 1.41 EXE or the OTA 2.14.661.2. My HBOOT version is 1.93.0002, RUBY PVT SHIP S-ON RL.
Thanks in advance for any help/suggestions, desperately just want my phone working again. I feel like I've been to the 4 corner's of google trying to solve this problem.
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
darkshadow1997 said:
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
Click to expand...
Click to collapse
Got it going!! Thanks for the suggestions. What did it in the end was this thread --> http://forum.xda-developers.com/showpost.php?p=27058110
I had EXT4 Recovery already, so I used his Zip and just flashed that. Phone came back up and is running great now... if only I had found his thread before the hr's and hr's I've been googling and trying things.
Hey everyone. After 22 logged hours of work on this phone and looking everywhere on XDA and AndroidForums I could really use some help guys. :crying: Since I cannot post links, please bear with my references.
HTC Evo 3D Shooter s-on hboot 1.58.0000 | device:HT17JHX02410 cid:SPCS_001 [sprint] mainver:2.95.651.6
Current status: stock rom successfully reloaded, relocked w/ security warning, stock rom stopped loading after relock. I can access 4ext as well as make commands from adb.
My goal is to flash PACMAN v 23.0.0 rom to my phone. I believe pacman uses Android 4.3. I tried flashing with 4ext, cwm, and twrp. As I recall the problem was an "error 7" across the board. Trying to solve this has lead me down the rabbit hole. I'm not even sure I'm on the right track anymore. I tried deleting the "assert getprop" lines from the beginning of the updater-script file as suggested by several users here, but that lead only to abortions. It may have something to do with 7zip asking whether to overwrite already existing files during extraction? I'm currently trying to return the phone to stock condition so I can downgrade to hboot 1.4 and get s-off, thus allowing me to flash PACMAN. This method was obtained from Unknownforce, Closeone, and RamJet73 all found on XDA.
Returning the phone to stock [in order to brick it via Unknownforce] has been a hassle because every tutorial requires that I lock the phone and then run the RUU update utility. I have tried several versions of this utility and they all drop the connection to my phone after restarting bootloader with an Error 170 [or 171]. There are several reasons for this error and one possible reason is that the software is incompatible. I think this is due to my mainver being 2.95 as opposed to 2.89 or lower. This is why I needed to find a .zip for the stock rom that would work, flash SetMainVersionLow, flash the rom zip, and then lock, bringing me to where I am now, which is a phone that will boot to bootloader and nothing more. This final method with setmainversionlow was obtained from remanifest on AndroidForums.com and I began using it because they mentioned something about 2.95 compatibility or something.
I can still lock/unlock the phone easily and flash any rom i wish, providing it is compatible. Where have I gone wrong? Is the PACMAN rom worth all of this!?
Thanks, all help is greatly appreciated.
-a
Update progress...
i can no longer get a recovery to load [4ext, twrp, cwm] and i think this is because i used a wonky verson of CWM. some have said CWM and htc 3vo don't play nicely together. all i have now is bootloader and adb. no rom loads either, just white screen with green HTC logo until battery dies. recovery programs flash successfully from adb but do not start.
my mainver has been reset to 1.00.000.0 and phone is relocked so i was trying to forget about the recovery and run a RUU. according to RamJet these are the two required items for running RUU. i've tried a 1.13 version as well as a 2.89 version. both of them act the same way as before -- immediately after the phone comes back and the program reads "erase user data" for one second, it fails and give me a 171 error.
please help. i'm a noob but i've looked EVERYWHERE for answers to these problems. if you have links to solutions i would appreciate that as well but i'd put money down that i've been there before.
i will never accept an OTA update again! all i need is hboot 1.4 and i'll be golden! how frustrating
Did you unlock again before trying to flash a recovery?
AFAIK there is no ruu that'll work for your phone until you get s off.
Sent from my Evo 3D CDMA using xda app-developers app
---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------
Short story
You need to get recovery
Then you need to flash a ROM that works on 1.58 or 1.4/1.50 and then you can get s off and downgrade your hboot and flash pac
This is more updated
http://forum.xda-developers.com/showthread.php?t=2539241
Sent from my Evo 3D CDMA using xda app-developers app
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
hanger-on said:
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
Click to expand...
Click to collapse
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
This is what I did, alternatively there's this thread with alternate methods (more designed for windows I think).
Normal disclaimer: This is (to the best of my recent memory) what I did after mucking up my E3D. Follow at your own risk, my memory, your phone, or anything else could be faulty and you could permanently brick your phone trying the following steps.
Assuming you're CMDA and S-ON still:
If you need to fix your hboot/etc download the latest (2.89) PG86IMG.zip
Download the 1.13 PG86IMG.zip
Download SetMainVersionLow.zip (I think you already have that).
Make sure you have adb and fastboot installed and working.
Make sure you're at a stable hboot with a custom recovery.
If not flash the 2.89 RUU (see flashing RUU below).
Reunlock and apply custom recovery if needed.
Run SetMainVersionLOW.zip from a custom recovery.
Before downgrading your hboot you should be (hboot 1.89, custom recovery, "fastboot getvar mainver" = 1.00.0000)
Downgrade your hboot to 1.4.something (Possibly like this)
Flash the 1.13 RUU to get a bootable system
Optionally, Revolutionary to get Revolutionary S-OFF
Optionally (CDMA ONLY), if you got S-OFF you may update the radio (the 1.13 RUU downgraded the radio too). I used the 1.06 version, the 1.09 may work as well but IIRC it was a VM leak so I just stuck with what I think is the latest Sprint image.
From here you should be able to install whatever recovery and ROM (As well as any other partition like radio, hboot, etc) that you like. Good luck.
Flashing RUU
Either use the windows exe (requires windows and a phone that boots correctly), or:
get to your fastboot/bootloader (vol down + power or "adb reboot bootloader")
fastboot oem rebootRUU
fastboot flash zip RUUFile.zip
fastboot reboot (back to bootloader if you want to).
OR
Put the zip on the root directory of the sdcard
Make sure it's named PG86IMG.zip (CaSe sEnSiTiVe)
reboot to a locked/relocked bootloader and apply the zip
Lots of credit to all the devs that made the tools, without whom I'd have been stuck on boring, outdated stock roms.
These steps collected from various xda posts and pieced together for my particular situation, including but not limited to:
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1889438
http://forum.xda-developers.com/showthread.php?t=1193101
http://forum.xda-developers.com/showthread.php?t=2074181
http://forum.xda-developers.com/showthread.php?t=1447839
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1653777
These guides should provide more background on why/how to do certain steps, as long as being better formatted and complete.
Thanks and Thanks
btharper said:
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
Click to expand...
Click to collapse
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
hanger-on said:
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
Click to expand...
Click to collapse
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
310 26345564
btharper said:
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
Click to expand...
Click to collapse
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
hanger-on said:
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
Click to expand...
Click to collapse
What were the last few steps you had done? The only time my hboot didn't come on was when I had my case on slightly off and the buttons didn't hold down correctly (try reseating your case as a last resort and make sure you can feel the buttons being pressed), at one point during the process you have to intentionally brick your phone as noted to corrupt the hboot, as long as you're S-ON it's okay and there are plenty of warnings that you must be S-ON, and one point right after recovering from that step where it's noted that you have to give it some time (I eventually just went to bed for the night because it wasn't working and I wasn't lucid enough to get it anywhere else). So probably just try pulling/replacing the battery and booting up hboot again and hopefully it works. If the red charging light is solid and dimly illuminated when plugged in then the hboot is corrupt and you can proceed to that part of the guide anyway http://forum.xda-developers.com/showthread.php?t=1547695
As well, adb only works when booted to recovery or once the normal system is booted, fastboot only works during hboot or right after rebootRUU (which is actually a part of the hboot, at least on the shooter), and emmc_recovery (used during hboot downgrade)/ultimate recovery tool should work and be able to unbrick the phone. Failing that are you on windows or linux? (revolutionary and some of the hboot downgrade steps require or work best on linux, there's a livedisc (bootable CD/USB stick that won't reset anything on your computer) you can use for the process made by closeone for the hboot downgrade process but you can use for the full process I would think (I did the whole thing on linux since that's my OS of choice) http://forum.xda-developers.com/showthread.php?t=1563342
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
hanger-on said:
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
Click to expand...
Click to collapse
Good luck with it, my advice is lots of nandoid backups and make sure you've got all the tools you need ready. The whole process can be done with linux tools (including the RUU flash). Feel free to let me know if you have any more questions.
Any luck?
Any luck on the new phone?
btharper said:
Any luck on the new phone?
Click to expand...
Click to collapse
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
hanger-on said:
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
Click to expand...
Click to collapse
If you pay all the fees/fines you can keep the phone. If not the esn will be marked as bad and it wont work on sprint.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Oh. Thanks for the heads up.
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