Develop Bugs

How do I use ADB Sideload?

A couple of days ago, I nearly bricked my phone to no return. In the process of this I remembered reading about ADB sideload. So I went ahead and tried to use the function to re-flash my ROM in TWRP. However, when I connected my phone my computer didn't recognize it and the "adb sideload 'filename'" command wasn't working it just kept telling me "device not connected". Is there a way I can set up my computer/phone for ADB sideload in case this ever happens to me again?

Did you have the drivers installed? Go to Control Panel > Hardware and Sound > Devices and Printers and make sure your phone shows up
You can also run this:
Code:
adb devices
To see connected devices

Reinstall the drivers and make sure that your adb is updated so u have the side load function.
Sent from my SPH-L900 using xda premium

CNexus said:
Did you have the drivers installed? Go to Control Panel > Hardware and Sound > Devices and Printers and make sure your phone shows up
You can also run this:
Code:
adb devices
To see connected devices
Click to expand...
Click to collapse
Yeah I have the drivers installed and I've always been able to use ADB just fine when my phone is up and booted but when I entered ADB sideload in TWRP it couldn't detect my device, adb devices showed no devices.

Adb won't detect devices that are in recovery, it has to be booted up because it checks whether debugging is enabled too

CNexus said:
Adb won't detect devices that are in recovery, it has to be booted up because it checks whether debugging is enabled too
Click to expand...
Click to collapse
I'm not saying you're wrong, and I thought the same was true too. But if that's the case why does a function like "ADB sideload" exist on TWRP at all? I just don't get it. I followed the instructions on their website to no avail. There must be some way to get my phone recognized in recovery

WAIT, no ignore that post lol
The evo lte can be rebooted into recovery through adb even when it's dead.....
So if the hardware supports it then it does work.....
To your question....that's strange, maybe your phone just isn't compatible with it for some reason
I know some peoples phones won't mount the sdcard through recovery, ever

CNexus said:
WAIT, no ignore that post lol
The evo lte can be rebooted into recovery through adb even when it's dead.....
So if the hardware supports it then it does work.....
To your question....that's strange, maybe your phone just isn't compatible with it for some reason
I know some peoples phones won't mount the sdcard through recovery, ever
Click to expand...
Click to collapse
Forgive me if this is a dumb question but what if I reinstall my drivers and connect my phone while it's in recovery?

sevenpioverthree said:
Forgive me if this is a dumb question but what if I reinstall my drivers and connect my phone while it's in recovery?
Click to expand...
Click to collapse
If your computer detects the device, it'll start installing the drivers

musclehead84 said:
Reinstall the drivers and make sure that your adb is updated so u have the side load function.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
My ADB is completely up to date and has a sideload function. I have figured it out though.
Basically I edited the "android_winusb.inf" file under "C:\android-sdk-windows\extras\google\usb_driver". I put my device into recovery and then went into device manager on my computer. I right clicked my phone which had a yellow exclamation mark and was named "Samsung_SPH_L710" (or something close to that) and went into properties, then the details tab and then chose "hardware ID". There were 2 lines there. The lines were:
Code:
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01
I took those lines and pasted them under:
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
I put the lines after the last line under the "Google Nexus (generic)". If you have a 64-bit computer then instead of [Google.NTx86] you put them under [Google.NTamd64]. The lines still go after the last line of "Google Nexus (generic)". The lines then looked like this:
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE1
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
[COLOR="Red"]%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228&MI_01[/COLOR]
The red lines are the new ones I inputted. I saved the file, uninstalled my phone under device manager, disconnected it, and while it was still in recovery, reconnected it and installed the driver. I had to point the installer to the "C:\android-sdk-windows\extras\google\usb_driver" folder. My computer then prompted me to reboot and upon rebooting it asked me to install the driver but this time I did not need to point it to any folder, and voila! I can now use adb in recovery. If you are using this method, then after you are done type in:
Code:
adb devices
If your device shows up, then you have successfully completed this!
I probably explained this is a really god awful way. This might be common knowledge among you guys but if it isn't then maybe one of you can re-write this in a more comprehensive way since ADB sideload could come in handy.
EDIT: I want to add that I did not figure this out on my own. I got it from this thread: http://forum.xda-developers.com/showpost.php?p=37993317&postcount=22. The only thing is I couldn't copy those values directly I had to find them myself under "hardware id"

