yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] mpgrimm2:
Leaked 2.89 Sprint Ruu from China?(Ramjet73 has a mirror on page 1 or 2, & has flashed it himself). No official leak in Football's thread yet.

http://xdaforums.com/showthread.php?t=1827712﻿

RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1 .09.00.0706__NV_NV_SPCS_1.43_release

Ramjet73's post with mirror (I'm getting Security errors with this now?)

Build: 2.89.651.2. CL 409645 Release Keys

Radio: 1.09.00.0706

Pri: 1.43_003 (what's Pri)

PRL: 21090

Kernel: 3.0.16-g294f767

Hboot: 1.58

EDIT:

Football has updated his thread with the 2.89 RUU, Here.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] closeone:
So, we have a leak it appears! It should work fine for this. I cannot say for sure though (I have not tested it). If you want to do the full downgrade, substitute the 2.17 RUU that's mentioned in the downgrade thread for this one, then follow the steps exactly as written out (that CD is focused a little more on the downgrade, and as such contains everything else you should need to get going).

You'll need to extract the ZIP file out of the executable RUU. Mpgrimm2 did a guide on how to do this here.

PRI: From what I understand, it generally changes with the Radio/Firmware. It apparently stands for Primary Rate Interface. I remember that there were some issues with PRI versions earlier (with the VM Firmware). 1.43_003 sounds like the version I remember.

Don't do this if you are already S-OFF, and don't use it if you haven't upgraded to the new version already (Use the 2.17 RUU instead). Make sure to follow the instructions in that guide to a "T." I am not responsible for damaged phones, or other items. If you've been following this for a while, you know the drill. ;)

~co~
[HTC EVO 3D] ZeRo2o9:
didt mean for it to sound rude closeone..was just mad cuz my phone is a tablet now. I flashed the firmware zip from virus. flashed viper3d rom and once it rebooted no signal. tried RUUs and the unknownforce radio fix but the radio fix says cant find the last puzzle piece. even a repair guy couldnt fix it. think it could be a partition? i have the backup that the radio fix makes if that helps
[HTC EVO 3D] thatisandwas:
Hey guys...first of all, awesome work.

Ok so, i'm no noob to flashing android stuff and i have used fast boot for unlocking and what not. I guess i just have a couple questions that might sound really dumb...so forgive me.

I have the VM firmware. I see two main components in the OP....I don't know if its for two seperate issues people may have but am i only supposed to do the radio fix portion of the instructions to fix this? Or am i supposed to also do all the steps after that in the section "Downgrade/Unbrick"? Again, i know that probably sounds really dumb, but i just read 20 pages of the thread...and can't figure out the answer.

Second, in the steps where it tells you to first flash all the files...By flash, do we mean through recovery? Fastboot? Another way?

I feel embarrassed asking because i see so many people have used this tool to fix it..but i just feel its better safe then sorry. Thanks in advance.
[HTC EVO 3D] KaSaBiS:
I actually read every page of the old thread that is now closed before seeing this one. I am at page 30, and still need help.

I have bricked, ran the linux tool, and now have hboot 1.4

I have always flashed with the zip. I am trying to do the next step with RUU 1.13 exe and get error 170 phone not recognized. my phone on bootloader says fastboot usb.

I was reading a lot on other threads and have sdk installed. but they tell me to switch program file paths around and I think I am missing something. the guide says now I need to RUU 1.13 exe in fastboot, then clean up the radios, then root. Just stuck on this hurtle..

any help is appreciated
[HTC EVO 3D] closeone:
All is good, and I'm sorry ZeRo2o9. I don't know about the firmware you flashed. This one should be the correct one to run (first link).

I'm not exactly sure about "the last puzzle piece." That's Unknownforce's area of expertise. :( I'm sorry.

Don't be embarrassed. You're fine. ;) I prefer the "better safe than sorry" approach to things. You'll just be doing the radio fix part of the guide. You'll be flashing those through Fastboot.

Try installing these drivers. That should fix your problem you're having.

~co~
[HTC EVO 3D] thatisandwas:
Thank you much close one :) Awesome job on these tools!

EDIT :

Could someone possibly post the fastboot commands needed? I downloaded all the files just not sure of the exact commands for fastboot
[HTC EVO 3D] KaSaBiS:
command lines? as far as I know you boot to bootloader, select fastboot, plug in, changes to fastboot usb, then dbl click your RUU .exe and it runs itself. if Im wrong ill find out tonight when I give it my first go using fastboot
[HTC EVO 3D] closeone:
Thanks thisisandwas, but I can't take credit for this. Unknownforce did the tool. Full props go to him. I just did the CD in Post #3.

