HELP - wiped my internal storage!!! - HTC Droid DNA

Moonshined my spare DNA thursday night. I've been trying out several ROMs. Tonight I wiped my entire internal storage by mistake. Sorry, wasn't thinking. Anyhow I can still get into TWRP recovery. I can get into HBOOT. I can get ADB to recognise my device. However I have not been able to PUSH or SIDELOAD a rom onto my phone. It will not boot into android. Any help would be wonderful, I'm really running out of ideas.

May it Help
sdamark said:
Moonshined my spare DNA thursday night. I've been trying out several ROMs. Tonight I wiped my entire internal storage by mistake. Sorry, wasn't thinking. Anyhow I can still get into TWRP recovery. I can get into HBOOT. I can get ADB to recognise my device. However I have not been able to PUSH or SIDELOAD a rom onto my phone. It will not boot into android. Any help would be wonderful, I'm really running out of ideas.
Click to expand...
Click to collapse
What I did was further up the thread, others have helped with this. I will explain though.
1. In TWRP, go to your Advanced Settings, then go ADB Sideload.
2. Swipe it to start.
3. Open CMD window in the folder platform-tools, located in your Android SDK.
4. Type in CMD -> adb sideload filename.zip (Obviously replace filename.zip with your ROM of choice.)
5. Not done yet, go back to the main screen.
6. Click install.
7. Click sideload.zip (If I remember correctly it is called this.) This will load up the sideload that was just created.
8. Reboot your phone and you should be on your way!
This was just a wrapup of everything, like you said, in case someone else may need it.
Note that I do not take credit for any of this, this was all put together from information provided by others in this thread
http://forum.xda-developers.com/showthread.php?t=2038366

finanandroid said:
What I did was further up the thread, others have helped with this. I will explain though.
1. In TWRP, go to your Advanced Settings, then go ADB Sideload.
2. Swipe it to start.
3. Open CMD window in the folder platform-tools, located in your Android SDK.
4. Type in CMD -> adb sideload filename.zip (Obviously replace filename.zip with your ROM of choice.)
5. Not done yet, go back to the main screen.
6. Click install.
7. Click sideload.zip (If I remember correctly it is called this.) This will load up the sideload that was just created.
8. Reboot your phone and you should be on your way!
This was just a wrapup of everything, like you said, in case someone else may need it.
Note that I do not take credit for any of this, this was all put together from information provided by others in this thread
http://forum.xda-developers.com/showthread.php?t=2038366
Click to expand...
Click to collapse
Okay, I'm in TWRP, advanced, ADB sideload. device is visible. I opened a command prompt in my folder [C:\android\ on computer] where sdk tools and Viper ROM are. Type in - adb devices - and I get...
C:\android>adb devices
List of devices attached
FA2C8S500897 host
Cool, device visible, then type in - adb sideload viperDNA_1.3.0.zip - and I get...
C:\android>adb sideload viperDNA_1.3.0.zip
Android Debug Bridge version 1.0.29
Then it spits out a list of adb commands and takes me back to my command prompt. What am I doing wrong?

sdamark said:
Okay, I'm in TWRP, advanced, ADB sideload. device is visible. I opened a command prompt in my folder [C:\android\ on computer] where sdk tools and Viper ROM are. Type in - adb devices - and I get...
C:\android>adb devices
List of devices attached
FA2C8S500897 host
Cool, device visible, then type in - adb sideload viperDNA_1.3.0.zip - and I get...
C:\android>adb sideload viperDNA_1.3.0.zip
Android Debug Bridge version 1.0.29
Then it spits out a list of adb commands and takes me back to my command prompt. What am I doing wrong?
Click to expand...
Click to collapse
Need to update your adb.exe, side load is a recent addition so older adb binaries lack it.
Tapatalked from my HTC DNA - Carbon

pio_masaki said:
Need to update your adb.exe, side load is a recent addition so older adb binaries lack it.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
:good: That was it. Thank you, both, very much.
Also would like to say sorry for starting a new thread. Thought I searched pretty good, guess I may have freaked out a little.
Thread moderators, feel free to delete this thread.

Related

Stuck In CWM Recovery Loop...