Nice! :thumbup:
Thanks for the fix as well

CNexus said:
Nice! :thumbup:
Thanks for the fix as well
Click to expand...
Click to collapse
No problem! I feel pretty awesome answering my own question. Is this worth making a guide for? I'm thinking it could come in handy if someone bricked their phone and wanted to use ADB sideload
By the way did you confirm this for yourself?

sevenpioverthree said:
No problem! I feel pretty awesome answering my own question. Is this worth making a guide for? I'm thinking it could come in handy if someone bricked their phone and wanted to use ADB sideload
By the way did you confirm this for yourself?
Click to expand...
Click to collapse
Afternoon: I have a sideload usage question.
I have tried ADB side load numerous times from various folders and nothing seems to work for me.
Is there an actual how to for ADB side load?
My adb works just fine.
The note on the TRWP utility screen says "usage: adb sideload filename.zip
When I make the side load selection in TWRP, and issue adb devices on PC, I receive "XXXXXXXserial sideload"
Can this be executed on the PC using path statements?
ex:
adb sideload \folderA\folderB\name_of_File.zip
The file can be any installation that uses a zipped manifest file such as ROM or APK.zip files?
I receive a listing of ADB help when I use the above syntax.

Just force the ADB Drivers for your device
If you have the exclamation mark beside the device when within recovery, just update the driver in device manager and manually locate and install the ADB driver for your device, it will give you a message that this may not be for your device blah blah blah, just say continue...it will install and your device will be detected.
sevenpioverthree said:
My ADB is completely up to date and has a sideload function. I have figured it out though.
Basically I edited the "android_winusb.inf" file under "C:\android-sdk-windows\extras\google\usb_driver". I put my device into recovery and then went into device manager on my computer. I right clicked my phone which had a yellow exclamation mark and was named "Samsung_SPH_L710" (or something close to that) and went into properties, then the details tab and then chose "hardware ID". There were 2 lines there. The lines were:
Code:
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01
I took those lines and pasted them under:
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
I put the lines after the last line under the "Google Nexus (generic)". If you have a 64-bit computer then instead of [Google.NTx86] you put them under [Google.NTamd64]. The lines still go after the last line of "Google Nexus (generic)". The lines then looked like this:
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE1
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
[COLOR="Red"]%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228&MI_01[/COLOR]
The red lines are the new ones I inputted. I saved the file, uninstalled my phone under device manager, disconnected it, and while it was still in recovery, reconnected it and installed the driver. I had to point the installer to the "C:\android-sdk-windows\extras\google\usb_driver" folder. My computer then prompted me to reboot and upon rebooting it asked me to install the driver but this time I did not need to point it to any folder, and voila! I can now use adb in recovery. If you are using this method, then after you are done.
Code:
adb devices
If your device shows up, then you have successfully completed this!
I probably explained this is a really god awful way. This might be common knowledge among you guys but if it isn't then maybe one of you can re-write this in a more comprehensive way since ADB sideload could come in handy.
EDIT: I want to add that I did not figure this out on my own. I got it from this thread: http://forum.xda-developers.com/showpost.php?p=37993317&postcount=22. The only thing is I couldn't copy those values directly I had to find them myself under "hardware id"
Click to expand...
Click to collapse

i just did this for my xperia u but still i didn't get it

CNexus said:
Adb won't detect devices that are in recovery, it has to be booted up because it checks whether debugging is enabled too
Click to expand...
Click to collapse
Forgive me if this has been pointed out, and I realise this topic is quite old but adb will detect devices which are in the 'sideload'ing state in recovery.

