Related
I guess I'm not the first to ask for help with this particular problem.
I use DJ_Steves 1.5.1 rom right now.
Is it possible to go back to Dell's official European software again?
I've read something about a 309 recovery file. What should I do with it?
Is it the file I need to install before I can download Dell's latest software to my phone?
Thanks in advance for your help!
yup u need the 309 recovery file.....flash it in fastboot...
once thts done...assuming u have the pkg file renamed as update.pkg in ur sd card u can boot into recovery and install update.pkg....
Thanx! i will search for the 309 file!
FOTA model name missmatch!
I guess i miss something??
I run a new stock.recovery.img and i worked. Then i run the new update.pkg from sdcard. But it didnt work.
Ii there more steps i have to do before i can run the update.pkg?
i went from 1.5.1 to stock 2.2. v 319 with no issues
First flash the recovery.stock.new.img - link http://www.megaupload.com/?d=8LDVERY4
then reboot to recovery and install update from the stock recovery.
Was a smooth ride for me .
I did exactly like like you but it didnt work. I think i have to change baseband but i didnt understand how
i think once u install the stock rom , it will flash the baseband as well.
OKey! Now im stuck on with Dell logo and the streak doesnt start.
Now im really dont know what to do. :S
omg
bearpower said:
OKey! Now im stuck on with Dell logo and the streak doesnt start.
Now im really dont know what to do. :S
omg
Click to expand...
Click to collapse
Go Back into the Fast boot and flash the Recovery then the update if you use the 309 recovery and 318 update you will not run into any problems i have gone from Steve's back to dells back to Steve's at least 10 times using the 309 recovery
okey! i will try again!
bearpower said:
FOTA model name missmatch!
I guess i miss something??
I run a new stock.recovery.img and i worked. Then i run the new update.pkg from sdcard. But it didnt work.
Ii there more steps i have to do before i can run the update.pkg?
Click to expand...
Click to collapse
I kept having the same issues also. I tried everything i could possible find and just ended up going back to bestbuy and get the phone replaced since i'm under my 30 days. Now i'm scared to even flash this darn white streak... =(
diffstyle said:
I kept having the same issues also. I tried everything i could possible find and just ended up going back to bestbuy and get the phone replaced since i'm under my 30 days. Now i'm scared to even flash this darn white streak... =(
Click to expand...
Click to collapse
Yes...i understand. Little bit scary. :-( B-)
lufc said:
Go Back into the Fast boot and flash the Recovery then the update if you use the 309 recovery and 318 update you will not run into any problems i have gone from Steve's back to dells back to Steve's at least 10 times using the 309 recovery
Click to expand...
Click to collapse
Hi, I was looking to get back to the stock 2.2 also from 1.5.1. So I install the recovery that is posted in the link here and where do I get the stock update file? Is this the one on my SD card from the original 12821 update?
bearpower said:
FOTA model name missmatch!
I guess i miss something??
I run a new stock.recovery.img and i worked. Then i run the new update.pkg from sdcard. But it didnt work.
Ii there more steps i have to do before i can run the update.pkg?
Click to expand...
Click to collapse
I ran into this same problem. Updated to the new stock recovery (link from this thread) then I tried to install the update (12821) from here:http://mobileupdate.dell.com/PackageProductionLocations/Streak_318_12821_00.pkg
This will update you to baseband: GAUSB1A131800 which is what I am already on so not sure if I'm missing something. Do I need to go to an older baseband to be able to install this update.pkg..?
UPDATE: Figured it out. I was using the wrong recovery image. I thought I had the 309 but I didn't. As soon as I used the 309 recovery with the lastest stock froyo rom (12821) I was golden. Back to 100% stock. If not for this thread, I would have been lost for awhile. Thanks guys!
Raspster said:
I ran into this same problem. Updated to the new stock recovery (link from this thread) then I tried to install the update (12821) from here:http://mobileupdate.dell.com/PackageProductionLocations/Streak_318_12821_00.pkg
This will update you to baseband: GAUSB1A131800 which is what I am already on so not sure if I'm missing something. Do I need to go to an older baseband to be able to install this update.pkg..?
UPDATE: Figured it out. I was using the wrong recovery image. I thought I had the 309 but I didn't. As soon as I used the 309 recovery with the lastest stock froyo rom (12821) I was golden. Back to 100% stock. If not for this thread, I would have been lost for awhile. Thanks guys!
Click to expand...
Click to collapse
Okey. great.
Where did u get the working 309 recovery file?
have a nice day...or night...whatever u have right now.
Hi
I looked around and saw a few ppl having trouble while rooting vibrant.
I've put update.zip on /sdcard, and when i reboot my phone in recovery mode it says something about my package not being signed.
So i googled and did this:
java -classpath "/home/ohai/Downloads/android-sdk-linux_86/tools/sign/testsign.jar" testsign update.zip file-signed.zip
(don't worry, i'm not that stupid, i DO have the sdk and the testsign installed here)
then renamed file-signed.zip to update.zip and replaced it on /sdcard, but still got the same message.
Does anyone have a link to a actually working update.zip to vibrant's froyo?
i'm using froyo.UVJL4, downloaded from samfirmware.com.
Thx in advance
?
Sent from my SGH-T959 using XDA App
Everyone's update.zip is usually different is what i'd think.
try getting titanium backup, click menu and click menu, and then CREATE update.zip
that might help you out.
Go to dec section and look for the jl4 rom from geodude(cant remember exact name...) His rom, odex or deodex both come prerooted with the 3e recovery fix as well. Flash that. KTB.
Sent from my SGH-T959 using XDA App
If you are comfortable using the voodoo lagfix you can flash the new voodoo 5 kernels. They come with the SU binary and clockworkmod recovery built in. Then download busybox and superuser from the market. You'd have to flash via ODIN though.
Thx for the tips, but i was not thinking about using modified roms... all i want is to root my default rom from samsung, is it possible?
You need the correct key to sign the zip file. My understanding is this key was not released by Samsung so you will not be able to sign your update.zip files to work with the 3e recovery.
The 2e recovery accepted a "test key" which is why we're able to use update.zip to root and use CWM.
The RATC method still works for rooting in the 2.2 Firmware. You can use SuperOneClick to root, and then replace the stock 3e recovery with the one from here. This is a modified 3e recovery which removes the signature checking.
How about trying the ALT METHOD in the Noob Guide (my signature)... then flash a stock rom with root?
http://forum.xda-developers.com/showthread.php?t=857974
personally, you are hurting yourself by not running a rom like Nero v3 or Eugenes Ginger Clones.
Rooting T-Mobile Vibrant Froyo 2.2 JL5
I have the T-mobile Vibrant US Phone. I upgraded to JL5 and have rooted my phone with a program from here:
http://forum.xda-developers.com/showthread.php?t=803682
Get the latest version and you might have to run the program 2 or 3 times for it to finish. Note on my phone these were the steps I took.
1. Put phone in USB Debugging Mode.
2. Plug usb cable to computer.
3. Run the rooting program above with windows administrator rights.
4. It will run then probably hang half way through and indicate WAITING FOR
DEVICE.
5. Shut windows program down.
6. Reboot phone (Turn Off then On).
7. Reconnect to usb.
8. Restart the Rooting Program and Root.
9. It should finish and ask if you want to test SU say yes.
10. That's It you should be good to go.
Hope this helps.
s15274n said:
How about trying the ALT METHOD in the Noob Guide (my signature)... then flash a stock rom with root?
http://forum.xda-developers.com/showthread.php?t=857974
personally, you are hurting yourself by not running a rom like Nero v3 or Eugenes Ginger Clones.
Click to expand...
Click to collapse
What's so good in those roms?
NihtSpi said:
I have the T-mobile Vibrant US Phone. I upgraded to JL5 and have rooted my phone with a program from here:
http://forum.xda-developers.com/showthread.php?t=803682
Get the latest version and you might have to run the program 2 or 3 times for it to finish. Note on my phone these were the steps I took.
1. Put phone in USB Debugging Mode.
2. Plug usb cable to computer.
3. Run the rooting program above with windows administrator rights.
4. It will run then probably hang half way through and indicate WAITING FOR
DEVICE.
5. Shut windows program down.
6. Reboot phone (Turn Off then On).
7. Reconnect to usb.
8. Restart the Rooting Program and Root.
9. It should finish and ask if you want to test SU say yes.
10. That's It you should be good to go.
Hope this helps.
Click to expand...
Click to collapse
JL5?
where did you get it?
atcasanova said:
What's so good in those roms?
Click to expand...
Click to collapse
You still can't get rooted & you want FroYo?
I attached cwm update.zip so just use that to get into CWM Recovery (Reinstall Packages, You may need to do it twice) and then just flash the following ROM
http://forum.xda-developers.com/showthread.php?t=881692
Master™ said:
You still can't get rooted & you want FroYo?
I attached cwm update.zip so just use that to get into CWM Recovery (Reinstall Packages, You may need to do it twice) and then just flash the following ROM
http://forum.xda-developers.com/showthread.php?t=881692
Click to expand...
Click to collapse
Sorry for being this dumb, but i don't have a clue of what is CWM
me too,
im desperately looking to root my vibrant from Bell canada. i just updated to JL2 using the kies pc software. i just got this phone for xmas so im quite new to it.
im hoping to find an app or website that can do most of the steps for me. or a youtube video with detailed step by step.
ive tried using the guide that s15274n wrote (btw, thanks for the awesome writeup) but i have the same problem of the update.zip file not passign the signature verifaction.
i would like to stay with a stock ROM for at least another couple weeks because of the super high chance of this phone bricking itself
my phone has a build date of 11.10
any thoughts?
thank you VERY much for any help
EDIT:
I have managed to root my phone! hurray!
heres how i did it:
i used the superoneclick method thanks to this link http://forum.xda-developers.com/showthread.php?t=803682
i used this guide to help me through the steps http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
thanks to everyone to put in work to make this possible.
THANK YOU!
chucked said:
me too,
im desperately looking to root my vibrant from Bell canada. i just updated to JL2 using the kies pc software. i just got this phone for xmas so im quite new to it.
im hoping to find an app or website that can do most of the steps for me. or a youtube video with detailed step by step.
ive tried using the guide that s15274n wrote (btw, thanks for the awesome writeup) but i have the same problem of the update.zip file not passign the signature verifaction.
i would like to stay with a stock ROM for at least another couple weeks because of the super high chance of this phone bricking itself
my phone has a build date of 11.10
any thoughts?
thank you VERY much for any help
EDIT:
I have managed to root my phone! hurray!
heres how i did it:
i used the superoneclick method thanks to this link http://forum.xda-developers.com/showthread.php?t=803682
i used this guide to help me through the steps http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
thanks to everyone to put in work to make this possible.
Click to expand...
Click to collapse
So many people figure out what was wrong and they are done. Thank you for posting your finding, I have been trying to Root my Bell Vibrant for a while.
Use SuperOneClickRoot - http://forum.xda-developers.com/showthread.php?t=803682
Works all the time for Vibrant!
I'm sorry if there is something already posted here somewhere about the rezound, but I haven't seen anything...yet...lol.
I've been trying to root my rezound ALL DAY and can't seem to figure anything out apparently.
If someone could help me out with sending me a link to the best way of unlocking bootloader and then rooting my phone. I had a dinc2 previously and that was not as hard to root compared to the rezound IMO. So please, if someone can take the time for me and help me out with getting my phone unlocked and rooted I would greatly appreciate it a TON!!!
Try this out http://forum.xda-developers.com/showthread.php?t=1648578
http://bit.ly/N3cfpa
hey guys thanks for replying back....I'm still getting no luck whatsoever with unlocking the bootloader.....I'm doing everything (or so I think I am) right with the steps on htcdev.com and when I get to the command prompt and type in fastboot oem get_identifier_token...this is what comes up
'fastboot' is not recognized as an internal or external command,
operable program or batch file.....now I have NO CLUE what the heck to do!! I'm getting pissed off lol. I could really use some help here. thanks
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
EmerikL said:
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
npainter7 said:
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
Click to expand...
Click to collapse
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
kzoodroid said:
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
Click to expand...
Click to collapse
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Fastbird said:
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Click to expand...
Click to collapse
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
npainter7 said:
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Click to expand...
Click to collapse
After you install Android SDK the directions on the HTCdev site tell you to run sdk manager and download the Android SDK Tools and Android SDK Platfrom-tools. What I did was to take this a step further and also install the Google USB Driver which is listed in ADB Manager under Extras and also the API's for GB and ICS. The API's really aren't necessary but I don't think ADB will recognize the phone without the Google USB Drivers.
npainter7 said:
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
Click to expand...
Click to collapse
This may not work for you, but one time my drivers weren't working because I plugged my phone into a USB 3.0 port, so when I used a USB 2.0 port, it worked fine.
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Hi, have you installed adb succesfully in your pc previously?
If yes then the next thing you need is fastboot.exe file, if not then start with that first then fastboot.
You can find what you need here, also if you search in my threads (link in my signature) you can find a tutorial about how to install and use ADB.
~ Veronica
Acclaim
I have the same challenge. I have ADB working successfully (and have used Veronica's guide to repartition my NT - thanks again). Yet when I use Cyanoboot and start Fastboot my device shows up in Other Devices as Acclaim and none of the USB drivers I have pointed to get installed. It isn't mission critical that I solve this but it would be nice from a knowledge base to understand what I am missing in case I ever need to use Fastboot. It seems to be a much easier tool to change the installed Recovery image than ADB. Any help would be appreciated.
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
ShinnAsuka said:
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
Click to expand...
Click to collapse
+1
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
bingoz said:
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
Click to expand...
Click to collapse
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
bingoz said:
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
Click to expand...
Click to collapse
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Can you explain more or upload the file already edit for me? Thank you
bingoz said:
Can you explain more or upload the file already edit for me? Thank you
Click to expand...
Click to collapse
each product id is different so uploading the file isn't going to do you much good. sorey
Sent from my Nook Tablet CM7 BETA using xda premium app
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
I don't have windows so I won't comment on that. There is one thing that I never see mentioned when talking of adb access problems.
On custom roms (your case cm9 0.05.1) in settings, developer options, Android debugging should be checked to allow adb access. If not checked that may be your issue.
If I'm having adb issues and it was working previously I'll boot to cwm (5.5.0.4 version not 5.0.2 or whatever) and go from there.
You should get adb working properly, but to flash recovery you can use one of the flashable zip files while in cwm. They work for me!
Got a few minutes on a windows 7 pc (people should take their breaks at their desk). If you are using Veronicas thread http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1 you will find a file runmefirst.bat if you run it and follow instructions about unplugging and replugging nook it will create and setup the previously mentioned file. Do not run zergy as suggested. When it pulls device manager your exclamation should say nook. Right click it, update driver software, browse my computer, let me pick, and then choose the directory with your usbdrivers, tell it yes to use them. Do not worry about anything else from runmefirst.bat including anything else to run. You just want it to set the codes for your nt and then it is of on use.
I had adb working for my nt quickly on that windows 7 pc. It had no previous adb or usb drivers installed.
Good Luck
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
nba1341 said:
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
Click to expand...
Click to collapse
like i said in a previous post, right click the acclaim item under other devices and look for the product id and edit the android_winusb.inf accordingly.
after that right click acclaim, update driver software, and browse for the drivers yourself. if all goes well fastboot should work. this is how i did it. not that i ever really use fastboot but its good to have just in case.
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
Check your android_winusb.inf to see if you have the right entry for the NT -- see http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
Penguin101 said:
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
Click to expand...
Click to collapse
Why not flash your NT using SD-based CWM Recovery (e.g., see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31)?
The easiest way under windows, is just choose the driver on your own, use the driver from the Android SDK (sdk\extras\google), and you will be presented with a couple of options, choose Android Composite ADB Interface.
It would, at this time to be prepared for s-off, making sure you have all htc drivers install, sdk tools and the like, have you recovery.img ready to go and your supersu zip in the proper place, don't wait to the last minute to do this, then your ready to go.
I've been working on gathering everything up. I'm unlocked so I need to relock, install update, unlock and get root back yet. I've been holding off cause I hate to give up viper and go back to stock.
Where would one start? I don't know where to get sdk....not to mention how to use it. Do you think you could come up with a list of you have the time? Every phone I've rooted has had unlock tools (unrevoked for og Inc and alpha rev for Inc 2)
Linch89 said:
Where would one start? I don't know where to get sdk....not to mention how to use it. Do you think you could come up with a list of you have the time? Every phone I've rooted has had unlock tools (unrevoked for og Inc and alpha rev for Inc 2)
Click to expand...
Click to collapse
go to unlimited.io and you can get latest htc drivers and adb sdk tools too, they have links there. you can get recovery from hasoons tool. we don't have a root tool yet, it's coming.i should say s-off tool
as far as using adb and sdk tools, should be some instruction here somewhere, search the forums for it you should find it.
Thanks boss yeah I know no tool yet
Aldo101t said:
go to unlimited.io and you can get latest htc drivers and adb sdk tools too, they have links there. you can get recovery from hasoons tool. we don't have a root tool yet, it's coming.i should say s-off tool
as far as using adb and sdk tools, should be some instruction here somewhere, search the forums for it you should find it.
Click to expand...
Click to collapse
Do we need root tool, or can we just flash recovery then su binary?
Sent from my Nexus 7 using Tapatalk 2
jamminjon82 said:
Do we need root tool, or can we just flash recovery then su binary?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
you can't flash recovery til you either get s-off or unlocked bootloader, you can't flash SU til you have recovery, so.
Aldo101t said:
you can't flash recovery til you either get s-off or unlocked bootloader, you can't flash SU til you have recovery, so.
Click to expand...
Click to collapse
I was saying once you have s-off
Sent from my DROID SPYDER using Tapatalk 2
I'd say get a ROM ready, once u get s-off, u can install recovery, then install a ROM.
the superuser root .zip is only needed if you plan to use the stock ROM.
I am so going to have to take my laptop to town to get to Wi-Fi to update Windows so I can root my phone.
To quote the juggernaut, "sh!t I've been ready to f!ck"
Sent from my DROID SPYDER using Tapatalk 2
Aldo101t said:
go to unlimited.io and you can get latest htc drivers
Click to expand...
Click to collapse
Whether I try to use the drivers from unlimited.io or the ones linked by jose51197 in the automatic unlock post I can't get them to install on my computer. I'm running 64-bit Windows 8 Release Preview Version 6.2 (Build 8400). OldNut5 mentioned that it worked for him on 64-bit Windows 8 Pro, so I don't think my operating system is the problem. As soon as the installer starts running, it shows an error message which reads:
Code:
The Driver Installer is not supported for this Operating System!
Has anyone else had this problem? I tried running it as administrator, as well as running it in compatibility mode for both Windows 7 and Windows XP (SP3), but it always produced the same error. Am I missing something obvious, or does this only work on the Pro version of Windows 8 for some reason?
altayh said:
Whether I try to use the drivers from unlimited.io or the ones linked by jose51197 in the automatic unlock post I can't get them to install on my computer. I'm running 64-bit Windows 8 Release Preview Version 6.2 (Build 8400). OldNut5 mentioned that it worked for him on 64-bit Windows 8 Pro, so I don't think my operating system is the problem. As soon as the installer starts running, it shows an error message which reads:
Code:
The Driver Installer is not supported for this Operating System!
Has anyone else had this problem? I tried running it as administrator, as well as running it in compatibility mode for both Windows 7 and Windows XP (SP3), but it always produced the same error. Am I missing something obvious, or does this only work on the Pro version of Windows 8 for some reason?
Click to expand...
Click to collapse
Drivers are designed to work for a specific operating system. I personally haven't been able to get a single driver for any device to work on Windows 8 that was designed for Windows 7. Vista drivers more often than not did work on Windows 7, though. Go figure.
In this thread, someone says they installed the most recent version of HTC Sync on Windows 8 and managed to get the drivers working. Try that.
EDIT: Just tried this on Windows 8 and it worked perfectly.
IceDragon59 said:
EDIT: Just tried this on Windows 8 and it worked perfectly.
Click to expand...
Click to collapse
Thanks a bunch! Installing HTC Sync didn't help, but this worked perfectly.
bleh, just use linux and you dont need to worry about drivers
nitsuj17 said:
bleh, just use linux and you dont need to worry about drivers
Click to expand...
Click to collapse
To be honest I dual-boot my computer and primarily use Ubuntu, but the automatic bootloader unlock guide was written for Windows with a handy zip of executables and a batch script, and I didn't want to have to figure out how to properly install adb on Ubuntu as well as risk messing something up if there happens to be a Linux-only issue.
It's nice to know that it should work on Ubuntu without any need for the drivers. I assume this is how I would have to install adb. It's a shame I can't just "sudo apt-get install adb" it...
altayh said:
To be honest I dual-boot my computer and primarily use Ubuntu, but the automatic bootloader unlock guide was written for Windows with a handy zip of executables and a batch script, and I didn't want to have to figure out how to properly install adb on Ubuntu as well as risk messing something up if there happens to be a Linux-only issue.
It's nice to know that it should work on Ubuntu without any need for the drivers. I assume this is how I would have to install adb. It's a shame I can't just "sudo apt-get install adb" it...
Click to expand...
Click to collapse
looks like a decent guide