I've ran a search and wasn't able to find anything that specifically outlined my issue.
to preface, I have a t-mobile Nexus One, and my PC is running Windows 7 64-bit.
I'm running into a bunch of trouble trying to root my Nexus One and add Cyanogen's latest ROM. My first problem was trying to get Android SDK setup to use adb. the instructions on adding the path were unclear (still unsure if I did that right), and then I couldnt get my device to show up becuase the drivers wouldnt install. I used this link http://forum.xda-developers.com/showthread.php?t=613217 (the adb devices command now worked fine at this point) and that installed the drivers and I was able to successfully unlock the bootloader.
Now, i've downloaded Amon_Ra's recovery image, changed the file name and placed it on the root of my SD card. Phone is in debug mode, rebooted to the bootloader, and did the "fastboot flash recovery recovery.img" command, but i get 'error: cannot load 'recovery.img' "
as a test, i used the adb devices command again, and it does not work. to test if it was a drivers issue, I used the same process as the link above. this time the Nexus One does not show, but i DO see Android Phone > Android Composite ADB Interface.
in "Eviroment Variables" in "Path" I have added "tools/C:\android-sdk-windows\tools" and (from a different link I have seen) i added a Custom User Variable called adb with the variable value "C:\android-sdk-windows\tools"
So.. what am I doing wrong? Is there something I may have missed?
Recovery
If you type in the "adb devices" command and see your device listed, you have set up your SDK properly.
I usually put the recovery.img on my computer where its easy to find. Once youre in bootloader try the command "fastboot devices" and once again make sure your device is shown. Then "fastboot flash recovery C:\Wherever\recovery.img"
so THATS probably what I was doing wrong. I would type in literally "fastboot flash recovery recovery.img" (cause hey, thats what it said to type!). I ended up using the "easy" clockwork method, and used his recovery image instead. had a few more hiccups, but about 5 hours later, I'm all rooted and running CM6.
thanks!
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.
Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar
PetarHolland said:
Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar
Click to expand...
Click to collapse
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.
Thanks, i will read this, then i'll post here if i still need some information The entire process seems to be very hard ^^
soupmagnet said:
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.
Click to expand...
Click to collapse
I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance
Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
ed! said:
I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance
Click to expand...
Click to collapse
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.
Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1
Indeed... The entire process is hard, i'm trying to organize the information. SO the step are:
-Fastboot
-Installing bootloader
-Cleaning the system/exporting img
-Installing the rom
-Wipe
-Reboot
android :victory:
Right?
Some questions:
I read about a special cable, i can't do the process with the standard miniusb cable?
I read about downgrade the firmware of my kindle... I have the 7.3.0.3 version, i need to downgrade before install the bootloader right?
ed! said:
Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1
Click to expand...
Click to collapse
@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!
Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
E_Zatopek said:
@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!
Click to expand...
Click to collapse
PetarHolland said:
Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
Click to expand...
Click to collapse
Just a note of caution, as with all flashing of rom's. Whilst the fastboot cable is not 'required/essential' if you do mess it up , there is a potential that you 'could' brick, and depending to what extent your at, the cable becomes vital. In a nutshell if you can get your hands on a cable its recommeded as the earlier thread stated its a kind of insurance!
Good luck
kgyuszko
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse
from ondom
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
PetarHolland said:
Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
Click to expand...
Click to collapse
ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
PetarHolland said:
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
Click to expand...
Click to collapse
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.
How can i test if my fastboot work? if i type fastboot on cmd i have the entire instruction of fastboot, so the command is recognised....
seokhun said:
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.
Click to expand...
Click to collapse
fastboot -i 0x1949 getvar product
<waiting for device>
but when i plug my kindle fire and reboot, no fastboot, still <waiting for device>
I previously installed the sdk developer tool and changed the PATH adding the skd folder path to the windows shortcut for the cmd.
soupmagnet said:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.
Nope, i tryed every possibility, plugging turned off, plugging turned on and reboot, leaving to "waiting for device" for 2 hours, and nothing happened. soupmagnet suggested me to use the kindle first aid script to reinstall the adb drivers, seems the best option atm....
seokhun said:
You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.
Click to expand...
Click to collapse
Cyanogenmod logo all the time
seokhun said:
Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.
Click to expand...
Click to collapse
I did exactly this and now i get the cyanogenmod logo all the time after reboot. been this way for 40 mins already. Can someone suggest what to do next?
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
I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices
Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.
Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs
boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..