Related
I went through the [GUIDE] Rooting the 10.1 Tab, but I cannot get into fastboot.
I went through pershoots advice of uninstalling and reinstalling the drivers. I used the driver he has posted in the thread when I reinstalled.
Win7 cannot find the fastboot driver though. (Image attached)
*ADB works fine
*LE GoogleIO SGT with 3.1
Thanks to anyone who has some advice for me!
PS-- I'm too noob here to post in the dev forum.
same problem here annoying as f**
Hi, I facing the same problem here. Do you guys solve the problem? Please give me advice. Thank you
Same problem here. adb working fine on the tablet but not fastboot. I have tried Linux, osx, and win7 none work. Fastboot works fine on my nexus 1 with all of these platforms.
Sent from my GT-P7510 using XDA Premium App
Hi I just use mac os to done it, cause my windows 7 cant find the driver
my tab had just alive.. i cant post the link here cause i m newcomer..
jamn224 said:
I went through the [GUIDE] Rooting the 10.1 Tab, but I cannot get into fastboot.
I went through pershoots advice of uninstalling and reinstalling the drivers. I used the driver he has posted in the thread when I reinstalled.
Win7 cannot find the fastboot driver though. (Image attached)
*ADB works fine
*LE GoogleIO SGT with 3.1
Thanks to anyone who has some advice for me!
PS-- I'm too noob here to post in the dev forum.
Click to expand...
Click to collapse
I had similar problems and managed to finally use fastboot.
You have to choose drivers manually.
Read this post on how to choose drivers in order to get fastboot working
http://forum.xda-developers.com/showthread.php?t=1176292
Still no luck
I have had this problem for months, I have tried everything on this thread and on at least 10 to 20 other threads acrost the internet. I really need some help getting fastboot to work with my Galaxy Tab 10.1 Google I/O LE. Could this problem be from it being a I/O LE? Its so different than the shipping retail product, maybe these guides are for the retail 10.1? I would really appreciate any help!
Thanks
Josh
flacojo32,
As having just purchased an i/o edition used, i know what you mean about the differences, but i was able to root through fastboot on mine.. i just had to figure it out myself.
try this page, i wrote my steps that were successful for getting fastboot to load recovery:
http://forum.xda-developers.com/showthread.php?t=1429344
you may need to purge other drivers. i don't know exactly what protocol or method the fastboot is using for communication, but it may be based off the windows networking stack. i'd also suggest disabling any firewalls if it continues to fail.
flacojo32 said:
I have had this problem for months, I have tried everything on this thread and on at least 10 to 20 other threads acrost the internet. I really need some help getting fastboot to work with my Galaxy Tab 10.1 Google I/O LE. Could this problem be from it being a I/O LE? Its so different than the shipping retail product, maybe these guides are for the retail 10.1? I would really appreciate any help!
Thanks
Josh
Click to expand...
Click to collapse
The problem is using the right drivers. Going from memory here but in genersl go to your android-sdk folder and run sdk manager, select 3rd party and make sure to select usb drivers. After installing that go to device manager connect hte tab and you should see android device. if it has an exclamation point click on it and select update driver then select let me choose (not the browse for driver) - youn can then browse a list of devices and select samsung device. Once you do that the drivers are installed. you should be able to do fastboot.
A quick test is with the tab connected to the pc open a commamd editor type 'fastboot devices' and it should show a number
Sent from my GT-P7510 using Tapatalk
Thanks all for you help, but still no luck. I have rooted and or installed many of custom roms but just can't crack this one. I have all the right drivers for my other nexus devices to root them but this samsung galaxy tab 10.1 Google I/O just does not do fastboot right. It goes into fastboot but I don't know if its actually pushing the information to the computer. When I look under the Device Manager it show up as an ADB device, not fastboot. Also ADB works fine so the issue is with the tablet and how the fastboot is accomplished. Is there any other way to get a custom rom on this without fasboot? I have tried to use Odin and ADB to push a recovery but when I ADB reboot devices it just boots back up. That is after I have pushed a recovery file to the tablet. Im hopelessly deadlocked, I thought the LE I/O tab was to be open in every way for devs. but I can't seem to crack this beautiful device. Thanks for everyones help!
Josh
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
Heck and I even used a mac that does not require drivers to try it, still it would not connect in fastboot mode. It did not even pull it up when I fastboot devices, just like on the windows machine.
Josh
flacojo32 said:
Thanks all for you help, but still no luck. I have rooted and or installed many of custom roms but just can't crack this one. I have all the right drivers for my other nexus devices to root them but this samsung galaxy tab 10.1 Google I/O just does not do fastboot right. It goes into fastboot but I don't know if its actually pushing the information to the computer. When I look under the Device Manager it show up as an ADB device, not fastboot. Also ADB works fine so the issue is with the tablet and how the fastboot is accomplished. Is there any other way to get a custom rom on this without fasboot? I have tried to use Odin and ADB to push a recovery but when I ADB reboot devices it just boots back up. That is after I have pushed a recovery file to the tablet. Im hopelessly deadlocked, I thought the LE I/O tab was to be open in every way for devs. but I can't seem to crack this beautiful device. Thanks for everyones help!
Josh
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
Heck and I even used a mac that does not require drivers to try it, still it would not connect in fastboot mode. It did not even pull it up when I fastboot devices, just like on the windows machine.
Josh
Click to expand...
Click to collapse
Sorry for dumb Qs but wanted to make sure we are all on the same page.
So i take it you dont get a response when you connect via fastboot and type fastboot devices
You said you can use adb to push recovery did you try booting up from cold with the power and volume keys combo to enter recovery mode?
Sent from my GT-P7510 using Tapatalk
Right no response from the device or the PC when I type fastboot devices either on a Mac or PC. The problem lies that there is no button combination to boot the Google I/O LE Galaxy Tab into recovery, the only two options the Power + volume down button boot provides are the Fastboot(USB symbol) and the Android dude shoveling stuff(ODIN) choices. I can push recovery all day using ADB but there is no way for me to boot into recovery on the Limited Edition Tab. This is even after I try to reboot into recovery using ADB (ADB recovery or something like that) all that does is to boot me to the two choices Fastboot(USB symbol) and ODIN(android dude shoveling). I have pretty much tried everything. I appreciate all the help you are providing!
Josh
Any ideas? I can't be the only one with this problem.
flacojo32 said:
Any ideas? I can't be the only one with this problem.
Click to expand...
Click to collapse
It sounds like you do not have recovery. And since fastboot does not seem to work then it is likely yoi have the wrong drivers. Can you confirm you were able to push the recovery via adb?
Did you install the google drivers as described a couple of posts before ie using android sdk
Sent from my GT-P7510 using Tapatalk
animatechnica, I thank you for all of your help. But I return triumphant. I have found it to be a driver issue. I was trying to use a newer version of PDANet for Android (version 3.02) which did not include the correct drivers for the Galaxy Tab 10.1 LE. So I downloaded the version 2.15 of PDANet and bam fastboot started working like a charm. So I appreciate all the help from you animatechnica and also shane86 for his words of wisdom too. But overall tonight was a good night the Tide rolled, got my ICS update on my Transformer Prime and got fastboot to work and installed Galaxy Task 10.x on my Galaxy Tab 10.1 Google I/O LE. Im off to geek it up. Thanks all.
sweet and i will take note of how you solved it for future reference
flacojo32 said:
animatechnica, I thank you for all of your help. But I return triumphant. I have found it to be a driver issue. I was trying to use a newer version of PDANet for Android (version 3.02) which did not include the correct drivers for the Galaxy Tab 10.1 LE. So I downloaded the version 2.15 of PDANet and bam fastboot started working like a charm. So I appreciate all the help from you animatechnica and also shane86 for his words of wisdom too. But overall tonight was a good night the Tide rolled, got my ICS update on my Transformer Prime and got fastboot to work and installed Galaxy Task 10.x on my Galaxy Tab 10.1 Google I/O LE. Im off to geek it up. Thanks all.
Click to expand...
Click to collapse
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
Click to expand...
Click to collapse
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Awesome Post. Thanks Alot.Need this tool very much .
shimp208 said:
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Click to expand...
Click to collapse
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
KMyers said:
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
Click to expand...
Click to collapse
Or Verizon Store, or any other store that sells smartphones and tablets . You could make a app that has a run button that when pressed automatically run's a root exploit such as Zerg Rush, then permanently flashes a custom recovery, then a custom ROM of your choice all one after the other. Think of it as mix of z4root, EZ-Recovery, and ROM manager all rolled into one. Only problem is not every device supports fastboot so some devices would be left out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
shimp208 said:
eft out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
Click to expand...
Click to collapse
Hello,
Just the host device needs a custom recovery only to install the tools (this can be perm flashed or temp flashed (fastboot boot recovery.img). Once the tools are installed, the recovery is no longer used.
The target device only needs USB Debugging enabled.
You are also correct in your statement that not all phones respond to the Fastboot protocol. The other tools such as Odin and NVFlash are not so easy to package. Some devices such as the ASUS Transformer TF700 have a Fastboot mode, assuming you unlock the bootloader. Fastboot is the standard on all HTC, Sony and any phone bearing the sacred "Nexus" moniker. It is also favored among "cheap/knockoff" devices.
There are several root tools that simply use adb to work.
What?!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
.....
HAVE FUN!!!
Click to expand...
Click to collapse
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
rainabba said:
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
Click to expand...
Click to collapse
Thanks,
I guess the reason many have not downloaded this is because it was stuck in one of the lesser active sections of XDA-Developers. I assume that most people visit the portal and device specific development threads. Aside from being featured on the portal, not many ways to get people in here.
Just tried this out on my nexus 7 running ubuntu, this is indeed awesome, thanks for compiling it
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
rmclardy said:
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
The new "secure adb" that was introduced in Android 4.2.2 will not work at this time. You may be able to try running "adb devices" at root to see if it works for you. If not, you can manually reboot it into recovery and use kfastboot to flash the new recovery
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
rmclardy said:
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
If your device is currently rooted, you should be able to run an App from the Play Store to reboot it into recovery (https://play.google.com/store/apps/details?id=com.liveov.rebooter ), from there, kfastboot will work
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
777.300 said:
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
KMyers said:
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
Click to expand...
Click to collapse
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
777.300 said:
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
Click to expand...
Click to collapse
Yes, I had a similar issue a few weeks ago. I was in Texas for a few days and my HTC EVO 4G LTE had an unfortunate run in with the Drink Cart on the Airplane. I had to go out and purchase a new phone at the Sprint Store in Texas. I had the phone purchased and rooted in about 10 minutes . Thanks to revone, unlocking the bootloader on the HTC one took almost no effort and I had S-Off to boot. All from my ASUS Transformer 700
so this is only for nexus?
Thank you very much!,
Testing on Samsung Galaxy Y
Just what i was looking for
I am yet to test it out, but i surely am very happy to see this thing actually exists. Just googled it out of the the blue and "kaboom!"here it was..
Keep up the good work.
Cheers
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Really desperate here.. :/
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Yousucks2 said:
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Click to expand...
Click to collapse
You are in a world of hurt. It's possible (likely) the device can be recovered but not without considerable effort and (probably) many failed attempts. Such assistance is beyond what can reasonably be provided via the forums. You can browse through HDX threads to get the gist of what needs to happen. If you are a technology/Android noob it will probably be easier to pick up a refurb at an auction site. Good luck.
PM for support is normally ignored
joltpodcast03 said:
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Click to expand...
Click to collapse
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
draxie said:
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
Click to expand...
Click to collapse
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Do your homework...
joltpodcast03 said:
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Click to expand...
Click to collapse
As I said, if fastboot works, it's fixable (in other words, it's not a brick).
BUT, you'll have to find one of the million guides on how to setup and
use fastboot all by yourself. That's not something I'm willing to spend
time on. Sorry...
As for cables, unless the device is a soft-brick, you don't need a special
cable, but it's preferable to use your factory cable not random junk.
BUT, seeing that you have MacOS, my 1-Click tool _should_ work for you.
Then, all you need to do is click through a web-UI. If you want to do that
instead, you'll have to wait though, because I need to iron out a wrink or
two, and haven't had the time the last week or so...
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Yousucks2 said:
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Click to expand...
Click to collapse
Technically not ADB if working in fastboot but guidance is still 100% relevant.
fastboot commands?
I'd like to start off by apologizing for having to waste somebody's time for something I can't find the answer to. I should preface this post by saying that I know nothing about ADB, but in the last couple of days I've done plenty of reading and to be quite honest the more research sometimes adds to the confusion with contrary and outdated information.
I'm basically trying to get TWRP onto my Mi Pad 4 LTE using ADB on my Windows 10 PC coming from the MIUI EU ROM Bootloader unlocked from the supplier. USB debugging enabled drivers installed etc
I had a lot of trouble until I came across this thread http://www.testedtechnology.co.uk/debloating-the-huawei-p30-pro/ because of an error I was getting in the Powershell window.
https://forum.xda-developers.com/attachment.php?attachmentid=4781060&stc=1&d=1561218064
So basically in short, thanks to the above thread I was able to get into fastboot mode having recognized the device using the precursor .\ as shown above, but one of my problems is I'm not sure if I should be use the .\ with all commands? My problem from here now that my device was in fastboot mode I didn't know how to direct it to the file. I just have no idea what commands to you use to find a particular directory to get to recovery-TWRP-3.3.0-0429-XIAOMI_PAD4(PLUS)-CN-wzsx150.
I'm really concerned about putting the device into bootloop as some of the problems I've seen seem almost insurmountable!
Anyway sorry again and TIA for anybody taking the time to help.
All sorted now thanks for all the help.