Installed latest version of CWM..made backup of original rom...Rebooted System...No problem...Flashed CM9 per instructions...Full Wipe...Played with it for awhile...Backed it up...tried to restore Stock Rom ...went into CWM loop...Read a lot of threads and I still have drivers and Asus is seen in Device Manager with ADB Interface...So I tried Command prompts for 1a...and what I get is 'adb' is not recognized as an internal or external command,operable program or batch file...
Am I typin the command right ???...I never used ADB before...Came over from Epic Touch 4g Forum here...and I only used Odin...Could someone give me a clue if on on the right path of Unbrickin this thing...
Thanx...
BTW its Unlocked and of course rooted...
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Hobbesian said:
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Click to expand...
Click to collapse
Yep it was a Nandroid Backup...Im not at all familiar with ADB ...Just Odin which I use Rooting Phones...Ill give it a try...This is drivin me nuts...Just cant get ADB to work for me thru commands...Ill definitely do what you suggest...Thanx a lot Ill let ya know what happens...
Still gettin this when I run a command prompt
adb is not recognized as an internal or external command,operable program or batch file..Says the same for fastboot...Am I typin the commands right...
Installed driver and extracted the files from the download to my c part of the drive...Do I have to open anything in the download folder inorder for it to work or just extract everything like I did...
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Help
ronny71 said:
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Click to expand...
Click to collapse
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
chrsbrrss said:
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
Click to expand...
Click to collapse
Extract it if you haven't already.... put your prime into recovery .... plug it into the pc... in device manager find the prime and update the driver manually... point windows to the driver and your there...
For adb... you need to download that too I use the one in the nvfashpack... so... you extract the file.. with the window open... press and hold shift then right click in the window (nvflashpack folder, where the adb.exe file is) and select open command prompt here. Now you can use the adb commands... if your trying to push a file...it is best to put it in the same folder (nvflashpack)

[Q] Sort of bricked phone.. What can I do?

I managed to accidentally flash the BLADE boot.img for CM10.1 to my phone before I transferred the ROM across to my SD card.
Didn't think this was a problem.. went into recovery to Mount USB Storage. Didn't work, so I flashed TWRP to see if it worked on there. No luck.
Tried performing a restore of the full working stock sense and wiped caches so I could try to transfer it over the OS. again no luck.
I've even tried pushing the .zip file to the sdcard using adb (run cmd as admin and use 'adb push ROM.zip /sdcard/ROM/') with no luck. It just tells me the device isn't connected. The drivers are definitely installed (fastboot is working).
I'm all out of ideas. If anyone could point me in the right direction, I'd be grateful. Thank you!
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Is there another way of accessing the SD Card through recovery?
No except adb, but that only works with twrp. Why not flash a stock rom, and copy the rom to the SD Card while booted into android.
Sent from my HTC One X+ using Tapatalk 2
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
NasaGeek said:
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
petedavison93 said:
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
Click to expand...
Click to collapse
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Kraizk said:
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Click to expand...
Click to collapse
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
petedavison93 said:
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
Click to expand...
Click to collapse
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type "adb kill-server" and then type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Kraizk said:
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Click to expand...
Click to collapse
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
petedavison93 said:
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
Click to expand...
Click to collapse
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Kraizk said:
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Click to expand...
Click to collapse
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
petedavison93 said:
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
Click to expand...
Click to collapse
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Kraizk said:
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Click to expand...
Click to collapse
Trying the sideload now
petedavison93 said:
Trying the sideload now
Click to expand...
Click to collapse
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Kraizk said:
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Click to expand...
Click to collapse
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
petedavison93 said:
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
Click to expand...
Click to collapse
You could flash the stock recovery and run the RUU
Kraizk said:
You could flash the stock recovery and run the RUU
Click to expand...
Click to collapse
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Although this still doesn't solve my problems with adb
petedavison93 said:
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Click to expand...
Click to collapse
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Kraizk said:
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Click to expand...
Click to collapse
Can't relock the bootloader without working drivers.. this is beyond annoying now ¬.¬
EDIT: Relocked but not enough battery to flash RUU. Do I just run the RUU from the computer while the phone is at the home menu in the bootloader?
I'm using a batch file to charge the device over night. Will try again tomorrow.

