Related
Hi all!
Without much ado I am presenting you this repo for CM10 that lets you build somewhat functional CM10 ROM for Kindle Fire HD 8.9".
(Obviously this is not end-user friendly yet. If you don't know how to compile CM10 yourself, you are not a target audience for this yet, sorry. Many things don't work to make it viable main ROM yet anyway)
Build instructions (assuming you met all other CM10 build dependencies).
Download code:
Code:
mkdir android/system
cd android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/bowser-jb/local_manifest.xml
repo sync -j16
Build:
Code:
. build/envsetup.sh
lunch cm_bowser-userdebug
. vendor/cm/get-prebuilts
mka bacon
In the out/target/product/bowser output dir you'll have two important files generated:
recovery.img and cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip
For the first install only:
Step 0; Connect kindle to your computer, have android sdk installed and adb and fastboot in the path.
Step 1: (very important) Back up raw partitions from kindle responsible for recovery, boot and system.
(this requires root, though root-less installation is also possible, you will need the backups to return to stock!)
Code:
adb shell su -c "chmod 777 /dev/block/*"
adb pull /dev/block/mmcblk0p9
adb pull /dev/block/mmcblk0p10
adb pull /dev/block/mmcblk0p11
[code]
Save these block images.
Step 2: Prepare and run CWM:
[code]
rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\x00\x50\x7c\x80' >>/tmp/stack ; done
adb push /tmp/stack /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot bs=6519488 seek=1"
adb shell su -c "chmod 777 /cache"
adb push /path/to/cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip /cache/
adb shell su -c "echo 0 > /sys/block/mmcblk0boot0/force_ro"
adb shell su -c "echo -n 3 | dd of=/dev/block/mmcblk0boot0 bs=1 count=1 seek=4104"
fastboot flash recovery /path/to/recovery.img -i 0x1949
This last command will stop waiting for the fastboot device to appear. Do not unplug the kindle from USB.
Now reboot kindle: either power it off and on via it's GUI, or do adb reboot from a different terminal session (do not interrupt fastboot command still waiting!)
You'll see a "fastboot mode" on the screen and fastboot command started earlier will finally finish after writing the image onto the kindle.
Reboot kindle again via fastboot:
Code:
fastboot reboot -i 0x1949
This will reboot you into CWM recovery
Step 3: In CWM recovery, do install from sdcard and install the cm-10...zip file we transferred in the previous step.
the /data/ settings from stock amazon install are not compatible with CM10, but (very important)Do not reformat /data/ and /cache from CWM, this will result in a corrupted filesystem due to 3.0.21 kernel currently used by amazon not having necessary fs features!!!
Instead, clean /data via adb while booted to CWM:
Code:
adb shell "mount /data"
adb shell "rm -r /data/*"
Step 4: Now, installation is complete, you may reboot and it will bring you to your freshly-installed CM10 - enjoy.
(note by default this CM10 install starts with adb disabled, so you'll need to enable it in settings again).
How to reflash back to stock
Step 1: Remember where did you put those backups from step 1 during install.
Step 2:
Code:
fastboot flash recovery /path/to/mmcblk0p9 -i 0x1949
Now either connect a powered off kindle, or reboot an already connected kindle.
(note: I don't remember if stock rom is smart enough to wipe /data in this case or if it bootloops, so you might want to do rm -r /data/* before the final reboot)
once Kindle enters fastboot mode and recovery image is written, write the other two images too:
Code:
fastboot flash boot /path/to/mmcblk0p10 -i 0x1949
fastboot flash system /path/to/mmcblk0p11 -i 0x1949 # This one will take a few minutes
fastboot reboot -i 0x1949
Now you are back to factory stock.
Not so short video on the install starting from somewhere around step 3 for those who cannot perform the steps, but need to ensure this ROM is not for them yet:
Many things don't work yet:
- Sound
- Video playback
- Sensors (no rotation)
- Camera
- BT
- probably some other stuff I have not noticed yet.
Please do send in your patches/fixes.
Very cool, I'm gonna give this a try when I get some time tomorrow.
Thanks!
Neato(tm)!
Sent from my Nexus 4 using xda app-developers app
These are some amazing news!
Thanks a lot, verygreen. You are doing a really importaint thing. In my country no amazon services work, so the stock ROM is the biggest problem with Kindle 8.9.
Looking forward for the next builds!
Best regards.
Sorry if this is a stupid/annoying/heard it a million times please shut up already question, but does this mean anything the 7" variant?
xDecapitator said:
Sorry if this is a stupid/annoying/heard it a million times please shut up already question, but does this mean anything the 7" variant?
Click to expand...
Click to collapse
Eventually, this will translate to the Kindle Fire HD 7" as well. :fingers-crossed:
So, can you tell us what is the status of the build right now? What works fine, what doesn't? When can we see the first build to test?
Thanks for your answers and best regards!
This question belongs in general discussion not Development
Witcher_Kh said:
So, can you tell us what is the status of the build right now? What works fine, what doesn't? When can we see the first build to test?
Thanks for your answers and best regards!
Click to expand...
Click to collapse
I am not the first to answer your question in the following manner and I am sure I won't be the last. These developers spend hours of their free time developing code so that people like you and I can use it without paying unless it is through a donation to the developer. They typically don't have time to answer every person who asks when will the code be ready. so for you and others who are not developers your answer is:
"The next release will be ready when it is released and not until."
Early stages with such promise, hoping for a HD 7" inch variant
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
somdave2005 said:
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
Click to expand...
Click to collapse
Uh, wut?
somdave2005 said:
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
Click to expand...
Click to collapse
No - KF HD is a beautiful piece of hardware at a nice price, crippled by Amazons software. Where I live, almost all Amazon content is blocked anyway, so I won't lose anything. Amazon ebooks are basically the only content available to me, but that's just a matter of installing the Kindle app in CM.
eagerly watching and waiting... i havent got the stones to try it out now but ill test the first alpha! thanks for your work
Very very nice. Just waiting hopefully the developers will completed soon.
What about KFHD 7" ? If CM10 will work for KFHD 8.9", will work for 7" too or not? Sorry my english, please.
I am eager to try working this over to the 7HD but it might be premature. Do you guys think this software will still work with the fire 2 and 7HD?
Sent from my EVO using Tapatalk 2
craby1925 said:
I am eager to try working this over to the 7HD but it might be premature. Do you guys think this software will still work with the fire 2 and 7HD?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I thought i ask the same. I have KFHD 7" as well and want to try CM10 on it..
esox_hu said:
I thought i ask the same. I have KFHD 7" as well and want to try CM10 on it..
Click to expand...
Click to collapse
Just to clear this up.
I do not have Kindle Fire HD 7" and so I cannot try.
We've got a volunteer to try this at irc and bootloader unlock works the same way (as expected, but you need a different bootloader binary).
We were not able to get anything to show up on the screen after booting CM10, thought it appears the OS boots and behaves fine, backlight is on too.
Anyway, I'd much rather prefer people to buy Nexus 7, it costs the same as Kindle Fire HD 7, but is a much more open device with much more developer support.
If you need CM10 and further, get Nexus 7 and you'll be soo much more happier. You still can run kindle app on it to read your books if you so desire.
With this out of the way, let's not touch on the 7" device topic here anymore, it's for 8.9" development discussion only. Thank you for your understanding.
Yes, exactly.
verygreen said:
Anyway, I'd much rather prefer people to buy Nexus 7, it costs the same as Kindle Fire HD 7, but is a much more open device with much more developer support.
If you need CM10 and further, get Nexus 7 and you'll be soo much more happier. You still can run kindle app on it to read your books if you so desire.
Click to expand...
Click to collapse
Hear, hear!
The N7 is an amazing deal, has incredible specs with pretty much everything included, AND it's been made easily unlockable by the distributor. To anyone who wants continued access to devices in the future, there's no reason to support closed, locked systems.
So I just want to voice my agreement. If you're in the market for a 7" tablet, N7 > Kindle Fire HD 7".
Pass it on.
fattire said:
Hear, hear!
The N7 is an amazing deal, has incredible specs with pretty much everything included, AND it's been made easily unlockable by the distributor. To anyone who wants continued access to devices in the future, there's no reason to support closed, locked systems.
So I just want to voice my agreement. If you're in the market for a 7" tablet, N7 > Kindle Fire HD 7".
Pass it on.
Click to expand...
Click to collapse
I would have gotten the N7 but I wanted a larger screen.
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.....
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
i tried to install swype custom keyboard and it was a fail and when i rebooted as required after install i can't type in my password to unlock the screen because it says swype has stopped and i could just remove the app but i can't unlock my screen because i can't type in my password i tried ADB to remove the the app but that didn't work because it is a system app and it keeps on saying i don't have permission when i try the remove command and i tried to run the root command and su command on adb so i could remove it but it didn't work even though my kindle is rooted so now what do i do that is a alternative to a factory reset ( last choice )
You have to mount system as read-write before you rm anything on it. Run this first: /
Code:
su
mount -o rw,remount /system
rm oathandorfilenamegoeshere
that should do the trick
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You have to mount system as read-write before you rm anything on it. Run this first: /
Code:
su
mount -o rw,remount /system
rm oathandorfilenamegoeshere
that should do the trick
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
it didn't work it said not permitted can you give me some ideas of what i might have done wrong
darth45013 said:
it didn't work it said not permitted can you give me some ideas of what i might have done wrong
Click to expand...
Click to collapse
if you mounted the system with read-write permissions i don't see any reason you wouldnt be able to do that short of not su-ing into root first.
Technically you can just restore the system partition without touching the userdata, i know srt wouldnt touch it but not sure about kffa, and you should be able to throw it into fastboot with
Code:
adb shell "su -c 'reboot bootloader'"
stunts513 said:
if you mounted the system with read-write permissions i don't see any reason you wouldnt be able to do that short of not su-ing into root first.
Technically you can just restore the system partition without touching the userdata, i know srt wouldnt touch it but not sure about kffa, and you should be able to throw it into fastboot with
Code:
adb shell "su -c 'reboot bootloader'"
Click to expand...
Click to collapse
sends back error device not found
darth45013 said:
sends back error device not found
Click to expand...
Click to collapse
hows that possible, you were already able to access a adb shell before this.
stunts513 said:
hows that possible, you were already able to access a adb shell before this.
Click to expand...
Click to collapse
its the only command that does it to
Then don't run it that way, try it this way:
Code:
adb shell
su
reboot bootloader
I just combined them for convenience last time so try running it like that.
Sent from my Amazon Kindle Fire HD using Tapatalk
h i will have to re try tomorrow also is their a way to open the default keyboard or set it to default via adb
Might be a configuration file that could be pulled and edited on a PC, most android apps I see have a database of some sorts, I have had to analyze a few of them to figure out some things before for a friend.
Sent from my Amazon Kindle Fire HD using Tapatalk
i have found the adb command for changeing defaults but i don't know how to use it for kindle fire hd
stunts513 said:
Might be a configuration file that could be pulled and edited on a PC, most android apps I see have a database of some sorts, I have had to analyze a few of them to figure out some things before for a friend.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Does anyone know the adb shell commands to change the default keyboard could really use them or I will have to do a factory reset
How do I do a factory reset on my kindle? I'm having the same issue with keyboard not comin up on lockscreen
Sent from my SPH-D710 using Tapatalk