stumbled onto this thread, thought i would respond: just mount data, then try adb..
C:\adb>adb devices
List of devices attached
FA2BXW4000XX recovery
thats what i get while browsing for a zip in TWRP (no sideload command)
when i run sideload adb doesnt recognize.

Linux?
Is there a tutorial anywhere that tells how to use adb sideload with a Linux PC?

Nexus 5
Im having a problem where the cmd terminal is telling me it cannot read my zip file when i try to sideload it.

What these instructors fail to realize is that most of us haven't been using shell commands since we were 11 years old.
I'm not even sure how to start ADB sideload. I just downloaded a whopping 389 mb package for the entire sdk when all I needed was adb sideload.
(but I couldn't find any place to download just the adb sideload).
Now when I double click on adb, the black screen comes up for two seconds and I see a whole bunch of lines scrolling down and then the black screen disappears.

Hints for using KFU on a stock KF1

Hi all,
Today I turned my KF1 into a stock JB 4.2.2 tablet.
I used KFU, but as soon as I tried to run the install, it hung on fastboot. Luckily for me, I also had created a Livelinux install on a USB drive and used Soupkit to get the unit back to normal. Here's what I did to get through the process
0. Build a livelinux install
1. Modify the install_drivers.bat program and add the "/lm" (legacy mode) switch on the 32- and 64-bit installs
2. Run the install_drivers program
3. Reboot the computer and attach the Kindle
4. Now, you should get an "Android Phone" device in your device manager. Open that up and you will see an "interface" line. Right-click on "Properties" and check the "Details" line - WRITE THIS DOWN AND DOUBLE CHECK
5. Run KFU and change into fastboot mode
6. Unplug the Kindle and plug it back in. Windows should try to install another device driver - don't worry if it fails. Do the same thing now for the "Composite" driver under the "Android Phone" as in step #4 above.
7. Uninstall the driver(s) and then go into your \windows\system32\drvrstore directory on your machine (you may have to turn hidden files on). Delete the directory that starts with "Android"
8. Go back into the \kfu\drivers\kindle directory on your PC and modify the android_winsub.inf file
Here's the trick:
Whatever you found in step #4 and #6, make sure that there is a matching line in the INF file. For me, I needed to add the lines:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006\0123456789ABCDEF
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01\7\&F7A5236&0&0001
Now, re-run "install_drivers" and reboot your machine again. Run KFU. You should be rooted, TWRP'ed and FFF'ed in no time!

[Q] TWRP Doesnt show my backed up to restore!

TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?

DSH said:
TWRP Doesnt show my backed up to restore! and i have not any rom placed on my sd-card to install and iam wiped :cyclops::crying:
Kindle Fire 8.9 and TWRP 2.6.0.0 by the way, why the usb storage mounting doesnt work in TWRP?
Click to expand...
Click to collapse
i have figuerd out what must i do!
now i have ADB and ADB doesnt find my device to push the rom on it!
plz plz plz help me
i had Drivers installed but when in fastboot connected to pc windows cannt find JEM-Prod... (something like this)
i neeed your help im so confused

Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Why are you in fastboot, you just need to sideload the ROM onto twrp. Usually u just goto advanced>side load and swipe the thing. Then on your PC put the ROM in the same folder as adb command if you haven't setup your paths, and run adb.exe sideload filename.zip. that will typically do the job.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thanks for your help but adb doesnt recognize my kindle fire! when in CMD i type "ADB Devices" no devices showd up and when "ADB usb" error shows
i think this is the cuase why your tip doesnt work for me (
ive tried this but step 3 give an error
Had been searching on & off over 2 months & finally found the sol
This now lets you use the KFU util and others to root & install new OS etc
You need to have installed ANDROID SDK and extras-usb & JAVA se
1)
you will need to modify the following two files:
a. adb_usb.ini – You can find it under your Users\YourUsername\.android folder
In a typical Windows 7 installation, adb_usb.ini will be located under C:\Users\YourUserNameHere\.android
Open the adb_usb.ini file with a text editor (Notepad is just fine) and add the following line at the end (on a new line). Save and exit.
0×1949
2)
android_winusb.inf – You can find it under the folder you installed the Android SDK, in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Open the file with a text editor (notepad is again good enough), locate [Google.NTx86] section and also the [Google.NTamd64] section and add the following lines to each section, like in the screenshot.
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
3)
Note: If your device list is empty, maybe you plugged-in Kindle Fire before you installed Android SDK and Android USB Drivers. In this case you’ll need to force load the Android USB driver. Right click on My Computer and select Properties then navigate to Device Manager. Under Other Devices you should see Kindle with a yellow icon containing an exclamation point.
Right Click on Kindle name and select Update Driver Software. A Dialog will pop-up asking how do you want to search for driver software. Select Browse and point toward the folder containing Google USB Driver (in my case C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). Select Next and proceed with the installation, choose Install this driver anyway when prompted.
Ok now you can
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
d. type adb kill-server followed by enter
e. type adb devices. If everything is fine, you should see a connected device (your Kindle Fire)
0000666665555 device
Click to expand...
Click to collapse

Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Sounds like you have a driver issue or the device would be showing up with adb devices, try using my drivers from this post: http://forum.xda-developers.com/showthread.php?p=44319953
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
thank you very much, but how must i install that?
in device manager i select update driver and locate this folder and it says windows was unable to install you kindle fire HD
i put my kf in recovery mod and plug in the cable!
why have i these problems ?
but again i wanna say thank you bro:good:

