lddrew
Newbie
Hboot .98 ROOT IS HERE!!
[Tool] Downgrade VivoW with hboot 0.98 - xda-developers
[Tool] Downgrade VivoW with hboot 0.98 - xda-developers
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root downgrade VivoW with hboot .98!!
- Thread starter lddrew
- Start date
bberryhill0
Android Expert
I see you got it to work. Any hints for people who don't want to wade through the XDA thread?
You may not have the drivers set up correctly. See this link: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Also, make sure you do not miss the step before that one: adb reboot bootloader
If it works correctly, it should boot into a white screen with 3 androids on skateboards down at the bottom.
I'm pretty sure the drivers are installed correctly but, after i ran cmd as admin and then ran the hack-vivow.cmd my phone booted into fastboot but quickly rebooted back up and nothing changed, i'm still at .98 am i supposed to do something?
Also, what am I supposed to do with the RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed ZIP file? Put it on the root of my SD card or....?
bberryhill0
Android Expert
My guess is that you need to put everything in a folder on your PC and run the .cmd from there. The script then pushes the .zip file to your phone. I think.
Okay, now do I need to do the commands manually?
bberryhill0
Android Expert
The whole point of the .cmd file (didn't they used to be called .bat?) is so you don't have to run them manually. If you see errors then you haven't completed the prerequisites. Sorry I can't be more helpful but I'm flying blind.
lddrew
Newbie
had all kinds of problems before i did it alex's way. MAKE SURE you run cmd prompt as admin. makes all the difference, follow his instructions and your golden. worked 1st time. sorry i'm just now getting back to this thread
loudaccord said:lddrew said:
Hi, I'm kind of a newbie also but I can try to help based on what I did. These are the exact steps I took to do this:
Make sure you have everything you need downloaded first... grab the other set of files including revolutionary from this thread.
Good info there too, once you run the last script in attn1's thread , you will have to run revolutionary to get s-off and recovery.
I am using windows 7 and the first thing I did was to make sure ADB was recognizing my phone. Make sure that debugging is enabled under applications on your phone. Once you do that, connect the phone to the computer and select Charge Only. You should see the debugging icon on the phone.
Once those steps are complete, I test to make sure that ADB can issue commands. Since ADB is in the android-win-tools folder, I put all the files I need there so I don't have to switch directories.
This is a screen shot of that:
With my phone connected and debugging enabled on my phone, make sure you're in the right directory on the command line. If you have the folder at the root of your c: drive, then it should be c:\android-win-tools
To get there:
cd c:\android-win-tools
and that will look like this:
the command adb devices will ensure that your phone is recognized.
From there, you can run through attn1's commands, just copy and paste (to paste into the command prompt, right click, paste).
Once complete, run through the revolutionary steps in the other thread I linked.
That should work, let me know what you get.
-Alex
Thank you for that! And just one more question, how do I fix permissions? Seems I don't have permission to run the commands even though I run it as admin.
lddrew
Newbie
are you sure that you have adb, fastboot, and the HTC drivers installed on your desktop??
i got the permission denied or whatever it says error when i forgot to run as admin. once i ran cmd prompt as admin, "cd..."'d to the right directory everything ran great.
lddrew
Newbie
yeah.. that's way too long. it definitely hung. some people have said they had to start over 2 or 3 times before it took. sorry to hear that. my whole process lasted less than i'd say 5 mins..
lddrew
Newbie
yeah keep us posted. don't freak out if you brick it at any point. there are ways to save it
Not sure if anyone could shed some light on this, but after I run adb reboot bootloader the phone will reboot to the white screen (skateboards).
I then run adb devices but nothing shows up. I'm thinking this is why it hangs on the 'fastboot flash zip RUU'
A hard reboot of the phone will send it back to stock OS, from there I can see the device in adb and reboot the bootloader.
Perplexed
I then run adb devices but nothing shows up. I'm thinking this is why it hangs on the 'fastboot flash zip RUU'
A hard reboot of the phone will send it back to stock OS, from there I can see the device in adb and reboot the bootloader.
Perplexed
lddrew
Newbie
Not sure if anyone could shed some light on this, but after I run adb reboot bootloader the phone will reboot to the white screen (skateboards).
I then run adb devices but nothing shows up. I'm thinking this is why it hangs on the 'fastboot flash zip RUU'
A hard reboot of the phone will send it back to stock OS, from there I can see the device in adb and reboot the bootloader.
Perplexed
wait what??
to start your phone needs to be ON. in the interface. connect it to the computer and select charge only and make sure usb debugging is on. detect and make sure the computer can talk to the device. once you get that confirmation go ahead and run the script. basically do alex's walkthrough. the reboot into bootloader happens after some of the under the hood work happens
Thanks again for the assistance! I do in fact understand this aspect of the process however.
On my 5th try, it finally took... just like you said it would. Hopefully others who encounter the hang will indeed try multiple times.
I can now happily report running bootloader .97.
lddrew, thanks again for the instant support. This is my first horrah into rooting, and starting with an unsupported bootloader kind of threw a curveball at me. I appreciate the help.
EDIT: Now the fun begins
lddrew
Newbie
Thanks again for the assistance! I do in fact understand this aspect of the process however.
On my 5th try, it finally took... just like you said it would. Hopefully others who encounter the hang will indeed try multiple times.
EDIT: Now the fun begins
I can now happily report running bootloader .97.
lddrew, thanks again for the instant support. This is my first horrah into rooting, and starting with an unsupported bootloader kind of threw a curveball at me. I appreciate the help.
EDIT: Now the fun begins
Hey man, not a problem. I was in the exact same situation earlier this week. I know how frustrating it is waiting on help anxiously, glad I could help you out. happy rooting!!
pworcester
Member
I used this an took it to 2.3.3 hboot.97 and ran the revolutionary exploit, then took it back to 2.2.1 stock with hboot .97 S-ON and it updated all the way through back to 2.3.4 hboot .98. Nice stuff!