Related
I think I bricked my Viewsonic G Tablet. I was running VEGAN perfectly then I decided to jack around with Ubuntu the Karmic link found here on XDA under "Ubuntu on G tablet" Did everything the best I could, failed, failed.. booted into clockwork, went to factory reset, no back up found anywhere, formatted EVERYTHING (data, cache, rom) If I plug the USB cable into my laptop it reads as H drive but when I click on H drive it says "please insert a disk in H:" if I put anything on the sd external, I can't get my tablet to even read the external. Every time I click on "mount SD ext" it just says failed. Without clockwork, I just get big red letters "Magic value mismatch" Please tell me I didn't brick it good...
I can get the roms or the zip files etc on the external SD but without being able to boot to or from it, I'm lost.
Thanks
http://forum.xda-developers.com/showthread.php?t=861950
Start there. If you need more help search for "nvflash" and you'll find lots of helpful posts.
Thank you for your quick reply! I am afraid to say that I am SOOOO ignorant on this stuff. I followed the link and it had a lot of information on running the nvflash (I think when you didn't have clockwork installed??) It said stuff about lots of stuff I don't understand, I am SO SORRY to be so basic. I do run Linux Ubuntu 10.10 and Windows 7 on a dual boot with my machine so we can work in either environment. I donwloaded the prereqs from the drop box so I have the files along with two different ROMs, but I can't get the Viewsonic tab to even recognize (via my laptop) the internal SD card. Then the External SD card either so I do not know of a way to get any of these files to the tablet?
Please continue to help me in the MOST basic way you can, if you will. I would be so VERY grateful and give kudos, thanks, or whatever needed. I just want to make it work.
If you are able to boot into recovery then go to advance, then select the option to partition your sd card then select 2048 then 0. See if that helps to get your internal sd card recognized. That has helped me before.
Just an idea. No guarantees it will work.
Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.
THANK YOU THANK YOU A MILLION times thank you! I can donate to you or XDA via paypal, please let me know how to repay you all! You are wonderful!
No problem. Here to help when I can. If you really feel the need then donate to roebeet (the author of the original instructions).
Have a great day.
K J Rad said:
Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.
Click to expand...
Click to collapse
THANK YOU!!!!! Man, I thought I had a $400 brick on my hands! I couldn't even boot into recovery! I'll donate to whoever I need to at this point!
These machines are incredibly hard to brick. I've tried ;-)
If you'd like to donate pick one of worthy developers from the GTablet Android Development section and support their work. I use Roebeet's TnT Lite and those instructions above were first written and posted by him as well, so...
Glad you got it working. Have a great day!
I can not figure out what the hell I am doing wrong here.
I downloaded the naked driver pack on the guide page labeled 'Drivers TF700: Windows (Patched Universal Naked Driver)'. I unzipped the folder and plugged my TF700 into my computer. I then opened up the Device Manager and clicked on 'Asus Android Devices', then right clicked on 'Asus Android Composite ADB Interface' and pressed uninstall. I checked the 'delete the driver software for this device' and pressed OK.
The drivers uninstalled successfully and I turned off my WiFi card. I then unplugged and re-plugged my TF700 and navigated to 'Other Devices' in the Device Manager. I right clicked on 'Asus Android Composite ADB Interface' and clicked 'update driver software...' and then on 'browse my computer for driver software'.
I then navigated to the folder that I unzipped the driver pack to and tried to install them (clicking the 'include sub-folders' option). No go, I got the error message 'Windows was unable to find the driver software for your device' or something very similar. I then tried specifically pointing to both the i386 and amd64 sub-folders just to see if that wouldn't work somehow but I got the same error message.
What am I doing wrong? I am using a Lenovo G550 (I think) 32-bit laptop running Windows 7. My TF700 is rooted and unlocked but not much else has been done to it.
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
diablodow said:
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
Click to expand...
Click to collapse
That step isn't till later
@OP - let it update the drivers form Windows. That should be fine. As long as you can see the device and it has no errors or warnings around it. you only need the specific drivers when you get to the APX mode, then it will find them.
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
MartyHulskemper said:
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
Click to expand...
Click to collapse
This.
I had big time problems as well with installing these correctly. You need to reboot after uninstalling all old drivers. 1) Hook up Infinity in Android Debug mode 2) uninstall/delete old drivers like you did 3) reboot PC 4) Plug in Infinity again in Android Debug mode 5) install drivers manually through hardware wizard (use have disk option)
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
SOTK said:
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify this? What do you mean by 'repeat this for fastboot mode'?
Sent from my unlocked Transformer Infinity
Still no luck. I uninstalled 'ASUS ABD Interface', unplugged the TF700, restarted the computer, plugged the tablet back in, and tried to uninstall. Told me the same thing, that Windows could not find the driver software.
Any other ideas? I have no clue what to do now...
Sent from my unlocked Transformer Infinity
I_EAT_BABIES said:
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Click to expand...
Click to collapse
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Eddie Hicks said:
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Click to expand...
Click to collapse
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Pretoriano80 said:
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
Click to expand...
Click to collapse
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Eddie Hicks said:
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Click to expand...
Click to collapse
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
buhohitr said:
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
Click to expand...
Click to collapse
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Pretoriano80 said:
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Click to expand...
Click to collapse
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Pretoriano80 said:
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Click to expand...
Click to collapse
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
buhohitr said:
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
Click to expand...
Click to collapse
So I see you are trolling this thread too... 98%??? Really??? Can you give a source for that or is that a number you just made up?
NVFlash is useless if you have not already made the backups. But you are completely incorrect if you are suggesting that it is useless even if you have made the backups.
Best not to troll when you clearly do not understand what you are talking about
I_EAT_BABIES said:
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Click to expand...
Click to collapse
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Damn,i can't believe this....When you get to this step " 4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK ... " look on the right bottom of that menu,do you see a "Have Disk" button?.
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Here is a screen capture from my system. Look in the lower right for the HAVE DISK button. Following the directions giving earlier should get you to this point. Just click HAVE DISK and guide to where you have the drivers on your system. You may not see the list of drivers as on the screen capture the first time you do it. Since I have already installed the drivers the system remembered where to look so the drivers are visible. Also make sure to connect your tablet to your computer in order for the device to be visible in device manager. The device in device manager should say android ABD Interface or something of that sort. It took me awhile to get it too
****edit***
Apparently the link opens another page.Once on that page click the little box for the image.
https://www.dropbox.com/s/ykuv2ac6zxdln7i/driver_update.JPG
As of the time of this reply I have got the Fasboot drivers installed, but I still saw now "have disk" option. After turning UAC off (don't know how that got back on) I was still just selecting a folder as shown in my previous screenshot.
About to try APX, will post results.
Got it! Thank you guys so much, I really appreciate it. This was seriously driving me crazy, but I still don't understand how we are looking at different menus.
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
ericdg said:
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
Click to expand...
Click to collapse
ADBSetup will get you the drivers you are looking for:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Worked for any Android phone I tried.
Thanks, I'll give that a shot and see what happens!
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
ericdg said:
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
Click to expand...
Click to collapse
Easiest way to tell is open up a command prompt in the folder that adbsetup installed to (C:\ADB I think) and type:
Code:
adb devices
If all is well, then the device will be part of the listing.
Thanks Joel.............I think it worked.
The ADB command came back with:
List of devices attached
HT22_______7 device
That's not a number that I've ever seen associated with my phone, but I assume that's it.
Confirmed.................I was able to reboot the phone by ADB!
Excellent! This will also mean the fastboot commands needed to unlock your bootloader will work too.
.........one would think so, Joel, but I can't get fastboot to do anything. ADB recognizes the phone, and will reboot into bootlocker, but once there it'll do nothing. Windows pops up a message shortly after bootlocker opens that says something to the effect of "there was a problem with USB device not recognized". I tried the command "fastboot devices", but got nothing. I know that I'm darned close, and it's probably something simple, but just can't get it to work. Maybe I need additional drivers for fastboot, or need to move it to another directory?
Thanks,
~E
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
joel.maxuel said:
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
Click to expand...
Click to collapse
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
ericdg said:
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
Click to expand...
Click to collapse
Dont know where you got your HTC drivers, but you should try the ones in this post (step one - hopefully its still live - if not I can dropbox it for you):
http://forum.xda-developers.com/showthread.php?t=1801106
Sent from my LG-D520 using XDA Free mobile app
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
ericdg said:
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
Click to expand...
Click to collapse
Uh-oh. Either the link was dead when I went through this process back in April, or I had bad organizing skills at one point and didn't put the file in the Doubleshot folder before completing a purge. Either way, I don;t have the file.
Nor did I really need it. The second Doubleshot I rooted I ended up using it in my native Linux environment (no drivers needed), vs my Windows XP emulated through VirtualBox. That's what you could do. Get a live Debian DVD (Im like the XFCE desktop version), boot in, get fastboot:
Code:
sudo apt-get install fastboot
And then use fastboot:
Code:
sudo fastboot ...
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
ericdg said:
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
Click to expand...
Click to collapse
Just need the one. My recommended file to download is this:
http://cdimage.debian.org/debian-cd...ybrid/debian-live-7.6.0-i386-xfce-desktop.iso
Burn the image (not the file) onto a DVD (can be a rewritable) and reboot with the disc in the drive. Once it's fully loaded, you can either enter commands by clicking on the "terminal" icon on the bottom of the screen (preferred), or press Ctrl + Alt + F1 to get a prompt (may have to log in as "user", there shouldn't be a password). Hope this helps.
Welcome to my tutorial !
You can find others tutorials related to the Cube i6 :
Update your EFI BIOS
Install Android 4.4.4 (Stock & RemixOS)
Disclamer: This process might contain ROM hacking, this is for advanced users.
Software included may be subject to copyright.
Flash your device at your own risk. Developer is not responsible for what you do on your device.
What you need:
Cube i6 Air (3G or Wifi)
2 Flash Drives (1Gb or more, and 4Gb or more)
OTG cable
USB Hub (3 Ports recommended)
WinPE for Win10 (Downloadable on my drive)
Win10 32 bits ISO (link in tutorial)
THIS IS THE LINK I'M REFFERING TO WHEN SAYING "THE DRIVE"
https://drive.google.com/folderview?id=0B8YPw4HjmqNCZktOZy1OTEN2ZVE&usp=sharing
What to do :
1.) Start by plugging the first usb drive (1Gb or more) into your computer, and format it to FAT32 using any formatting tool,
MAKE SURE YOU CHANGE PARTITION TABLE STYLE TO GPT, EITHER YOU WILL END UP WITH ERROR ON WINPE INSTALL
2.) Now you need to download WinPE from the drive, go to your device folder, then go into the windows folder, and download it.
Once you downloaded it, uncompress. You will find a "WinPE_XX" folder inside, take all of its content, and extract it to your freshly formatted drive.
Heres what looks like the root of your key:
3.) Your USB Install Drive is ready. You can plug it off and save it for later.
You now need to download a 32Bits ISO version of windows, if you already have one, it should work, if you don't, you can download it from Microsoft Website
4.) Now take your downloaded ISO, and mount it with either windows, daemon tools, PowerISO, or any Disk Image Manager.
Once mounted, you need to navigate to the X:\sources\ folder, and extract "Install.wim" anywhere on your PC. Thats the windows system we will install.
5.) Go to the drive, into your device folder, go to windows folder, and download the "Image_Recovery_Extra.zip" you can find there.
It contains recovery + Files mandatory for install (because the Windows PE we're using is hacked from Cube).
6.) Take your second USB Drive (of 4Go minimum, it needs to hold windows), and format it to NTFS Filesystem with any formatting tool.
Now you can extract the "images" folder of the previously "Image_Recovery_Extra.zip" downloaded (KEEP THE IMAGES FOLDER THIS TIME)
And also copy inside that "images" folder your previously extracted Install.wim image file.
7.) You're good to go ! You can unplug the keys from your PC, and start working on the tablet as of now !
You need to boot to BIOS settings, using "ESC" key at startup of tablet. Once there, go to SCU Settings, the bottom right square.
You need to set your primary boot to "Windows" in the boot tab, or the key won't boot. If it is already, you can exit SCU and start step 8.
If it is not, just select it, then press F10. Tablet should reboot. Press ESC again at startup, and start step 8.
8.) Now everything is straightforward: Just select "Boot from EFI File", select your USB key in the list, and go to EFI folder, then go inside BOOT folder, and select "Bootia32.efi"
The tablet should boot to a command prompt (it lags much, but we will install drivers later) and it should install windows automatically then shut down.
If install fails, update your BIOS and try again or post here for some help.
Preparation looks like this:
Working device looks like this:
9.) Now you can get rid of the installation USB keys, you only need mouse and keyboard. Fire up your tablet freshly flashed, it should boot to a chinese logo with a circle under it. it might reboot a few times, it is actually expanding filesystem and populating your win10 install. Wait until you end up in language screen. if it shuts down, put it on again if it does not automatically.
10.) Windows is ready, now follow the instructions, language, set your name, until you end up on the windows desktop. When you are here, you need to download from the drive the Driver Package for windows 10, which is located inside the driver folder, inside the windows folder of your devices folder. It sould be named "Z37XX_CPU_Chipset.zip"
Extract it on the tablet, and run the included "Setup.exe". When finished, reboot your tablet.
you can also find various driver i added for os switch and gyrometer
Congrats! You successfully Installed Windows 10!
I do not guarantee it works on every device, nor with every windows version, but it works in my installation with a regular Win10 x86 Pro.
There might be some upgrades to do, as I personnally hacked the WinPE that is available on Cube's site, with Windows 10 ADK WinPE,
so feel free to report bugs, enhancements to this method. and report cube for not doing this so far !!!
Regards,
Max.
Top! Thank you!
I had exactly the same issue and want to fix it this weekend. My I6 arrived on Thursday. Now I follow your instructions to update to Windows 10.
Hi, glad it is helping! tell me if you are having issues, or if some steps aren't detailed! i'll upload some photos later. if you need something for this tablet feel free to ask
regards
stalker2106 said:
Hi, glad it is helping! tell me if you are having issues, or if some steps aren't detailed! i'll upload some photos later. if you need something for this tablet feel free to ask
regards
Click to expand...
Click to collapse
Hey Max,
now I have the first problem.
On my Windows 10 Image I do not have any install.wim file. There is only a install.esd (about 2GB) file in the \sources\ folder. But this file is not possible to extract with 7zip. The only *.wim file in the directory is the boot.wim. What have I to do?
scharrrfi said:
Hey Max,
now I have the first problem.
On my Windows 10 Image I do not have any install.wim file. There is only a install.esd (about 2GB) file in the \sources\ folder. But this file is not possible to extract with 7zip. The only *.wim file in the directory is the boot.wim. What have I to do?
Click to expand...
Click to collapse
Alright, i don't know what ISO of windows 10 you have, but i found a tutorial on how to convert esd to WIM, so no worries (http://www.intowindows.com/how-to-easily-convert-install-esd-to-install-wim/) furthermore, i would recommend using PowerISO for extracting the file, as i'm not aware of how to extract from ISO with 7zip
Okay, thank you. With this it works
But I have some error when I boot the WinPE on step 8. I get the message: "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f""
On this point the tablet do not recognize any keyboard command.
scharrrfi said:
Okay, thank you. With this it works
But I have some error when I boot the WinPE on step 8. I get the message: "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f""
On this point the tablet do not recognize any keyboard command.
Click to expand...
Click to collapse
What is that \EFI\Microsoft\Boot\BCD you are trying to boot from ?
You should select \EFI\Boot\bootia32.efi. If it does not work make sure your BIOS is at version 206 (its my case, so i guess it can be this) and if not, upgrade it with the provided tutorial, maybe you'll have more luck with that ? You can check its version on android by going to device info in settings and check IFW Version.
EDIT: The WinPE media might be trying to access your hard drive EFI folder to use its BCD configuration, check that too, maybe you can format that EFI partition before booting to winpe ?*
EDIT2: Check BCD integrity maybe, 262 144 bits is what it weights on my side
stalker2106 said:
What is that \EFI\Microsoft\Boot\BCD you are trying to boot from ?
You should select \EFI\Boot\bootia32.efi. If it does not work make sure your BIOS is at version 206 (its my case, so i guess it can be this) and if not, upgrade it with the provided tutorial, maybe you'll have more luck with that ? You can check its version on android by going to device info in settings and check IFW Version.
EDIT: The WinPE media might be trying to access your hard drive EFI folder to use its BCD configuration, check that too, maybe you can format that EFI partition before booting to winpe ?*
EDIT2: Check BCD integrity maybe, 262 144 bits is what it weights on my side
Click to expand...
Click to collapse
I do not know, why it says \EFI\Microsoft\Boot\BCD. I selected the correct .efi-file.
But I think my tab is now gone. I have try the bios update from 203 to your 206. It have flash completed to 100% and turns the tablet off. I wait a few minutes and then I try to turn it on again for another try to install Windows 10. But it will not turn on again. It does also not recognize the charger anymore. I think I brick the i6 with the 206 Bios. What a bother!
scharrrfi said:
I do not know, why it says \EFI\Microsoft\Boot\BCD. I selected the correct .efi-file.
But I think my tab is now gone. I have try the bios update from 203 to your 206. It have flash completed to 100% and turns the tablet off. I wait a few minutes and then I try to turn it on again for another try to install Windows 10. But it will not turn on again. It does also not recognize the charger anymore. I think I brick the i6 with the 206 Bios. What a bother!
Click to expand...
Click to collapse
Ok, if the process went 100%, then there is a high probability it is not bricked.
Remember that still, you can boot using DnX mode holding power and volume +.
What do you mean by "it does not recognize the charger" ? when you plug it, the charging led does not light up ?
Thats very odd. because its not controlled by bios but only hardware derivation I guess.
please keep me tuned in on that !!
Edit: FYI I used the exact same BIOS on my model, which is a i632GB15378650186.
stalker2106 said:
Ok, if the process went 100%, then there is a high probability it is not bricked.
Remember that still, you can boot using DnX mode holding power and volume +.
What do you mean by "it does not recognize the charger" ? when you plug it, the charging led does not light up ?
Thats very odd. because its not controlled by bios but only hardware derivation I guess.
please keep me tuned in on that !!
Edit: FYI I used the exact same BIOS on my model, which is a i632GB15378650186.
Click to expand...
Click to collapse
DnX mode does also not work. And yes i mean, that the LED does not light up at all.
My model is i632GB15224920293. I think it is an older one.
scharrrfi said:
DnX mode does also not work. And yes i mean, that the LED does not light up at all.
My model is i632GB15224920290. I think it is an older one.
Click to expand...
Click to collapse
Wow. You mean there are older model with other BIOS System ?
I'm so unhappy to hear your story. I hope i can help to fix it !
Whatsoever, how can any BIOS accept flashing itself if its not corresponding ?
Good thing you point out there, but c'mon, how can your tablet be bricked if the process went OK...
Maybe you can contact cube about it ? Maybe if you hold power long enough it will turn off ?
Once the tablet did this to me, had to hold power 10s to get it back off !
EDIT: good thing I remember is that i had it shipped with 205 BIOS, so i guess you're right and its an older model you have. Still, I have spare BIOS Firmware 204 that I flashed for testing purposes that also worked flawlessly !
EDIT2: found that there might be tons of differents models like raspberry pi, look this one does not match with any of ours : http://winphonetech.com/wp-content/uploads/2015/08/cube.jpg or maybe it is just a serial number generated from the # produced or the current date of prod ?
stalker2106 said:
Wow. You mean there are older model with other BIOS System ?
I'm so unhappy to hear your story. I hope i can help to fix it !
Whatsoever, how can any BIOS accept flashing itself if its not corresponding ?
Good thing you point out there, but c'mon, how can your tablet be bricked if the process went OK...
Maybe you can contact cube about it ? Maybe if you hold power long enough it will turn off ?
Once the tablet did this to me, had to hold power 10s to get it back off !
EDIT: good thing I remember is that i had it shipped with 205 BIOS, so i guess you're right and its an older model you have. Still, I have spare BIOS Firmware 204 that I flashed for testing purposes that also worked flawlessly !
EDIT2: found that there might be tons of differents models like raspberry pi, look this one does not match with any of ours : http://winphonetech.com/wp-content/uploads/2015/08/cube.jpg or maybe it is just a serial number generated from the # produced or the current date of prod ?
Click to expand...
Click to collapse
Yes, I think you are right, that the last numbers are any kind of a serial number. Do you have another Bios file? On the web I found only the 201. I can try to buy an ISP programmer and reflash the tablet.
And I have tried different buttons combinations on hold in hope that the tablet wake up again. But still nothing
scharrrfi said:
Yes, I think you are right, that the last numbers are any kind of a serial number. Do you have another Bios file? On the web I found only the 201. I can try to buy an ISP programmer and reflash the tablet.
And I have tried different buttons combinations on hold in hope that the tablet wake up again. But still nothing
Click to expand...
Click to collapse
Thats some freaking bad news ...
I uploaded 204 BIOS to the drive... cheers, fingers crossed.
It's a great news that the I6 Air is possible to upgrade to Win10 now. But before taking action, I have one question to clarify. After the upgrading, is the Android system still there and can switch over freely as before?
dahuzi said:
It's a great news that the I6 Air is possible to upgrade to Win10 now. But before taking action, I have one question to clarify. After the upgrading, is the Android system still there and can switch over freely as before?
Click to expand...
Click to collapse
Yeah, windows fill the partition space that is already configured, it means even if you resized your android to a 8 Gigs partition, the windows will not erase it !
For the switching process, it is even better because YOU install the switcher, and configure it the way you want (dektop shortcut, taskbar button, ...)
I can bring windows screenshots on purpose if needed
regards,
Stalker2106.
stalker2106 said:
Yeah, windows fill the partition space that is already configured, it means even if you resized your android to a 8 Gigs partition, the windows will not erase it !
For the switching process, it is even better because YOU install the switcher, and configure it the way you want (dektop shortcut, taskbar button, ...)
I can bring windows screenshots on purpose if needed
regards,
Stalker2106.
Click to expand...
Click to collapse
Thanks for clarification, another question, how about the system activation? Will the system become activated automatically?
And moreover, the drive folder you provided has no more WinPE available. Please check.
Thanks again.
dahuzi said:
Thanks for clarification, another question, how about the system activation? Will the system become activated automatically?
And moreover, the drive folder you provided has no more WinPE available. Please check.
Thanks again.
Click to expand...
Click to collapse
Hi, bad manipulation yesterday led me to delete archive from drive, but its uploading again !
I tried again the tutorial because of the problem of " scharrrfi" to check if its not broken in any manner, and it worked flawlessly !
Furthermore, the system is yours, and therefore, is not activated by default, it asks for a serial key !
Files should be on the drive later today
EDIT: The files are up on the cloud !
Now I wait for my ISP programmer. But I know, why I get first the message "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f"". I found the solution in another forum. There was a problem with the formatting of my USB stick. I have to format it with an partitioning tool to GPT. And then it should work.
If I know this before, I have not to try to flash the bios...
scharrrfi said:
Now I wait for my ISP programmer. But I know, why I get first the message "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f"". I found the solution in another forum. There was a problem with the formatting of my USB stick. I have to format it with an partitioning tool to GPT. And then it should work.
If I know this before, I have not to try to flash the bios...
Click to expand...
Click to collapse
Yeah, I admit that was kind of my fault telling you that upgrading your bios would change anything in your boot configuration, i'm so sorry
Let's hope this will work, still hope, windows 10 will make its way to your tablet no worries !
After some days of using it i report some glitches though:
Orientation sometimes get rekt, i dont know why but you have to set it manually...
Also the tablet is not as responsive as it is on android, but I guess power consumption is higher on windows, as it heats much more !
Sometimes i touch the part near the lens and it feels really hot !
Btw when on low battery, the power saver settings got me doubling my battery time, which is nice !
And on idle, locked, the battery charge way faster than on android.
Hi I have an other error - if I boot with the bootia file I got short 4 error messages: UEFILINUX ERROR [uefi_get_battery_status:121] Failed to get battery status - und error 160, 121 again and 149, all error with the battery. I haved update the firmware from 201 to 206. The battery is over 90% full in windows. Have you an idea whats wrong?
I have a ZTE tablet model K90U, Android version 6.0.1. I tried Kingoroot and it failed. I next tried iRoot and the tablet keep blocking iRoot. Saying the prog maybe infected or corrupted. I have been looking for info to root this tablet without luck. I know from having successfully rooting at lease 4 phones, 2 tablets and hard bricking 1 phone. That I know the right setup has to be used or else, and I don't need the "or else". So what do I use to root this tablet? I am lost. I have (and used) ADB and Fastboot if I can find the right cmd's for this tablet.
Steve
After days and days of searching the internet I finely found the right key file for the ZTE K90U tablet at www.opensource.ztedevice.com/ But I have 1 other small problem. Do to a clumsy mistake that I made while I was recombining 2 partitions back into 1 on a SD card for a tablet that I sold. I didn't pay attention to which drive letter I was on and I accidently deleted the partition on my D storage HD in the USB case were I store install prog's, info files like how to use prog's like fastboot and CWM. I am having to rebuild those instruction files. I think I found the right one for fastboot at http://forum.xda-developers.com/showthread.php?t=2277112 . But I am not 100% sure. I also not sure whether I should use fastboot or CWM to root the ZTE tablet.
Steve
reble1 said:
After days and days of searching the internet I finely found the right key file for the ZTE K90U tablet at www.opensource.ztedevice.com/ But I have 1 other small problem. Do to a clumsy mistake that I made while I was recombining 2 partitions back into 1 on a SD card for a tablet that I sold. I didn't pay attention to which drive letter I was on and I accidently deleted the partition on my D storage HD in the USB case were I store install prog's, info files like how to use prog's like fastboot and CWM. I am having to rebuild those instruction files. I think I found the right one for fastboot at http://forum.xda-developers.com/showthread.php?t=2277112 . But I am not 100% sure. I also not sure whether I should use fastboot or CWM to root the ZTE tablet.
Steve
Click to expand...
Click to collapse
Greetings and welcome to assist. I can find very little information at all on your device, if you have cm recovery for it then I would use that to flash the latest su zip to get root
Good Luck
Sawdoctor
I posted the wrong link. This is the right one http://opensource.ztedevice.com
Update:
I have found in the tablet's recovery mode (power + volume down) that this tablet doesn't have a normal menu. Instead of the "boot=download" or "boot to download{". This tablet has :
Apply update from abd
apply update from sd card
Under the "apply update from adb" is "now send the package you want to apply to the device with, adb sideload <filename>."
I have gotten as far as the cmd "adb devices" and reply back "list of devices attached, 21499c28 device".
Now if I do a "adb reboot bootloader" the tablet reboots normal mode then a box comes up saying "allow USB debugging and a box to check ok". I check ok, the box goes away and then after that nothing happens. If I type "fastboot boot bootload". The terminal window just sits there with the words on it "waiting for any device". And that's were I am stuck. What is "adb sideload"? I could use some help please.
Steve
Sawdoctor typed "Greetings and welcome to assist. I can find very little information at all on your device, if you have cm recovery for it then I would use that to flash the latest su zip to get root"
I found an article that explains what "sideloading" is http://www.wow.com/wiki/Sideloading But it doesn't help me as far as solving my problem.
Well I finely figured out the syntax of the cmd structure for this tablet. I now have the tablet talking to my laptop. Now I just need to find the right recovery-CWM image file for this tablet.
reble1 said:
Well I finely figured out the syntax of the cmd structure for this tablet. I now have the tablet talking to my laptop. Now I just need to find the right recovery-CWM image file for this tablet.
Click to expand...
Click to collapse
I can't find cwm for your tablet but have a guide to compile twrp if it helps
http://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good Luck
Sawdoctor
Thanks Sawdoctor for the link http://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024 I am going to give it a wack. I also have an advantage over someone trying this out of the gate cold turkey. I have written prog's in MSDOS Basic and Windows Visual Basic. It is not the same as Ubuntu and Android. But writing code is writing code. If you don't have all your ducks lined up in the right order and all your T's crossed and all your I's doted right the prog won't work.
sawdoctor said:
I can't find cwm for your tablet but have a guide to compile twrp if it helps
http://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good Luck
Sawdoctor
Click to expand...
Click to collapse