In regards to Fastboot commands, you shouldn't need to use any. For the executables, you'll put your phone into FASTBOOT USB mode and run the file from Windows. For the ZIP files, you'll copy one at a time to the SD Card (ensuring that each one is named PG86IMG). You'll flash it by booting into the bootloader and putting the phone into FASTBOOT mode. You will need to let it boot all the way after the flash is finished. You'll need to delete the file off the SD Card (so it doesn't attempt to flash it again), before moving onto the next.

~co~
[HTC EVO 3D] thatisandwas:
Ohhhhhhhh (lightbulb moment) Thanks a ton! and you're very welcome. Big props to Unknownforce also in that case! Ill make sure to thank button him.
[HTC EVO 3D] Unknownforce:
Sorry guys, haven't been on the forums much as of late. Lots of issues in life right now. Trying to get everything sorted out. I haven't disappeared, and I'm not abandoning anyone. I'm just really busy. I've helped just about everyone I could, and most questions look answered at this point. Thanks to those that have helped out as best they could.

Again, best way to get me right now is to PM, I'll get around to it when I can, like I said, a lot of things have just been hectic lately.

With regards to hboot 1.58, I cannot say for CERTAIN, but if the update works the same as the others, it should be possible to downgrade from that as well, assuming the bootloader is still flashed during the PG86IMG.zip flashing process. It is also possible that they could have patched it in some way. Unfortunately I cannot test this as I don't have a device to test it on... As you may or may not know, I have moved to the SGS3.
[HTC EVO 3D] KaSaBiS:
is there any benefit or difference between flashing methods? I.E. the guide states to flash from fastboot, which I was having issues with (and will try again tonight thanks to you and unknowns tips) but I could have sd zip booted but wanted to do it exactly verbatem
[HTC EVO 3D] thatisandwas:
Just finished, using the usb cd method. It worked PERFECTLY. Thank you guys SO MUCH. Couldn't have been easier. A little tedious flashing the different PC86IMG's but thats to be expected. But very, very well done!

---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------

Put the PC86IMG.zips on your card and boot to fastboot with the standard vol up and power method and flash that way after doing the RUU
[HTC EVO 3D] linty:
BRICK!

Uh oh. I guess a write error is bad? I think it was when writing partition 19. Now total brick. None of the recovery commands work, won't power on, no faint red light, won't even browse porn.

Hi ho, hi ho, it's off to Sprint store I go :(
[HTC EVO 3D] KaSaBiS:
Bad news. thats the step ive been working on for 3 hours. maybe I dont want to complete it.

to CO or unknown. I have successfully installed sdk and so far have ran "adb devices" through cmd to verify my phone is connected and all is working, yet when I run your code

"adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/current19.img

it tells me "cannot open for read: permission denied" and for

adb pull /sdcard/current19.img

it says "/sdcard/current19.img" does not exist

calling it quits for tonight. hopefully make progress tomorrow

edit: this if from coming from 1.5hboot s-on to achieving 1.4 something s-off with twrp and revo
[HTC EVO 3D] linty:
How I "bad bricked" the phone

Okay, so here's all the information I can think of leading up to a perm-brick.

Steps:

A couple of months ago when UnknownForce needed additional partition 19s I decided I'd help the community as I never flashed the VM firmware.

1) I backed up my original partition 19 with adb shell dd if=/dev/block/mmcblk0p19 of=/sdcard/original19.img

2) I flashed the VM virus.

3) I made a copy of the new partition 19 and gave both to UnknownForce.

4) I stupidly tried the following: adb shell dd if=/sdcard/original19.img of=/dev/block/mmcblk0p19 **THIS MAY HAVE CAUSED THE BRICK**

5) Nothing happened.

So yesterday the process continued:

1) I downloaded all the requirements from the OP.

2) I followed all the instructions up until using the tool.

3) I tried running the process from VirtualBox, discovered that I had to keep clicking on the button to share my phone through USB and it wasn't working. I then read that VirtualBox won't work (DOH!)

4) I got my flash drive from home and followed the instuctions in post #3 by downloading 2.3 RC1 and core2usb.

5) At some point during the process it gave me an image write error, I hit retry and it appeared to continue.

6) It got to the end and said: You may now put your battery back in and boot up!

7) I put my battery back in, turned the phone on, and .... nothing.
[HTC EVO 3D] KaSaBiS:
Oh god. I flashed the VM firmware on my sprint phone. I didnt know what VM stood for until I saw virgin mobile everywhere on my phone. anyone know the best way to recover from this and correct (revert) my radios and firmware.

