• 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!!

There was a request to sticky this thread, but it still seems a bit in flux as a procedure, so the thread doesn't quite seem sticky worthy.

It is active enough to keep it bumped near the top for now.. let's keep an eye on it.

If you feel strongly about wanting it stickied, let me know.
 
I'm working on a step-by-step guide for this process (crazy as that might be). I got it done, but first I installed SDK because when I read "get adb and fastboot working on your pc" on the XDA post I thought that is what was necessary.

Is that true? Or can you just extract the zip file folder to, say, C:\Android and run the cmd script from there without messing with SDK?

Also, I got a huge number of errors saying "The system cannot find the path specified" when I ran the script, but everything worked anyway. Any idea why that happened?
 
bberryhill0 said:
I believe that adb and fastboot are included in the .zip file.
Click to expand...
They are. Do you have to do anything special to use them or are they just supposed to be sitting there available in the unzipped folder? Do you run them first by double-clicking them?

I suppose I could delete everything I installed and try it again without SDK just for experiment's sake.

Nevermind...I think that is exactly right. You don't need SDK to run any of this.
 
dbpullman said:
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.
Click to expand...

Ending up in the same place, with <waiting for device>
I tried testing to see if the adb even detected the phone, which it did not. From cmd (as an administrator):
Code: 
C:\> cd C:\Users\Me\Downloads\vwhk-12102011-c\tools\win
C:\Users\Me\Downloads\vwhk-12102011-c\tools\win> abd devices
List of devices attached

C:\Users\Me\Downloads\vwhk-12102011-c\tools\win>

So, seems like I did not get the HTCDriver3.0.0.007 installed right. Basically, I downloaded it, ran it, it closed, and that was it. I tried downloading it again to run it in case it didn't install right the first time, but nothing at all happened (no setup wizard or anything). I guess my issue is installing the HTCDriver3.0.0.007. Has anyone else had similar problems installing it, or is there a special way you have to install it?

Thank you in advance for the help!
 
frogger4 said:
Ending up in the same place, with <waiting for device>
I tried testing to see if the adb even detected the phone, which it did not. From cmd (as an administrator):
Code: 
C:\> cd C:\Users\Me\Downloads\vwhk-12102011-c\tools\win
C:\Users\Me\Downloads\vwhk-12102011-c\tools\win> abd devices
List of devices attached

C:\Users\Me\Downloads\vwhk-12102011-c\tools\win>

So, seems like I did not get the HTCDriver3.0.0.007 installed right. Basically, I downloaded it, ran it, it closed, and that was it. I tried downloading it again to run it in case it didn't install right the first time, but nothing at all happened (no setup wizard or anything). I guess my issue is installing the HTCDriver3.0.0.007. Has anyone else had similar problems installing it, or is there a special way you have to install it?

Thank you in advance for the help!
Click to expand...
It does sound like a driver problem. Try uninstalling, re-downloading, and installing drivers again. If they work adb should detect your phone.
 
Heeeelllllp. I've ran this multiple times and it seems like it worked, only to look in the settings and I'm still on 2.3.4 I've attached a pic of my screen when I'm in the dos prompt. Anyone have any ideas on what this n00b is doing wrong? I ****'ed out my device name. Everything else is as it ran... THANKS!
flel1z.jpg
 
It looks like there is an error with sending the downgraded Rom to your phone (the largest file). I don't know what the problem is but I would try downloading zip again and starting fresh from folder off C: drive.

Also try putting all files you need in *one* folder.
 
annielouwho said:
Heeeelllllp. I've ran this multiple times and it seems like it worked, only to look in the settings and I'm still on 2.3.4 I've attached a pic of my screen when I'm in the dos prompt. Anyone have any ideas on what this n00b is doing wrong? I ****'ed out my device name. Everything else is as it ran... THANKS!
flel1z.jpg
Click to expand...

First, did you make sure to turn fast boot off and turn debugging on? Also, did you start the command prompt window as administrator?
 
debugging is enabled
Fast boot is disabled
I am logged in as admin (on XP) is there something else I should do?

I'm going to re-download everything again and unzip all to one folder with no subs and try again. Thanks for your help. :)
 
The ZIP file named RUU&#8203;_Vivo&#8203;_W_Gingerbrea&#8203;d_S_VERIZON&#8203;_WWE&#8203;_2.18&#8203;.605&#8203;.3_Radio&#8203;_1 [...] inside the main ZIP file is corrupt. So I'm downloading the main zip again while looking for alternate download sites for the Gingerbread Zip. I'll try to keep you updated as I go along :)
 
annielouwho said:
debugging is enabled
Fast boot is disabled
I am logged in as admin (on XP) is there something else I should do?

I'm going to re-download everything again and unzip all to one folder with no subs and try again. Thanks for your help. :)
Click to expand...

Once you open the command prompt window, right click in the top and select administrator. Or, in windows 7, type cmd in search files. When cmd.exe appears, right click on it and select administrator.
 
I have tried this like 10 times now. I have done/tried all of the following:

run cdm as admin
run proper code lines
installed adb
found serial # of phone
installed drivers
removed sync
charge only
debugging
uninstalled and reinstalled drivers
have an sd card installed

I have searched every forum I can possibly find and tried every possible fix but everytime I run the script I get: FAILED (remote: 43 main version check fail)

why is this error happening when I'm doing everything correctly?
 
You must log in or register to reply here.
Back
Top Bottom