yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] otto325:
Forgive me for being such a noob with this stuff.

I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.

So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?

The stock

is there, so do I remove that one and replace it?

I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?

*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader

I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.

Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that
[HTC EVO 3D] mpgrimm2:
What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?
[HTC EVO 3D] otto325:
This one:

http://xdaforums.com/showthread.php?t=1563342
[HTC EVO 3D] mpgrimm2:
Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.

see here

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
THANKS

Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:

Step 1... Plug in Device while holding down Volume Down key...

Waiting for device...

Just a matter of getting a new data sync cable now and I can do this...

Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..

Will report back in a couple days, hopefully with a newly rooted phone

--------

Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
[HTC EVO 3D] mpgrimm2:
Yep. Previously...

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
OK

The downgrade worked and I am:

SHOOTER XC SHIP S-ON RL

HBOOT-1.40.0000

RADIO-1.09.00.0108

eMMC-boot

Jun 8 2011, 17:20:22

Only now I am stuck on the 1.13 RUU EXE and the phone boot loops.

When I run the 1.13 EXE, part way through the processes it stops with an error:

...

And when I unplug the phone, phone says:

RUU main version is older! Update fail!

....

Also do I delete the PG86IMG.zip folder from the main directory of the sd card?
[HTC EVO 3D] mpgrimm2:
From Unknownforce's URT 3.1 thread...

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
I followed those steps. You could have highlighted the part you think I missed. Can you be a little more specific?

I read in this thread the phone needs to be bricked a second time after down grading from 1.58. Unknownforce's phone was 1.50...

I am now tryng to repeat the URT downgrade after bricking again but it does not seem to be working this time. I am still S-ON so I didn't permanently brick my phone??? Unknown specifically states not to brick the phone with S_OFF
[HTC EVO 3D] mpgrimm2:
Not trying to be short, just don't have much time at moment

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
k well SOMEHOW after bricking the second time(after achieving 1.4) then unsuccessfully running the URT downgrade again, my phone has returned to hboot 1.58 and boots up to 2. 95.

Also has

*** LOCKED ***

*** Secutiry Warninig ***

EDIT: it's not booting past bootloader...