DOH!
[HTC EVO 3D] Unknownforce:
The tool in this thread is exactly what you need to fix it. Read the first three posts.
[HTC EVO 3D] vivix:
Hello. I have HTC EVO 3D GSM version aith HBOOT 1.53.007. I used an SUPER-WIPE script for EVO 3D and i hve no Firmware installed which previousli i had this : 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.exe <- which is a stock ROM. I have as well 1.53.007 HBOOT in RUU. My HTC EVO is now bricked and a weak red dim light glowing all the time. It have no firmware itself. I tried UNBRICKING PROJECT solution for GSM version in UBUNTU 12.04 and all operation was successful but my EVO is still dead. I have no RIFF BOX to get a kickstart for it. I want to need if this SOLUTION here will work for me and if someone can prepare for me a files for ULTIMATE which not BRICK my phone even more. Maybie someone of you know if i can PUSH in LINUX a RUU files straight to phone. Phone status : Its not turning one. ADB and FASTBOOT saying - waiting for device - also its not charging. Tomorrow i will get EXTERNAL BATTERY charger to have a try. Any hope for me ?​
[HTC EVO 3D] mpgrimm2:
I'm not an expert with this by any means, but initially I can tell you that this is specifically for CDMA phones not GSM phones because the partitions are different. Whether or not anything can be done will have to be answered byUnknownforce or someone that knows the file systems/code for GSM.

Sent from my "Up all night, Sleep all day" EVO3D!
[HTC EVO 3D] Nurdyboy:
RUU not working

im trying to run the ruu file that is in the main post and I keep getting

" Windows cannot Find 'C:\Users\....\RUU_Shooter....Make sure you typed the name correctly, and then try again"

Any one ever run into this or have a good copy they can link me to

---------- Post added at 09:44 PM ---------- Previous post was at 09:37 PM ----------

now im getting

"The version of this file is not compatible with the version of Windowns your running. Check your computers system information to see wether you need an x86(32-bit) or x64(64-bit) version of the program, and then contact the software publisher."

Can anyone help?? I have a windows 7 64-bit computer and in big need of getting my e3d back to life as my new phone is now broken
[HTC EVO 3D] mpgrimm2:
Is an Exe or zip? Which file?
[HTC EVO 3D] closeone:
Hi Nurdyboy,

Please know that I'm not trying to pester you. May I ask what you're doing, how you're doing it, what you've already done, what you're currently trying to do? We need as much information as you can provide us. Too much information is (almost always) better than not enough information. What happened to your device, and what's it doing now? Again, I'm not trying to belittle you (people that know me here, know that I wouldn't do that), but I need just a little more information.

Thanks,

~co~

Edit: Darn. You are fast Mpgrimm2. ;)
[HTC EVO 3D] Nurdyboy:
I dont think that at all. I am using an exe file.

Back in May I took the leaked zip file that cause my PRl to be switched over to VM. After about 2 weeks HTC got mean early addition of the EvoLTE and never looked back untill this morning when my wifes S3 shattered and took EvoLTE and downgraded me to the 3d lol

AS the phone stands its got

s-off

Android 4.0.3

Stock 1.13 (rooted)

Sence 3.6

PRI 1.53_144

PRL 21087

Im getting ready to start step 2 but like i stated before i cant get the Exe RUU file to open up so i can run it and get going.
[HTC EVO 3D] closeone:
Thanks. That helps a lot. ;) From what I can tell, it's possible that you got a corrupted download.

If it's the 1.13 Stock (the one I'm pointing to in the quote, you can get that here. Even if that's the place you already got it from, it's possible that you had a bad download.

Sorry,

~co~
[HTC EVO 3D] Nurdyboy:
Thats what I think happened but well all is good now to get this bad boys radios updated to ICS and have it connected tomorrow.

