Related
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2
soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.
I realize there are dozens of similar threads but none so far has helped. I'll keep looking but in the mean time I thought I would try asking for advice.
I screwed up somehow attempting to root my Kindle HD 7". It was stuck in a loop returning to the "restore factory" screen w/ orange triangle every time. I bought a factory cable and the kindle is now in Fasboot mode.
However, every set of instructions I can find to take the next step of restoring the original firmware requires adb and/or fastboot to recognize the kindle. I cannot figure out how to get that to happen. Both fail to recognize it. I modified my adb_usb.ini file to add the line 0x1949 and I modified
sdk\extras\google\usb_driver\android_winusb.inf file to have the required hardware ids for the kindle (I tried the "stock" ids as well as the ids currently listed for the tablet in device manager). I added the sdk paths to my environmental variables. adb & fastboot commands work but neither finds the kindle.
Windows Vista is recognizing the kindle HD as Other Devices > Tate-PVT-08 but fails to load any drivers when it is first found (I get an error).
Any ideas?
Edit/update: I found a thread explaining how to force Windows to change the drivers. I forced it to change to the Android Sooner Composite ADB Driver and it is now listed as an ADB Interface device. still not recognized in adb though.
Another thing is that I am unable to update the drivers to use the adb kindle drivers. Windows simply reports that it "could not find driver software for your device".
Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Your drivers were recognized and installed by Vista! Windows now sees it as an Android Phone > Android ADB Interface. Still no luck getting adb to find the kindle though. I think next I'm going to try deleting/uninstalling adb & the sdk and starting again. It isn't spelled out anywhere but I half suspect the paths are wrong somehow.
I can update to Windows 7 if there is any chance that would help.
Thanks for your help!
Michael
stunts513 said:
Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yes, if I uninstall the device and let Windows Vista find it, it is listed as a Tate device. My kindle is indeed in fastboot (I have a factory cable). If I manually force it to switch drivers I can have windows list it as a ADB interface device.
Ahh, I tried fastboot -i 0x1949 getvar product and I get a response from the kindle!
So...I guess on to the next step! One of these 40 tabs I have open probably has something on flashing the rom.
Thanks all!
Michael
stunts513 said:
Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
MichaelBrock said:
I realize there are dozens of similar threads but none so far has helped. I'll keep looking but in the mean time I thought I would try asking for advice.
I screwed up somehow attempting to root my Kindle HD 7". It was stuck in a loop returning to the "restore factory" screen w/ orange triangle every time.
Click to expand...
Click to collapse
I know this is an old thread, but it seems to be the one most relevant to my problem.
I've got pretty much the same issue, but its because i was trying to install chainfire on my rooted kindle fire hd 7 (tate). Installation was taking longer than expected, actually thought my kindle had frozen so did a hard reset....big mistake as now it doesn't load past the kindle fire logo screen.
I bought a factory cable and the kindle is now in Fasboot mode.
Click to expand...
Click to collapse
Done the same, but when in fastboot, nothing.
However, every set of instructions I can find to take the next step of restoring the original firmware requires adb and/or fastboot to recognize the kindle. I cannot figure out how to get that to happen. Both fail to recognize it. I modified my adb_usb.ini file to add the line 0x1949 and I modified
sdk\extras\google\usb_driver\android_winusb.inf file to have the required hardware ids for the kindle (I tried the "stock" ids as well as the ids currently listed for the tablet in device manager). I added the sdk paths to my environmental variables. adb & fastboot commands work but neither finds the kindle.
Windows Vista is recognizing the kindle HD as Other Devices > Tate-PVT-08 but fails to load any drivers when it is first found (I get an error).
Any ideas?
Click to expand...
Click to collapse
This is pretty much where i'm at now, except on a windows 8 laptop, tried uninstalling everything related to my kindle, all adb, fastboot and sdk etc from my laptop before reinstalling and trying to update drivers but still not being recognised, did all the same things as above post, as been trying to sort this off and on for a while.
stunts513 said:
Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
Click to expand...
Click to collapse
I've tried to install the drivers from your sig but keep getting the message "the hash for this file is not present in the specified catalog file, the file is likely corrupt or been the victim of tampering" so i'm at a bit of a stand still at the minute.
stunts513 said:
Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
Click to expand...
Click to collapse
Any command i try use through fastboot just gives the <waiting for device> message with no response from my kindle. If either of you (or anyone else who reads this) can help it would be greatly appreciated.
EDIT: Got it recognised by windows finally, I opened "device manager", clicked "update driver software", "browse my computer for driver software" then "let me pick from a list of device drivers on my computer" where i found the right driver to enable fastboot to work and windows to recognise my tablet. Now to fix the damn thing.
Having same issue where my kindle isn't found in fastboot for some reason. When I type
Code:
fastboot -i 0x1949 getvar product
I get back Tate-PVT-08, but when i do fastboot devices I get nothing. I have Andoid ADB drivers installed and a factory cable. What is the problem?
Edit: Turns out i had to paste this in before everything -i 0x1949.
I'm glad this is a current topic again. I also need help. I've been running my rooted Kindle Fire HD 3d Gen going on two years now. I was using the firerooter to get it updated to 4.5.5 today and I'm pretty sure I bricked it--again. But this time I think I bricked it up real good.
I was doing this to hopefully get a recently updated game working again. But when it got hung up I freaked out for a second and made a mistake... I went ahead with a factory reset but then I realized that this would delete my game progress and I hadn't made a game backup before the update came on today so I was pretty much screwed in several ways.
Right, so when I was in the middle of the factory reset I was like... "****! I don't want to lose all my game progress!" and I immediately powered it down. And I immediately punched myself in the face after I turned it on and it did the lovely "kindle_fire" grey-scale initial load screen loop over and over. Based on what I've read, I'm pretty sure I've corrupted the bootloader or possibly deleted some boot partition.
I'm about sick of Amazon's bull****. They don't manager this part of their business very well at all. /RAGE
But before I throw this garbage in the dump where it belongs... I'm tempted to try to get this thing working.
I have a fastboot cable and some time. I can get to the fastboot info such as "fastboot -i 0x1949 getvar product" and it returns "product: Soho-PVT-Prod-07" . But, I can't get anything out of the adb commands to recognize the device. I've updated the .ini files from the android SDK.
Is there any boot partition I can load to this thing? Some way to hack into this? thx for any help
Hi
I've been at this for a few hours now and I'm just getting nowhere. I know this is a common issue but I assure you I have read every other thread and tried everything I have seen.
I have a HTC One M7 on the UK network Three with CWM recovery. Previously it was running Android Revolution HD, I tried to install the other Android Revolution HD Google Edition and right at the very end when I was asked to install Superuser is where I started running into problems. As it stands, my device is in a bootloop. If I'm careful I can time it right and boot into bootloader. From here, trying to enter recovery just puts me back into a bootloop.
All my HTC Drivers are installed fresh as of today. If I run erase cache, get var or anything along those lines all I get is <waiting for device>. When plugged in the device displays in Device Manager with the following details. I'm on Windows 8.1.I can't post a screenshot so it's text.
Unknown USB device (device failed enumeration)
Device status: Windows stopped because this device has reported problems (code 43)
I can't even find a RUU for my device, if it would even help at this point. Here's a transcript of my bootloader info.
*** TAMPERED ***
*** RELOCKED ***
M7_ UL PVT SHIP S-OFF RH
CID-H3G_001
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Where do I go from here? Bootloader factory reset does nothing, trying to flash a ROM doesn't work because the device isn't recognised, etc. I'm totally lost. The only suggestion I've even found is that I might have more luck in Windows 7, but I only have one system which will take 8-9 hours to back up to an external HD and unless it was a 90%+ shot I want reinstalling Windows 7 to be an absolute last ditch attempt.
Is there anything I'm missing?
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Harish_Kumar said:
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've never used Linux but I'll make a live usb stick and try to work it out.
toyfights said:
I've never used Linux but I'll make a live usb stick and try to work it out.
Click to expand...
Click to collapse
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
toyfights said:
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
Click to expand...
Click to collapse
Cool
Sent from my HTC One using Tapatalk
Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk
pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.
I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.
Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.
Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app