Is it bricked?
[HTC EVO 3D] mpgrimm2:
Do me a favor if you haven't already. Read through the first 2 posts of Unknownforce's thread (and faq's) as well as from my post 781that I linked earlier. Make sure to watch the video for downgrade/unbricking, then post in his thread so we aren't bouncing back and forth between your thread and his for directions (hard to do on a phone). Heck I have to keep going back and reading it after a year.

I doubt you are perma bricked if you are still S-on and Locked Bootloader plus you can boot the bootloader.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
I don't know why I tried brick/downgrade twice. I was on hboot 1.4 S-ON, except 1.13 .exe did not work so I repeated the downgrade a second time and now the downgrade Linux tool will not recognize my phone....And somehow I am back to 1.58 S-on

After attempting the the downgrade each time(and it never works), the phone will not boot afterwords and stays on boot loader with security warning. Until I VOLdown+Power on and re-run the PG86IMG bricking , then the phone boots normally again...real strange

What happens if I let the PG86IMG run through the whole update?
[HTC EVO 3D] mpgrimm2:
Yes. If you run a Full ruu PG86IMG.zip (i.e. the last 2.89 or 2.95 vs the ota zip) it should be able to boot.

Edit:

If it accepts the full ruu zip to run.

I will have some time in about 2 hr's if you are still up before I start tinting windows on a car.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
That may be reason the URT tool in Linux was was not recognizing the phone the second time around(and booting with security warning). I have to full reflash update with the PH186IMG. Lemme try that but this data cable is really bad, I'll hopefully have a good quality one early this week...

Done the window tinting by the way. Great way to save yourself some $$having it done professionally if you have the patience:good:
[HTC EVO 3D] mpgrimm2:
I'm available if u are.. Gathering up files and my old 3d. Reviewing URT 3.1 directions and videos....

Edit:

- You probably want to microSD cards to keep things from getting mixed up with the zips on the root of the sdcard..

1 small one ( class 4 or less) for the brick step with just the PG86IMG.zip from the 2.95 OTA with newer Hboot file (About 18mb)

1 Other microSD Card with the full 1.13 RUU extracted as a PG86IMG.zip file for after the brick to downgrade.

May need to go to http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/

to get their Universal USB Installer to create a bootable Linux USB Drive from the LiveCD if you don't plan on burning a CD (I used Pendrive and selected "Unlisted Linux ISO (NEW) at the bottom)
[HTC EVO 3D] otto325:
Available for what? How about monday or tuesday when I have a new sync cable. Because the Evo didn't come with any power supply or data cable so I've been using a crappy one that losing signal all the time
[HTC EVO 3D] mpgrimm2:
I just relocked my phone and set it to S-On. So I am in the same boat as you now...

FW: 2.95.651.6

SHOOTER XC SHIP S-ON RL

HBOOT-1.58.0000

RADIO-1.09.00.0108

eMMC-boot

Edit:

- You probably want to microSD cards to keep things from getting mixed up with the zips on the root of the sdcard..

1 small one ( class 4 or less) for the brick step with just the PG86IMG.zip from the 2.95 OTA with newer Hboot file (About 18mb)

1 Other microSD Card with the full 1.13 RUU extracted as a PG86IMG.zip file for after the brick to downgrade.

OK. I put the PG86IMG.zip - 18.73 MB file (2.95.651.6 OTA with Hboot 1.58.0000 ) on the root of one sdcard and was "Finally" able to rebrick the phone. I had to wait and pull the battery after it had unzipped and it was "updating" the bootloader (item 2. with this PG86IMG.zip file) which is after it is unzipping/updating item 1. BOOT (if you pull during this step, the phone can't boot to anything but the bootloader).

I know it's bricked from Unknownforce's OP which says...

Edit: DIDNT BRICK YET ! arrggh.

and 1.5hrs later I finally bricked it.

On to the "Unbrick" URT LiveCD....and to rebrick it twice...

FYI: The URT 3.1 wouldn't find my phone to "Downgrade Hboot" with the battery in, so leave it out when it says to plug it in.

Also, If the bootloader shows Hboot 1.40 and version-main: 0.01.651.1. you're done (i.e "fastboot getvar all"). If it's 2.95.xxx, brick/downgrade again.

- Put the phone in "FASTBOOT USB" mode (should see this in phone's screen), connect to pc, and run the Full 1.13.651.7 RUU.exe from PC. Now you are Downgraded to 1.13 with Hboot 1.40 and ready to run Revolutionary's S-Off tool

EDIT:

Post 14 (dev host link to 2.89 zip) and post 52 summarizes the update from 1.13 to 2.89 to 2.95 ota's
[HTC EVO 3D] mpgrimm2:
Revolutionary ran fine: Hboot 1.40, S-Off, 1.13 FW

Remember to go to:

Settings - Applications - Development and check USB Debugging

Settings - Power and Uncheck "Fastboot" (power save thing)

You wont get the option to get the "beta key" without clicking the download link on their site which req's the phones SN to get it also.

There is a way to copy/paste from the file menu of the Revolutionary program, see attached.

-------

Now to run the last full RUU.zip (2.89.651.2) as a PG86IMG.zip file and then get the OTA updates to get back to 2.95.651.6 (or whatever). Once s-off, always, s-off unless you set the flag manually.
[HTC EVO 3D] otto325:
HELPFUL

Bricked the phone properly this time and downgraded successfully through linux(though it took about 50 tries with this data cable, probably unsafe)

But I am now downgraded to hboot 1.40 again with S-ON.

...

Having a problem with the 1.13 rUU using the

RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed

from this list

Not sure what I'm missing, probably it's my cable but it finishes sayings:

....

On the phone screen:

Also. should the PG86IMG zip folder from the SD card be removed?
[HTC EVO 3D] mpgrimm2:
Yes, the 1.13 Ruu.exe fw from my devhost is the correct one. Verify the md5 is 8c7702f1d7a53c82227d027de22ebfa5

and also make sure the phone is in "fastboot USB" mode before running the exe. The bootloader screen is different than the fastboot screen.

One of the things the URT 3.1 does in addition to changing the hboot is set your main version (FW) to an early value, 0.97.xxx (something like that). You may need to brick it twice to get urt 3.1 to set the main version lower so the 1.13 FW will run.

You can check after the downgrade using the " fastboot getvar all " command or " fastboot getvar mainver " I think.

It sounds like your main version number is still 2.95.xxx

Once bricked, you can move, remove or rename the PG86IMG.zip file so you don't accidentally run it again.

Hope this helps you. Not exactly sure what you are missing. I used the 18mb 2.95 ota PG86IMG.zip from Unknownforce's post for the brick.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
The PG86IMG from your quote back on page 2(post #14), (second quote) worked to brick the phone before running URT 3.1.

How do I verify "md5" is 8c7702f1d7a53c82227d027de22ebfa5??

...

Results from "fastboot getvar all"

C:\rootevo3dnew>fastboot getvar all

< waiting for device >

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.40.0000

(bootloader) version-baseband: 1.09.00.0108

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.95.651.5

(bootloader) serialno: HT1CGHX04613

(bootloader) imei: 355195000000010

(bootloader) product: shooter

(bootloader) platform: HBOOT-8260

(bootloader) modelid: PG8610000

(bootloader) cidnum: SPCS_001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3800mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: bb55392bbe351c9fdb551155d0d623b36cb3fe1

getvar:all FAILED (status malformed (1 bytes))

finished. total time: 0.035s

...

Still main version 2.95.651.5, though I believe it was 2.95.651.6 before................

If I need to brick the phone again, I just repeat; brick with PG86IMG file and URT 3.1 in Linux again?? Last time I tried this my phone locked with security warning and reset to 1.58 but I was also not bricking properly when re-attempting....
[HTC EVO 3D] mpgrimm2:
Yep the 2.95 main version is stopping you.

I used the battery pull brick method on a full battery (piece of tape makes the pull easier) to save wear on my usb port. (See post 32 for brick twice quote).

You can Google MD5 checker to get a PC app the compares the number I gave to a value of the file to verify a good download if they match (always recommended to avoid issues with bad files)

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
MD5 came back correct:

8c7702f1d7a53c82227d027de22ebfa5

K, so re-brick and URT 3.1 it is then
[HTC EVO 3D] otto325:
The battery pulling method works better...the phone doesn't turn off before the right time to pull the power. Not the right AC adapter either so there you go
[HTC EVO 3D] otto325:
Bricking the second time with 18mb PG86IMG absolutely not working....tried 3 times

this is what happens after pressing VOL-UP to do the update "bootloader" unplug....Skips 1st "BOOT" altogether and starts on the 2nd on the list "bootloader". So bootloader unzips and updates, but nothing else. When I pull during bootloader update, the phone simply doesn't brick. Has blinking(not solid) red light and powers back to 1.4(unless I let the bootloader update without pulling then I am back at 1.58 with security warning
[HTC EVO 3D] mpgrimm2:
Yep, have to brick/pull power during some "magic" moment while its updating the bootloader. Took me an hour and a half to get that step done. 30-40 times for me. And I never got the solid dim light, just wouldn't boot or anything. PIA.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
Ok, will report back. Thing is, it likes to reset on it's own back to 1.58 so I have to start from the beginning and that's ANNOYING...
[HTC EVO 3D] otto325:
Bricking has become IMPOSSIBLE after using the battery pull trick. AC cord no longer works and I am in 1.58 just trying to do the first brick...

:eek:

Edit: AC cords WORKS, but the phone shuts off when it starts the boot update without the battery in...Have two AC adapters, one for a KOBO 7" tablet and one for an LG cell phone(older botton phone) Both are doing the same thing
[HTC EVO 3D] mpgrimm2:
I had same issue on the cord with oem HTC charger and 2 amp Touchpad charger. Had to use the battery.

02:45 Edit:

Process appears to go: Unzipping/Updating/(brief transition)/OK.

Seems to brick (for me) during that very brief transition between updating and OK. Note the time that the bootloader updating step takes and try to hit it right at the end. Good luck, it can be done.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] otto325:
It updates so quick there almost isn't any transition whatsoever....and if it "ok's" before I get the chance to cut the power, the phone is back to 1.58 and I'm starting over again.:eek:

But Ok.

Didn't know micro sd's were different but this one says:

Sandisk 16gb HC I...not sure which class that is, but on the regular SD adapter the date is 2013-11-19A
[HTC EVO 3D] otto325:
FINALLY. I found that actually using the AC and battery on full charge worked well. Pull battery then AC...also the light does go solid dim the second brick also

1.13 RUU successful

C:\rootevo3dnew>fastboot getvar all

< waiting for device >

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.40.0000

(bootloader) version-baseband: 1.09.00.0108

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 0.01.651.1

(bootloader) serialno: HT1CGHX04613

(bootloader) imei: 355195000000010

(bootloader) product: shooter

(bootloader) platform: HBOOT-8260

(bootloader) modelid: PG8610000

(bootloader) cidnum: SPCS_001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3800mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.450s

After 1.13 RUU

C:\rootevo3dnew>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.40.0000

(bootloader) version-baseband: 0.97.10.0530

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.13.651.7

(bootloader) serialno: HT1CGHX04613

(bootloader) imei: 355195000000010

(bootloader) product: shooter

(bootloader) platform: HBOOT-8260

(bootloader) modelid: PG8610000

(bootloader) cidnum: SPCS_001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3800mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status malformed (0 bytes))

finished. total time: 1.038s
[HTC EVO 3D] otto325:
-Revolutionary-

SHOOTER XC SHIP S-OFF RL

HBOOT 1.40.1100

RADIO 0.97.10.0530

eMMC-boot

NOW to get my main version back to 2.95, I run a 2.89 .zip as PG86IMG (Where do I find this .zip?? I could only find a 2.89 .exe in your list(Footballs's))

And then OTA(regular system updates from the OS?) will update me back to 2.95?
[HTC EVO 3D] Brian706:
Woooo hoooooooo!

2.89 zip:

https://copy.com/iAKHV
[HTC EVO 3D] otto325:
This goes in the download folder, correct? Do I remove and replace the existing .zip folder there?

Or is it renamed PG86IMG.zip and placed in the main directory? I don't have a downoad folder after formating the sd

Also, OTA = regular system updates from the internet, right?
[HTC EVO 3D] otto325:
Ok I ran the .RUU.(Thanks Brian) as PG86IMG in main directory (PG86IMG.zip doesn't get recognized)

It ran through twice....looked like it skipped a bunch of the things in the list the first time....then rebooted and unzipped/updated each thing...

Finished, reboot and on 2.89 main version

Phone says ***LOCKED*** instead of -Revolutionary- on the boot screen so I guess my next step is to do the HTCdev.com unlock?????
[HTC EVO 3D] Brian706:
The RUU replaced your revolutionary hboot with the stock hboot. It's not necessary to unlock the bootloader now that you are s-off, but if you want to, you can do it by flashing the zip in this post via your custom recovery. Just flash the unlock_bootloader.zip (probably obvious :p)

I think that you can't use all fastboot commands if the bootloader is locked. So it needs to be unlocked to allow those extra commands, or alternatively you can use a patched hboot that will allow the extra commands even with a locked bootloader. I would suggest using one of the juopunutbear patched hboots. For your current setup you would want to grab the ICS HBOOT - 1.58.5858 from them.

Just rename the file to PG86IMG.zip and place on the root of the sd card like you did with the RUU. It will update your hboot with the jpbear one.
[HTC EVO 3D] mpgrimm2:
Glad you got s-off finally. PIA right?

Once you get the 2.89 ruu zip run (PG86IMG.zip on root of SD), remove/rename the zip after reboot, connect to internet and let/force the phone to check for the 2 updates to get you up to 2.95.651.6. You can download them yourself but I was never able to get them to work manually (see my my quote in earlier post).

There are 2 threads in my signature you need to review, especially the one about hboot locked/unlocked/s-off differences. Fyi, certain hboots only work with certain roms/kernels.The other thread will cover some basics but some of the links may be older files. As Brian706 suggests, go with jbear hboot 1.58.5858 on the 2.95 FW is a good place to start and with the 3d, "4ext Recovery" is Highly Recommended (Cwm Compatible).

Remember to backup your stock ROM after getting a custom recovery installed (save it to PC). A good custom ROM to consider that is compatible with multiple hboots is Negalite BluRom (r121 was last version I used).

Sent from my "Up All Night Sleep All Day" Nexus 5!
[HTC EVO 3D] Brian706:
Just as reference, I have a thread with all the 3vo radios and hboots and stuff here. And a thread with all RUU downloads here. I don't plan on taking them down. Nothing is more frustrating than looking for downloads and they've all been removed by the time you need them. Unless something unforseen happens, I plan on leaving them up indefinitely.
[HTC EVO 3D] otto325:
Thanks for all the help

So in order to gain root(I mainly just want to delete bloatware apps from the internal drive) I need to be unlocked so is HTCdev unlock not recommended after this process?

Also, what is PIA?? :confused::laugh:

Oh and revolutionary tool installed a recovery as well
[HTC EVO 3D] Brian706:
Root is separate than unlock or s-off. They usually go hand in hand though.

You never HAVE to unlock because you are s-off.

If you just want to stay stock (which it sounds like) with root privileges, you just need to flash superSU via your custom recovery.

This will flash the binaries you need and add a super user app to grant permissions.

You can grab that flashable zip here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip
[HTC EVO 3D] otto325:
How exactly do I flash the zip via custom recovery?
[HTC EVO 3D] Brian706:
You simply download that file either on pc and transfer the file, or even easier, download via your phone's Web browser.

So have the file on your SD card. Boot into your custom recovery and go to the install menu. Browse to the zip file and confirm the install.

No need to rename the file or anything. This is different than the bootloader flashable file.

If you need more detail, let me know.
[HTC EVO 3D] otto325:
How do I access it? Should there be an option for custom rcovery on the hboot screen?

All there is is just normal recovery and selected it brings up an exclamation icon for a couple minutes and the phone reboots,

Also, do I put the zip on the main(root) directory? And keep the name(as in dont rename it PG86IMG
[HTC EVO 3D] Brian706:
Okay. You still don't have a custom recovery installed then. That is how you access it, by selecting recovery from the bootloader screen.

So to install a custom recovery, you will need to unlock the bootloader via fastboot or install the juopunutbear patched hboot.

Download this: https://www.dropbox.com/s/smdbibra6q6salh/4ext_1.0.0.5.rc9_recovery.img

Rename to recovery.img

Place in your fastboot directory on the pc.

Use the command: fastboot flash recovery recovery.img

Then from here you can type: fastboot boot recovery.img

Or access the recovery via the bootloader. Then install the file as described above.

Edit:

Your custom recovery got replaced by the ruu, just like your hboot did. The ruu is the ultimate return to stock tool.
[HTC EVO 3D] otto325:
Right and I can't run revolutionary again with 1.58...Ok thanks I will try this now
[HTC EVO 3D] Brian706:
You don't need to run revolutionary again. You are permanently s-off now unless you purposely turn s-on with a fastboot command.

You never have to worry about s-off again. Ruu removes root and returns you to stock, but it will not overwrite s-off and root is simple to add again when you are s-off.

Edit:

Sorry, since you are s-off, you can also flash a recovery from the bootloader.

https://www.dropbox.com/s/t6q8wi58xzidgan/4ext_1.0.0.5.rc9_PG86IMG.zip

If you download that and rename PG86IMG.zip you can install the recovery just like you ran the ruu. No need to unlock the bootloader or flash the recovery.img via fastboot.
[HTC EVO 3D] otto325:
I was using "cd \rootevo3dnew" to retrieve phone info with the fastboot getvar all...is this the same folder I will place the reovery.img in and run the commands?
[HTC EVO 3D] Brian706:
Yes. If that's the folder that contains fastboot.exe which I'm pretty sure it is.

Oh yeah, it definitely is if you ran your getvar all.
[HTC EVO 3D] otto325:
SD custom recovery and SuperSU updates worked!! happy happy happy thanks

Also, should I run a backup with the recovery or do anything else with all those options?
[HTC EVO 3D] Brian706:
Definitely a backup. If anything goes wrong, you can restore your phone to the exact state it was in at the time of the backup. Other than that, congrats! You went through some **** and powered through! You deserve a beer sir.