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

[RussianBear]

Thats what the companies tech use to fix brick phones brother sorry, to say but its not kang but sharing to root.

just to make my previous post clear:

i've posted it in the defense of the op, and not to entice him for anything extra lol
let's focus on something more important now, shall we?

 

[notsointeresting]

Sorry to ask again, but I want to be sure, in Linux what drivers/ programs do we need.
Like adb,etc

 

[EGOvoruhk]

Fuses, who is credited in the original post, is the biggest reason this is possible. Without his tool, we wouldn't be flashing downgraded HBOOTs

http://forum.xda-developers.com/showpost.php?p=23566551&postcount=249

 

[Unknownforce]

You either need to move from USB to AC while the battery is in and it's in fastboot, OR start off with the battery in and plugged into AC. once you're in fastboot, you should be able to remove the battery while the phone stays powered on. You must remove the battery in fastboot, not hboot. If you remove the battery while in hboot, it will shut off.

I'm either reading this wrong or confusing myself trying to read it.

Here's the step by step...

1.) Prepare the sd cards
2.) Put the sd card with the 2.08 image in the device
3.) Leave the back cover off
4.) Boot to HBOOT and plug it into AC
5.) Then pull the battery, it will stay on
6.) Let it detect the image and get to the prompt to press the button to update
7.) Then swap the sd cards for the 1.13 image, and press vol up to update...

That is the way I remember doing it. But again, it's been said that it's copying the file to the device anyways, if that's the case, I don't know why it worked for me... and it's possible that the sd card swap wasn't even necessary. I have much testing to do tonight.

 

[AndroidGraphix]

Awe news. Hopefully this can be done on the rezound. I'll let you know how it goes. Jk but hopefully we can do this later. I can't stand s on.

 

[Unknownforce]

Sorry to ask again, but I want to be sure, in Linux what drivers/ programs do we need.
Like adb,etc

I used ADB and fastboot in windows. Other than those things I did NOTHING special to the install of WUBI other than just install it, give it my password, copy the emmc_recover and hboot image to my home folder, and run those things (I did basic diagnostic stuff before to make sure devices were correct, but nothing that would affect the outcome)

There are no drivers needed in linux if you don't use adb or fastboot in linux, which I didn't so I don't know what's needed if you DO use those two in linux... but google can probably tell you what you might need to have them run properly.

 

[shizkoff777]

You know your doin something right when you have haters

Sent from my PG86100 using XDA

 

[notsointeresting]

I used ADB and fastboot in windows. Other than those things I did NOTHING special to the install of WUBI other than just install it, give it my password, copy the emmc_recover and hboot image to my home folder, and run those things (I did basic diagnostic stuff before to make sure devices were correct, but nothing that would affect the outcome)

There are no drivers needed in linux if you don't use adb or fastboot in linux, which I didn't so I don't know what's needed if you DO use those two in linux... but google can probably tell you what you might need to have them run properly.

Alright thanks , time to try it for ****s and giggles

 

[freeza]

I'm either reading this wrong or confusing myself trying to read it.

Here's the step by step...

1.) Prepare the sd cards
2.) Put the sd card with the 2.08 image in the device
3.) Leave the back cover off
4.) Boot to HBOOT and plug it into AC
5.) Then pull the battery, it will stay on
6.) Let it detect the image and get to the prompt to press the button to update
7.) Then swap the sd cards for the 1.13 image, and press vol up to update...

That is the way I remember doing it. But again, it's been said that it's copying the file to the device anyways, if that's the case, I don't know why it worked for me... and it's possible that the sd card swap wasn't even necessary. I have much testing to do tonight.

I wonder if it's possible to access the temp location that the pg86IMG gets copied to, then just replace it with another one

 

[il Duce]

I wonder if it's possible to access the temp location that the pg86IMG gets copied to, then just replace it with another one

Isn't there a temp emmc partition?

 

[Vinchenzop]

Isn't there a temp emmc partition?

You'd probably need to basically use the method here to push that in while the phone is in the emmc mode, since you'd still technically be s-on. Of course to do this, you'd have to be able to brick...#endlessloop

 

[m0fizor]

I think this was covered, but:
I HOPE YOU GUYS SEND THE PROMISED MONEY TO THE DEVS

I'm speaking about the thread in the general 3vo forum.

 

[mildlydisturbed]

I think this was covered, but:
I HOPE YOU GUYS SEND THE PROMISED MONEY TO THE DEVS

I'm speaking about the thread in the general 3vo forum.

oh I will when the thing is totally working, although someone's going to have to break it down by what dev / what involvement / what percentage and donate links

---------- Post added at 03:01 PM ---------- Previous post was at 02:58 PM ----------

I'm either reading this wrong or confusing myself trying to read it.

Here's the step by step...

1.) Prepare the sd cards
2.) Put the sd card with the 2.08 image in the device
3.) Leave the back cover off
4.) Boot to HBOOT and plug it into AC
5.) Then pull the battery, it will stay on
6.) Let it detect the image and get to the prompt to press the button to update
7.) Then swap the sd cards for the 1.13 image, and press vol up to update...

