Hey,
i just flashed (hope thats the right word) the TWRP recovery manager on it according to the instructions here:
http://forum.xda-developers.com/showthread.php?t=2277105
I already rooted it before and everything worked.
Now after i put TWRP on it, it just doesnt boot anymore and is stuck at the blue bootup screen.
What i want to do now is simply flash another Custom Rom on the Device (Stari or CM10.1, probably Stari though), problem is, that i don't have this on the Fire and don't know how to put it on the Fire.
I can open up TWRP and click USB mount and connect it to my computer, but no device shows up (tried 2 different Laptops, 1x Win7, 1x Win8) and besides from that i have no clue how to either get back in Amazon Stock Rom to connect it to the computer and put files on it or how to do this in TWRP
Help appreciated !
OK what I would do is push the file over adb to your sdcard while booted into twrp, so if u have the android SDK or any tools like binaries root, put your ROM in the same folder as adb.exe and run from a command prompt that's cd'd into that directory
Adb.exe push romnamehere /sdcard/romnamehere
I don't know if your computer shows the extensions but I'm guessing that romnamehere will need to have .zip added to the end of it unless its there already.
Also thought I'd mention if your computer refuses to accept the fact that adb is connected I heard at one point that twrp for kindle didn't have the same vid for adb as it does in the kindle os, so you would have to mod the drivers with the new one. I can confirm this in a few min if need be.
Edit: yep my kindle registers as 0x18d1 as the vid in twrp, though I am slightly confused, I couldn't get adb to work, kept saying no permission. I read about the adb side load button as well it may be of use but I'm unsure.
Try reading this:
http://forum.xda-developers.com/showthread.php?t=2283230
First post should be useful
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
In order to get adb going while in recovery. Download kindle fire utility not that you will only be using this for the driver installation anything else will permanently brick your kindle. After extracted go to drivers/kindle folder and open android_winusb with notepad add
Code:
;Kindle Fire HD
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
under [Google.NTx86] and[Google.NTamd64] then click save and run the driver install.bat then plug in your device and you should have adb going on both CM10 and in recovery.
thanks guys, never used ADB before, but doesnt sound too difficult, i'll try tomorrow
getting another error (tried this on 2 PCs, one with german windows 7 and one with english (US) windows 8
i editted the lines into the android_winusb, then started the batch file and getting this:
{
"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"
}
well the device showed up in device manager and i manually selected the drivers, which worked, so without the bat
thank you guys, saved my weekend!
Related
hello every1
first i will give u info about me:
phone: DHD
rom: Revolution HD 1.9.3
windows 7 x64
eclipse Helios 32bit
JDK 32bit
everything was working perfectly, until the latest update to 2.3 SDK, which kept crashing the adb over and over. i dont know what is the problem
Edit: it's like there error in this post http://forum.xda-developers.com/showpost.php?p=9830639&postcount=1684 but no one gave him an answer
I'm no expert, but from looking at the attached post it looks like the DHD is rejecting ADB connection attempts & commands.
Can you confirm that USB Debugging is enabled? Also the others users were using Eclipse which they said "kills the adb.exe". Could you try to run ADB without Eclipse running.
Failing any of this, you could update to Android Revolution HD 2.0.1
andyharney said:
I'm no expert, but from looking at the attached post it looks like the DHD is rejecting ADB connection attempts & commands.
Can you confirm that USB Debugging is enabled? Also the others users were using Eclipse which they said "kills the adb.exe". Could you try to run ADB without Eclipse running.
Failing any of this, you could update to Android Revolution HD 2.0.1
Click to expand...
Click to collapse
the USB Debugging is enabled, the problem started after i installed Revultion Rom and upgraded the SDK to 2.3, so i dont know what really caused it
even if i used the command line with the phone(without eclipse) adb.exe crashes.
i just tried the comand adb install .......
and the server crashed many times before actually installing it
just upgraded to 2.0.1 and still the same problems exist
Just a quick check, you do know that adb.exe has been moved in the new SDK update. It's now located in SDK\platform-tools not SDK\tools.
andyharney said:
Just a quick check, you do know that adb.exe has been moved in the new SDK update. It's now located in SDK\platform-tools not SDK\tools.
Click to expand...
Click to collapse
Yes sir, i know that
if this could help
when i enter the adb shell mode and type the ls command, i get weird names
{
"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"
}
Yesterday at work while my phone is charging it just suddenly went to google screen and i waited for about 5-10 mins and still there, i thought its a minor problem...take out the battery and still stuck up, i went to recovery and accident wipe everything. My main problem is i have a Samsung Laptop and it wont recognize my phone, ( it will recognize for a second when i turn on my phone going to google logo and it will say device is malfunction etc etc. it will also recognize for a second going to recovery mode when pass the google logo and again it will say malfuction ) I tried ADB, but wont recognize my device because of the computer? I tried ODIN but still my device wont recognize by my computer. I tried Gnex tool kit, Rootkit and heres my device manager looks like
I hope someone can help me.
That looks like a problem with the drivers you have installed on your computer. It should show up under Android Phone and then have Android ADB Interface (or Samsung Android ADB Interface). Try installing the drivers from here.
{
"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"
}
mwalt2 said:
That looks like a problem with the drivers you have installed on your computer. It should show up under Android Phone and then have Android ADB Interface (or Samsung Android ADB Interface). Try installing the drivers from here.
Click to expand...
Click to collapse
I download it and how can i use this one?
benjiebench said:
I download it and how can i use this one?
Click to expand...
Click to collapse
Install samsung kies.you just need driver from kies. Dont open samsung kies when you want to use adb.
Sent from my GT-I9300 using xda premium
Samsung kies on a Galaxy Nexus ??? Put the phone in adb mode and manually install the ADB interface drivers from the google SDK. You will need to uninstall and erase all previous drivers from the device manager and then install the .inf from the sdk
Sent from my Nexus 4 using xda app-developers app
As of now, I'm trying to unbrick my kindle fire 1st generation, but my computer isn't recognizing it as ADB, only as Android, is there anyway to get it recognized as ADB so I can install twrp and flash a rom?
{
"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"
}
carlybelle said:
As of now, I'm trying to unbrick my kindle fire 1st generation, but my computer isn't recognizing it as ADB, only as Android, is there anyway to get it recognized as ADB so I can install twrp and flash a rom?
Click to expand...
Click to collapse
Try updating the driver in driver settings. That was the problem with my PC once. I just updated and ADB was recognized
Sent from my Amazon Kindle Fire using xda app-developers app
404-Not Found said:
Try updating the driver in driver settings. That was the problem with my PC once. I just updated and ADB was recognized
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Nope, but thank you anyway, the problem is that my kindle fire has no os and it's just stuck at the stock boot up screen without any recovery...
You need a Fastboot cable/adapter/etc.
You can make one yourself by soldering 4th contact/the one with the missing spot to the 1st contact (red wire/power wire).
And then you can use whatever to recover.
AND make sure you use Kindle Fire FIRST GENERATION SOFTWARE. OTHERWISE YOU WILL BRICK AGAIN, AND THEN, COMES JTAG.
mr_verystock said:
You need a Fastboot cable/adapter/etc.
You can make one yourself by soldering 4th contact/the one with the missing spot to the 1st contact (red wire/power wire).
And then you can use whatever to recover.
AND make sure you use Kindle Fire FIRST GENERATION SOFTWARE. OTHERWISE YOU WILL BRICK AGAIN, AND THEN, COMES JTAG.
Click to expand...
Click to collapse
Okay thank you!
Hi all,
I made a stupid mistake: I erase all files from my kindle.
So now, it's stuck on kindle fire logo.
I try KFU, KF Unbrick, try to install Firekit on Ubuntu without success.
I have a factory cable but don't know if/how it works. And I read a lot of posts on this forum but nothing works!
Help!! I need somebody...
Thanks...
Do you have CWM or TWRP installed?
Sent from my SM-T210R using Tapatalk
How is it listed in device manager?
Sent from my XT894 using Tapatalk
@sd_shadow & @jlshady00
Device is listed as offline and twrp seems not installed. Only have KF logo...
KF was rooted. I didn't use it for months. Maybe the Amazon update unroot the device?
Is There a solution??
Thanks for your precious help!
not KFU. device manager:start>Control panel>hardware>device manager
sd_shadow said:
not KFU. device manager:start>Control panel>hardware>device manager
Click to expand...
Click to collapse
@sd_shadow
Before my mistake, device was ok in device manager. Now, I tried to uninstall and reinstall the same drivers but device manager shows there is a problem with my KF (KF appears but is not recognised: drivers not found).
I'll make a screen capture tomorrow....
Thx and have a nice week end!
@sd_shadow
Can't post outside links... s24.postimg.org-b5s2i05bl-Kindle.png (change - with /)
And I follow your collection of links (driver on android file host).... no change...
{
"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"
}
that is from devices and sound?
device manager looks like this
---------- Post added at 10:59 PM ---------- Previous post was at 10:56 PM ----------
may need to delete old drivers and reboot pc a couple of times, till correct divers work.
@sd_shadow
Don't work... can't install drivers with KFU (error message: The current language is not supported by the Device Driver Installation Wizard. Contact the vendor that provided you this package.).
So I install official Amazon Driver... try to install, uninstall but nothing works
what version of windows 7, 8...
sd_shadow said:
what version of windows 7, 8...
Click to expand...
Click to collapse
@sd_shadow Windows7
JohnBeu said:
@sd_shadow Windows7
Click to expand...
Click to collapse
could try my driver folder here
unzip Kindle Fire.win7.Drivers.zip and copy to C:\Program Files\Common Files\Kindle Fire
then
Start>control panel>Hardware>device manager>
select Kindle> properties>uninstall driver
disconnect usb from kindle, reconnect kindle
select kindle again in device manager, update driver, browse my computer for driver software> select driver folder you downloaded and click next
Don't work... think I'm good to buy a new one...
I purchased an LG-G3. Performed an OTA update to latest: 47A. I connected to my Windows 10 box, enabled debugging, worked fine.
I downgraded using TOT method to 10B. The device is now running 4.4. Reconnected device to Windows 10 box, enabled USB debugging, does not work.
The device only shows up in device manage as a portable device
I have tried the sticky on this forum, unfortunately it does not apply as I do not have any of the items listed to remove
I have uninstalled all LG Driver/LG Verizon Driver/Google driver etc.
I have used USBDeview to remove anything named LG/ADB/Google
I have rebooted my machine, double checked the USB list with USBDeview
I have enabled/disabled/revoked USB Debugging, switched between MTP/PTP, rebooted phone
I feel like every time I google the problem a different way, I end up back at the Google USB driver download page or the LG Verizon driver download page
I would appreciate a fresh set of brains, I have a feeling I am now tunnel visioned and won't ever get out, please help ;0 I never get that prompt on the phone to allow the computer access to the phone, is that permission still on the PC is some fashion and needs to be revoked?
{
"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"
}
I ran a system update and the phone downloaded ~200mb file, applied and rebooted. Looks like that was 35B bootstack and now the phone does enable USB Debugging. Unfortunately if I take the phone back to stock USB Debugging still does not work
I also connected the fresh stock phone to another Windows 10 machine with the LG G3 Verizon Drivers installed and could not get USB Debugging to enable...
Cmd as admin, cd *adb path* , adb devices and an authorization should appear on your phone, usually works with me.
myclarity said:
Cmd as admin, cd *adb path* , adb devices and an authorization should appear on your phone, usually works with me.
Click to expand...
Click to collapse
Appreciate the suggestion, tried that and adb devices command just reports no devices connected and no prompt on the phone
mhum said:
Appreciate the suggestion, tried that and adb devices command just reports no devices connected and no prompt on the phone
Click to expand...
Click to collapse
The cmd part as admin is very important, dunno why but it wouldn't recognize my phone unless cmd was started like that.