So in the task manager is showing a device with an exclamation mark over it right? If so right click the device and hit properties, then goto the details tab, and choose hardware id's from the drop down menu and post them here, I'll see about modifying the driver if I can. Don't know why mine wouldn't work I had the old and new vendor id's for twrp in that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

When i connect to pc in fastboot, in device manager shows as Other devices "Jem-PVT-Prod-04" and the Hardware Ids is:
USB\VID_1949&PID_0008&REV0100
USB\VID_1949&PID_0008
and when just plug the usb cable in recovery mod task manager show it as Portable Device and "Amazon Kindle Fire HD" with a yellow mark! and the hardware Ids is:
USB\VID_1949&PID_0008&REV_0216
USB\VID_1949&PID_0008
thank you bro

ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,

stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
OMG OMG OMG you saved me and my KINDLE FIRE
i have best wishes for you bro best wishes :good::good::good::good::good::good:

Help!?!?!?
stunts513 said:
ok i guess the hd 8'd have a slightly different pid than the 7 inch model, here i uploaded the updated version to this thread. Try updating the amazon kindle hd device and using recovery if u can, its a better option to just reflash stuff from that rather than fastboot unless u need to, makes things little bit easier imo. This should also work with the jem-pvt-prod-04 device as well,
Click to expand...
Click to collapse
i flashed recovery.img to my kindle using flashify and than i rebooted it than it came up saying kindle fire than the red screen slides across the screen. the app says that you may see a red screen.so im stuck now.

You probably just need to reflash the recovery partition from fastboot.

TWRP Software Brick FIX! Kindle Fire 2

