Ok, I am COMPLETELY lost and have read this forum here from start to finish and still have no idea how to fix my Kindle Fire.
http://forum.xda-developers.com/showthread.php?t=1428428
My KF is stuck at the "Kindle Fire" screen, not the triangle screen, or any other screen. I can shut it "off" and turn it "on" but it never gets past that screen. I have installed and tried to run "the Kindle Fire Unbrick Utility V1.1" and it always always always gets to the "waiting on device" part. I don't understand how to download or install new drivers or anything of that nature.
If someone could please give me a step by step guide on how to fix my problem that would save me a lot (more) hours of search and failure. I just want it back to normal (un-rooted) and I never should have rooted it in the first place. That was a HUGE mistake from someone who doesn't completely understand this stuff. Any help is greatly appreciated.
Bumpity bump bump.
Did you install the drivers using the kfu? Is your kindle showing up in device manager on your computer?
Sent from my SPH-D710 using xda premium
First thing....scrap the KFU. It's time to learn to use command line tools.
Plug your device into the computer, turned off.
Locate the folder that comes with KFU that has the files called "adb" and "fastboot" and place it on your desktop.
Open your command prompt and type:
cd Desktop/NameofFolderYouPlacedOnDesktop
Turn on your Kindle
In your command prompt type:
fastboot devices
If you see a bunch of numbers move on. If not, reinstall drivers and try again.
Then type:
fastboot -i0x1949 oem idme 4000
Hold down power button until device shuts off
It should restart normally
Then see this thread to find out why you did that:
http://forum.xda-developers.com/showthread.php?p=24039339
Sent from my Kindle Fire using xda premium
Let me know how it works out.
[EDIT:] The cool thing about the Kindle Fire is that its virtually unbrickable, short of screwing up the bootloader...which you didn't. So don't worry, its fixable.
If it works out for you and you want to re-root it, I can help you out so you don't get left in the dark. You might even learn something.
Sent from my Kindle Fire using xda premium
Thank you for the reply and assistance in this problem. I am stuck in the middle of the process. Maybe I am doing something wrong. My exact steps I am taking are listed below. To get into the command prompt I type into the "run" section of my computer "cmd" and then it opens up the command prompt.
-Plugged my KF into the desktop turned off
-Drag the entire folder called "tools" from the KU onto the desktop which has the "adb" and "fastboot" files.
-typed in "cd Desktop/tools" and now it shows this on the cmd C:\Users\myname\Desktop\tools>
-I then turn on my KF and type in "fastboot devices"
nothing shows up except C:\Users\myname\Desktop\tools>
-If I just type "fastboot" I get a whole explanation of commands I can input, but no numbers.
-To uninstall my driver and try agian I do the following: go to "device manager" and find my KF which is shown by an exclamation mark. Right click and "Uninstall" Rinse and repeat.
Should I be doing something differently? Thank you again for the help!
No, that's exactly what you should do. You need to get fastboot to connect. In order to do that your drivers need to be working.
Sent from my Kindle Fire using xda premium
Ok, should I just keep uninstalling and reinstalling the drivers until it works or is there another way to fix the driver problem?
When installing your drivers, did you make sure to choose "I'll select which drivers to install"?
Sent from my Kindle Fire using xda premium
I am clicking on the "install drivers" from the KF utility and then uninstalling from the "device manager" Guess there's more to this driver thing that I'm even more unaware about lol.
Ok , forget about the KFU for a second. Go to your device manager and select update driver.
Then select I'll choose which drivers to install
Browse to the tools folder on your desktop and select...I think it is called adb_driver.ini
Sent from my Kindle Fire using xda premium
There are no compatable drivers in the "tools" folder. The only one is in the KF utility under drivers and it is called android_winusb.
I am also experiencing a new problem... It is now in a constant state of quick restarts. It turns on, shows the KF start up screen for 4 or so seconds and then shuts down. It is doing this non-stop.
Ok go here and download and unzip this file:
http://downloadandroidrom.com/file/KindleFire/root/KindleFireRoot.zip
look for a file called adb_usb.ini
open it with text editor and type:
0x1949
then save and install it
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
For your android_winusb.inf open it in text editor and make sure you have these 3 lines at [Google.NTx86] and [Google.NTamd64].
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
I had the same charging issue. B63 help me with this issue. Basically your kindle is not charging successfully. Try using the charger that came with the kindle. It worked for me.
Sent from my SPH-D710 using xda premium
Im no dev but this is what I did. Plug in your kindle and check if the drivers are installed. If your device shows up as unknown in device manager then that means the drivers are not installed. That's perfectly fine. Now unplug your kindle and power it off. Go to the kfu folder that you extracted and install drivers. Now plug in your device and it should automically power up and your device should show up as kindle in your device manager. If it is showing up go back to to the kfu folder and click run. After clicking the run button your device should show up as offline in adb status and unknown in boot status. That is perfectly fine. Now click on 1. Bootmode menu. Then click on 1 again which is Normal (4000). Your device should reboot after that. That's what worked for me. By the way I'm assuming your using kfu 0.9.5. Good luck and I hope this helps you.
Sent from my SPH-D710 using xda premium
It's working now!!! Thank you so much EVERYONE!!!
Now the next thing I am wanting to acomplish is "unrooting" it and restoring it to factory settings. How would I go about doing this? I don't think I have any recovery installed..
bjg020683 said:
Im no dev but this is what I did. Plug in your kindle and check if the drivers are installed. If your device shows up as unknown in device manager then that means the drivers are not installed. That's perfectly fine. Now unplug your kindle and power it off. Go to the kfu folder that you extracted and install drivers. Now plug in your device and it should automically power up and your device should show up as kindle in your device manager. If it is showing up go back to to the kfu folder and click run. After clicking the run button your device should show up as offline in adb status and unknown in boot status. That is perfectly fine. Now click on 1. Bootmode menu. Then click on 1 again which is Normal (4000). Your device should reboot after that. That's what worked for me. By the way I'm assuming your using kfu 0.9.5. Good luck and I hope this helps you.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ugh so many questions to ask (I'm sorry)
1. "If your device shows up as unknown in device manager then that means the drivers are not installed." Mine does not show up as an unknown but it shows up as an android phone and when clicked it is "Android ADB Interface".
2. "your device should show up as kindle in your device manager." I installed the driver but it didn't show up as Kindle in device manager
3. "After clicking the run button your device should show up as offline in adb status and unknown in boot status"
ADB Status: Online
Boot Status: Unknown
4. When I clicked bootmode menu, and typed 1:
"The system cannot find the drive specified"
Sorry for these noobie questions but please help me
Related
I'm having trouble getting this POS rooted. Got it unlocked with little problem, but now that it comes to rooting, it's extremely confusing to follow the tutorials. Is there any working one-click methods? I'm no stranger to Android OS, I had my Dinc2 rooted in about 5 minutes after unboxing. But this abomination is really working my nerves. Help please?
There is no "One-Click Root"
But rooting using the given instructions is not difficult at all.
Its as simple as downloading a few files, and typing a few codes.
what have you tried so far? and what firmware are you running?
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Cat_On_Droid said:
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Click to expand...
Click to collapse
the wait for recovery to load is HORRIBLE!! lol. push the menu button once in a while if you are unsure. i did. it makes the wait (for me) less painful but installing the .zip and rebooting successfully with a rooted phone is AWESOME!!
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
chattguy said:
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
Click to expand...
Click to collapse
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
mehdi.moha said:
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
Click to expand...
Click to collapse
Sony Ericsson sa0102 is installed, but I'm not seeing anything in my device manager about S1 Fastboot. Hmm...how would one go about installing it? I have the fastboot folder on my desktop. It has two subfolders, Fastboot and USB_drivers .
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
In this case if it's either still 'waiting for device' or trying to boot recoveryPLAY.img, then you're safe to try again since nothing is being flashed
When connected next time, in fastboot mode, before booting the .img, type this:
fastboot devices 'enter'
It will show a list of devices attached.
It might be that your missing some drivers so fastboot is not working correctly and won't detect your device. Have you pc companion installed? I don't remember if there came any drivers with the fastboot download but check that, there might be some drivers you didn't install.
Regards Dousan...
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
chattguy said:
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
Click to expand...
Click to collapse
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
AndroHero said:
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
chattguy said:
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
Click to expand...
Click to collapse
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
AndroHero said:
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
Click to expand...
Click to collapse
Mother. Of. God.
I did it. No, f**k that, you did it. All of you, thank you so much. You guys really helped me out bigtime, without berating me and calling me a noob lol. I sincerely appreciate it.
Also a special thanks to Alejandrissimo for unlocking the bootloader. Without you, this wouldn't have even been possible. Yay this blasted phone is finally rooted...
...and nobody had to die in the process.
That's what we are all here for. Learning about things through each other. We were all without knowledge at one point
Sent from my R800i using XDA App
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
Hi,
I got my Nexus 9 around launch date and used Wugs toolkit to unlock bootloader, root and install teamwin recovery.
I kept gettting OTA updates for 5.0.2 but they wouldn't install. After months of ignoring I thought I'd update.
It wouldn't update so I tried to use Wugs toolkit to 'Flash stock + unroot to latest version'.
This failed saying something about no fastboot device, although the device went to the white screen and seemed to be displaying hboot/fastboot as options...
I got frustrated and used TWRP to wipe everything, including the OS!
I'm used to Samsung so expected an Odin type program to flash over my mess... I can't seem to do anything now.
HELP! (Please!)
A reason I don't like tool kits. If they don't work as expected you have no idea what to do next. Follow the long method of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
jotan said:
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
Click to expand...
Click to collapse
Vol down and power does bring you into the bootloader. Do you have usb drivers setup? Go into device manager on your pc with the device connected. Do you have an icon with a yellow exclamation mark? If so right click on it and go to where you can choose a driver from a list on your computer. Choose Android adb composite interface.
Sent from my Nexus 9 using XDA Free mobile app
Sorry about the late reply, been on my honeymoon! For some reason it just wouldn't work on my PC, so I used my laptop and all was well.
Thanks.
Thread closed!
Hello XDA,
I just got a v10 and while i'm new to the phone, I'm not new to rooting/ installing custom roms etc. But for the life of me I cant unlock to bootloader of this phone which if im not mistaken, is the only way to get root. I just installed adb on my windows 10 laptop and I'm trying to enter fastboot on my devices by plugging in the power cable and pressing the volume down and I'm greeted with a screen that says"*welcome to fastboot mode for bootloader unlock: *quick Guidance...etc" I cant exit out of this mode so I assume this is fastboot mode? It doesnt look like any fastboot mode Ive ever seen. Anyways when trying to run the fastboot oem unlock command, I am stuck on "waiting for device". I honestly dont know whats wrong with my setup but if someone could help that would be fantastic. I have tried installing the Lg united drivers and samsung drivers but they dont seem to work. Please advise if you could.
http://forum.xda-developers.com/showthread.php?t=3490604
gamin92 said:
http://forum.xda-developers.com/showthread.php?t=3490604
Click to expand...
Click to collapse
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
ayo234 said:
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
Click to expand...
Click to collapse
I looked online at some forums about this issue and I got it fixed Here what the post said
1. Connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. Windows device manager should show an item in the list that simply says Other devices, and will expand to "Android". Do those next steps quickly! (OR: just disconnect from the internet. Some people report it works). You have between 5-10 seconds until Windows changes it to another driver. If device manager changes the driver to "Kedacom USB device" (or something else, start over from step 8).
13. Right click and choose "Update driver software" -> Browse my computer for driver software -> Let me pick from a list...
14. Choose "Kedacom USB device" (or something else that seems logical)
15. Uncheck "Show compatible hardware"
16. Choose "Android bootloader interface version _" that is the latest (should be 28.8.2016).
17. Hopefully it will work for you
Extremely helpful and it solved my problem. Here the original thread, its post number 33
http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
androidferret said:
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
androidferret said:
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
androidferret said:
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
Click to expand...
Click to collapse
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Augustoandro said:
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Click to expand...
Click to collapse
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
androidferret said:
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
Click to expand...
Click to collapse
I meant Kingoroot for PC and not Kingoroot Android.
They are different, although from the same company.
Wow it turns out I was using a fake Kingoroot from the Play Store so I take back my comments regarding KingoRoot.
I can't believe the Play Store allows such trash.