Many Thnaks CO
[HTC EVO 3D] mrwicked:
I had the same issue. Just got my replacement phone yesterday and 5 seconds was to long for me as well. He's right this new phone is much faster then what it was on my older phone for this step.
[HTC EVO 3D] yergo88:
awesome awesome tool! just wish that it worked in my case :(

quick questions:

1. will the live CD in post #3 aka URTB_2.3RC1.iso work in a virtual image? would it detect USB etc? anyone ever try it? thanks!

2. says on dev-host that URTB_2.3RC1.iso's server is being worked on, any alternative links?

VIVA LA ANDROID!
[HTC EVO 3D] closeone:
Hi yergo88. If you are doing the downgrade, I'd probably recommend using the HBOOT Downgrade Toolkit instead, as it includes more tools that are for that use. Otherwise, if you are trying to do the Virgin Mobile radio fix (flashed that firmware), this would be the tool to use.

If you're talking about using it with a virtual machine, generally speaking the answer is no. VirtualBox has been a no-go, and VMWare, may work, but I wouldn't recommend using it in there.

About the server, here's a mirror to the file. :)

~co~
[HTC EVO 3D] krazyfukr:
Maybe it's just me...

I have hboot 1.58 with 2.89... I have tried many times and cannot get the device to brick.

Has anyone had any luck getting this to work with 1.58/2.89?

Thanks.

-----------------------------------

UPDATE: Ok, I did finally get the device to brick. I ran the Downgrade, everything looked fine. Success on steps 1 and 3.

hboot 1.40 was displayed on the screen

when I tried to run 1.13 it gives me an [error 140] bootloader version error and will not install v1.13....

any info on this and if it's possible to get around it? I loaded it back up with stock 2.89 for the time being....

Further updated: I bricked and recovered a few more times and never did get the device to allow the installation of v1.13, so I got tired of messing with it and just used the htcdev.com method with the wire trick. That worked flawlessly on the first try. I am currently running MeanROM with no issues and now have hboot 1.58.5858 installed.
[HTC EVO 3D] Smac7:
I wan't to fix a device that is not longer activated. I am looking to sell it but i don't think it will be worth much considering it says Virgin Mobile everywhere. Will this work on an inactivated device?
[HTC EVO 3D] Unknownforce:
Yes, this will work on a device that is not activated, it will clear out all the information on it though, so it will keep trying to activate every time you boot the phone until it does finally activate. But that's OK, you can just cancel it.
[HTC EVO 3D] closeone:
Forget my comment.

EDIT: How in the world does that always happen to me? Thanks Unknownforce.

My original comment (it wasn't actually too far off):

~co~
[HTC EVO 3D] TheSilverStig:
Wow!

Well, I sold my evo 3d and got an sgs2 back when the VM Firmware issue first came out, and I can't believe you guys fixed this! I should have known! Amazing work Unknown you not only s-offed my evo, you could have purified it back to Sprint too!
[HTC EVO 3D] digitalhigh:
You know - I found a flashable on Team Nocturnal forums that you just drop into bootloader, run, and bladow - banner and radios fixed. I didn't even have to change my ROM. This was done on 1.4 revolutionary. Afterwards, I re-flashed the latest OTA firmware, and all was good.

http://forums.team-nocturnal.com/showthread.php/833-Virgin-Mobile-Banner-and-radio-fix!-Test
[HTC EVO 3D] closeone:
Please understand that I am not trying to offend you, start any sort of thing, or, to put it bluntly, just have you (or anyone else for that matter) p***ed off at me. So please understand that I want to avoid confrontation here.

There is a long story about that fix. It was something that was talked about, and talked about before this tool ever came out. Now, I don't know what has become of this, but I can say with reasonable certainty that this did not fix the problem. The files in there are HEX edited to display the correct banner. If your PRI ends with "VIN," I'm certain that this has not fixed the problem. It's a figurative bandaid. So much got messed up by that firmware being flashed, that it goes beyond what that fix does (Writing to partitions that never should have been written to in the first place).

It's detailed heavily back in jlechner's thread, while this whole thing was occurring.

Here's a decent starting place. Trust me. This thread wouldn't be here if that had worked.

http://xdaforums.com/showthread.php?p=26759030#post26759030

Again, I'm not trying to belittle you or your comment, but I'm trying to make you aware that there's more to it than this.

Thank you,

~co~
[HTC EVO 3D] erick1499:
Ok so I back to hboot 1.40 but now i can not run the 1.13 ruu I get a customer id error, anyone have any idea as to what i can do? btw I started off with hboot 1.58 and software 2.89 my guess is that the phone sill thinks it's on 2.89(even though it's not) and refuses to take anything else so maybe deleting some partition where that information is stored would allow me to flash.
[HTC EVO 3D] mpgrimm2:
Erick,

Here's some info from the Hboot 1.40 Downgrade Tool thread where someone stumbled upon getting this to work with 2.89. It may work for you too. If not you can always flash the 2.89 RUU and head over to the Jbear Wire trick. But it would be nice to see the confirmation here too. Basically, check your MainVer first, and Rebrick again.
[HTC EVO 3D] erick1499:
mpgrimm,

Thanks for the help, so from what I understand is once I have bricked the phone and am back to hboot 1.40 and have the "security warning" banner, I need to brick and unbrick again? again thank you very much for the help!

Update: It worked! basically what i did was make a zip of the 2.89 ruu and followed the procedure in the OP, after ubnbricking I bricked and unbricked once more using that same 2.89 ruu zip after which my version number(which u can see using fastboot getvar mainver)turned to 0.00.641(something like that) which allowed me to run the 1.13 ruu exe! So now all that's left for me to do is s-off using revolutionary and flash a custom recovery.
[HTC EVO 3D] spirithandler:
I am having no luck with this at all! this time around I cant get it to recognize my device when I plug it in. Yes I have debugging enabled.

Why is it I have to have an issue doing this it's baffling to me.

Unknownforce do I have to start the CD process in android or can I start it in fastboot?
[HTC EVO 3D] masbirdies:
Same with me on the device recognition. I am talking to the device via adb/windows. Not through the CD/Toolkit
[HTC EVO 3D] spirithandler:
adb/windows is not going to do you any good with this procedure since the device needs to be bricked and windows is short bus slow recognizing usb's connected to it and you only have something like a 5 second window to push files to the phone in it's bricked state.

It would be nice to get a linux/Ubuntu instruction's for the files Unknownforce linked to in the OP.
[HTC EVO 3D] masbirdies:
Thanks but I was just trying to say I know the device communicates because I can do it in adb/windows. Can't get the device recognized in the toolkit. I know it's not the device or pc (tried multi pcs)
[HTC EVO 3D] genstukov:
I aslo found the ruu here Link

Was downloading at 2.46MB/s
[HTC EVO 3D] wwjoshdew:
http://goo.im/stock/shooter/ruu
[HTC EVO 3D] stacktrace:
Excellent work, Unknown. My virgin mobile nightmare is finally over!

Thanks!
[HTC EVO 3D] spirithandler:
I didnt know if you knew what I posted or not.

Did you try it with a CD or USB? I tried it with USB and it did not work for me I am right now in the process of installing Ubuntu to a USB and going to see if I can get it to work that way!
[HTC EVO 3D] cniels01:
One thing that might work for people that are having problems might be to start over with the ruu, the two firmware files and then the eng hboot and make sure to get to the home screen between each one and then try the cd again.
[HTC EVO 3D] Unknownforce:
Unsure why people are having issues with device detection...

But there is a possibility... What are the first two letters of your serial number on your device? (use the command "adb devices" to look at this)
[HTC EVO 3D] Mexiking10:
Thanks for the hard work Unknown, but I seem to be having some trouble... I've followed the instructions to a T twice now, but when my phone finally boots back up after running the Toolbox, I still have the VM banner and PRI.

This is what I've done both times:

1. Make sure I'm S-OFF and have all the correct files downloaded.

2. Run the 1.13 RUU to stock unrooted. Boot up, get to home screen, reboot to bootloader.

3. Flash VM firmware from bootloader. Boot up, get to home screen, reboot to bootloader.

4. Flash 2.17 firmware from bootloader. Boot up, get to home screen, reboot to bootloader.

5. Flash ENG HBOOT. Boot up, get to home screen, turn on USB debugging.

6. Restart PC, boot from USB, select Radio repair option in toolbox.

After that, everything runs through just fine, no errors at all. But like I said above, after it finishes and I boot up, I'm still on the VM firmware and such.
[HTC EVO 3D] genstukov:
My phone was once a virgin, but then unknownforce came, and now its a dirty little sprint again :laugh:
[HTC EVO 3D] spirithandler:
sh18
[HTC EVO 3D] Unknownforce:
Step 6 is most likely where you're having issue,can you get me the full output from what you're doing?
[HTC EVO 3D] Mexiking10:
PM sent.
[HTC EVO 3D] jdmsleepr:
This worked great!!!! Thanks for all your time and hard work on this!!
[HTC EVO 3D] cniels01:
Has anyone noticed that in ##data# the wimax settings still have virgin mobile in it. I thought this might have been left over from the vm firmware, but my wife's evo 3d (that has never had the VM firmware) had the same settings. Just a weird observation.
[HTC EVO 3D] masbirdies:
I couldn't get it to boot via USB. I made a cd rom and that worked, however, the toolkit could not recognize the device. I thought that was the issue you are having.
[HTC EVO 3D] Unknownforce:
OK, the problem with not recognizing devices is because it's relying on a certain type of serial number... I will have to put in a different check for finding the device. I was using adb wait-for-device, but that method can screw up sometimes too.. adb is... a pain to work with in scripting..

I'll find a better more reliable detection method... I'll update when it's fixed...