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

[spirithandler]

Does my phone need to be on stock? or can I just lock it back up on meanrom and downgrade?

 

[dimqs153]

so
i just relocked
run PG86IMG.zip 2.17 ( coz i already update to 2.17 once )
root using tacoroot
continue ur tutor

am right?

 

[Unknownforce]

Does my phone need to be on stock? or can I just lock it back up on meanrom and downgrade?

This process will revert completely to stock anyways. But as long as you have # in adb shell, you don't have to revert to stock to begin with.

Just backup your stuff, relock the boot loader and start from step one.

 

[Unknownforce]

so
i just relocked
run PG86IMG.zip 2.17 ( coz i already update to 2.17 once )
root using tacoroot
continue ur tutor

am right?

Correct, verify your root by doing adb shell and seeing the # sign.

 

[dkdude36]

Seems right...

What does it say at the top of your boot loader in purple?

it says relocked and then right under that it says security warning (cuz i'm still running a custom rom and it's unbootable). i would revert to stock, but i cant run an ruu to do that

 

[Unknownforce]

it says relocked and then right under that it says security warning (cuz i'm still running a custom rom and it's unbootable). i would revert to stock, but i cant run an ruu to do that

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.

 

[dimqs153]

i dont get mainver: 1.10.651.2
i got mainver: 2.17.651.2
u can see on my attachment
what should i do?

 

[Unknownforce]

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.

Oh and remember to start from step one all over again, cause the main version will go back to 2.17 when you run the ruu.

 

[Unknownforce]

i dont get mainver: 1.10.651.2
i got mainver: 2.17.651.2
u can see on my attachment
what should i do?

What is the output from the rest of the commands that you ran before those?

 

[dimqs153]

first attemp was fail
it told to unplug n replug after reboot
2nd attemp succes

 

[Unknownforce]

first attemp was fail
it told to unplug n replug after reboot
2nd attemp succes

Not sure what that means, when you type adb shell do you see a # or a $

 

[dimqs153]

se my attachment

 

[Unknownforce]

se my attachment

You didn't get temp root to work right, the misc_version failed because it couldn't access what it needed to because there was no root.

Are you using tacoroot or zergRush?

 

[dimqs153]

tacoroot
coz im on 2.17

 

[Unknownforce]

tacoroot
coz im on 2.17

Do it again and check the output there for errors.

 

[jasKaos]

TEMP ROOTING PROCEDURES

FOR ALL ADB OR TEMP ROOTING, be sure to enable USB Debugging...

Here's the basics for zergRush rooting: (2.08)

adb push zergRush /data/local/
adb chmod 755 /data/local/zergRush
adb shell /data/local/zergRush

PROCEED WITH STEP 1

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!

 

[Unknownforce]

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.

 

[klept0]

Add me as another success story to your list....thanks to the whole team who made this a reality!

 

[Will32]

I'm trying this tonight but I need to iron a few things out.... Beside 1) in the second step, does it mean the Rom.zip or the ruu.zip?

 

[mnomaanw]

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!

I was on 2.17 and tacoroot does the same with me.
I relocked the bootloader and ran the 2.17 RUU.
Booted the phone and without unlocking did the tacoroot and it worked fine.