I've cracked the kindle code for ADB Sideload / Push In TWRP recovery! :highfive:
If you have access to TWRP and nothing else, this is for you.
Like many, I foolishly formatted my internal storage on my Kindle Fire 2 while in TWRP. with no Zips to flash I was stuck trying everything I could think of to get a file onto my Device. Read up on ADB Sideload.. But my PC would not recognize ADB Sideload AT ALL, and I Couldn't Find the Drivers.
Read up on Mounting.. No drivers no mount. Updated my Android SDK, drivers there didn’t work. Almost threw my kindle in the river.
But then I Found A certain set of Drivers from Amazon's support section. (See Attached)
So here's how to get your kindle back: :fingers-crossed:
Download and Extract the driver files. Run the Kindle Drivers. Once the Drivers are finished plug in your kindle fire 2, windows will not recognize it and we need to install the driver manually.
Go to My Computer icon. Right click and select Properties. Open Device manager in the top left.
Your Kindle will show as a yellow triangle Kindle or Kindle Fire Device (or in some cases it will have the wrong driver installed, {right click and uninstall current driver, your PC will have to restart.})
Right Click on Kindle Fire Device> Click Update Driver Software..> Click Browse my computer for Driver software> Click Let Me pick from a list of device drivers on my computer>
NOW {Kindle} will show up on the list a few times, find the one that has: ADNROID COMPOSITE ADB INTERFACE and install this driver for your kindle. If everything worked your kindle fire will now be recognized and install.
NEXT STEP!
Sideload will not work for this, so don’t even try. No SDK is required for this process just the ADB Files (Attached)
Make sure you extract the ADB.zip right onto your C:/ drive to make this easy.
Download any Kindle Fire 2 Rom (Found in Kindle Fire 2 Android Development section, preferably a Small File Size like CM 10.1),
Rename this ZIP to kindle.zip (or another short name)
Download the Gapps File for the version of ROM you just downloaded from Goo.im,
Rename this ZIP to gapps.zip (or another short name)
Place both ZIPs directly into the C:/ADB folder
Open a command prompt by going to Start > Run > CMD and hit enter. A DOS Command prompt will open.
First line will say
C:\USERS\YOURNAME>
Type> CD C:\ADB Now it will change your Directory to the C:\ Drive ADB folder
Ok on your Tablet now in TWRP, Tap MOUNT> next check [x]DATA and [x]System and tap MOUNT USB SYSTEM
Windows will not notify you of the change so don’t freak out.
ADB needs to be at least Version 1.0.29, you can check by typing the command: ADB version
Next type> ADB devices
Will now say>
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
(IF it doesn’t say anything under list of devices you will have to uninstall and reinstall the driver in step 1)
Next TYPE> adb push kindle.zip \sdcard\kindle.zip
Wait about 30-40 seconds without touching anything, it will be sending the file.
IT WILL SAY>
3589 KB/s (128302247 bytes in 34.908s) or something similar.
Next Type> adb push gapps.zip \sdcard\gapps.zip
Wait about 30-40 seconds without touching anything, it will be sending the file.
IT WILL SAY>
3262 KB/s (57280392 bytes in 17.143s) or something similar.
BAM! Files are on your device!
BACK TO THE TABLET!
Tap Unmount and click the home icon in the top right.
Click INSTALL and tap (UP A LEVEL) to get to the root of the kindle fire.
Your files should be there Labeled Kindle.zip and Gapps.zip!
Install normally! AND Don’t forget to Wipe your Dalvik/Cache! :good:

All this info is available in the forums here but I'm really glad you did this. It should prevent a lot of redundant questions. Very well written, simplified and explained.
Kudos!
-> Sent from my mind to your screen.
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.

hi, i am using Chinookgod's method to push the kindle.zip and gapps.zip to my kindle successfully
but when i try to 'swip to confirm flash', it shows 'Failed' ,
and E:Mount: Unable to find partition for path '/\sdcard\kindle.zip'
Error flashing zip '/\sdcard\kindle.zip'
Updating partition details..
below is the screen cap
hxxp://imgur.com/ecjcZZF (please change hxxp to http)
what should i do? plz help :crying:
below is my cmd.exe screen cap, please note that it still shows
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
hxxp://imgur.com/WJs4ABY (please change hxxp to http)

Easy.
bon1025hk said:
hi, i am using Chinookgod's method to push the kindle.zip and gapps.zip to my kindle successfully
but when i try to 'swip to confirm flash', it shows 'Failed' ,
and E:Mount: Unable to find partition for path '/\sdcard\kindle.zip'
Error flashing zip '/\sdcard\kindle.zip'
Updating partition details..
below is the screen cap
hxxp://imgur.com/ecjcZZF (please change hxxp to http)
what should i do? plz help :crying:
below is my cmd.exe screen cap, please note that it still shows
LIST OF DEVICES ATTACHED:
123456789ABCDEF RECOVERY
hxxp://imgur.com/WJs4ABY (please change hxxp to http)
Click to expand...
Click to collapse
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.

