Related
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.
ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Thanks Haschode - worked first time
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
Blimey - a little less aggressive would be good!
If adb is not recognising your device perhaps the drivers are not installed properly as it worked fine for me first time.
Assuming you have the android sdk installed, if you need help installing the drivers look at posts 7 and 8 in this thread.
Im still on stock rom rooted has 2nd bootloader and CCW
try to back up but I got this when i try to pull
D:\sdk\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
D:\sdk\sdk\platform-tools>adb pull /sdcard/boot0block.img
remote object '/sdcard/boot0block.img' does not exist
Any thing i did worng? and boot0block.img is not in my sdcard folder
Thanks advance
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
Depending on your setup & your environmental variable paths, you may have to launch the CMD window from your Android SDK folder. Depending on what version of the SDK you are using, it may be in platform tools for the older sdk, or in X:\Android\system\bin, where X equals whatever drive you installed the SDK on. It works from that folder every time for me & only sporadically from anywhere else.
Yes. Had same problem here.
I am on build 0511 at present and everything is good enough to me.
Since Hash reminded all of backup for one more image 0boot recently. Then I tried to connect to pc in ADB mode so I can backup it and push it to my pc in OS windows7. The enviroment for adb was good because I used same computer and system to install the second bootloader already.
At first I stuck with enabling ADB in my kindle but I eventually figure out how to do that. However, now when I hook my kindle to pc, the adb still doesn't work as a result adb.exe (command: adb devices) can not recognize my kindle device. At same time when my kindle connects to pc I found kindle is recognized as a removable device (MTP mode). And in kindle, in notification bar there are 2 items, one tells me that kindle is connect as Media Device and the other tells me ADB is enable. This is weird when both MTP and ADB are enabled at same time and I guess maybe this is the reason why pc can not see kindle in adb mode.
Then I tried to disable MTP (uncheck MTP in setting-storage-setting) to see whether ADB will work, I found I just can not do it, I can only switch between MTP and PTP rather than unselect both MTP and PTP.
Fastboot always works.
Appreciate if any help.
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire HD using Tapatalk 2
While you are figuring out the problem, you can still backup this boot0 by issuing the command from the kindle cmd terminal and copy it over to some place safe.
AlexAquarium said:
While you are figuring out the problem, you can still backup this boot0 by issuing the command from the kindle cmd terminal and copy it over to some place safe.
Click to expand...
Click to collapse
Did it as you said.
Thanks.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
CM10 cannot be detected with ADB devices
ryanhein said:
I tried to backup my device's 0boot however,
I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.
I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?
Thank you.
Click to expand...
Click to collapse
I am pretty sure the reason is that the Vendor ID in the Cm10 build is not 0x1949 (Kindle).
Before you flashed the Cm10. the Vendor ID was 0x1949 and after was not (Probably was google 0x18D1).
Unless your PC is setup to recognize the new Vendor ID, ADB and Fastboot will no longer work.
The good news is that if you loaded 2nd bootloader and TWRP, if you are in recovery, the recovery Vendor ID is 0x1949.
The solution is to wait until Hashcode modifies his CM10 builds to put the 0x1949 vendor ID back into the build.
This kind of thing happens more often than you would think and creates some issues after a ROM change.
Regards Jerry
@Hashcode
Just curious...is this something that was added to Amazon's code (intentionally, perhaps?), or is it just an unfortunate byproduct of making a mistake while attempting to modify the device?
Is it due to a recent update or had it always been the case?
soupmagnet said:
@Hashcode
Just curious...is this something that was added to Amazon's code (intentionally, perhaps?), or is it just an unfortunate byproduct of making a mistake while attempting to modify the device?
Is it due to a recent update or had it always been the case?
Click to expand...
Click to collapse
There is code in 1 of the bootloaders to erase the boot0 block and reset the info after many failed boots. And this info is so important that I felt it was worth keeping a backup of. Without it, you can never re-register the Kindle w/ Amazon services.
Sent from my XT894 using Tapatalk 2
So, apart from screwing people over, would there be any real need for such an addition?
Not to revive a old thread but how would one know if the boot0block had definitely been wiped or reset what can be done to check if it had been or not?
I read up on guides to fixing it, ordered a fastboot cable.
Back story: I stupidly wiped my entire KFHD, OS and all
Still can access TWRP, my question is, can it be fixed? Can i just plug my fastboot cable in and transfer CyanogenMod 10.1 and flash it?
Thank you for you help.
I think i can help you a little bit , did you try the adb sideload option?
if not , the only thing you need to do its send the .zip file via adb sideload and you are done
Use the factory/fastboot cable only to get into fastboot, but don't use it to enter commands or transfer files. Switch cables and use adb to transfer a new ROM to your sdcard
ThatLatinGuy said:
I think i can help you a little bit , did you try the adb sideload option?
if not , the only thing you need to do its send the .zip file via adb sideload and you are done
Click to expand...
Click to collapse
no. my kindle is wiped and I cannot connect it to my pc. It's detected but I can't find the empty folder to put stuff in
EDIT: Googled adb sideload and tried it out, my kindle isn't detected when i use the adb devices command. That's probably why it isn't working.
EDIT2: Fixed, many thanks to ThatLatinGuy.
RaptorYeshua said:
no. my kindle is wiped and I cannot connect it to my pc. It's detected but I can't find the empty folder to put stuff in
EDIT: Googled adb sideload and tried it out, my kindle isn't detected when i use the adb devices command. That's probably why it isn't working.
EDIT2: Fixed, many thanks to ThatLatinGuy.
Click to expand...
Click to collapse
You are welcome , and if you need something else just tell me
Can You Help Me?
I have a similar issue. It looks like the OS has been wiped from my Kindle Fire HD 7. My PC does detect it and I can see folders. They are empty, mostly. On start up I get "Kindle Fire". Then I get to a welcome screen with an android icon. I press start and it sits for a bit then a window pops up saying that there was an error. My PC does not detect my Kindle as ADB and it will not boot up in fastboot.
Rednival said:
I have a similar issue. It looks like the OS has been wiped from my Kindle Fire HD 7. My PC does detect it and I can see folders. They are empty, mostly. On start up I get "Kindle Fire". Then I get to a welcome screen with an android icon. I press start and it sits for a bit then a window pops up saying that there was an error. My PC does not detect my Kindle as ADB and it will not boot up in fastboot.
Click to expand...
Click to collapse
I think we need a little more information.
1. What were you trying to do when the OS disappeared?
2. Do you have a fastboot cable?
3. Did you back-up your Kindle stock images?
4. What do you want to achieve at the end? Stock OS or modified OS or what?
Did you follow the instructions for putting the kindle into ADB mode before the OS disappeared?
calkenneth said:
I think we need a little more information.
1. What were you trying to do when the OS disappeared?
2. Do you have a fastboot cable?
3. Did you back-up your Kindle stock images?
4. What do you want to achieve at the end? Stock OS or modified OS or what?
Did you follow the instructions for putting the kindle into ADB mode before the OS disappeared?
Click to expand...
Click to collapse
as calkenneth said we need more details if you want help , tell us what happened and who did you get wipe your os , then i will do my best to help you
Hi, I have a similar problem and was not sure whether to start a new thread or not.
I had tried rooting the 7HD and it only kind of worked.
It is still working for some things but not Netflix and Amazon video streaming so I would like to go back to the stock ROM. I have tried everything I have found online, and nothing is working. Unfortunately, the root I used did not include adding TWRP.
I just tried adb sideload as mentioned above but the instructions call for v1.0.029 or later and mine is 1.0.026 and I can't find a download link to that later version.
I have a fastboot cable and after four or five tries starting the 7hd, it will boot and stop at the Fatsboot but I can't do anything with it as it appears locked up.
With the standard cable I can see the Kindle on my win7pro-x64.
I have Superuser showing on the 7hd carousel.
When I plug the 7hd in, windows tries to install the drivers and then says, "drivers were not installed correctly. The Device Manager shows Kindle under "Other devices" but it has a yellow question mark.
...and when I run abd shell, it gets started OK, but hen says "Device not found," even though I can see the Folders with Windows Explorer.
Thanks for anything you can offer to get this unrooted.
Harry
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
CreamEggKing said:
I have the exact same problem as the OP, I tried sideloading but all I get is a bunch of gibberish adb related in the cmd window whenever I enter anything, i.e. adb push, adb device, adb sideload same stuff comes up in the cmd window but nothing is sideloaded onto the device. What am I doing wrong ? I was attempting to install paranoid android port, was wiping everything and in my eagerness I wiped the system/OS, can still enter twrp.... a bit of help would be appreciated!
Click to expand...
Click to collapse
It would he helpful to know exactly what messages you are receiving...
soupmagnet said:
It would he helpful to know exactly what messages you are receiving...
Click to expand...
Click to collapse
this is the message I recieve, a bunch of commands and explanation as to what adb commands do. :good:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I think either my xda app is glitching or that photo got resized so small the text is unreadable. But I am throwing a guess that the command syntax was wrong so adb threw up its default usage text. BTW here's a tip, instead of screen-shotting your PC, right click in the command prompt and press mark, it will let u highlight the text, when done highlighting, tap enter on the keyboard to copy, then you can paste the text here, preferably in code brackets if there is a lot. I find it funny most people don't know this considering how often most people use copy and paste now days, then again Microsoft didn't exactly label it very well. What exactly did you type into the command prompt?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
the pic came up small because it is a thumbnail to the larger pic which is in photobucket, didnt want to flood he page with an overly large photo, thanks for the pro tip! didn't know that but it shall come in handy in future.
I typed in adb sideload /pa_tate-3.90-20130801.zip and then got the following:
hope it helps! yes I'm aware my first name is in there, not bothered! )
C:\Users\Wil>adb sideload pa_tate-3.90-20130801.zip
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Click to expand...
Click to collapse
do I need to provide more detail ? because I'm pretty sure everything you need to know is right there. The OP solved his issue, would of been helpful if he said how?
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Everything we need is right there, I'm trying to figure out why its doing that be cause the syntax looks correct to me. I'll do some checking on mine, have to ask, u did put the file your trying to side load in the same folder as the adb command right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
doh!
Its always the simple things we forget to do! Will try it in the morning and let you know! Cheers bub.
I placed the file in the android sdk folder at C:/Android SDK still no joy, keep getting the same message pop up..... is there a specific folder within android sdk it needs to be in ? build tools ? temp ? platform-tools ?
On a side not Amazon has agreed to send me another one. Theyve asked that I return this one after I get the new one, question, would they be bothered if I didn't ? Or would they try to charge me for the price of a second one ? latter option seems more likely imho...
The adb command I believe is in the platform tools folder, put it in there and try it. Also just call amazon and ask them to cancel it and tell them you got it working, I doubt there would be any problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
yeah I figured it was the platform tools folder, still nothing, I have tried various syntax entries followed the guidelines laid out by twrp for sideloading, still no joy, same bunch of adb commands are displayed after enter.... I do not know what I am doing wrong, this is not my first time working adb or with rooted devices.....
Note: I would have posted this in the developement forum as I've tried following both threads. (These: http://forum.xda-developers.com/showthread.php?t=2271909 and http://forum.xda-developers.com/showthread.php?t=2128848). Everything works okay as far as CMD entries etc, and it boots up in fastboot, at which point KF First Aide says <waiting for device>, and the Kindle is just sitting on the fastboot logo. No errors or anything, it just sits there.
Holding power on the Kindle shuts it down, and it will boot up normally. But it doesn't look like flashing back to 7.2.3 is working, because it stills shows up as 7.4.6. (It is already rooted as well.)
Not really sure how to proceed from here, I'm trying to install CM10.2 on it ultimately.
Edit: Also, I did already make backups.
Sounds like the fastboot drivers aren't installing, once you see the fastboot logo, check the device manager for a device with a yellow triangle, if there is one its probably called tate-pvt or something like jem or otter2 then use the drivers in my signature by right clicking the device, hitting update drivers, and pointing it to where you extracted my drivers and once the the device is I stalled it should continue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sounds like the fastboot drivers aren't installing, once you see the fastboot logo, check the device manager for a device with a yellow triangle, if there is one its probably called tate-pvt or something like jem or otter2 then use the drivers in my signature by right clicking the device, hitting update drivers, and pointing it to where you extracted my drivers and once the the device is I stalled it should continue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Looks like that was it, it's working now. Now to install PAC Man ROM.
Thanks!
Okay new problem.
"6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
I'm at this issue, and when I run adb it opens a cmd window which does something(lots of text scrolls), and then goes away(cmd then closes.). So I can't type the command in. Any ideas?
Well adb is a command line tool, so if you want to use it you need to run it from a command prompt...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Halo_003 said:
Okay new problem.
"6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
I'm at this issue, and when I run adb it opens a cmd window which does something(lots of text scrolls), and then goes away(cmd then closes.). So I can't type the command in. Any ideas?
Click to expand...
Click to collapse
You need to actually type command in your run box to open a dos prompt. THEN you can do the adb commands. Don't just try an adb command from your windows run box. It will run adb without modifiers, give you the help screen and then quit because windows thinks the program ran and completed.
NapalmDawn said:
You need to actually type command in your run box to open a dos prompt. THEN you can do the adb commands. Don't just try an adb command from your windows run box. It will run adb without modifiers, give you the help screen and then quit because windows thinks the program ran and completed.
Click to expand...
Click to collapse
Okay so here's what I didreplace *'s with h.)
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_38_376_zps0b71405b.jpg
Once in cmd, type adb and hit enter. Binary version looks good.
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_49_904_zps374e53f3.jpg
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_46_102_zpsaa0f7ff7.jpg
But then when trying sideload it doesn't work.
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_38_20_363_zps989da0dd.jpg
Am I doing it wrong?
Any ideas on how to get it working?
Halo_003 said:
Any ideas on how to get it working?
Click to expand...
Click to collapse
Stunts write up should get you there http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Halo_003 said:
Any ideas on how to get it working?
Click to expand...
Click to collapse
I got the chance to check out your DOS screenies.
There is no such command called sideload in some ADB versions. Here are the basic ADB commands.
3. Basic ADB commands
ADB push (sends files to your phone) -- adb push c:\example.apk /sdcard/example.apk
ADB pull (Receives files from your phone) -- adb pull /system/app/example.apk c:\example.apk
ADB install (installs application) -- adb install c:\example.apk
adb shell (Begins shell connection with phone)
adb reboot (reboots phone)
adb reboot recovery (reboots phone into recovery)
adb reboot bootloader (reboots the phone into bootloader/the white screen)
adb remount (remounts the system)
4. Commands to run while in ADB Shell
cd (changes directories) -- cd /system/app
ls (lists all files in the directory) -- cd /system/app
rm (removes files) -- rm /system/app/example.apk
cp (copies files) similar to cat -- cp /system/app/example.apk /sdcard/example.apk
cat (copies files) -- cat /system/app/example.apk > /sdcard/example.apk
exit (exits shell) -- exit
Click to expand...
Click to collapse
You have to make sure the ADB you have knows what the sideload command is.
Yep thank you guys! I got it working with that like LE gave me. Much appreciated!
LinearEquation said:
Stunts write up should get you there http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Click to expand...
Click to collapse
Ah yes! That was it! I wasn't doing the cd command so that's the issue I was having. Thank you!
Hello all,
My Kindle Fire has been dead for a long time- by dead meaning un-used, no OS problem- As I'm trying to fix said issue, ADB will not take the Push/Sideload command. When attempted to execute the command, it simply gives me a string of what I can do with ADB. Any ideas?
are you trying to issue the command in recovery or when booted up?
when you type
Code:
adb devices
what does it say?
Prallday168 said:
are you trying to issue the command in recovery or when booted up?
when you type
Code:
adb devices
what does it say?
Click to expand...
Click to collapse
The device is in recovery when I use ADB. Just stuck on the boot screen, it's not recognized. ADB devices shows something like "ABC123 Recovery"
If it didn't accept the push command and gave you a list of commands then your command syntax was probably incorrect. Put a copy of the ROM in the folder the adb command is in and run:
Code:
adb push romname.zip /sdcard/
That should be the correct syntax.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If it didn't accept the push command and gave you a list of commands then your command syntax was probably incorrect. Put a copy of the ROM in the folder the adb command is in and run:
Code:
adb push romname.zip /sdcard/
That should be the correct syntax.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did as described and still ran into the same problem- Just the string of commands.
Sent from my DROIDX using xda app-developers app
Well I'm scratching my head here, unless maybe the filename was invalid I don't see why the list of commands are listing outside of typos and such, try a newer adb command maybe? You could always just download the SDK, or try the one in a tutorial I made I posted in a zip file, it should be fairly recent, just look at topics I made and you should see one about what to do when you can only boot into twrp, that's where in boosted it, and don't worry I haven't made that many topics so it should be easy to find.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app