Related
In the past days, I've seen many threads with messed up instructions on how to root EVO 3D.
Steps are simple.
It depends on "what" you wanna do.
Now, here's a step by step guide but first, you need to know what we will do here.
TO PREVENT YOU FROM WASTING YOUR TIME, GIVE THE WHOLE THING A VAGUE READ BEFORE STARTING THE PROCESS.
WARNING: FLASHING ROMS AND UPDATING RRU "WILL" WIPE ALL DATA FROM YOUR PHONE. BACKUP.
NO, YOU CAN NOT BRICK YOUR PHONE. UNLESS YOU'RE REALLY THAT RETARDED. HBOOT AND BOOTLOADER CAN ALWAYS BE USED TO UNBRICK A BRICKED PHONE.
1) Root - Its like administrator on windows 7. Just allows you to access and modify files a normal user wont be able to access. Anything that needs to be tampered with outside of your SD card, especially a folder called "system" will need root.
2)Hboot - Bootloader. It turns your phone on. Only 08/09 version has S-OFF ability. You can check this version by removing the battery, then putting it back in and pressing vol- and power at the same time till it goes into bootloader. HBOOT version is in the top left corner.
3)Superuser - An Application to grant other applications to have access to "system" folder.
4)RRU - your software/firmware/update
5)Bootloader - Turn off, remove battery, put it back in, press vol- and power at the same time to access bootloader.
6)Fastboot - Control the bootloader.
7)ABD - its like ssh shell but for controlling your phone via computer command prompt with usb cable attached.
8) S-OFF - Gives you the ability flash unsigned Boot.img/kernel zImage files etc.
VODAFONE USERS, TRY THIS: http://forum.xda-developers.com/showthread.php?t=1495657
I don't have a vodafone branded phone so I have no idea what they are saying.
It depends on many what exactly it is that you want to do and what exactly is convenient for you.
FIRST BASIC THING FOR IT ALL. UNLOCK
http://www.htcdev.com
go there, get everything you need, follow the instructions, and unlock your phone. Cant get much simpler.
I would read the steps first because they're all about how to get ADB and FASTBOOT. http://revolutionary.io/ <--- go here, click download for windows and you'll get all the tools you need. ADB/Drivers/Fastboot/revolutionary.
Make a Folder in C:\ named "adb" and extract the contents of this zip into that folder.
AFTER THIS, THERE ARE MANY WAYS.
1) Flash recovery and roms. Use Fastboot to flash boot.img from every rom you flash or kernel. Why choose this? Simpler but takes time, not 100% compatible with every rom.
2) Flash A recovery called TWRP with dumlock. ----> http://forum.xda-developers.com/showthread.php?t=1509748 Why choose this? hy choose this? Simple, but again, Not compatible with every rom and takes time.
3) Flash Recovery and use FLASH IMAGE GUI. *Google this.* Why choose this? Simple, but again, Not compatible with every rom and takes time.
4) Downgrade your hboot, as follows. *Why choose this? Simple. Takes time the first time, but is 100% compatible with every rom out there, and more convenient, fast, etc etc.
SECOND BASIC THING: (IGNORE THIS IS YOU HAVE HBOOT 1.49.0009 or below.)
Recovery.
For the time being, we shall use Revolutionary cwm ---> http://forum.xda-developers.com/showthread.php?t=1218800
Why? It works. Thats why. Only 2 recoveries can charge, this and TWRP, we'll head to that later.
Keys are simple. Volume to go up and down, Power/camera for selecting an option.
After the recovery is done, http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Put this in your sd card, get into recovery *Open bootloader, go to recovery, press power to select and it will reboot into recovery. Select install and choose the superuser-something.zip and it will install. If it gives an error, go back, select advanced instead of install and choose fix permissions, reboot into rom.. then reboot into recovery and try installing again.
After thats done, your rom is rooted.
THIRD STEP:
DOWNGRADING HBOOT: (IGNORE THIS IS YOU HAVE HBOOT 1.49.0009 or below.)
Any hboot above 1.49.0009 cant Have s-off.
Make sure USB debugging mode is on which you can find in settings, applications, development.
Click start, in search, write "cmd" and cmd will show up in top, *assuming you're on windows 7, windows xp is start, all programs, accessories*
After the command prompt opens, write "cd CD:\adb" <--- the folder i asked you to create and extract in step 1
then write
"adb shell"
"su" <-- this will ask you you for permissions on your phone, click ALLOW.
"dd if=/mnt/sdcard/mmcblk0p31.img of=/dev/block/mmcblk0p31"
What it should Look like --->http://cache.gyazo.com/6c8c47a5f9c34e3725c081c048dd3271.png
Don' close command prompt and switch your phone to USB storage mode, and copy mmcblk0p31 into your pc. <-- make an extra copy of the original and keep in safe place in case you **** up.
http://www.mediafire.com/?3j0httaa7o171ai <--- hexeditor.
open this, then open mmcblk0p31
Change version in xvi32 1.22.720.1 to 1.20.720.1 and save file. Or just reduce the number.. basically it makes the updater think you are running on a older software version and you need to update. also NOTE DOWN YOUR CID.
Save it back in the memorycard and switch back to charging mode
In the command prompt, write
"adb shell dd if=/mnt/sdcard/mmcblk0p31.img of=/dev/block/mmcblk0p31"
then "adb reboot-bootloader"
Next step is tricky.
http://forum.xda-developers.com/showthread.php?t=1208485
http://www.filefactory.com/file/c0a...00_10.13.9020.08_2M_release_203403_signed.exe <--- europe RRU
You'll either just need european RRU IF you have a european device OR European RRU and your region based RRU IF YOUR DEVICE ISNT EUROPEAN.
I was gonna post multiupload links but multiupload doesn't work anymore *hurray*
When you run the downloaded file, it will extract some stuff. Then it will show you the main menu where you get to agree licence ****. **** that.
when you're at the agree thingy, just minimise, and open Tast manager *press ALT+CTRL+DEL*, go to processes, choose the setup,in my case, it was ARUWizard. How you can know? It's description is gonna be "ROM update utility". right click it, and click open file location. There, you'll see a "rom.zip"
Copy it somewhere else and rename it to "PG86IMG" <-- this is the update.
within this update, you'll see a android-info.txt file which contains all the CIDs this RRU supports. See if your CID *which you noted down in the previous step* is there in this file.
Otherwise your device is meant for a different region and you'll have to try some other RRU, extract rom etc etc.
NOW HERE'S THE TRICKY PART.
If your device is european and your CID is there in the european RRU's android-info file, you can just use the european version. Otherwise you need to extract the hboot from european RRU, Rename it to the hboot from your native RRU and recompress.
Here's an example.
AAAA.zip <---- european
BBBB.zip <---- My native, say chinese?
AAAA.zip has hboot.xxxx and BBBB.zip has hboot.YYYY
what im gonna do is. extract hboot.xxxx, rename it to hboot.yyyy and put it in BBBB.zip.. *CANT MAKE THIS MORE NOOB FRIENDLY*
use winrar or winzip, remember, files need to be compressed in .zip format.
NOW put this PG86IMG.zip in your memory card. Remove your battery. press vol- and power to go to bootloader. There, it might take up to 5 minutes to scan the PG86IMG.zip and will ask you if you want to update. Select yes. Let it update.
*THIS WILL WIPE ALL YOUR DATA FROM PHONE, NOT MEMORY CARD, SO BACK UP PLEASE*
Now that you have hboot 1.49.0009, lets get S-OFF.
FOURTH BASIC STEP. S-OFF
its simple, turn on usb debugging, run revolutionary.
http://www.youtube.com/watch?v=GmQswv3vKrU&list=PL2D3BF8B6A00AABCF&index=1&feature=plpp_video <--- to help you better.
**REFLASHING THE STOCK ROM/RRU WILL GET YOU LOCKED AGAIN**
**YOU DONT NEED TO FLASH STOCK RRU AFTER THIS STEP BECAUSE YOU'RE ALREADY STOCK**
FIFTH BASIC STEP:
Flash your desired rom/recovery.
If you want your stock rom Rooted, the video in the 4th step till the end.
BAAM! YOU HAVE A ROOTED S-OFF STOCK ROM.
CREDITS:
http://forum.xda-developers.com/showthread.php?t=1471246
http://forum.xda-developers.com/showthread.php?t=1248231
http://forum.xda-developers.com/showthread.php?t=1208485
http://forum.xda-developers.com/showthread.php?t=1495657
http://forum.xda-developers.com/showthread.php?t=1509748
http://www.youtube.com/watch?v=GmQswv3vKrU&list=PL2D3BF8B6A00AABCF&index=1&feature=plpp_video
I'm Bored, Trolling, Post is real but posted alot, and no, I don't need a thanks. I'm jus killing time and posting useless threads coz others are too lazy to use search. ----> http://forum.xda-developers.com/showthread.php?t=1458032
You sure know how to make simplified tutorials...
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
noob friendly.
even my autistic imaginary bro can follow this tutorial. *hopefully*
N00b friendly, you say? Tell me, how can be such amount of information friendly for anyone?
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
Never said its easy, but its necessary. *goes for jihad*
Awesome tut, very clear.
fahadj2003 said:
Never said its easy, but its necessary. *goes for jihad*
Click to expand...
Click to collapse
Seriously? I got bored to death after minute of reading it! And without learning anything!
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
Terepin said:
Seriously? I got bored to death after minute of reading it! And without learning anything!
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
Click to expand...
Click to collapse
you're not a noob..
believe me, if talk.maemo.org has taught me one thing, its noobs, real ones, dont even know how to decompress a .zip file..
and they had a n900.. *google this*
baby, maemo kills android..
they dun have no rooting ****.. and hell of alot more open then android..
nokia jus ****ed up the hardware..
Then they have the right to **** up their phone for doing it poorly.
Terepin said:
Then they have the right to **** up their phone for doing it poorly.
Click to expand...
Click to collapse
i was a noob too when i moved from maemo to android..
i jus used a ported version of android *NITDroid* for n900.. wasnt full but it was pretty cool..
And you think I was pro when I arrived here? But I wasn't a n00b, but newbie with common sense and logic and I had experiences with forums. Basics, which n00bs always lacked.
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
man.. its not jus the forums..
i have experience with stuff.. ppl ask me **** u know..
and asking is good.. im ok with that.. but i realized people are too stupid.. even to use google most of the time.. they want things dumbed down to the tiniest bit as to where to insert the penis at night.. if i were a sex-ed teacher, my students would gives answers like nose and ears and ****..
there is no such thing as a short tutorial.
Five pearls of Scottish wisdom to remember...
1. Money cannot buy happiness but somehow, it’s more comfortable to cry in a Mercedes Benz than it is on a bicycle.
2. Forgive your enemy but remember the bastards name.
3. Help a man when he is in trouble and he will remember you when he is in trouble again.
4. Many people are alive only because it’s illegal to shoot them.
5. Alcohol does not solve any problem, but then neither does milk.
Unfortunately true.
Odoslané z môjho HTC EVO 3D X515m cez Tapatalk
Maybe I didn't understand something from OP.
My phone had S-ON with *** LOCKED *** and with HBOOT-1.49.0018
with latest unbranded firmware
What I did is this:
1.downloaded RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
2.downloaded latest device drivers
3.downloaded revolutionary files
uninstaled HTC sync
4. started phone normaly,
5. start RUU upgrade(downloaded in 1. - in my case it's downgrade)
6. after that my HBOOT is 1.49.0007 still ***LOCKED*** and S-ON
7. from revolutionary web site generated beta code for my phone
8. Restart phone, turn USB debuging ON
9. start revolutionary.exe and paste beta code from their generator
10. wait for it to finish
11. Now I got 1.49.1107 HBOOT with S-OFF
12. Tried to flash the same RUU again and I after that I get again HBOOT 1.49.0007 from RUU but ***LOCKED*** and S-OFF!!!
miksi said:
Maybe I didn't understand something from OP.
My phone had S-ON with *** LOCKED *** and with HBOOT-1.49.0018
with latest unbranded firmware
What I did is this:
1.downloaded RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
2.downloaded latest device drivers
3.downloaded revolutionary files
uninstaled HTC sync
4. started phone normaly,
5. start RUU upgrade(downloaded in 1. - in my case it's downgrade)
6. after that my HBOOT is 1.49.0007 still ***LOCKED*** and S-ON
7. from revolutionary web site generated beta code for my phone
8. Restart phone, turn USB debuging ON
9. start revolutionary.exe and paste beta code from their generator
10. wait for it to finish
11. Now I got 1.49.1107 HBOOT with S-OFF
12. Tried to flash the same RUU again and I after that I get again HBOOT 1.49.0007 from RUU but ***LOCKED*** and S-OFF!!!
Click to expand...
Click to collapse
lol
dude..
thats it..
its jus till step 11.. u dont flash the rru again..
then jus get superuser and flash it through recovery..
**edit
i actually had to add a 5th step just for people like you sir.
and then they say that my tutorial is too long ._.
12. Tried to flash the same RUU again and I after that I get again HBOOT 1.49.0007 from RUU but ***LOCKED*** and S-OFF!!!
Click to expand...
Click to collapse
Hm, would s-off remaining if I flash RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.9020.00_10.15.9020.06_M_release_219793_signed.exe ??? With this would have s-off, and 1.49.0018 hboot ???
Sorry for bad English
micens said:
Hm, would s-off remaining if I flash RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.9020.00_10.15.9020.06_M_release_219793_signed.exe ??? With this would have s-off, and 1.49.0018 hboot ???
Sorry for bad English
Click to expand...
Click to collapse
moment you flash an official RRU, the hboot gets locked and reflashed
follow the last part of step 4 to maintain 1.49.0007/8 hboot
REFLASHING THE OFFICIAL ROM WILL RESTORE THE HBOOT.
and its already flashed, why would u flash it again to start with? :|
OK, TO MAKE THIS MORE NOOB FRIENDLY, YOUR ROM IS ALREADY STOCK. YOU DONT NEED TO FLASH STOCK ROM AGAIN.
With flashing RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.90 20.00_10.13.9020.08_2M_release_203403_signed.exe I have 1.49.0007 HBOOT, then I do s-off with revolutionary, and then I have revolutionary 1.49.1107 HBOOT with S-OFF, ok. And if I wont to have newer hboot such as 1.49.0018, I can flash RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.90 20.00_10.15.9020.06_M_release_219793_signed.exe, without loosing s-off??? This is just question if I decide to have newer hboot...
micens said:
With flashing RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.90 20.00_10.13.9020.08_2M_release_203403_signed.exe I have 1.49.0007 HBOOT, then I do s-off with revolutionary, and then I have revolutionary 1.49.1107 HBOOT with S-OFF, ok. And if I wont to have newer hboot such as 1.49.0018, I can flash RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.90 20.00_10.15.9020.06_M_release_219793_signed.exe, without loosing s-off??? This is just question if I decide to have newer hboot...
Click to expand...
Click to collapse
only 1.49.008 or lower can have s-off.. not higher..
why would i ask ppl to downgrade their hboot if we can still s-off it?
please explain that to me
micens said:
With flashing RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.90 20.00_10.13.9020.08_2M_release_203403_signed.exe I have 1.49.0007 HBOOT, then I do s-off with revolutionary, and then I have revolutionary 1.49.1107 HBOOT with S-OFF, ok. And if I wont to have newer hboot such as 1.49.0018, I can flash RUU_Shooter_U_HTC_Europe_1.20.401.8_Radio_10.59.90 20.00_10.15.9020.06_M_release_219793_signed.exe, without loosing s-off??? This is just question if I decide to have newer hboot...
Click to expand...
Click to collapse
this is just dump. You don't need higher hboot, higher hboot has nothing to do with software. Okay maybe when ICS comes we will need a new hboot as the Sensation users does, but then we will get a fully s-offed hboot.
p.S. how dare you to call this thread a tutorial?^^
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hey man the phone isn't bricked if you have a pulsating dim red power light, alot of people came across the problem of actually killing batteries trying to brick their phones. If its pulsating just leave it charging on the wall socked for a while bit if it is a very very dim constant red light it is bricked and you would have to use a compatible computer that takes the drivers for your phone. Read through the thread you linked and search for your issue, it is a common one
****'ll Buff Out
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Thanks, it's just dead as can be. I did eventually get it recognized by linux on the live cd and it successfully went through it's routine to get to hboot 1.40. The next step should be to install RUU 1.13. It's a KDDI phone. I used this
RUU_Shooter_K_S_KDDI_JP_1.11.970.2_Radio_1.02.00.0906_NV_1.39_01C_release_246058_signed.exe
for initially bricking it. I extracted the ROM first. That part went smoothly . I think I did everything right and i'm where i should be now but it just doesn't do anything... nothing. I did try to mess with emmc_recover but no luck yet. When I do the RUU I just keep getting "error 170 usb connection error." I've tried uninstalling/re-installing/different versions of HTC drivers. I keep messing with it for a bit and hopefully something gives! Oh and battery, no battery, I can't get anything. If I could get it recognized on the PC I think I'd have a shot! Thanks again,
gjash
runcool said:
The evo3d was designed for americans. We don't support the Japan people do to over population of your race. Also if you used your head you'd notice that the computer you're using likely is in the crappy Japan language no one uses. Therefore, you need to try another computer and it'll work. We can't support every computer out there. The Drivers won't work for every type of computer on the planet.
To make this racist reply short, it's your computer. you gotta try another computer. Try using an older system. I'll have to open it up to figure out which drivers they put in there, but I know for a fact it won't work on my computer. I'd have to use it on another as well.
They should put that in the instructions. hmmm But after trying another computer, get back with us.
ps again, you said you "tried it on other computers" model numbers of those and what language are they in? It does make a difference. But I'm glad you speak english or I'd just laugh. I'm really mean today. so sorry. hahaha. Let me know if I'm right.
ps again. remember drivers drivers and drivers. drivers only work with certain types of hardware.
edit, you said linux machine, BUT DID YOU EVEN INSTALL the drivers on it? lmao!?
Click to expand...
Click to collapse
Your a complete douche bag! Its people like you that drag society down! If I met you in person I would ***** SLAP you so hard it would not be funny!
The last I checked we all bleed red.
@op I am glad you got it worked out unfortunately I can not help because I have no idea who your carrier is. What I do know is if you update to ruu 2.17.651.5 you will be back on Hboot 1.5 but with S-off.
Sorry that is all the info I can give you.
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
gjash said:
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
Click to expand...
Click to collapse
After downgrading/flashing Hboot 1.40, the goal of the RUU is to install an earlier fully working Stock Rom (S-On still) that came with the same Hboot 1.40 that is pushed to the phone with the downgrade tool/process. Hopefully you can find an early KDDI ruu with Hboot 1.40 for this part. This allows you to run " http://Revolutionary.io 's rooting/S-Off tool to gain "S-Off" and install a custom Recovery like Revolutionary CWM Recovery 4.0.1.4 (or 4Ext Recovery).
From there (make a nandroid backup) you can update the firmware/radio if needed (make sure hboot 1.50 isn't included) and flash a current rooted rom (stock or custom) that matches your radio/baseband as appropriate. Maybe there is a current rooted stock KDDI RUU (PG86IMG.zip) without the hboot 1.50 or someone (like Mr.Esp, freeza, or xhausx) can help you pull the stock rom apart for this step.
You can also flash the SuperUser zip (app & binary) from custom recovery to gain root on a currently installed stock rom once you have S-Off.
That's my LIMITED understanding, but I'm not 100% sure about your situation overseas since I thought all foreign carriers outside the U.S. used GSM devices.
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Can't really do anything at the moment. I can't flash RUU 1.13 and I can't get it to be recognized on USB so I could use ADB and try pushing something to it. I have no idea! This is a learning thing at this point. I did root my Asus transformer before though! Thanks for any help!
gjash
gjash said:
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Click to expand...
Click to collapse
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
closeone said:
But take the RUU .EXE that you upgraded your phone with already and grab the ROM out of there.
To get to your temp directory: press the Windows key and R on your keyboard at the same time. Type in this exactly: %temp%
Rename the rom.zip to PG86IMG.zip and put it on your SD card.
Click to expand...
Click to collapse
I haven't made any progress. I'm assuming I need to use emmc_recover to overwrite the boot partition and maybe the misc partition. So can someone help me figure out identifying the partition, how I can get linux to recognize the device so I have a chance to recover? Also, at this point I settle for anything working, any Hboot, whatever... It would be nice if I could post in the original thread, hmmmm. moderator, can you help there?
thanks,
gjash
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
mpgrimm2 said:
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
Click to expand...
Click to collapse
You are right... both KDDI 1.09 and 1.11 have Hboot 1.50. I guess the trying Sprint 1.13 wouldn't be an option? That's the question and I can't really find out as the KDDI ones and the Sprint ones don't work because I always get USB 170 connection errors. So kinda stuck, but greatly appreciate the help!
gjash
mpgrimm2 said:
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
Click to expand...
Click to collapse
I will start looking there... I was thinking that the KDDI Evo 3d is CDMA and it would have the same partition layout. I'd like to determine that and go from there. Can someone explain the sprint evo 3d partition layout? thanks!
gjash
I'm willing to mess with this phone so if any developers have something I can do, please let me know. Otherwise, I just try to get back to stock.
I extracted original hboot from latest KDDI RUU and renamed it hboot.img and then executed 'downgrade'
I got this error:
Waiting for device...
Found the Correct Device!
Writing image file!
dd: opening `/dev/sdf34': Permission denied
FAILED!!
Any ideas? Thanks!
gjash
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
mpgrimm2 said:
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
Click to expand...
Click to collapse
Getting closer I think... I just needed to do a sudo ./downgrade and it flashed fine. Now I have a red light on which is more than I had before. I will go to windows now and try to flash the KDDI RUU. thanks for the help.
gjash
Update:
I'm back up where I started. I used Unknownforce's hboot downgrade but renamed the original hboot from the KDDI RUU to hboot.img, according to Unknownforce's direction (thanks!). After I did that, the phone just booted up normally. I thought I would have to flash the RUU but wasn't necessary. I think with some changes this whole exploit could work with the japanese cdma version of the Evo 3D. If anyone can outline what I'd need to do, it might be fun. especially that I already ordered another phone, but I won't actually need it.
gjash
Does your device happen to be the KDDI ISW12HT?
(I assume it is from what you've said)
Do you know the exact model you have?
The current CDMA models that I'm aware of are the:
X515c: CDMA800, CDMA1900, ESMR800, WiMAX 2.5-2.7GHz (the sprint one)
X515d: CDMA800, CDMA1900 (I forget)
X515e: CDMA900, CDMA2100 (the HTC rider)
The ISW12HT is listed as having CDMA800, CDMA2100, which arnt any of those 3.
Do you happen to know what submodel you have? I have no idea how to check as I've never touched one.
I'm wondering if it's the X515b or a yet unknown one (by unknown I mean with regards to the model number)
I've already listed all the common and less-common models on the wiki: HTC Evo 3D - XDA wiki.
But I have no idea what the ISW12HT's model is, and a fair amount of googling turns up little.
If you could poke around your device/box/manual and find it I'd appreciate it
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
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
hello friends...
i try this all method http://forum.xda-developers.com/showthread.php?t=1743466
and als try http://unlimited.io/ wire trick
not work ... for me
i want to s-off . bcz i am going bore with official ics ..
plz help me
Are you on the stock rom, or did you flash a modified one? If you are still on the stock rom, unlock your bootloader via www.htcdev.com and then try the wire trick again. I had to do it a lot of times, but it eventually worked. Just keep trying and eventually you will succeed
thanks
posedatull said:
Are you on the stock rom, or did you flash a modified one? If you are still on the stock rom, unlock your bootloader via www.htcdev.com and then try the wire trick again. I had to do it a lot of times, but it eventually worked. Just keep trying and eventually you will succeed
Click to expand...
Click to collapse
thanks bro from last 3 days i try more then 20 time but not work ...
i always stuck on juopuntbear screen after that adb not work ...\i don't know what should i do
i try restart my pc and mobile both so many time but not work for me
it sucks .....
thsnks for reply
faizan950 said:
thanks bro from last 3 days i try more then 20 time but not work ...
i always stuck on juopuntbear screen after that adb not work ...\i don't know what should i do
i try restart my pc and mobile both so many time but not work for me
it sucks .....
thsnks for reply
Click to expand...
Click to collapse
Did you get s off or not? Tell me exactly what you have done so far. I can give you step by step instructions and guide you through the process.
MrJyrks said:
Did you get s off or not? Tell me exactly what you have done so far. I can give you step by step instructions and guide you through the process.
Click to expand...
Click to collapse
thanks bro ....
i try with control bear box
my mobile going junpuntbear after that my pc not dedect my htc .... adb fail always
my phone is unlocked recovery installed
i want s-off
i also attached one picture ... stuck there every time....
wait for you tips
thanks
First of all, you must be on stock rom. Every sense 3.6 based rom should work. Did you run ControlBear as administrator?
If you did, run murder.bat from the attached .rar as administrator, wait till it's done. Try again. Still not working? Extract all the files from the rar to a folder. Run controlbear from there (run as admin). Give me feedback if it worked!
Edit: I have to upload the file somewhere else, it's over 8 mb so cant upload here.
Here's the link: https://docs.google.com/file/d/0B-fWg2dqIcnRT0xSZUdnVFRHeVk/edit?usp=sharing
Also It's a good idea to disable antivirus. I always do it as a precaution so I don't screw up anything.
If you need to know, the bat file searces for processes that may be interfering with controlbear and kills them.
Also none of this is my work, so all the thanks go to unlimited team.
MrJyrks said:
First of all, you must be on stock rom. Every sense 3.6 based rom should work. Did you run ControlBear as administrator?
If you did, run murder.bat from the attached .rar as administrator, wait till it's done. Try again. Still not working? Extract all the files from the rar to a folder. Run controlbear from there (run as admin). Give me feedback if it worked!
Edit: I have to upload the file somewhere else, it's over 8 mb so cant upload here.
Here's the link: https://docs.google.com/file/d/0B-fWg2dqIcnRT0xSZUdnVFRHeVk/edit?usp=sharing
Also It's a good idea to disable antivirus. I always do it as a precaution so I don't screw up anything.
If you need to know, the bat file searces for processes that may be interfering with controlbear and kills them.
Also none of this is my work, so all the thanks go to unlimited team.
Click to expand...
Click to collapse
thank you very much ....
i just use samsumg galaxy s3 data cable and every think work fine and finlly i did s-off thanks for you reply ...
Hello, I tried this junpuntbear s-off tutorial, but I'm stuck on junpuntbear boot. My pc can't find my phone from adb and it just stays there.
I unlocked with htcdev my bootloader, 4ext recovery installed, rooted. "Still not found device" etc... Any suggestion? I installed all drivers, fastboot/adb works fine. I installed mwakious3Drom 16.0.150_BASE_FINAL_RELEASE rom on my phone, is this the problem?
mhnx said:
Hello, I tried this junpuntbear s-off tutorial, but I'm stuck on junpuntbear boot. My pc can't find my phone from adb and it just stays there.
I unlocked with htcdev my bootloader, 4ext recovery installed, rooted. "Still not found device" etc... Any suggestion? I installed all drivers, fastboot/adb works fine. I installed mwakious3Drom 16.0.150_BASE_FINAL_RELEASE rom on my phone, is this the problem?
Click to expand...
Click to collapse
You need to go stock ROM first and then try s-off
Sent from my Evo 3D GSM using xda premium
simran420 said:
You need to go stock ROM first and then try s-off
Sent from my Evo 3D GSM using xda premium
Click to expand...
Click to collapse
Thanks for your reply, how can I go to stock ICS? Which RUU I must pick to flash? I'm from Greece. (GSM Model)
If I keep a Nandroid, can I restore it after s-off with wiping the stock rom? Or I must start from the begining?
Well, in theory any sense 3.6 based roms should work. Not sure about mwakiousrom though. To go completely stock you must flash a ruu as far as im concerned. Just download the appropriate ics RUU. Link
Since you are s on, lock bootloader with"fastboot oem lock". Run RUU. It will take a long time to finish. After that you must unlock bootloader from htcdev. Flash recovery. And finally, do the wire trick. After wire trick flash hboot 1.49. Link. You need to format all partitions except sd card after hboot change.
You can get the correct Europe ICS RUU from here -> http://www.androidfiles.org/ruu/sec...00U_11.25.3504.06_M_release_262714_signed.exe
MrJyrks said:
Well, in theory any sense 3.6 based roms should work. Not sure about mwakiousrom though. To go completely stock you must flash a ruu as far as im concerned. Just download the appropriate ics RUU. Link
Since you are s on, lock bootloader with"fastboot oem lock". Run RUU. It will take a long time to finish. After that you must unlock bootloader from htcdev. Flash recovery. And finally, do the wire trick. After wire trick flash hboot 1.49. Link. You need to format all partitions except sd card after hboot change.
Click to expand...
Click to collapse
I will do it with revolutionary because I know how revolutionary works (old Desire Z user ) but I need to downgrade hboot. In theory can I get a nandroid and restore after all this? Or the rom should be unstable?
You can restore stuff from a nandroid using this app
It restores apps/data, wifi settings, sms etc. It will require you to have a rooted rom. So in theory after you have done the wire trick you can flash a rooted rom and restore important stuff with this app
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
https://play.google.com/store/apps/details?id=com.rerware.android.MyBackup&hl=en
Another backup option
And just a reminder, wire trick sometimes corrupts sdcards. so save your backups before doing wire trick
Oh, your on hboot 1.49? Revolutionary tools needs 1.49 afaik. If so, get the gb RUU.
MrJyrks said:
Oh, your on hboot 1.49? Revolutionary tools needs 1.49 afaik. If so, get the gb RUU.
Click to expand...
Click to collapse
I'm downloading the GB RUU, I think...
Code:
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
is that right?
and one last thing, I think my mobile is vodafone branded, CID VODAP102.
then you should flash a vodafone ruu. And what hboot do you have? you cant run a GB ruu on a phone with the ics bootloader(1.53)
EM|NEM said:
then you should flash a vodafone ruu. And what hboot do you have? you cant run a GB ruu on a phone with the ics bootloader(1.53)
Click to expand...
Click to collapse
I have 1.53.0007 hboot. how I can downgrade the hboot? any suggestion?
mhnx said:
I have 1.53.0007 hboot. how I can downgrade the hboot? any suggestion?
Click to expand...
Click to collapse
Gosh. Maybe there is a way, but i am not aware of it. It is certainly a lot more easier to do the wire trick.
MrJyrks said:
Gosh. Maybe there is a way, but i am not aware of it. It is certainly a lot more easier to do the wire trick.
Click to expand...
Click to collapse
Then I'm going to make the wire trick, just hoping the ics ruu will work to get stock back. How much fool am I?
EDIT: The
Code:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
RUU doesn't work, It reads the software info, I press start and nothing happens to my phone.