Please Help

my phone wont go past HTC starting screen.
How can i flash stock att rom ?
I am stuck. suggestions appreciated.
Why won't it? What did you do to get to this state? What did you flash?
The more details you give...the more likely someone will be able to help you!
well i have unlocked bootloader.
i flashed one mod for extended power menu and after that my phone wont go past HTC one screen so i wiped and did factory reset still phone wont boot.
I went in to recovery menu and formated system and now i dont know how to flash stock rom.
varuun said:
well i have unlocked bootloader.
i flashed one mod for extended power menu and after that my phone wont go past HTC one screen so i wiped and did factory reset still phone wont boot.
I went in to recovery menu and formated system and now i dont know how to flash stock rom.
Click to expand...
Click to collapse
Here is all you need to know.
HTC One FAQ
I take it you did not make a NAND backup?? Always advised to make a BU before flashing anything!
What recovery did you install?
shawman said:
Here is all you need to know.
HTC One FAQ
Click to expand...
Click to collapse
Somehow i can not access USB storage so in this case how can i put rom into internal storage?
varuun said:
Somehow i can not access USB storage so in this case how can i put rom into internal storage?
Click to expand...
Click to collapse
ADB Sideload it. Here's the stock Deodexed ROM I used when I had that problem.
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
wmg316 said:
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Click to expand...
Click to collapse
..... Is that..... Mike G.??? You're an Android Guy too!
That's me! Who is this?
wmg316 said:
That's me! Who is this?
Click to expand...
Click to collapse
Josh S. from Landmark
Small world!!
wmg316 said:
Small world!!
Click to expand...
Click to collapse
No kidding.
P.S TrickDroid is a pretty sweet ROM.
Hi
I am doing as you said but i am getting attached screen. its not working for me.
wmg316 said:
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Click to expand...
Click to collapse
Do you have TWRP recovery?
If so, did you boot device to recovery?
If so, did you then select Advanced, ADB Sideload...then swipe to start?
THEN...run the command adb sideload One_1.29.401.13_deodexed.zip
EDIT:
ADB Sideload does not work until you are in recovery, and select and run adb sideload within recovery.
Also, if you get device not recognized...run:
adb kill-server
adb start-server
then try adb sideload again...
i have clockworkmod recovery v6.0.3.1
I booted into recovery then selected install zip from sideload. but its not working as it suppose to. Am i doing something wrong?
varuun said:
i have clockworkmod recovery v6.0.3.1
I booted into recovery then selected install zip from sideload. but its not working as it suppose to. Am i doing something wrong?
Click to expand...
Click to collapse
"Fastboot erase cache"
when i checked log in to recovery its says that"failed to open adb driver control:no such file or directory"
and when i type adb devices it says
"
C:\fastboot>adb devices
List of devices attached
HT348W900356 host
"
Any clue?
I don't use CWM, so don't know anything about it. Try buying a USB-OTG cable, get a USB stick (USB flash drive) and put the ROM on the USB stick, connect USB stick to phone and mount USB-OTG in recovery. Flash from that. That's the only other thing I can think of.
Sent from my HTC One using Tapatalk 2
varuun said:
when i checked log in to recovery its says that"failed to open adb driver control:no such file or directory"
and when i type adb devices it says
"
C:\fastboot>adb devices
List of devices attached
HT348W900356 host
"
Any clue?
Click to expand...
Click to collapse
Do you have HTC Sync Manager installed? Do you have all the HTC Drivers?

Kindle HDX 7''. Pushing system update files - Android ADB Interface - Bootloop -

Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK,I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2

[Q] SDK and ADB

