Hey all,
I’m not sure if this is the right place, but I hope so (feel free to move this as necessary). A few months ago, I got a Razr XT910 on Rogers. It came with 2.3.5, and so I decided I would give ICS a shot. I successfully managed to get Team Kang’s ICS 4.0.4 running on it, through CWM. That went through fairly easily.
Now, however, I’m trying to get the thing back to its stock ROM (which I already have), and have been trying to get it going through RSDlite (newest version downloaded as of yesterday).
Now I’m not a pro at this stuff, but I wouldn’t say I’m completely inept… but I can’t get it to revert. Mainly because I can’t even get RSDlite to recognize my phone, due to the MTP Usb driver failing to install. (Specifically, it says Code 10: cannot start for the error message). I’ve googled, and searched through here, but all the work arounds don’t work. (Uninstalling, selecting generic drivers manually, etc). I had chalked it up to being an issue with Win7 x64, so I tried a fresh install of XP pro x86 (through a VM), and I get the exact same error in XP.
I don’t know what I’m missing, or what I’ve messed up. It was a fresh install of XP, I downloaded the Moto driver helper as well as a new version of RSD lite. I can’t for the life of me figure out how to get this driver working. I seem to be able have made step by step progress getting there, but I would really like to have this last piece of the puzzle solved, so here I am. Any help/tips would be appreciated!
If any more info is required for help, just let me know, I’ll get you what I can!
Apotheos said:
Hey all,
I’m not sure if this is the right place, but I hope so (feel free to move this as necessary). A few months ago, I got a Razr XT910 on Rogers. It came with 2.3.5, and so I decided I would give ICS a shot. I successfully managed to get Team Kang’s ICS 4.0.4 running on it, through CWM. That went through fairly easily.
Now, however, I’m trying to get the thing back to its stock ROM (which I already have), and have been trying to get it going through RSDlite (newest version downloaded as of yesterday).
Now I’m not a pro at this stuff, but I wouldn’t say I’m completely inept… but I can’t get it to revert. Mainly because I can’t even get RSDlite to recognize my phone, due to the MTP Usb driver failing to install. (Specifically, it says Code 10: cannot start for the error message). I’ve googled, and searched through here, but all the work arounds don’t work. (Uninstalling, selecting generic drivers manually, etc). I had chalked it up to being an issue with Win7 x64, so I tried a fresh install of XP pro x86 (through a VM), and I get the exact same error in XP.
I don’t know what I’m missing, or what I’ve messed up. It was a fresh install of XP, I downloaded the Moto driver helper as well as a new version of RSD lite. I can’t for the life of me figure out how to get this driver working. I seem to be able have made step by step progress getting there, but I would really like to have this last piece of the puzzle solved, so here I am. Any help/tips would be appreciated!
If any more info is required for help, just let me know, I’ll get you what I can!
Click to expand...
Click to collapse
You cant go back to gingerbread after installing ICS as far as i know.
Related
Yesterday, I upgraded my new white dell streak to from 1.6 to 2.2 using the QDLtool. BTW, its easy as pie, it took about 30 mins, even with the extra task for using a 64-bit OS!!! I used the phone as i would normally yesterday and everything, GPS, internet, Facebook, etc worked perfectly.
Today, I try to do anything web related (i.e. Market, internet, Facebook, etc.) and I get 'A network error has occurred' message. I have tested the phone service and it seems to be working fine.
Has anyone else ran into this or have ideas of what I might try? Thanks in advance, cheers.
SOLVED
****PROBLEM SOLVED****
I FEEL LIKE A NOOB FOR THIS...
At any rate, I solved this problem by resetting the APN to default.
Settings > Wireless & networks > Mobile networks > Access Point Names > Press the 'Menu' key > Reset to default > check the radio button under ATT US.
Data network seems to be working fine at this time. I will post if anything changes.
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
sukemecuke said:
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
Click to expand...
Click to collapse
No experience at all for me. I had never even touched an android phone prior to the streak.
I haven't heard of anyone bricking their phones with QDL when following the guide, many have bricked them by other means though. It took 10 minutes from unzipping the download to rebooting into 2.2 for me. The software did all the work. I have heard of several people successfully unbricking with QDL.
Some people have issues with getting drivers installed but the tool will not act without the correct drivers so there is little risk there. If stock 2.2 is your goal there is no easier way that I have seen. After QDL is done I think the process on to 1.5.5 is easier also.
There is a guide at streakdroid.com
sukemecuke said:
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
Click to expand...
Click to collapse
Qdl is simple. Its mostly automated. I havent seen anyone brick it with qdl yet. Drivers can be a pain, but fairly simple if your familiar with windows at all. Easier with vista/seven in my opinion.
Sent from my Dell Streak using XDA App
jeremyritzmann said:
Qdl is simple. Its mostly automated. I havent seen anyone brick it with qdl yet. Drivers can be a pain, but fairly simple if your familiar with windows at all. Easier with vista/seven in my opinion.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
that's good to know. I have quite a few options. I have a linux machine with ubuntu, an older win XP with 32 windows, and a W7 64 bit machine. The XP machine is hella slow though, so the W7 machine is my preferential option. A smidge concerned about the extra step since it's a 64 bit machine. I'm going to look into it tomorrow since I am off work for the rest of the year for the holidays. I'll report back with my results.
I'm coming from rooting my G2..Now I'm gonna try to root my girls streak. I advised her to get the phone and now feel bad shes still stuck with 1.6. I'm gonna attempt this tomorrow as it sounds easy. Just wondering why you don't have to root in order to update. Is there no root necessary to update?
sukemecuke said:
that's good to know. I have quite a few options. I have a linux machine with ubuntu, an older win XP with 32 windows, and a W7 64 bit machine. The XP machine is hella slow though, so the W7 machine is my preferential option. A smidge concerned about the extra step since it's a 64 bit machine. I'm going to look into it tomorrow since I am off work for the rest of the year for the holidays. I'll report back with my results.
Click to expand...
Click to collapse
The extra 64-bit steps were easy to do. I did install the wrong driver at first. I installed the 'Modem 9002' driver instead of the 'Diagnostic tool 9002'. I just went back to 'Device Manager', removed the wrong driver and installed the correct one. After that, make sure you install ADB drivers and then use the QDL tool. As stated previously by others, the tool does all the work. I hope this helps. let us know how things go.
sukemecuke said:
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
Click to expand...
Click to collapse
My previous experience comes from hacking a few iphones, then I switched to android devices. The biggest difference I have seen is that the android hack require more command line tasks than the iphone. DO NOT FEAR THE COMMAND LINE, MAKE IT YOUR B****!!!!!
But a tip I'll give is, ALWAYS follow the guides STEP BY STEP, and make sure you know where the files you are working with are!!! A lot of the bricks come from poor file management i.e. the fastboot or update.pkg file not in the correct directory or file name is wrong and needs to be changed.
The QDL tools was suggested for the white streak as it slightly different from the black unit in the form a of preventative hacking measure, at least that is the only different that I am aware of.
Do your research and good luck, cheers
keep us posted
ccb04 said:
I'm coming from rooting my G2..Now I'm gonna try to root my girls streak. I advised her to get the phone and now feel bad shes still stuck with 1.6. I'm gonna attempt this tomorrow as it sounds easy. Just wondering why you don't have to root in order to update. Is there no root necessary to update?
Click to expand...
Click to collapse
Nothing I have read required the streak to be rooted before hand but my device was rooted. i have not rooted the build yet either. If she isnt going do anything that really requires rooted then she may not even need it. But 2.2 is pretty smooth so far and she will most likely benefit from having the better device with 2.2 than being rooted, IMHO.
The entire process took about 30 minutes and after fixing the APN issue the only other problem I had was what UI i was going to use.(Currently running Laurncher PRO - with the purchased key...AWESOME!!!!!)
QDL Tool how to (I used the streakdroid guide):
http://streakdroid.com/?page_id=92
http://forum.pocketables.net/showthread.php?t=8214
For 2.2 rooting use the z4root downloadresearch first as I have not used this)
http://www.androidzoom.com/android_applications/tools/z4root_ngtp.html
Good luck, cheers
asher73 said:
The extra 64-bit steps were easy to do. I did install the wrong driver at first. I installed the 'Modem 9002' driver instead of the 'Diagnostic tool 9002'. I just went back to 'Device Manager', removed the wrong driver and installed the correct one. After that, make sure you install ADB drivers and then use the QDL tool. As stated previously by others, the tool does all the work. I hope this helps. let us know how things go.
Click to expand...
Click to collapse
Since I've tried other methods of installing ROM's previously by using the W7 machine it wouldn't work. So I did a system restore to get rid of the previous stuff. Now it won't even let me install the the ADB drivers can be downloaded from Dell: ftp.dell.com/Handheld/R288920.exe
It just say's error on install. So I tried it on my super old XP machine which was brutally painfully slow. And it won't even update the driver manually. It just says "The specified location does not contain information about your hardware." I will say that under device manager on the XP machine it just lists it in other, like it should, as a Generic Volume instead of the Qualcomm stuff. Weird.
So just outta curiosity, since this froyo build puts your baseband at "00", wouldn't it be possible to then use's dells officially 2.2 unlocked rom and flash it through recovery? I mean using the update.pkg file from your sd card?
It sounds like it worked, but did it? If so which method did you end up using?
In the streakdroid guide there is a command line task you needed to execute before doing anything. To the best of my knowledge that task set WIN 7 to run in a testing mode which allowed for the ADB drivers to be installed properly.
asher73 said:
It sounds like it worked, but did it? If so which method did you end up using?
In the streakdroid guide there is a command line task you needed to execute before doing anything. To the best of my knowledge that task set WIN 7 to run in a testing mode which allowed for the ADB drivers to be installed properly.
Click to expand...
Click to collapse
I was wondering if you had to do the command line portion prior to installing the ADB drivers. Going to give that a go. Wish I could just get it to work with the XP machine, but I can't get it to recognize in the device manager that it's plugged in without turning the device on. It makes the sound as if it realizes a device is connected, but nothing ever shows up in the device manager. grrrrrrrrr
sukemecuke said:
that's good to know. I have quite a few options. I have a linux machine with ubuntu, an older win XP with 32 windows, and a W7 64 bit machine. The XP machine is hella slow though, so the W7 machine is my preferential option. A smidge concerned about the extra step since it's a 64 bit machine. I'm going to look into it tomorrow since I am off work for the rest of the year for the holidays. I'll report back with my results.
Click to expand...
Click to collapse
good deal. if you need any help with anything you can catch me on google talk. [email protected]
sukemecuke said:
I was wondering if you had to do the command line portion prior to installing the ADB drivers. Going to give that a go. Wish I could just get it to work with the XP machine, but I can't get it to recognize in the device manager that it's plugged in without turning the device on. It makes the sound as if it realizes a device is connected, but nothing ever shows up in the device manager. grrrrrrrrr
Click to expand...
Click to collapse
What kind of machine are you using? xp/vista/7?
This sounds easy...I will try tonight using Streakdroid guide...good to hear from someone doing this with a White Dell Streak and being successful.
I have read that others have flashed the 2.2 *.pkg with success. The QDL installs dell's 2.2 during its process. I stopped there and have had no issues othe than the APN. Now that I think about it, I think that the QDL 2.2 is meant only to write over the device itself with out any of the specific carrier bloatware. And because of that it did not know what APN to the use until I re-registered.
At any rate, I think this link may help you out:
http://www.streaksmart.com/2010/11/how-to-get-official-android-22-update-on-dell-streak.html
Let me know.
sukemecuke said:
I was wondering if you had to do the command line portion prior to installing the ADB drivers. Going to give that a go. Wish I could just get it to work with the XP machine, but I can't get it to recognize in the device manager that it's plugged in without turning the device on. It makes the sound as if it realizes a device is connected, but nothing ever shows up in the device manager. grrrrrrrrr
Click to expand...
Click to collapse
I did do the command line portion before the ADB install. But that portion is meant for the 64-bit win 7. what happened when you tried it on win 7?
the streakdroid guide:
http://streakdroid.com/?page_id=92
jeremyritzmann said:
What kind of machine are you using? xp/vista/7?
Click to expand...
Click to collapse
using the W7 64bit machine. This is where I am at.....at about 8 hours in at this point. I've pretty much given up for today though.
Just copied and pasted from another forum:
Ok so I have the option of 2 machines to try this on.........and I'm going on about 7 hours with no luck with either of them. One is a hella old laptop with Windows XP on it. The other is a newish laptop with 64 bit W7 on it. I originally tried it with the XP machine. I can get the drivers DLed and installed successfully on the XP machine, on the W7 machine is immediately says failed when I try an install. I should preface this with saying that I previously had the Dell PC suite installed on the W7 machine using a different version than what's listed in the streakdroid guide. Then onto plugging in the phone on the XP machine if I do that battery out the volume up/down method it makes the sound as if something is plugged in, however it isn't visible in device manager. Not that is matters since I can't even get the drivers installed on the W7 machine, but it's the same. Makes sound as if something is plugged in, but nothing under device manager. When going through the guides it say's it should fail on install when hooking up the device for the first time........wel nope not on either machine. It installs it correctly as a mass USB storage device. Dammit.
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Hello community,
I have been trying for 8 hours (5 last night and three so far today) to get this to work but have failed utterly each and every time. I own the Samsung Galaxy Tab 10.1 (the Verizon 4G LTE model), and I'd like to revert back to the stock Honeycomb 3.1 that came with my tablet when I first purchased it from my local Verizon Wireless store.
I've followed this guide as closely as my understanding of it allowed me to (http://forum.xda-developers.com/showthread.php?t=1171089), and I also followed the video linked to in that topic (http://www.youtube.com/watch?v=krQDP7xYlWg) but I was not able to get Odin to work properly. After trying this on three different computers, I was able to get the third computer to recognize my tablet plugged in via USB and the yellow "COM4" box appeared in Odin, but when I clicked "Start" in Odin, it went all the way up to "Setup Connection" and then sat there for at least 10 minutes, showing no signs of a connection having been established. I've installed the Samsung USB drivers from both the topic linked to previously and from the video linked to previously (uninstalling one before trying to install the other, of course), and my tablet is recognized by the computer, yet Odin still stalls at "Setup Connection". I have not been able to push past this first step to rooting my device in order to revert back to stock Honeycomb 3.1, and this is very frustrating. I did have Download Mode open and the terminal that appeared on my tablet did say "Connected to USB, click [Start] in Odin" (or something to that effect). For what it's worth, all three computers I've tried this on were running Windows 7 64-bit (Ultimate and Professional editions).
Please, if anyone could help me, I'd greatly appreciate it. Also, once this is all sorted out, I am not exactly sure how to proceed after getting Odin to push past "Setup Connection". I don't even know if I'm following the correct path to reverting my device back to stock Honeycomb 3.1... as I mentioned before, I am a complete and utter Android noob (just got this tablet for Christmas) and I need all of the assistance that I can receive.
Thanks again, community. Hopefully we can get this sorted out and I can get back to using my tablet soon.
Excellent news: I was able to accomplish my goal without any problems using this concise, yet effective, tutorial: http://forum.xda-developers.com/showthread.php?t=1342995
I successfully reverted my Samsung Galaxy Tab 10.1 (SCH-I905, Verizon 4G LTE model) back to stock Honeycomb 3.1, removing the TouchWiz UX update completely. It's as though I've just picked it up out of the box for the first time, and I am thrilled.
I realized that Windows 7 was creating some issues that was leading Odin to stall at "Setup Connection", so I tried it again in the Windows XP Mode VM on my machine and, after a couple of hours of tinkering and reinstalling Kies, it finally worked. Thanks to XDA for such great tutorials and developers! Hopefully this topic will help others in my shoes in the future.
http://pastebin.com/4NnjMHT4
Okay so I have finally come to a point where I am going to need some help On my journey to root this phone, which is my first time rooting a verizon phone, i have learned that verizon is a *****. This phone is the GN2 VRAM3 SCH-i605. I have already flashed the keis update for this back to 03/29/.2013. I basically followed the guide, and have just been effin around doing things a bit differently everytime because it usually fails right away. I have been using zadig from heimdall to replace drivers, I have a windows 8.1 computer with the full Android sdk installed, obv with adb and fastboot, and i also have a windows 7 pc with the sdk tools installed and zadig and all that stuff. I have been trying to use casual, and this bad boy has been fighting me the whole way, This is the furthest I have gotten and was wondering if anybody had any other suggestions for me to get this guy to run through successfully. Thank you very much in advance.
Hey everyone.
I'm running into a really annoying issue. I picked up the T-Mobile GS5 a couple weeks ago and rooted it shortly thereafter. That is the only mod I've done, but it obviously blocks OTA updates.
With the new (NE6) update stable, I want to upgrade, so am trying to use Kies. Unfortunately, I can't get it to work. Everytime I try, I get the "new firmware available" alert, but when I attempt to proceed, Kies just freezes. I've tried not using the auto-update and selecting "Firmware Upgrade" manually, but no difference.
I was originally trying on an XP virtual machine (VMWare Workstation under Linux), and thought maybe that was the issue so tried under a Windows 7 VM. Same issue. So I tried the Mac version of Kies on my MBP. This time, I got to the screen where you need to check off that you agree to the update terms, but when it begins to download, Kies loses connection to the phone and it eventually errors out. So I tried a Win7 bootcamp attempt, but same general Windows failure. So I tried a baremetal (on PC hardware) Windows 7 attempt, and I'm sitting here at a slightly grayed out Kies screen that is unresponsive. In each method above, I tried numerous times with reboots of the computer and phone.
I searched, but couldn't find any similar issues. Based on the number of attempts on different computer scenarios, I have to believe it's an issue with my phone, but outside of this it works great. I've tried disabling developer mode, rebooting numerous times (phone and computer), etc. etc.
Does anyone have any idea what could be wrong? I consider myself fairly adept at Android and have a lot of custom experience with Nexus devices, but am not super familiar with the intricacies of Samsung products.
I used the Odin root method, and see there are firmware packages to upgrade that way, but believe it would factory reset my device - correct?
Any help would be greatly appreciated.
Thanks.
I read that sometimes having an external SD card can cause issues. Just tried removing that since I did have one installed. No difference.
try right click and run it as administrator with Kies see it work or not, also download the NE6 firmware files from sammobile and use odin to flash it, it wont factory reset yr phone, only thing u will lose is root but it can re-root with same step u did before.
koolboyztn said:
try right click and run it as administrator with Kies see it work or not, also download the NE6 firmware files from sammobile and use odin to flash it, it wont factory reset yr phone, only thing u will lose is root but it can re-root with same step u did before.
Click to expand...
Click to collapse
Thanks, I did try that too but no difference. For some reason, my phone seems to be incompatible with Kies.
After a lot of frustration, last night I did manually upgrade using Odin and the firmware files in the stock zip thread over in the dev section here. Initially, I only did the 'firmware' upgrade, since it seemed that the 'full' package would wipe the device (based on the comments in that thread), but that actually caused a lot of issues (fingerprint reader stopped working, etc.). So I was forced to use the full one, and it worked without wiping my device, which I'm quite happy about.
I did lose root, but for now I'm good. I mainly wanted it to restore from TiBu, but haven't needed root since, so I'll leave it stock and try the next OTA update.
I'm just more concerned about why Kies failed on 5 different machines (virtual or physical).