Will it work for me?
I got backup of my rom in my sdcard but having the same problem when try to restore. stuck with no OS. Help
My Phone Lg lu6200

Still need help
Chinookgod said:
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Click to expand...
Click to collapse
I tried following your instructions and the directory came up. I then tried entering "adb shell" as a command and got the following:

Doesn't work for my Kindle HD 8.9...any help please?

I get an error closed closed

Chinookgod said:
Thats easy. You can fix this by doing a system wipe then do a factory data reset to prep the system.
Click to expand...
Click to collapse
hi,
i have Kindle Fire HD 7" after some issues i try to flashing, voip all data and delete backup etc, my WTRP V.2.7.8.0 changed to v.2.6.3.1 and stuck in kindle fire logo and not connected to pc or not show storage in my computer.
please help me and restore my kindle fire tate. thanks a lot (i am using Ubuntu 14.04 LTS)

[HOW TO]UnBrick - If you get a bad download and stuck with TWRP use adb push . . .

I wanted to try a new Kindle rom over at the developers section and downloaded a rom, connected the Kindle to the Windows 7 computer and dropped it into the Kindle to flash.
After the rom was flashed I discovered that there were lots of error messages and to make a long story short, the rom was a bad download.
I could not get the Kindle to be recognized with the Windows 7 computer after the flash, meaning that I could not drop in a rom to the Kindle because the Kindle was not working and all I had to use was TWRP with out a decent or working rom to flash.
So I re-download the rom and then I could not get the rom into the Kindle.
The only resource that I had was TWRP 2.6.3.
Being stuck with COLOR="RoyalBlue"]TWRP 2.6.3.[/COLOR] I was able to fire up the ANDROID sdk and push the rom into the Kindle
Here are the steps that I took...
Download the Java SDK, you will need it without JAVA you can not get the Android SDK and the Android "adb" to work.
Download the Android SDK.
When you start up the Android SDK for the first time, ensure that you select the Android SDK Tools, the Android SDK Platform-tools: down at the bottom of the Android SDK Manager, select Extra folder with the Google USB Driver.
Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools\ the directory where the adb.exe was found and place all of your goodies there such as the rom or the gapps and such. This was conducted on a PC Win 7, but you could extract the adb.exe and place it anywhere you wanted because the adb had to be in the same directory as the files that you want to place into the Kindle via the push commands.
Uninstall the amazon drivers and disconnect the Kindle.
After the kindle was disconnected and no drivers were installed, start up the Kindle Fire Utility v0.9.9 and use it to install the drivers
Connect the Kindle to the computer and the magical moment happen for me right here. The PC noticed and recognized the Kindle for me. From here on it was all downhill
type in the adb commands
Type adb kill-server then enter.
Type adb devices then enter.
Once you see your device listed as 584398823829342343 then you can start the push command
The push the rom "adb push cm-11-20131230-1957-otter-sgt7.zip /sbcard/cm-11-20131230-1957-otter-sgt7.zip" This was very critical to add the slashes into the command. I had to try this 4 times before I figured it out. The forward slash denotes a folder in the scrips
The push the gapps "adb push gapps-kk-20131119.zip /sbcard/gapps-kk-20131119.zip"
disconnect the Kindle, then flash the rom and the google apps and let it do its thing
These were the steps that saved me and I may have missed one or two minor details. I was so driven that I could not give it. It took me 4 hours into the late evening hours but I was able to get the Kindle up and working.
I now love this Kindle even more.
The sideload command could have worked for me but there was not enough documentation found on Google or YouTube . It would be nice iif someone could write up a sideload tutorial . . . Or maybe I will write up a push tutorial.
The Rom is solid and I cant get enough of it after this soft-brick accomplishment that left me scared wondering who was going to save me.
It was then that it kicked in 2:00 AM, there is no Calvary coming in to save the day . . .
I would have to learn these applications such as the Android SDK and how to use the adb commands.
Yes, Google did help me big time and the resources here at XDA.