Like many of you, my S6000F was easily rooted; but, isn't cooperating with my attempts to unlock it.
I have been following the directions posted at Lenovo Ideatab S6000 Unlock Bootloader Tutorial (not allowed to post a link on xda); but, have hit a brick wall when trying to execute the command line: fastboot-windows oem unlock
I get one of two error messages:
1) If I am at the command line, and the tablet is in normal Android, it will say: Waiting on device
2) If I have the tablet in fastboot mode, it will say: fastboot is not recognized as an external or internal command
I have ensured that
ADT was fully installed and configured
the correct adb windows and adb drivers were installed (I have tried the Google drivers provided with the guide I lined to above; and, also tried the Universal Naked Drivers)
adb can 'see' the tablet, as can Windows (in device manager with the tablet in normal and fastboot modes)
I use an administrative command prompt window
adb, fastboot and sdk are all in the same folder; and, that I open an administrative command prompt in that same folder
I have honestly spent hours trying to find relevent info via Google and Bing; and, then researching in the forums that show up in the searches. All the steps that I bulleted above are the results of what I have found, piecemeal; but, I havn't been able to find one, complete lucid guide to this issue. Any solid direction would be greatly appreciated.
Thanks, in advance!
PJ Arts
Related
I been trying for days to get my HTC Flyer with Honeycomb rooted via the GUIDE but I am stuck at step 1.
"If you are not on an appropriate gingerbread version, eg. if you have upgraded to honeycomb then downgrade by using an appropriate RUU; to identify your RUU see: here"
(downgrade to Gingerbread) but I get stuck at the "Fastboot getvar cid" stage to find out which RUU I have. When I have the Flyer in Fastboot mode and connect the cable, I get an error when it trys to install the "Android 1.0" driver.
I have uninstalled, rebooted, reinstalled, repeatedly. I just tried another link that suggested to try installing PDANet for Android to get around this problem. Now when I run Fastboot, rather than just "waiting for connection", I get an error that says "getvar:cid FAILED (status malformed (1 bytes)) finished.
*** Update***
I just tried a different HP Laptop with Windows 7 installed & I had the exact same error regarding the Android 1.0 driver as soon as I plugged in the Flyer when it was in Fastboot mode. Is there some other setting other than Fastboot off I need to do on the Flyer itself? Any other suggestions would be GREATLY appreciated.
Please help!! I am at my wits end here.
thanks,
sPk
still need help
I am still struggling here.
By pointing the Android 1.0 driver installer to the PDANet directory, it found a ADB driver and installed it. But I still get the "malformed error" when I try to use "Fastboot getvar cid" command to find RUU version. Is there another way to get the RUU version??
I think the driver is communicating with the Flyer as I was able to get Flyer to respond to the serialno command.
I have OTA update and want to root/Rom with HBoot 1.11.00011.
If I can't get the RUU version, is there a most likely suspected RUU for a WiFi only Flyer that I just got from Buy.com for US market.
thanks in advance for your help.
sPk
You have the android sdk installed right?
Andriod SDK
Gumby63 said:
You have the android sdk installed right?
Click to expand...
Click to collapse
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
windsurfsail said:
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
Click to expand...
Click to collapse
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
SDK
Gumby63 said:
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
Click to expand...
Click to collapse
I was able to get the Android SDK & Java installed properly. I uninstalled the driver in the Device Manager and then pointed the driver install to Android SDK/Tools and it indicated that the driver was already installed. I tried Fastboot command for the zilllionth time and still got the same malformed error. So I uninstalled driver & deleted it this time and tried to re-install but now it doesn't find the driver files (because I deleted them). I can re-install SDK or just point it to the PDANet directory again.
Is the correct driver for Fastboot the the Android ADB? It is the only one I have been able to get to load when I plug in the Flyer in Fastboot mode.
thanks,
sPk
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
hboot & fastboot confusion
globatron said:
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
Click to expand...
Click to collapse
DOH!
Globatron, thanks for the clarification. In all my reading of threads, I never saw any definition of hboot & fastboot. Since it wasn't working, I installed the other drivers in an effort to fix what was apparently a driver issue.
Is "fastboot mode" just having the "Fast boot" box checked under the Power settings?
thanks again!
sPk
Fastboot mode
After searching in the forums for a while, I found a description on how to get into "fastboot mode". I have added below in case someone else is new enough not to know.
I ran the command & it finally worked. Being in the right mode was key.
sooo, I now have the cidnum= BS_US001 but looking through the list of the RUU's files, I still don't see any reference to this CID. Another stupid question: How do I find which of the list of 25 RUU files is correct for my WiFi Flyer?
UPDATE: Found out how to find RUU file from link.
http://forum.xda-developers.com/showpost.php?p=18508220&postcount=2
modelid: PG4140000 (Wifi Flyer)
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001
cidnum: HTC__055
sPk
----------------------------------------------------------
You need to be in fastboot mode. Two ways to get there.
Get into boot then select fastboot
Or
While booted in android connect to PC then enter "adb reboot bootloader" (assuming you know adb a little)
Once in fastboot you need to enter the commands in a cmd terminal on your PC just like adb
What I learned, that may help you...
I had a surprisingly difficult time getting my OTA Honeycomb US WiFi Flyer S-Off'ed, Rooted & uploading a new ROM. I did get it done but there were some basic things I should have known or done. Thanks to Globatron & all who post on this board.
1: Before you start, make sure your PC's drivers are 100% working. I had Windows driver problems that caused other problems. Make sure that your tablet is properly recognized by the PC when the tablet is in Fastboot/Hboot modes, and in regular Android mode.
2: I didn't understand the difference between Hboot & Fastboot. This small thing made all the difference and was one of my major issues. Because I had the tablet in Hboot not Fastboot, the Fastboot commands didn't work and I couldn't get my RUU version
3: Pay attention to the phone's settings. Especially USB Debug mode, Fastboot mode.
4: After I had finally downgraded to Gingerbread. I couldn't figure out why Revolutionary wouldn't recognize my tablet. The simple answer was when I had downgraded to Gingerbread, all my phone settings were back to stock also so I had go in and change the USB Debug and Fastboot modes. It would be helpful to add a reminder in the GUIDE to make sure that these settings are changed before running Revolutionary.
5: Not really related but I had a problem when I wanted to backup my newly Rooted/ROM'ed phone. I had previously purchased the Titanium Backup Pro and I installed it on the Flyer but it wasn't listed in the Apps menu but was listed in the Manage Apps. Because Google-Play/Android Marketplace only copied over the paid apps to my newly upgraded Flyer, it didn't copy the free version of Titanium Backup. You must load both the free version & the paid Pro version for it to work.
I hope this helps someone who runs into any of the same issues I had.
thanks,
sPk
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Vibestarter said:
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Click to expand...
Click to collapse
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
fastboot oem unlock Failed
The-Immortal said:
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
Click to expand...
Click to collapse
Hello, I tried your command suggestions to unlock the bootloader and they failed. The command 'fastboot oem-info' does not return anything and 'fastboot oem unlock' returns RESULT: FAIL (unkown OEM command) on the tablet and in the cmd window. Thanks for the suggested attempt nonetheless.
Still having this problem
fastboot oem unlock fails on the TF103C and it says RESULT:FAIL(unknown OEM command). It would be great if Asus could release a tf103c_unlock.apk utility like they have for other Asus tablets (for instance the TF701T has tf701_unlock.apk which works).
Asus, please help!
I have literally tried everything. Sony's website does NOT have driver for the XA2!!! What gives?
I'm trying to unlock the bootloader through flashtool but I keep getting this message "Device connected in flash mode but driver is too old".
I also tried the 15 Seconds ADB Installer thing, no luck.
I also tried following Sony's guide but get stuck at the bold part:
Turn off your device.
Connect a USB-cable to your computer.
On your device, press the Fastboot key (Volume up for most devices, see Useful key combinations) at the same time as you connect the other end of the USB-cable.
Windows users: When asked for a driver, open the Devices and Printers directory, click on the fastboot driver and press Update. Browse and point towards the location of the new android_winbus.inf file.
When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
Enter the following command:
fastboot devices
Verify that you get an answer back without any errors.
I don't have the option to open a CMD, but only powershell, and powershell doesn't let me run the "fastboot devices" command properly. Keeps trying to open an application.
What else can I do? I found some driver online and tried to install it through "legacy" mode in device manager but I keep getting some kind of error.
Can someone please help me out? I really want to root this thing
Thanks!
Anyone?
Wow! I came here looking for an answer to the same question and nothing but crickets? Sony does not list a driver for this device and I find it odd. Does it use the XA driver? You would think they would be listed together if it did. Nobody has an answer on this?
I found out you use the XZ2 driver. Worked for me.
I was attempting to flash lineageOS from https://forum.xda-developers.com/mi-pad/development/lineageos-16-0-07-12-2019-shield-blobs-t4015965. Keep in mind my firmware knowledge was less than ideal so when I got to step 5 which was "5) execute command: fastboot flash tos your path to tos.img", I copied it word for word into fastboot and obviously it didn't do anything (I didn't understand the "your path to" portion was supposed to be the file directory then) I then searched the internet trying to look for a solution, thinking I had missed a step. I came across this article https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/ and got up to step five where I executed the "fastboot oem unlock" command and unlocked my mipad's bootloader I couldn't understand the next few steps so I gave up on this set of instructions. When I reattempted to use fastboot after figuring out what "your path to" meant on the first set of instructions, my device couldn't be detected through executing "fastboot devices", my computer's device manager, or MiFlash even though all ADB drivers were initially installed and I even installed it again just to be safe. How do I get my computer to detect my mipad again? Note: my mipad is now rebooting straight to fastboot
TLDR: unlocked mipad 1 bootloader using fastboot, mipad no longer detected by computer and only reboots to fastboot. How to get mipad detected by computer
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!