[DOWNGRADE HBOOT/UNBRICK] HBOOT 1.50 -> 1.40 for S-OFF/Root

[filmaker]

Hey okay so I quickly threw together a quick GUI application (Windows only) that will automate step one and the first part of step two. (Obviously..an application can't physically unplug your phone) Anyway.I threw this together really quick..so there are bound to be bugs and my 3D is already rooted, therefore I couldn't test it, so if any brave soul wants to test it, you're welcome to it. It runs the temp root, pushes all the necessary files and gets you up to the part that you have to unplug your device. Oh, and this is only for base 2.17, I didn't include 2.08. Thanks.

http://minus.com/mnKanHwd4#1

 

[Unknownforce]

OH, I just realized why you're having problems...

it should be:

adb shell chmod 755 /data/local/zergRush

NOT:

adb chmod 755 /data/local/zergRush

Sorry, I wrote those up in a hurry. I'll fix it.

 

[jasKaos]

OK, first thing... step back and breath.

Lol...

After you have done that...

do an adb shell and press enter.

Then type in chmod 755 /data/local/zergRush (THIS IS CASE SENSITIVE)

There shouldn't be an output, if there IS an output, it's likely an error message.

Let me know if this works for you or not.

Lol I'm relaxed.

I did that. Zero output. So does that mean it's good now to continue?

 

[Unknownforce]

Lol I'm relaxed.

I did that. Zero output. So does that mean it's good now to continue?

Yes, continue from there, just exit out of adb shell first (just type exit)

 

[il Duce]

If it's not one this with this entire guide, it's another. This is become such a horrible hassle/ordeal and I don't understand why!

I have zergRush in the folder, I can push the fucking file, but for the life of me, whenever I try AT ALL to chmod, it doesn't do anything at all!

I try the 3rd line, and it says permission denied. IN FACT, it's like adb doesn't let me CHMOD at all!! WTF?

Please, for the sake of my own god damn sanity, please help. I am about to die here. I keep trying different methods, and nothing. I can't seem to get TempROOT so I can brick and continue on. HELP! HELP! HELP!

OK, first thing... step back and breath.

Lol...

After you have done that...

do an adb shell and press enter.

Then type in chmod 755 /data/local/zergRush (THIS IS CASE SENSITIVE)

There shouldn't be an output, if there IS an output, it's likely an error message.

Let me know if this works for you or not.

chmod is a shell command no?

so it should be:

adb shell chmod 755 blahblahblah

correct?

 

[Gimik]

holy balls that was fun. that was the most fun I've had with an android device. I am working on my friend's evo and was just going to send it back to him on 1.5, but when I read that I had to intentionally brick this thing, I just HAD to try it.

Worked like a charm. Thanks man.

 

[Unknownforce]

chmod is a shell command no?

so it should be:

adb shell chmod 755 blahblahblah

correct?

Yep caught that a couple posts back, fixed now.

 

[jasKaos]

Bricking this device seems to be realllllllly difficult too. lol. I keep pulling after 4 seconds, i'm going to try 5 next! I mean, how fast do you need to unplug and replug this back in???

 

[Unknownforce]

Bricking this device seems to be realllllllly difficult too. lol. I keep pulling after 4 seconds, i'm going to try 5 next! I mean, how fast do you need to unplug and replug this back in???

Yeah, you have to wait like 5-6 seconds, and plug it right back in, doesn't have to be instant, but quickly.

 

[jasKaos]

Yeah, you have to wait like 5-6 seconds, and plug it right back in, doesn't have to be instant, but quickly.

Ok, say I wait 5-6 seconds and it stops saying "Updating..." and starts the next process and then I unplug it and plug it back in... It won't brick, right?? It has to be done like RIGHT before the next part after "Updating", correct?

BTW I can't seem to watch ANY of the videos for this tutorial. Kind of sucks X_X

 

[Unknownforce]

Ok, say I wait 5-6 seconds and it stops saying "Updating..." and starts the next process and then I unplug it and plug it back in... It won't brick, right?? It has to be done like RIGHT before the next part after "Updating", correct?

BTW I can't seem to watch ANY of the videos for this tutorial. Kind of sucks X_X

You have to unplug before it gets to the next one, which is boot, dont' worry if you do it too late, boot is only your kernel for your current rom, which you will be overwriting when you go back to 1.13 anyways, if you do it too late, just restart again and go just 1 second sooner.

 

[mnomaanw]

Ok, say I wait 5-6 seconds and it stops saying "Updating..." and starts the next process and then I unplug it and plug it back in... It won't brick, right?? It has to be done like RIGHT before the next part after "Updating", correct?

BTW I can't seem to watch ANY of the videos for this tutorial. Kind of sucks X_X

You have to connect to a/c outlet and then take out the battery first, then start the update without battery and after 5 sec of updating bootloader remove the charger.

 

[Unknownforce]

Just an update, I think it might be possible to do the linux part on a VM rather than having to have a separate PC or a dual boot environment.

I'll be testing this shortly.

 

[jasKaos]

You have to connect to a/c outlet and then take out the battery first, then start the update without battery and after 5 sec of updating bootloader remove the charger.

Trust me I've done just that. It never bricks. LOL Danny this cursed device! I'll try again later after work ha.

Sent from my PG86100 using xda premium

 

[dkdude36]

The security warning is probably what's stopping you then. Idk.

If you have your stuff backed up, you can definitely just run the stock ruu exe in windows while booted to FASTBOOT USB to revert to stock.

i've actually tried running the ruu and can't get it to run. might just be that it's not set up right (got windows running in parallels) but i doubt it. i think im going to try to return to stock 100% manually. here i come flashing, adb shelling, and removing su apks! let's hope somebody put out a rom.zip somewhere with stock system

 

[Unknownforce]

sounds more like a setup issue... I don't know parallels well enough... what error do you get when you run the ruu?

 

[alammori]

I ended up just unlocking my phone with HTC's method and flashed a rooted ROM. After I had root via the unlock method, I just went back and redid the first steps again: pushing the necessary files and changing the version again. Except this time ignoring the temp root and just using my full root. Once this step was done, I re-locked my bootloader (fastboot oem lock) and THEN with the PG86IMG.zip file on my sdcard, booted into the bootloader, and this time it wanted to update.

All else was cake after that. Got it bricked the first try

Unknownforce,

I know that your instruction are general steps for those with hboot 1.5. but looking at what Austin3600 did. I am assuming it is not necessary for those who previously used the HTC Unlock method to install 2.08 or 2.17 rom and use the temp or permanent root in order to push the version hack files.
Does that mean that since we are htc-unlocked with custom or stock rom we need to:

1. Change your directory to that location where you extracted the Tools.zip and type the following commands,
adb push misc_version /data/local/
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver

2. then Re-lock the phone.
then straight to Second Step

 

[Bairdog35]

Just an update, I think it might be possible to do the linux part on a VM rather than having to have a separate PC or a dual boot environment.

I'll be testing this shortly.

And you told me it couldn't be done... How dare you discourage my emotions

 

[Unknownforce]

Unknownforce,

I know that your instruction are general steps for those with hboot 1.5. but looking at what Austin3600 did. I am assuming it is not necessary for those who previously used the HTC Unlock method to install 2.08 or 2.17 rom and use the temp or permanent root in order to push the version hack files.
Does that mean that since we are htc-unlocked with custom or stock rom we need to:

1. Change your directory to that location where you extracted the Tools.zip and type the following commands,
adb push misc_version /data/local/
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/misc_version -s 1.10.651.2
adb reboot bootloader
fastboot getvar mainver

2. then Re-lock the phone.
then straight to Second Step

This is correct

 

[Unknownforce]

And you told me it couldn't be done... How dare you discourage my emotions

Eh, it's not looking good thus far, windows only detects a single device... So it's not passing them all to the guest Linux box... I'm still testing.

But, I'm also using the limited VirtualBox... it passes through USB DEVICES, not PORTS... which is poor... I think VMWare might do things better... gonna check that out next.