I have an old EVO 3D i want to use as an mp3/media player and camera. Problem is I'm having a hard time rooting it so I can get the pre-installed apps off it. I tried the one guide off here, but either the HTC Sync manager could find my phone, some of the tools required for the root don't work with my phone (HBOOT 1.58) or they are gone/changed. The steps involved seem more complicated than it should. Any way this can be fixed?
Depends alot on how you want to do things.
Check to see if hboot says; locked, unlocked, or relocked. If locked you will need to go to htcdev website to get unlock token and see how to unlock. Unlocked hboot lets you install custom recovery, from which you can install su. If it says relocked, all you have to do is send fastboot command to unlock, phone has unlock token already.
It sounds like you are using windows, newer then xp, which you will need to find drivers :and fixes to get phone to connect.
I would use ubuntu, linux, no need for drivers and can run from flash drive. Or windows xp, anything newer has usb issues.
Sent from my DOWNGRADED EVO 3D
this is what i get from the revolutionary exe:
PG86100 (shooter-1.58.0000, Android:4.0.3, ROM version: 2.95.651.6)
not supported
this is the Tool 0.4pre4
doesn't say locked or anything else at all really. how would i find out if it's locked or not?
turn phone off, pull battery, to ensure full power down. Put battery back. Press and hold vol. down button, then press power button.
Read this for more info:
http://forum.xda-developers.com/showthread.php?t=1817513
Sent from my DOWNGRADED EVO 3D
It says LOCKED. so where do I go from here?
You unlock, or s-off.
Sent from my DOWNGRADED EVO 3D
I put together an easy(easy as it gets) guide for s-off'ing your CDMA Ev03d with hboot 1.5x
the process is a little more complicated for 1.5x hboot phones due to revolutionary s-off not supporting any version newer than 1.4. And don't bother with unlocking with the token retrieval / HTcdev.com mess. It won't work with hboot 1.58. besides you will not have the full benefit of S-off with just unlocked phone
So you must brick the phone, then plug into linux terminal and and run recovery tool which will downgrade the hboot to 1.4 and the main version to 0.01. Then flash the main version to 1.13 by running a RUU exe. After that, you may run revolutionary s-off and you're rooted. Run the latest RUU and you are done and back on main version 2.95(after system updates) with hboot 1.58 and S-OFF, fully rooted
Things you'll need:
blank CD and burner, know how to boot from a CD
data USB cable
Micro-sd adapter so you can put files directly on your micro-sd from your PC
All summarized in my post here
http://forum.xda-developers.com/showthread.php?t=2794935
Good luck
okay
could ya explain all that to in a way that even a noob like me can understand?
Cieran said:
could ya explain all that to in a way that even a noob like me can understand?
Click to expand...
Click to collapse
Without some basic tech know-how, you're going to have a bad time
Your Hboot 1.58 needs to be downgraded to 1.40(the dirty way) before you can run revolutionary S-OFF.
Things you'll need:
Linux live boot disk/USB, trial version
USB data cable
Micro-sd adapter so you can put files on your micro-sd from your PC
All summarized in my post here in the first post
http://forum.xda-developers.com/showthread.php?t=2794935
This isn't completely true. You can soff on hboot 1.58. It's been done many times and I did it myself.
This guide is pretty straight forward and geared exactly toward your situation: http://forum.xda-developers.com/showthread.php?t=1889438
Otto, how's it going? , I know your situation sucked. It happens for some people, but it's not the case that everyone on 1.58 has to go through it. Most people can just go with juopunutbear s-off. It's usually when there's a phone repair and the motherboard had been swapped. It causes a mismatch in firmware with no option to run an ruu.
Brian706 said:
This isn't completely true. You can soff on hboot 1.58. It's been done many times and I did it myself.
This guide is pretty straight forward and geared exactly toward your situation: http://forum.xda-developers.com/showthread.php?t=1889438
Otto, how's it going? , I know your situation sucked. It happens for some people, but it's not the case that everyone on 1.58 has to go through it. Most people can just go with juopunutbear s-off. It's usually when there's a phone repair and the motherboard had been swapped. It causes a mismatch in firmware with no option to run an ruu.
Click to expand...
Click to collapse
Oh yeah you could do that! Though I am totally unfamiliar with the juopunutbear, I was under the impression that it was for GSM only
I recently walked another user through rooting their sprint 1.58 hboot with success with brick/downgrade, though unknownforce's ultimate.zip did not work for them
http://forum.xda-developers.com/htc-evo-3d/cdma-development/help-root-unlock-t2829008
Related
Is there anyway to reset the Rezound to the factory locked bootloader?
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment); here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/sho...uide to S-On to restore that too if you wish.
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment) and have it handy; here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Now make sure your bootloader is Locked before running the RUU. Check this and be certain; have to do a bit of extra work if it isn't, so please say you didn't Dev Unlock again after doing S-off lol. (I did this. Had to repeat the whole S-off process to achieve a "Locked" message ultimately. Not fun.)
Ok, after making sure bootloader is Locked... Running that RUU should put the stock hboot back on, verify that after the process. And remeber to turn USB Debugging back on in the stock ROM after running that RUU lol . Then proceed with the guide on the same computer you got all those Dev tools on from doing S-off.
Click to expand...
Click to collapse
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
LakerStar25 said:
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
PhantasmRezound said:
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
Click to expand...
Click to collapse
Cool I was just trying to help out lol.
Sent from my ICS Rezound
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
This is the General section. Refer to the Questions and Answers section. Just because you weren't rooting doesn't mean you can't post in the correct section.
Sent from my PG86100 using XDA
Evo3d HBoot/S-off Differences/Rooting Background Info 8-5-12
Edit: I will no longer be maintaining this post. Instead I have started a full thread to help track the changes:
http://forum.xda-developers.com/showthread.php?p=29844067#post29844067
I've had the Evo3D for a few months now and must say I really have come to like it.
If you want root, it's a bit quirky, You basically have 3 options:
(See the Hboot 1.50 HTC Unlock Guide in my signature for info & links)
1) HTCdev.com's "Bootloader Unlock":
Basically this leaves the bootloader's (Hboot 1.50) security flag on (S-On) but "unlocks the bootloader" (kinda like the phones Bios) so that you can manually flash everything except for Radios (Baseband) and Boot Logo's (Splash Screen). Kernels & roms can be flashed once a custom recovery is installed, but there are "extra" steps involved because the /boot partition (kernel/zImage) can only be set to write access from the Android OS or by initiating custom recovery from a pc's "Fastboot Command Prompt". There are workarounds, some work better than others. To flash Radio updates, you have to relock the bootloader and flash an OEM Full Stock Ruu (Rom Update Utility), kinda like Samsung's Sw Updater for the Transform. You also have to register your device with HTC and it "may void your warranty".
2) Downgrade Bootloader from Hboot 1.50 to 1.40 (to get S-Off):
This is a recent development by Unknownforce in the last few weeks. Basically involves corrupting the flashing process of the RUU by removing power in the middle of the flash and "bricking it" (more like mostly bricked). It forces the phone into a special eMMC Download mode that can only be fixed by pushing the older bootloader to the phone from a Linux pc. Good thing is that Closeone has a Linux LiveCD.iso that you copy to a USB Drive or CD and temporarily boot to a custom Linux Interface specifically set up for flashing the bootloader.
Once that's done, you rerun an earlier RUU (compatible with Hboot 1.40) to get the phone working fully, then root via "Revolutionary's site" (another fastboot/adb rooting tool) to get S-Off (Full root), load a recovery, update the radio, then you can flash roms & kernels like normal.
My current setup (keep coming back to MeanRom):
Hboot 1.40.1100 (Downgraded)
Firmware: 2.17.651.5 (Base)
Radio: 1.06.00.1216 (from 2.17 base)
Recovery: 4ext Recovery (Fully Compatible with CWM, which was a bit buggy except for v4.0.1.4)
Rom: MeanRom ICS
kernel: atx 1.9.1
Mods: LeeDroid Tweaks CDMA, ADW_Ex Launcher, Several Apps removed with SDX Stock App Remover (posted in SDX Evo3D General section).
3) Edit: Juopunutbear's S-OFF Wire Trick:
There is a similar third option now to brick (short out pins with a wire) & replace the bootloader on 1.50 with s-off but I haven't tried it. (Must HTC Unlock first & have a rooted "Stockish" rom installed)
dmdelgado said:
I wanted to share with everyone else suffering from HBoot 1.5 that if you have been using Chads ICS Firmware fix because of constant bootloops you dont need to downgrade your HBoot to 1.4. I know every time i would flash the firmware fix it would break many bugs that had already been fixed, I had to flash it to avoid getting constant boot-loops. But Juopunutbear's Wire trick to get S-Off was a miracle fix, and after it turns S-Off it asks if you would like to install a custom Juopunutbear Hboot. After this is done you are officially on HBoot 1.5 S-Off! And can flash any ICSense ROMS successfully without having bootloops! I really hope this helps someone enjoy their ROMs that much MORE because i know it feels good TO FINALLY BE FREED FROM THE CURSE OF S-ON!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------
HBoot S-Off Background Info:
mpgrimm2 said:
To be honest I have not considered anything about the bootloader since downgrading and getting s-Off. I will point out that us "downgraders" don't have hboot 1.40 but "Revolutionary Hboot 1.40.1100".
My understanding is that it has more functions than stock hboot 1.40/1.50 but less functions than the Engineering Hboot. Kinda like your Jbear Hboot 1.50.5050, but I could be wrong. I'm sure one of the devs like Mike, Chad, Joeykrim, xhausx, freeza, Unknownforce, Closeone, etc would know.
Hboots:____________________Differences:
1.04.xxxx ? (Eng Hboot) = Extended functions .... Appear to be incompatible with newer 2.89 based kernels
1.30 (Stock Hboot with 1.07.651.1 Gb) .......... Appear to be incompatible with newer 2.89 based kernels
1.40 (Stock Hboot with 1.13.651.7 Gb) ......... Appear to be incompatible with newer 2.89 based kernels
1.40.1100 (incl. w/Revolutionary S-Off) ................. Appear to be incompatible with newer 2.89 based kernels
1.50 (Stock Hboot with 2.17.651.5 Gb) ........ 2.89 based kernels status unknown
1.50.5050 (incl. w/Jbear for GB S-Off) .................. May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.57.5757 (incl. w/Jbear for ICS S-Off) ................. May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.58 (Stock Hboot with 2.89.651.2 ICS) ............. Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
...............................................................................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)
Click to expand...
Click to collapse
Unknownforce said:
First, keep in mind, that there are technically two S-OFF's, the hboot and the radio. This is somewhat misleading. When you're phone displays S-OFF on the hboot screen, this is actually the Radio S-OFF, not hboot S-OFF. Gaining hboot S-OFF is actually just as simple as flashing a new modified hboot. (which is why there are revo hboot and now jbear hboot, they have been modified to now have hboot S-OFF)
hboot S-OFF is almost the same as unlocking your bootloader via HTC's method. Just that HTC's method doesn't get you S-OFF and is more limited than revo/jbear S-OFF.
So a few of the the differences here are:
1.) ENG Hboot is S-OFF and offers more fastboot commands and a few more unlocked features. This is an advanced hboot that you can do serious damage to the partitions in your phone if you don't know what you're doing. It's kind of like an all access pass.
2.) The stock hboots are S-ON, they don't allow very many of the fastboot commands. These are limited to very basic fastboot commands.
3.) revo/jbear are S-OFF, they allow for many of the "standard" fastboot commands, like flashing to partitions and whatnot, but not nearly as "feature packed" as the eng hboot, these are typically enough for normal users.
As to it providing any benefit to using a newer version of hboot, the only one that provides more features is the eng hboot for more fastboot access. What this means is that there's no major feature/performance difference between 1.30 and 1.57 aside from some appearance and some security adjustments (to allow HTC Unlock and also attempt to counter the S-OFF/exploits)
As I understand it, the differences between radio S-OFF and hboot S-OFF are basically as follows:
Radio S-OFF has signature verification off, what this means is that you can flash any PG86IMG.zip and it doesn't have to be signed by HTC. This will allow it to flash just about anything from there. This is why you can revert to a lower hboot without having to do anything special when you accidentally (or purposefully) flash a new hboot over your revo or any other hboot. Radio S-OFF also doesn't check the signature of most of the current partitions (so you don't get "security warning")
hboot S-OFF allows many more of the fastboot commands to be accepted and opens up the ability to flash some of the restricted partitions from it as well.
Hope this helps clear up some confusion.
Click to expand...
Click to collapse
fergdogg23 said:
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1585846
mnomaanw said:
Try this http://forum.xda-developers.com/showthread.php?t=1585846
Click to expand...
Click to collapse
I wouldnt try this.
I would first try to downgrade hboot or just unlock your hboot 1.50 and use 4ext to flash roms and flash GUI to flash kernels..
I ended up bricking my evo by using the Juopunutbear S-OFF wire trick.
fergdogg23 said:
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
Click to expand...
Click to collapse
I know exactly how you feel. I used to flash my HTC Wing all the time with Windows Mobile. Even tried my hand at cooking some roms. Coming over to Android many years later -- yeah makes you feel like a noob again.
Its not that hard really. You are already familiar with what is involved with flashing. All you have to do is take it one step at a time. Just like you did years ago with Windows Mobile. Lots of tutorials walk you right through it. After you do it, you'll look back and see how easy it really was.
You'll need to unlock your bootloader and root the phone. Once you've done that you can flash almost any rom on here. I would not go S-Off just yet. I have read that downgrading your H-Boot slows the phone way down. There really is no good way to do it with 1.5 yet. There may not ever be as Sprint stopped selling the Evo 3D and lots of people are moving on to other phones.
The night I did mine, I started at 7:00 pm and finally figured it all out and got it done it was 4:30 am.
Just have to do alot of reading. No way around that.
How does soff slow the phone?
Sent from my SPH-D710 using Tapatalk 2
patrao_n said:
How does soff slow the phone?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Just read on here, its not S-Off that slows down the phone, its the downgrade of H-Boot.
Here is the link to what I read:
http://forum.xda-developers.com/showthread.php?t=1661709
Here is what the guy says:
frexe said:
I recently downgraded to 1.4 hboot with revolutionary s off. I then updated with Freezas AIO. And running meanrom ics 1.0 now.
The problem is that my 3g speed is at slug speeds. Ping is up at 900ish download and upload is below 100.
Before I was on hboot 1.5 2.17.651.5_Radio_1.06.00.1216 and had decent speeds.
Just wondering if someone can shed some light to this problem. Or maybe I have to go back to 1.5hboot and live without a true root.
My Phone is flashed to boost.
Click to expand...
Click to collapse
iTzLOLtrain said:
I wouldnt try this.
I would first try to downgrade hboot or just unlock your hboot 1.50 and use 4ext to flash roms and flash GUI to flash kernels..
I ended up bricking my evo by using the Juopunutbear S-OFF wire trick.
Click to expand...
Click to collapse
This^
Unlock and try 4ext first it will allow you to flash roms and kernels without the need to downgrade. I downgraded to hboot 1.4 because I was getting boot loops but I read that a lot of unlocked hboot 1.5 S-On people are fine so try first before going through what can be a tricky and somewhat risky process to get S-Off.
I have experienced no slowdown from downgrading and I can't see how that would have an effect but I'll let someone more knowledgeable chime in if that is a factor or not.
I haven't seen any speed slow downs with Hboot 1.50 downgraded to 1.40 either. I have seen slow downs when sprint was working on tower upgrades that went away after a week or two (drove me nuts). I would point out that the person that reported downgrade "related" slow downs had flashed the phone to Boost mobile, so there's another factor to consider. Edit: Reading thru the rest of that thread proves it wasn't related to Hboot/S-off.
I'm a bit leary on the Juno method, but I've seen references to people shorting out the pin before in lieu of a Jtag setup, so it's pretty much as sound/risky as Unknownforce's Downgrade method. Although, the hboot downgrade has a huge number of successful attempts and the handful of permabricks where because someone got in a hurry and skipped a step/didn't pay attention to what they were doing.
mpgrimm2 said:
I'm a bit leary on the Juno method, but I've seen references to people shorting out the pin before in lieu of a Jtag setup, so it's pretty much as sound/risky as Unknownforce's Downgrade method. Although, the hboot downgrade has a huge number of successful attempts and the handful of permabricks where because someone got in a hurry and skipped a step/didn't pay attention to what they were doing.
Click to expand...
Click to collapse
Agreed.
I'll admit that the JuopunutBear (wire trick) method may look a little more risky than the HBoot 1.4 downgrade process, but I've done two Evo 3D's using a paperclip wrapped in scotch tape (not the preferred equipment) and haven't had a problem with either phone. Several of the "bricked" users have reported a USB status in Windows of "QHSUSB_DLOAD" in the HTC Unbricking Project thread and I added this post from the HTC Amaze forum to the thread which claims that status is not a real brick (if it was there wouldn't be any indication the phone was even connected in Windows) and it can be recovered using the ControlBear utility. I got no feedback from the people that were reporting that status, and the OP also indicated that the phones were probably not hard bricked.
I haven't seen any feedback from anyone with a "bricked" phone about contacting the developers via the IRC channel they advertise on their website (#juopunutbear on freenode) or PM'ing them as I suggested in the jb thread. I have only been able to identify a few users that claim to have bricked their phones via the jb method, but they seem to be posting about their negative experience with that process in many different threads.
I don't really care which method people choose to get to S-Off as they all have risks involved and it's up to each person to determine what level of risk they are willing to take. The JuopunutBear method was a lot simpler for me and I'm not convinced the risk is that high if you use the right type of wire (insulated copper wire is recommended) and follow the instructions as documented (which a lot of people don't), but that method is fairly new and I wouldn't blame people that are HBoot 1.5 S-On for waiting a little while longer to see how many more users claim to have bricked their phones with that method.
Most people can get by with HBoot 1.5 S-On using tools like 4EXT SmartFlash and Flash Image GUI, but for those that have problems with the stock ICS kernel or want to get to S-Off for other reasons, at least there are alternatives now.
ramjet73
just stay with 1.5 s-on
ive been on 1.5 for awhile with s on and it hasnt been that big of a deal. My old evo was soff and there were some nice rom switching with cwm but I uaes to use cwm to flash roms on my evo and it worked like a charm but it does not let you flash the kernal, I was having to flash kernal seperatly with flash gui which is a free download but 4xt works fine and dont have to flash kernal seperatly but eitherway is fine as I usually use specific kernals anyway. I found a routin that I am happy with and wont switch until I brick my phone or get a new one lol.
Good luck
htc evo 3d custom coolıcs ınstalled and hboot 1.53.0007 s-on bootloader unlocked .how to return orginal gb rom ? and what must ı do? ım tried joupebar error secondary backup failed
i believe getting s-off is your only option. can't down grade bootloader with security on.. that i know of. try the wire trick its easy.
i have hboot 1.53,0007 am unlocked with s-off how do i get a rom to work?
a.k.a.jus.cuz said:
i believe getting s-off is your only option. can't down grade bootloader with security on.. that i know of. try the wire trick its easy.
Click to expand...
Click to collapse
I unlocked my device (I bought 2 more evo's so have 3 now) and one of them has hboot 1.53.0007 and is s-off I have tried to install more than one rom and none of them get past the HTC screen before rebooting except Kingcobra it reboots after the funky animation screen. I cant get fastboot to flash a new kernel or hboot. It always says remote not allowed. And I have tried using 4ext and clockwork both touch and non touch versions. I don't know what to do from here.
As you are s-off I would suggest you downgrade your hboot using method E (step 1 to step 4 only)
http://forum.xda-developers.com/showthread.php?t=1743466
Your hboot is the problem. It causes problems with lots of roms. Yoda's ICS and Viper3D are two roms that i'm sure work fine with your hboot. But it will be a lot easier if you tried the method above to downgrade
EM|NEM said:
As you are s-off I would suggest you downgrade your hboot using method E (step 1 to step 4 only)
http://forum.xda-developers.com/showthread.php?t=1743466
Your hboot is the problem. It causes problems with lots of roms. Yoda's ICS and Viper3D are two roms that i'm sure work fine with your hboot. But it will be a lot easier if you tried the method above to downgrade
Click to expand...
Click to collapse
Thanks for the reply. I have tried the PG86IMG.zip file more than once and also checked the MD5 before and after moving it to the SD card it checks fine but when it tries to install it it says
Model ID incorrect!
Update Fail!
Press <POWER> to reboot
no matter how many times I try to install it. So I will give the ROMs a try that you mentioned. Out of curiosity I thought that when I got juopunutupbear sauced enough lol it would also give me a new Hboot at the same time it asked me if I wanted it installed I picked yes. The first phone I unlocked took three tries (it's still my current one I don't want to sell that one, sentimental reasons for making the paper weight that was given to me work again) but this one took about 10+ tries to get it to work. I think that after this when I pick up any EVOs I will check the Hboot first.
Oh and it also has an extra entry under RADIO it's OpenDSP-v02.6.0.226.00.0202 The other ones don't have that and also have different Hboots (the ones that worked the first go pretty much) and I looked it up and apparently its also an x515a which from what I gather means it has an extra frequency 850 1900(?),and 2100 (i may have gotten exact values wrong, can't rem off the top of my head. Anyway I will get back to you once I have tried the ROMs.
I have three EVO 3Ds (trying to make a buck buying locked phones from pawn shops and then unlocking them and reselling for a profit, once I get this one going again and sold I can work on the next and so on. Then I can also (each time I get one done) give a percentage of the profits (20% or so split up I think is OK) to places like this and to the devs that put together all the necessary bits to achieve a rooted any carrier phones and ROMs. I wholeheartedly support this type of philosophy and am going through the process of learning to become a dev too and can't wait till I too can participate just as much as the rest but that's enough rambling sorry for going on there got off topic.
EM|NEM said:
As you are s-off I would suggest you downgrade your hboot using method E (step 1 to step 4 only)
http://forum.xda-developers.com/showthread.php?t=1743466
Your hboot is the problem. It causes problems with lots of roms. Yoda's ICS and Viper3D are two roms that i'm sure work fine with your hboot. But it will be a lot easier if you tried the method above to downgrade
Click to expand...
Click to collapse
i tried them both and they didn't work either. Am going to give downgrade a go. And also if I change the cidnum in the info file inside the zip it will work for Wrong ID errors? I am surprised to hear that (read it somewhere else earlier) I thought that file was like a readme.txt file. I am edgy about messing about with the RADIO as I hear that if you get that wrong you may not be able to get back into Hboot and if that happens it has to go to the factory to get fixed. Please advise on that if you know. Thanks
EM|NEM said:
As you are s-off I would suggest you downgrade your hboot using method E (step 1 to step 4 only)
http://forum.xda-developers.com/showthread.php?t=1743466
Your hboot is the problem. It causes problems with lots of roms. Yoda's ICS and Viper3D are two roms that i'm sure work fine with your hboot. But it will be a lot easier if you tried the method above to downgrade
Click to expand...
Click to collapse
OMG! I got it working YAY!!! Finally, man you saved me from having to do the ROM roulette testing each one and switching up the various tweaks each time, wiping, etc... Thank you so much. I got Yoda ICS to run with the Stock HTC kernel. It's a bit twitchy but if it locks up the soft keys or taping stops working I just hit power to turn off the screen and then turn it on with power again and then it goes back to accepting input again. I am going to make a back up of the device and then see what is different from the other one I have and if they are the same (MD5s for a start then if they are different and when I take a look at unyaffs I will delve further)
Anyway I did notice that I wasn't getting the boot to flash properly at least according to the logs and when I looked at the version of the device it was Android 2.3.7 so maybe that had something to do with it. Anywho thanks again. And when I get to it I think I will write a nubs guide/checklist that has either links or whatever it needs for all the quirks I have come up against while doing this phone and the other one. Obviously it will have to be specific to the EVO and for the specs that mine have. Plus I know in the future to stay away from Hboot 1.53.0007 for dang sure. You made my day I hope you have just as good of one.
Glad to see you've got it working again. Theres a text file inside pg86img thats checks your cid. You should take a look here it will clear up some of your questions
http://forum.xda-developers.com/showthread.php?t=1906172
I'm running revolutionary hboot and i have had no problems at all on any rom. Just make sure you are running the latest firmware and you'll be good to go
Sorry for the short reply. Im at my uni, busy week ahead
Sent from my HTC EVO 3D X515m
GSM HBOOT 1.58.0007 S-ON to S-OFF? unable to downgrade to hboot 1.49.0007
Hi, i have also similiar problem, so I would like to ask anyone for help... I unlocked my EVO3D by HTCdev HBOOT is 1.53.0007 and I want to downgrade to hboot 1.49.0007/8 for revolutionary because otherwise I cant flash CM9/10 roms succsessfully....I have read a lots of threads but only thing what was succesfull is the hboot unlock...but Im not S-OFF...
So for the instance, the phone:
Is HTC EVO3D GSM
CID is HTC__001
was on stock ICS 4.0.3 OTA rom
HBOOT 1.53.0007 S-ON
UNLOCKED S-ON by htcdev method
followed this thread to root http://forum.xda-developers.com/show...php?p=28106291 and flash ROM Method D and B, but i didnt do the wire trick way - my phone is some kind of different so I think wire trick is not possible, so I skipped that (and controlbear.exe and the download links are no longer working on unlimited.io, only way i get the files was from htcevohacks.com but controlbear.exe shows me some error that I dont remember for now, i will try and post it).
Then it's working on ICS NonSense® 4.0
to downgrade HBOOT to 1.49.0007 and get revolutionary S-OFF so i followed this http://forum.xda-developers.com/show....php?t=1471246
The first method copying mmcblk0p31.img to sdcard and here im stuck....I dont understand why, but the command "adb shell dd....." copies mmcblk0p31 file of 16kB size and total empty content, so I cant change any version to 1.20.720.1 and cant downgrade....
So how to solve this problem? Is it cause that first I need to get hboot 1.53 S-OFF? If so, how?
Im sorry but currently the only method to downgrade your hboot is AFTER you get s-off with wire trick. What kind of problem are you facing with the wire trick? It sometimes takes more than a couple of attempts to do it right
EM|NEM said:
Im sorry but currently the only method to downgrade your hboot is AFTER you get s-off with wire trick. What kind of problem are you facing with the wire trick? It sometimes takes more than a couple of attempts to do it right
Click to expand...
Click to collapse
The first problem is that on all tutorials and vids the HTC EVO3D back look like this
Code:
h ttp:// htcevohacks.com/wp-content/uploads/2012/06/howto-downgrade-soff-htcevo3d-9-500x344.jpg
But my phone look like this - the SIMcard slot is just on the SD slot
Code:
ht tp:// syenceiction.7u.cz/IMG_20121001_165929.jpg
(sry for the code but im not allowed to post outside links yet...)
So i dont know if there is a way how to make the wire trick, because the SIMslot seems to be blocking the contact to SDcard...
And the second problem, this is what happens when I plug the phone to USB and run controlbear.exe:
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....
Backing up......
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.....
Click to expand...
Click to collapse
And here it ends and I can't do anything...USB Debugging enabled...
bro if you read through this thread the OP tells you that you have to ignore that failed warning and continue.
http://forum.xda-developers.com/showthread.php?t=1743466
and yes the method is a bit different for gsm phones.
http://unlimited.io/jb_shooteru.htm
you need to tap on the sim card metal slot instead of the sdcard one(in case of cdma)
...thanks... this needed to know. It's the first time im flashing evo3d, I sit whole day reading threads, tutorials and watching vids, so this went already out of me so I was surprised by the differences.
But in case of the controlbear.exe, I read whole post but I don't see anything about this error. How can I ignore it if the program stops with message "Press enter to exit" ?? I press enter, the window with program will close, so I run program as admin again and the same error is repeating...maybe its because actually the phone is on 20% battery so Im charging it now then i will try it with at least 75%...but...
Are you sure you are rooted? cause you need to be for this to work
If using windows make sure to run the program as admin.
unlimited.io is working for me
heres the file you need
Thans, I already find and downloaded, I have all the time the "GB" version.
Yes I think I rly am rooted...for root I followed the steps in the method B by friend.evil http://forum.xda-developers.com/showthread.php?t=1743466 and installed exactly the superuser.zip file in step B9. Also I installed titanium Backup and other apps requiring root acces all working...
But strange was when I tried in adb.exe command "adb shell" then "#su" on th phone nothing happens - nothing like "super user permission granted" (I have it in other language than english so i dont know the form of the exact msg in eng").
//So now it looks like i made a big stupidity, I run the !GB" version of controlbear, everything was now working, phone restarted but because I realized that Im on ICS not GB ROM i Closed the controlbear when waiting for device...and the phone is now stuck on JuounutBear Screen.........
//So i can get to Hboot so it shouldnt be bricked, I will try to solve this reflashing boot.img via fastboot.
http://forum.xda-developers.com/showthread.php?t=1743466&page=29
a guy did the same thing you did. flash the boot.img of stock rom in fastboot
EM|NEM said:
http://forum.xda-developers.com/showthread.php?t=1743466&page=29
a guy did the same thing you did. flash the boot.img of stock rom in fastboot
Click to expand...
Click to collapse
Thank you very much...I've just successfully performed the wire trick and have JuopunutBear HBOOT 1.53.7777 S-OFF....I wonder how someone can figure out some wire trick and other mods...its nice.
Hopefully now I should be able to downgrade the HBOOT to 1.49.0007...
Good luck with that
now i can finally go back to studying damn i hate my uni
GL too...
but still ther is the problem with copying mmcblk0p31.img to SDcard...Im still wondering why, if my microSD is bad or the ROM is bad or what...when trying this way from CMD http://forum.xda-developers.com/showthread.php?t=1471246 this is doing my cmd:
Code:
C:\evo3dflash>adb shell dd if=/dev/block/mmcblk0p31 of=/mnt/sdcard/mmcblk0p31.im
g
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
32+0 records in
32+0 records out
16384 bytes transferred in 0.002 secs (8192000 bytes/sec)
this is bad, it should be 2045+0 records in 2045+0 records out and 1047040 bytes copied...
Anyone knows why? why is the image size of 16kB and total empty? because there is no information about the version as it should be according to this http://cache.gyazo.com/a0c2a86fabf917602dbb82a1a6a93d82.png
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
I had the same thing happen. No clue how to make it work. Earlier hboot maybe...
Sent from my PG86100 using xda premium
Did you take the OTA?
Even if you didn't, I had the same problem.
What I had to do to fix it is run the RUU.
http://forum.xda-developers.com/showpost.php?p=30106576&postcount=20
Then do the HTC unlock crap again. It will then work.
You'll know because your phone will display a pop-up asking you if you want to unlock or not.
Didn't take the ota..
Sent from my PG86100 using xda premium
I would try it anyways. Can't hurt.
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
Click to expand...
Click to collapse
Have you tried the 2.89 RUU that was linked in post #3 above? I flashed it after using virus's firmware upgrade and taking the Sprint ICS OTA and it still ran fine for me. It should be the same as the OTA, but I have more confidence in the RUU.
ramjet73
halfaddict said:
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
Click to expand...
Click to collapse
FOUND SOLUTION..............
You have to download the RUU that matches the HTC Software on your phone. Go to settings > about > scroll down to Software Version and google search the RUU that matches.
Enable USB Debugging and let phone sit at home screen.
Run the RUU exe from withing windows on your PC wait for it to finish and and it will wipe phone in the process.
After it is done, boot to fastboot and run the HTC Unlock Token command again and this time you will get the prompt on the cell phone screen.
I spent 6 hours plus trying to root my wife phone wile tetherd from my Epic Touch GS2.
Samsung side of the world is a WHOLE lot easier. Everything is done within Oden for Samsung devices.
Anyway, there you go guys!
hypersonicx said:
FOUND SOLUTION..............
Click to expand...
Click to collapse
That's what I was recommending, except you don't have to relock your bootloader before running the RUU and unlock it after if you are S-OFF. And here's the downloads for the current RUU so others don't have to Google it.
Glad it worked for you.
ramjet73
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
htcdev.com said:
HTC has identified a known issue that may be experienced by some users with a Sprint EVO 3D that shipped with version 2.08.651.2, even if it was updated to a newer software version via FOTA. When attempting to unlock, a blank screen appears on the device after step 12 in the instructions and the process does not complete. As a workaround for users who experience this issue, we suggest you upgrade the ROM to 2.17.651.5 first via OTA then download and install the RUU from the table below to fix the issue before attempting the unlock process. This issue will also be fixed in the ICS update scheduled for EVO 3D.
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
ramjet73 said:
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
Click to expand...
Click to collapse
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
Click to expand...
Click to collapse
t3project said:
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
Click to expand...
Click to collapse
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
ramjet73 said:
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
Click to expand...
Click to collapse
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
The firmware updates don't update you 100% to the 2.89 build. You need to flash the 2.89 RUU to do that, as has already been pointed out in this thread, and for some reason the HTC unlock appears to work after that. I really don't know what the difference is between taking the OTA and flashing the RUU is, but they should be the same.
For someone like you that is already S-OFF, you could always flash the JuopunutBear 1.58.5858 bootloader if you need to run the 2.89 kernel and get most of the benefits of the ENG bootloader. However, that bootloader will not work properly with GB and AOSP ROM's.
ramjet73
i know this man!!! lol
t3project said:
i know this man!!! lol
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's good. Now you also know that flashing the 2.89.651.2 RUU.exe will let you do the HTC unlock with the 1.58 bootloader.
ramjet73
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
I concur. I'm not a novice when it comes to unlocking bootloaders & rooting phones. I've unlocked more bootloaders through htcdev.com than I can count & this gentleman is absolutely right! HTC really needs to get it together! Samsung devices are so much easier to work with. You don't run into these stupid little problems with Samsung phones. Usually, what goes for one Samsung device goes for all!
I digress, but anyhow, I'm well aware that reinstalling the operating system on an EVO 3D via an RUU will allow the token that you get from htcdev.com to work, and I have used this fix several times in the past on the last Gingerbread OS (Software version 2.17.651.5), but here's my issue. I have an EVO 3D with S-ON & a LOCKED bootloader that was updated over the air to ICS & when I go to unlock the bootloader via htcdev.com, nothing happens & HTC claimed that this issue would be fixed with the ICS update, but guess what? It wasn't!
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
So what I did from here is requested for someone from the XDA community to create a PG86IMG for me so that I could see about reinstalling the ICS OS on the phone through the bootloader (Shout outs to Karl! He came through on this right away. Karl you are the man!). Unfortunately, when I go to use the PG86IMG file, it does all of this loading & appears as if it's going to work but ultimately goes back to the HBOOT home screen & doesn't give me an option to install the f'n operating system! This sh*t blows & I am all out of ideas as to what to do from here. I am basically stuck.
On anther note, I tried to use the ICS RUU that I have on another EVO 3D with no success, but I was successfully able to reinstall the ICS operating system on this same EVO 3D via the PG86IMG file that Karl provided. What in the world is going on here?! If anyone can offer any helpful advice, I'd certainly appreciate it. Thanx in advance. (On a side note this other EVO 3D that I was able to reinstalled the ICS OS on via the PG86IMG file has an UNLOCKED bootloader & is S-OFF. I don't know if this makes any difference, but I thought I'd share this anyway.)
RioSoul said:
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
Click to expand...
Click to collapse
The 170 error means that the RUU.exe can't find your phone. Make sure the phone is in "fasboot USB" mode in the bootloader, then try running "fastboot devices" from the PC directory you used to root your phone. It should come back with a serial number that starts with "HT". If it doesn't, you may have a problem with the USB port on your phone, although it probably won't go into fastboot USB mode in the bootloader if that is the case. If you get the serial number, try running the RUU.exe again from there. If you get a 17x error with the RUU.exe, usually restarting it will get past that error as long as you have the proper connectivity to the phone.
ramjet73
achppr who
Confirmed, this worked for me. Thanks for your help! :good:
I bought 3d evo a year ago and I tempered with it at first to root. I could not root it but it was s-off. Anyways , this whole time I thought I was getting updates and such because I was receiving update notifications and downloading them, and phone was restarting afterwards , so I thought everything was ok. Then, recently I checked software versions in settings and I was shocked. My phone was exactly the same as the first day. Then I tried to do a hard factory reset from settings. It did not work. Tried again from the bootloader menu, it did not reset again. There was a method by relocking it at first and using RUU's to make it back to original state. I relocked it but RUU file did not work , i think it was incompatible and gave an error.
Here are the version numbers in settings:
Android version - 2.3.4
HTC Sense - 3.0
Software - 1.20.468.6
This is the bootloader screen:
*****Relocked*****
****Security Warning*****
S- On
Hboot 1.49.0018 Emm-boot Oct 3-2011
I have a phone which can not revert to original state and can not apply any updates. Hboot version is an issue I always see guides about 1.50.
Do I have to start over and S-off first ? I have tried everything, putting pc86img.zip file to sd card , it reads during bootloader but does not ask to update. I tried sprint ruu file from windows but it did not work either. Need directions because I am really pissed off. Please help. Thanks.
bro i'm pretty sure that thats a gsm phone. please dont try to flash any cdma(sprint) stuff on it.
Normally I would have directed you to a thread containing gsm RUU's but apparently the new hosting site is down. Keep checking here though
http://forum.xda-developers.com/showthread.php?t=2094402
A word of warning: If you update using the RUU you will have the new hboot 1.53 and it is only possible to achieve s-off on that hboot with the wire trick. Whereas your current hboot can make use of flashmaniac's tool to downgrade and s-offf using revolutionary
EM|NEM said:
bro i'm pretty sure that thats a gsm phone. please dont try to flash any cdma(sprint) stuff on it.
Normally I would have directed you to a thread containing gsm RUU's but apparently the new hosting site is down. Keep checking here though
http://forum.xda-developers.com/showthread.php?t=2094402
A word of warning: If you update using the RUU you will have the new hboot 1.53 and it is only possible to achieve s-off on that hboot with the wire trick. Whereas your current hboot can make use of flashmaniac's tool to downgrade and s-offf using revolutionary
Click to expand...
Click to collapse
thanks man, I looked around and found stock a rom suitable for my region.And it worked. Now I'm updating to android 4