Ok, I'm just going to ask it...
How do I set up SDK and ADB on my 3rd generation HDX 8.9. I find quite a few sets of instructions from 2011 but nothing seems up to date. And android studio is installing the driver in amazon.com which seems weird.
This is the latest I tried--here
I've searched and searched--I've tried several of these with no luck getting the pc to recognize the kindle.
Please no hateful replies--I've been at this for 2 days and I or really wouldn't ask.
Links would be really useful.
Thank you
Unless you are developing, you do not need android studio, jdk, or anything else. All you need to to do is download the sdk.
From here I am going to assume you are on Windows. Probably win 8 or 8.1?
Extract the sdk to a folder where you have write access.
Now find the folder called platform-tools in the sdk folder.
Now, in the Windows explorer bar, select all the text and type cmd
If you do this right, it will open a command window in the platform- tools folder.
If that is confusing, you can go to the sdk folder and then open the command prompt from the start window. Then type cd and drag the platform-tools folder to the command window.
Right now, all the devs are crying, because these are lazy shortcuts, but they work and save you from adding this folder to your path which is better programmatically, but a bit more involved.
Anyway, now you are where you need to be so, type
Code:
adb devices
And you should see your device, but, you probably won't. Stay tuned...
Sent from my KFTHWI using Tapatalk
You don't need to install the whole Android Studio suite — just the SDK Tools will suffice.
As for the Kindle Fire drivers...
https://developer.amazon.com/appsan...ing-up-the-ADB-Driver-for-Kindle-Fire-Devices
So, hopefully you got either a printout of your device, or you got a blank line like...
Code:
List of devices attached...
This is because you do not have the driver installed. If you get another error, either you are in the wrong folder, or you did not enable and on your device.
Code:
To enable adb on your device, click on the serial number in settings>device options 5 times and it will give you the developer options. Enable adb is a toggle there.
Alright, now we need the driver. Go to device manager in your computer and delete anything that looks android or kindle in nature. Unhook your tablet and reboot.
Download the HDX toolkit from the developers error forum and try the install drivers tool in it.
Reboot.
Now, making sure you have enabled adb on your device, open up a command prompt in platform-tools, and try the command again.
Code:
Adb devices
You should see your serial number.
If you have any issues, report back. I may have skipped a step or two as I am giving these directions from memory.
Good luck.
~Leko
Whew! Thank you! Doing this now.
Will update
Did I say thank you?!!!!
Update...After extracting the sdk zip file, platform tools is not showing up.
Downloading the installer file now...
Update2...found platform tools
Oh, my bad, I'm on windows 7...
Update--
The kindle died..thanks for all the input! Greatly appreciated:good:
lekofraggle said:
So, hopefully you got either a printout of your device, or you got a blank line like...
Code:
List of devices attached...
This is because you do not have the driver installed. If you get another error, either you are in the wrong folder, or you did not enable and on your device.
Code:
To enable adb on your device, click on the serial number in settings>device options 5 times and it will give you the developer options. Enable adb is a toggle there.
Alright, now we need the driver. Go to device manager in your computer and delete anything that looks android or kindle in nature. Unhook your tablet and reboot.
Download the HDX toolkit from the developers error forum and try the install drivers tool in it.
Reboot.
Now, making sure you have enabled adb on your device, open up a command prompt in platform-tools, and try the command again.
Code:
Adb devices
You should see your serial number.
If you have any issues, report back. I may have skipped a step or two as I am giving these directions from memory.
Good luck.
~Leko
Click to expand...
Click to collapse
So I am stuck adb devices--the line is blank
--ADB is enabled
--USB debugging is checked
--kindle driver installed
--portable device deleted in device manager
--SDK is set up C:\Program Files (x86)\Android\android-sdk\platform-tools
The driver installed in a separate file in program files as amazon.com which looks odd to me.
Maybe my path is wrong?
Update I've tried the method found here but after 2 tries with reboots, I'm still getting MTP device and portable device->fire. Each time i see the last one I delete it, reboot plug in again and portable device appears.
I've also tried Amazon instructions here
Anyone have any ideas?
Thanks in advance!
It sounds like you are on the right track.
Unplug your kindle, delete the devices again, and try this file.
http://forum.xda-developers.com/showthread.php?t=2665683
Use it just to install the drivers. (That is all it can do for you).
Then open a command prompt.
And plug your device in.
.
If the drivers are installed correctly, the path only matters to get adb to work (which the blank line tells you it is).
Also, there is a chance the devices will show up the same after the correct drivers are used. Mtp is able to run aside adb, but on Win 8 anyway, not fastboot (don't worry about fastboot).

Categories

Resources