That is the way I remember doing it. But again, it's been said that it's copying the file to the device anyways, if that's the case, I don't know why it worked for me... and it's possible that the sd card swap wasn't even necessary. I have much testing to do tonight.

Quick question - you're trying to get it into brick / EMMC recovery mode at step 7. Can't this just be done via the paperclip trick in the s-off discussion thread without having to brick the device?

Sorry if it's been covered before

 

[sunilromy]

Hello OP,

preparing my homework, Getting ubuntu, and following RUU.

RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed_2.exe

RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed.exe


hope i am on right RUU? Really cant wait my downloading speed sucks.

 

[Unknownforce]

oh I will when the thing is totally working, although someone's going to have to break it down by what dev / what involvement / what percentage and donate links

---------- Post added at 03:01 PM ---------- Previous post was at 02:58 PM ----------



Quick question - you're trying to get it into brick / EMMC recovery mode at step 7. Can't this just be done via the paperclip trick in the s-off discussion thread without having to brick the device?

Sorry if it's been covered before

Nope, I tried this for hours, it never got to emmc mode, the bricking puts it into a different DL mode than what is gained by this trick.

 

[Unknownforce]

Well, I'm back on 1.50.0000 and S-ON. Ready for when I get home... Hopefully all goes well tonight... should have an update in like two-three hours.

 

[USSENTERNCC1701E]

Well, I'm back on 1.50.0000 and S-ON. Ready for when I get home... Hopefully all goes well tonight... should have an update in like two-three hours.

I can't really test this with my phone without going S-ON and upgrading HBOOT myself. And since you're already at this point, uh, I'm not going to go there, lol sorry. But, if you find that you cannot brick your phone and it was just a fluke. Try putting a file on your sdcard titled SMART_IO.crd doesn't matter what the file is, could just be a blank txt file you've renamed. Boot the phone to bootloader, insert an sdcard with this file, then switch to fastboot mode, then back to hboot mode. Phone should lock up, maybe this will trick it into the emmc mode. I never did this while connected to linux.

Now that we know the mode exist, it's just a matter of finding a solid way in. Everything else about this method is solid. It may even be possible to brick it by messing with the radio and still get into the emmc recovery. That would require repairing the radio partition too, and be a lot riskier though. Also did you verify that the phone doesn't repair itself after a battery pull. It could just be the timing of something that you did without even thinking of it.

If you need to, maybe lock this thread down to keep the haters STFU and get together with Crackanug, video tape everything you do, and see if he can/will try to emulate it.

Whatever happens, this is a hell of a lot closer than any of us have been on the 3VO. You had 1.40 and went back to 1.50 purgatory. Not many would do that to themselves. Mad props dude.

 

[Unknownforce]

I can't really test this with my phone without going S-ON and upgrading HBOOT myself. And since you're already at this point, uh, I'm not going to go there, lol sorry. But, if you find that you cannot brick your phone and it was just a fluke. Try putting a file on your sdcard titled SMART_IO.crd doesn't matter what the file is, could just be a blank txt file you've renamed. Boot the phone to bootloader, insert an sdcard with this file, then switch to fastboot mode, then back to hboot mode. Phone should lock up, maybe this will trick it into the emmc mode. I never did this while connected to linux.

Now that we know the mode exist, it's just a matter of finding a solid way in. Everything else about this method is solid. It may even be possible to brick it by messing with the radio and still get into the emmc recovery. That would require repairing the radio partition too, and be a lot riskier though. Also did you verify that the phone doesn't repair itself after a battery pull. It could just be the timing of something that you did without even thinking of it.

If you need to, maybe lock this thread down to keep the haters STFU and get together with Crackanug, video tape everything you do, and see if he can/will try to emulate it.

Whatever happens, this is a hell of a lot closer than any of us have been on the 3VO. You had 1.40 and went back to 1.50 purgatory. Not many would do that to themselves. Mad props dude.

Not a bad Idea actually. I remember trying that and it trashed my sd card, but it also put it into a no boot scenario as well. Good thinking.

And yeah, all that's left to do is to get the brick method working for all, the rest is easy, and a script can be written for the whole multiple /dev/sd*13 thing and all that... But primary goal of tonight is... BRICK!

 

[Vinchenzop]

Unknownforce, also look which hw version you have to see if maybe that's what your method is dependent on

 

[Unknownforce]

Unknownforce, also look which hw version you have to see if maybe that's what your method is dependent on

It is possible that it is dependent on it... but I do know for sure that I was on 2.17 because I remember taking the OTA to get rid of CIQ just a few days ago, which is exactly what I did just now, ran the 2.08 RUU exe, which put 1.50.0000 back on, (which was S-OFF) and then ran fastboot oem writesecureflag 3, so it's now back to S-ON and fully stock, (says LOCKED at the top) then accepted the OTA, (and did the voicemail update that it was complaining about) exactly like before.

So I'm back to exactly where I started, other than having my own personalization on the stock rom, which was wall papers, sounds and and apps from the market... that kinda crap... which, if those matter, there's something very wrong haha...