Develop Bugs

[Discounted] [ONSCREEN KEYBOARD] [20-oct-2012] Linux on your Kindle Fire

hi!
This is my manual for how to install linux on your Kindle Fire.
there are some some steps you should to do.
1. Assure you have working adb and fastboot.
2. Download the follwing files: kernel (http://narod.ru/disk/59236733001.2e2d29e2c7bd762bd285ddf22a9c3fc6/boot1.img.html), bootloader (http://www.mediafire.com/?l6aaqgsdkiksfw0), and linux rootfs (new image has been uploaded.[url]http://depositfiles.com/files/mkpjrbixe
) , COTR recovery (http://narod.ru/disk/59880845001.8639567518823dcc1a9e4d51161ad75b/recovery_CTOR.img.html)
3. unpack these files and place them to adb & fastboot directory
4. reboot your kindle into fastboot.
5. boot CWM recovery by fastboot boot recovery_COTR.img
6.it's very important step. be careful with your sdcard partition.
now you'll resize it and make partition for Linux installation.
type the following in command line (windows/msdos) (terminal (linux/mac)):
~$: adb shell
then parted /dev/block/mmcblk0
then resize
then 12
then 2309 (start?)
then 5680 (end?) (it takes some time to resize partition)
then mkpart 13 5680 7597
then mkpart 14 7597 7609
then type quit
then mke2fs -T ext4 /dev/block/mmcblk0p13
then parted /dev/block/mmcblk0 name 14 linuxboot
then parted /dev/block/mmcblk0 name 13 linux
after doing this do the following:
mount sdcard storage to computer
now you must format sdcard partition.
in Windows select "Format" in main menu.
then place deb.img file to storage (it also called sdcard)
after copying debian image select safely remove in tray, but don't disconnect your kindle from computer.
on the screen tap Unmount button.
then type in command line: adb shell
then cd /mnt/sdcard/
then dd if=/deb.img of=/dev/block/mmcblk0p13
it took me about 20 minutes.
after that reboot into fastboot and type the following:
fastboot flash linuxboot boot1.img
fastboot flash bootloader u-boot.bin
7. all done.
8. enjoy
videos of how-to:
http://www.youtube.com/watch?edit=vd&v=4DBELK0cCpI
http://www.youtube.com/watch?edit=vd&v=F-IjFgBVHVM
there are images and video:
http://www.youtube.com/watch?v=NEXxSxhLoOI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to:
Hascode
Seishuku
And others

If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium

rbeavers said:
If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
what does you mean by p`n`p?

rbeavers said:
If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
you should follow guide by seishuku to install this. i simply solved some causes for myself. i think that my vision of this debian setup is rather good.
i also working on touchscreen bug and wifi.
later i`ll add suspending by power button and ability to managing sound volume and screen brightness

I was downloading it. But it looks kind of hard to install
Sent from my Amazon Kindle Fire using XDA Premium HD app

Very good job .
Envoyé depuis mon GT-I9000 avec Tapatalk

partition layout
link to download deb.img: http://depositfiles.com/files/aq1vtxbr0
after downloading my image you should make the same partition layout.
simply reboot your kindle in fastboot and boot it from CWM recovery (it contains program parted( partition manager). you should know how to use it).
after repartitioning select "reboot into fastboot" in reboot options in "reboot options"
and flash debian partition with my image (i called mine as "linux"(flash command is: fastboot flash linux deb.img))).
also you must install the seishuku's bootloader http://www.mediafire.com/?l6aaqgsdkiksfw0
and make empty partition to flash kernel (it must be named linuxboot link to download is:http://upwap.ru/2675690) (partition number for debian should be 13!!!!)
you MUST flash bootloader ONLY after flashing debian image!!!
because every when you flash bootloder you update partition scheme in bootloader configuration.
MacBook-Aroslav:~ yaroslav$ adb shell
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 5680MB 3371MB fat32 media msftres
13 5680MB 7597MB 1917MB ext2 linux
14 7597MB 7609MB 12.0MB linuxboot
(parted)
after doing all this you`ll get fully working deabian tabletop
installing is easy)
enjoy)
just for fun.

a little later i`ll make a detailed guide how to install this if you have stock kindle.
it'll be simple, so beginners colud follow my future guide and install debian and make dualboot for android and debian

a little later i`ll make a detailed guide how to install this if you have stock kindle.
it'll be simple, so beginners colud follow my future guide and install debian and make dualboot for android and debian
I will continue to fix bugs and add features and improve performance

Please feel free to ask any questions about this topic

Someone needs to try booting Chromium on it!
BTW, you still need OTG, correct?

Jessical said:
Someone needs to try booting Chromium on it!
BTW, you still need OTG, correct?
Click to expand...
Click to collapse
yes of course.
you still need OTG. but. but. i`m working on wifi and touchscreen. also i want not to use OTG with kbd and mouse.

He would be nice if you could make a video about how to install it
Sent from my Amazon Kindle Fire using XDA Premium HD app

jsisaev said:
what does you mean by p`n`p?
Click to expand...
Click to collapse
I can flash it, and it works ;')
Sent from my MB855 using xda premium

rbeavers said:
I can flash it, and it works ;')
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
you can flash this using dd or fastboot. i recommend you to reboot in recovery, place deb.img to sdcard and do the folowing: open a terminal. do adb shell (your kindle must be in recovery). then change current directory to /sdcard and enter this: dd if=deb.img of=/dev/block/mmcblk0p13

Do you need a keyboard or can you use the on-screen one?

FroyoShark said:
Do you need a keyboard or can you use the on-screen one?
Click to expand...
Click to collapse
i'm searching onscreen keyboard.
at once i got touchscreen working correctly.

I`ll upload new image tomorrow

After installing it on my Fire, I have a few questions, One: Do you have the mouse bugout fixed? Two: Am I going to have to download a big IMG again? And three: Can you make a DSL port after this one is perfected?
Also, Can you fix it to support OTG please?

Starzie said:
After installing it on my Fire, I have a few questions, One: Do you have the mouse bugout fixed? Two: Am I going to have to download a big IMG again? And three: Can you make a DSL port after this one is perfected?
Also, Can you fix it to support OTG please?
Click to expand...
Click to collapse
otg is supported.
at once you may not to download new image. just do the following:
in file /usr/shrare/X11/xorg.conf.d/10-evdev.conf replace last section with the following:
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Option "SwapAxes" "yes"
Option "InvertY" "yes"
#Option "InvertX" "no"
Option "Calibration" "0 3950 0 2370"
#Option "IgnoreRelativeAxes" "yes"
Driver "evdev"
EndSection
after that reboot.
all done. you now have correctly working touchscreen

Unable to mount data & cache

Hi all, got my kindle fire brick. I think my partition is messed up. I bought a factory cable which able me to install twrp and i succefully(i guess) flashed energy ICS. But it prompt me "e:unable to mount '/data" e:unable to mount '/cache". I were to boot to normal boot it will just boot endlessly but i still can access to fff and twrp.i did some research on repartitioning for kindle fire but i need some guidance. Help is much appreciated
Sent from my GT-I9100 using xda app-developers app

Usually this is a fairly bad indication but do this go to the mount section in twrp and make sure there are no checks in the boxes of data and system if so uncheck them, I know you said data and cache but this should have a check in the box then try a reboot also were you previously using cwmr? If so you may have been bitten by the bug a very unsightly one that generally means the death of your kindle unless you know how to repartition around a broken emmc. What did you do prior to this that caused this to happen?
Also energy is not the best for good mounting just saying...

I was using fireparted to backup my partition when my pc suddenly shut down. Thats when everything screws up. Also my data and cache are not able to check or uncheck. I hope theres a kind soul to guide me through this process
Sent from my GT-I9100 using xda app-developers app

If you ask me I would say its toast but maybe someone knows a way to restore factory partitions I know many are looking for a solution for thier parts only kindle....

From what I understand...
Code:
fastboot oem format
...will rewrite your partition table to stock. And as long as you haven't messed with the partition sizes, your data will stay intact.
Enter:
Code:
shell cat /proc/partitions
To get a list of your current partitions and sizes to check to see if they even exist to begin with. And if so, it's likely just a case of broken or missing mountpoints.
Now, whether or not "fastboot oem format" will restore broken or missing mountpoints, I couldn't tell you for sure; I've never had to try it. But in your situation, it probably couldn't hurt to try.
You can also recreate mountpoints manually if needed.
[Edit:] It has just been explained to me that "fastboot oem format" won't do anything about mountpoints.

Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?

dean11 said:
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?
Click to expand...
Click to collapse
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.

kinfauns said:
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.
Click to expand...
Click to collapse
OH MY GOOOOD!!!! MY KINDLE IS ALIVE!!!! THANK YOU SO MUCH @kinfauns!

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!

june12 said:
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!
Click to expand...
Click to collapse
I don't know who or what did that to your partition table, but partitions 10-12 are not right. It looks like mke2fs is complaining because your userdata partition is only ~178KB. I'm also a bit concerned that you've extended the media partition as far as you have. You might have some additional problems there.
The easiest way for you to get started on a fix is to get into fastboot mode with FFF and run...
Code:
fastboot oem format
That will bring your partition table back to stock, so you can run those mke2fs commands to remake those filesystems on the two partitions. You'll also have to remake the media partition in parted. You can find some instructions on how to do that here...
http://forum.xda-developers.com/showthread.php?t=1658885

Hey,
My current ROM is fine, but I can't mount data & cache in TWRP.
Nothing happens when I click mount data or mount cache in TWRP 2.6.3.1
I reflashed twrp two times and checked the md5sum.
When I try to backup my rom:
When I try a factory reset:
This is what I tried in fastboot:
Code:
fastboot oem format
...
OKAY [ 0.064s]
finished. total time: 0.065s
fastboot oem idme bootmode 4000
...
OKAY [ 0.081s]
finished. total time: 0.081s
fastboot reboot
rebooting...
finished. total time: -0.000s
adb shell cat /proc/partitions
major minor #blocks name
7 0 8348 loop0
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
179 64 512 mmcblk0boot1
179 32 512 mmcblk0boot0
254 0 8347 dm-0
The parted command isn't working for me.
I have never repartitioned them as far as I know.
Wha't wrong with my partitions?

Still Stuck on TWRP, but now able to see device via Linux!

Hey all,
So I was able to run KFU and it got me stuck on the boot screen. Got help with that and was able to run KFU again but it got stuck on removing boot check and now I'm stuck with the TWRP homescreen.
My device was recognized in device manager but in the KFU it says ADB Status: Offline and Boot Status Unknown. ADB Device List is empty.
I am unable to mount the device from TWRP it keeps failing. I am also unable to mount the sdcard partition what-so-ever.
Pooch sent me info on how to boot up via usb drive into Linux (Mint) and I can find the device in the adb device list but I am not familiar enough with Linux to know how to push the ROM to the device as well as a better/newer version of TWRP. Any help in this would be greatly appreciated. Thanks.

I sent you full instructions on how to proceed in a pm the reason I chose that system is because its nice and small it will get you going.. you only have 150 mb to work with follow instructions and you should be fine

Issues persist
Hello! So, I was able to detect my device via adb in Linux with the help of ThePooch. (thanks a bunch!!!) However we have a small problem.
I am unable to mount my SD Card partition in TWRP at all. I wasn't sure why so we tried a bunch of stuff: We tried pushing a ROM, We tried mounting it via adb in terminal on Linux... We tried "fastboot oem format"... We tried adb shell echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
We tried updating the recovery to TWRP 2.2.2.0.
We tried a lot of things however we were very unsuccessful in this and I am still unable to click "Mount SD Card" in TWRP or format it or wipe it.
What's confusing is that I was able to push files (zips) to the sd card temporarily and see them when we click "install" on TWRP however they fail to install and anything pushed to the sd card is, or course, erased on rebooting.
Really don't know what to do at this point as I am at a loss and would appreciate any assistance in this. Thanks so much!

Boot into recovery and enter:
Code:
adb shell
parted /dev/block/mmcblk0
print
...and post the results here.

soupmagnet said:
Boot into recovery and enter:
Code:
adb shell
parted /dev/block/mmcblk0
print
...and post the results here.
Click to expand...
Click to collapse
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB media

hmm wish I knew what I was looking at it looks to me like some things still exist even after a full wipe if I`m reading it correct glad soup knows what to look for

sphinxdog said:
Really don't know what to do at this point as I am at a loss and would appreciate any assistance in this. Thanks so much!
Click to expand...
Click to collapse
I've ran into this a couple of times and what I usually do is to delete the "media" partition, create it again with parted, name it "media", and then finally let the stock Kindle Fire recovery repair it. You may be able to skip the delete/create part and just boot into the stock recovery to see if it can repair it.

probably would work if in fact he had a working system but there isnt a bootable one at least..

Code:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB media
Thepooch said:
hmm wish I knew what I was looking at it looks to me like some things still exist even after a full wipe if I`m reading it correct glad soup knows what to look for
Click to expand...
Click to collapse
The 'parted' program manipulates the partition table, which basically tells the device how the storage partitions are laid out. The 'print' command used to obtain the output above just displays the information stored in the partition table. I set the output in CODE so it's easier to read. The bottom portion of the data is the more interesting part and you can see the column names there...
Number - This is the partition number. You may have seen "/dev/block/mmcblk0p5" in the past referring to the recovery partition. That number after the letter 'p' refers to the partition number.
Start - This is the offset value for where the partition begins.
End - This is the offset value for where the partition ends.
Size - This is the size of the partition calculated by the difference of the two offset values above. Imagine a ruler where your "Start" offset is the 1 inch tick mark and your "End" offset is the 6 inch tick mark. The "Size" between the tick marks... 6 - 1 is 5.
File system - This is how the partition has been formatted... ext4 is a commonly used filesystem for linux. It's blank if parted doesn't recognize the filesystem type or none has been specified.
Name - The name given to the partition. You'll recognize some as ones you've used to refer to these partitions in fastboot. FYI, userdata typically gets mounted to /data and media gets mounted to /sdcard.
Flags - Used to indicate special characteristics of the filesystem.
The significant part of the output above is the missing filesystem for the media partition. It should have a fat32 filesystem. I'll leave it to soupmagnet to explain how to fix it.

kinfauns said:
The significant part of the output above is the missing filesystem for the media partition. It should have a fat32 filesystem.
Click to expand...
Click to collapse
As always, kinfains is correct. I've dealt with an issue similar to this on my own device pretty recently, so I knew immediately what we'd be dealing with. So you're going to remove, recreate and repartition your sdcard and then you'll be all set. Needless to say, any data on your sdcard will be lost, if it isn't already. Not to worry though, considering everything you have gone through up until this point, this part should be pretty painless.
Code:
adb shell
parted /dev/block/mmcblk0
rm 12
mkpartfs primary fat32 2309 7690
name 12 media
quit
mount /sdcard
exit
adb reboot
You may not need to reboot, but in my case, I did. You'll then be able to mount your sdcard over USB, or use "adb push" to transfer a ROM to flash in recovery. Just remember to wipe System and "Factory Reset" in recovery first, or you may very well find yourself in the exact same situation as before.
Have fun.

SUCCESS!!!! That took care of it! And I was able to load up the ROM with no problem. Thanks for all the help ThePooch & SoupMagnet!!!
Sent from my Kindle Fire using xda app-developers app

[Q] Pulling my hair out over Dual Booting!

Ok, I'm 90% of the way to getting my Kindle exactly how I want it, but I'm getting stuck at the last hill. Let me take you through a step by step of what I've done, and then what I want to do, and lets see if I can get some help and finally get this thing working!
I bought my 1st Gen Kindle a year after it came out, and immediately rooted it. Within a month, I put some old version of TWRP on and flashed to a custom ROM. Since then I've purchased Amazon Prime and wish to be able to use my Kindle with it. this involves having a perfectly Stock, non-rooted ROM installed. Thus began my nightmare of trying to get it back into such a state.
After 3 hours of running down dead end paths, I finally ran the latest Kindle Fire Utility (0.9.9) and had to finally use COTR recovery to flash the 6.2.3 stock rom because I was getting all sorts of errors using TWRP.
Now I have a perfectly back to Stock Kindle, but I still want Gapps and Netflix, but without rooting my device to break video streaming. Solution? Dual boot!
Ran the TWRP installer, and then the FFF installer. Then ran the Dual Boot installer, choosing the option to prepare FFF for dual booting. Now my kindle has the FFF bootloader, can boot into Stock as the primary and can boot into TWRP Recovery. However, when I tried to flash an alt rom (SBloods' ROM found https://code.google.com/p/kindle-alt-roms-cm10-cm9-dev/downloads/list ) it says it completes successfully, however when I attempt to boot into the alterante boot, it just stays at the Fastboot Booting screen.
What do I need to do and/or use in order to get my alt ROM (or any alt ROM) booting properly?

asrrin29 said:
Ok, I'm 90% of the way to getting my Kindle exactly how I want it, but I'm getting stuck at the last hill. Let me take you through a step by step of what I've done, and then what I want to do, and lets see if I can get some help and finally get this thing working!
I bought my 1st Gen Kindle a year after it came out, and immediately rooted it. Within a month, I put some old version of TWRP on and flashed to a custom ROM. Since then I've purchased Amazon Prime and wish to be able to use my Kindle with it. this involves having a perfectly Stock, non-rooted ROM installed. Thus began my nightmare of trying to get it back into such a state.
After 3 hours of running down dead end paths, I finally ran the latest Kindle Fire Utility (0.9.9) and had to finally use COTR recovery to flash the 6.2.3 stock rom because I was getting all sorts of errors using TWRP.
Now I have a perfectly back to Stock Kindle, but I still want Gapps and Netflix, but without rooting my device to break video streaming. Solution? Dual boot!
Ran the TWRP installer, and then the FFF installer. Then ran the Dual Boot installer, choosing the option to prepare FFF for dual booting. Now my kindle has the FFF bootloader, can boot into Stock as the primary and can boot into TWRP Recovery. However, when I tried to flash an alt rom (SBloods' ROM found https://code.google.com/p/kindle-alt-roms-cm10-cm9-dev/downloads/list ) it says it completes successfully, however when I attempt to boot into the alterante boot, it just stays at the Fastboot Booting screen.
What do I need to do and/or use in order to get my alt ROM (or any alt ROM) booting properly?
Click to expand...
Click to collapse
Boot into recovery and enter the following commands:
Code:
adb shell parted /dev/block/mmcblk0
print
If the shell complains that 'parted' isn't installed, you can install it temporarily (until reboot).
1)Download 'parted' here: http://d-h.st/h81
2) place the 'parted' binary in the same directory from which you are entering your commands and enter the following:
Code:
adb push parted /sbin/parted
adb shell chown 0.0 /sbin/parted
adb shell chmod 755 /sbin/parted
Once you have 'parted' running and have entered the 'print' command to print the partition table, copy it and post it here.

Here's the output:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)

asrrin29 said:
Here's the output:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)
Click to expand...
Click to collapse
Well there's your problem. In order to have a dual boot, you have to have separate sets of partitions for both boots. You should go back to the instructions for dual booting and see what you missed.
Hint: you should have a total of 16 partitions.

Ok, so I redid the the dual-boot and set up the partitions, but now I am unable to copy files to the sdcard. I keep getting an Error: 80070057 the parameter is incorrect.
I tried installing SBlood's ROM and this time it restarts the recovery everytime it goes to initialize scripts. I then tried to get a different ROM (The MIUI one) onto the kindle by using ADB push, and I get an unknown error when trying to install it.

asrrin29 said:
Ok, so I redid the the dual-boot and set up the partitions, but now I am unable to copy files to the sdcard. I keep getting an Error: 80070057 the parameter is incorrect.
I tried installing SBlood's ROM and this time it restarts the recovery everytime it goes to initialize scripts. I then tried to get a different ROM (The MIUI one) onto the kindle by using ADB push, and I get an unknown error when trying to install it.
Click to expand...
Click to collapse
What did you use to set up your partitions? Did you create them manually or did you use the format-all.zip?

soupmagnet said:
What did you use to set up your partitions? Did you create them manually or did you use the format-all.zip?
Click to expand...
Click to collapse
I used the altrom-format-all.zip that came with KFU 0.9.9.

asrrin29 said:
I used the altrom-format-all.zip that came with KFU 0.9.9.
Click to expand...
Click to collapse
The error you are receiving may be a problem with Windows, and not necessarily the device or the dual boot.
Try the following and see if it makes a difference:
http://support.microsoft.com/kb/982736

soupmagnet said:
The error you are receiving may be a problem with Windows, and not necessarily the device or the dual boot.
Try the following and see if it makes a difference:
http://support.microsoft.com/kb/982736
Click to expand...
Click to collapse
The error only happens on the dual booted Kindle. I can plug any other android device, or my kindle when it's in single boot mode, and it doesn't happen.

asrrin29 said:
The error only happens on the dual booted Kindle. I can plug any other android device, or my kindle when it's in single boot mode, and it doesn't happen.
Click to expand...
Click to collapse
When you print your partition table, does the media partition have "msftres" beside it?

[GSI][ANDROID 12 STABLE] Android 12 and any GSI larger than 2.6GB

If you need help, feel free to post logs here. For more discussions about Android 12/GSIs join the telegram group!!
*REQUIRED FOR GSI* Follow the guide I made here to increase your system partition.
Click to expand...
Click to collapse
Download Android 12 Stable (Pixel 4a) GSI here: Direct link.
You don't need Gapps, they are preloaded.
Click to expand...
Click to collapse
Make sure to use Android 11 as base before flashing the GSI.
After that, you can install any GSI/flash any size Gapps without issue.
Reboot into fastboot mode.
Wipe your data partition: fastboot format:ext4 userdata
Clean cache and factory reset: fastboot -w
flash the GSI: fastboot flash system_a path/to/system.img
flash the GSI in other slot: fastboot flash system_b path/to/system.img
Test boot.
If it doesn't boot, download vbmeta for your device and flash in fastboot mode.
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot -w
Bugs:
No sound in call.
Some fixes:
Install GMS with adb install -r -d path/to/gms.apk to login to Google (not necessary anymore)
After flashing system image, don't reboot into system, immediately boot into TWRP and flash this file! This is necessary to disable encryption, so TWRP can boot successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download

@Dollscythe
Appreciate the resize guide, especially as i like a full GApps install
But the ROM is impossible to download it seems...
Note: Im able to download other files at SF
Update: Finally found a working mirror - for anyone else try the Gigenet mirror (Chicago), by clicking "Problems Downloading"

Dollscythe said:
If you need help, join the telegram group.
Follow the guide I made here to increase your system partition.
USE STOCK RECOVERY!!!!!!!!
After that, you can install any GSI/flash any size Gapps without issue.
Download Android 12 Beta 3.1 GSI here: Direct link
You don't need Gapps, they are preloaded.
Reboot into fastboot mode.
Wipe your data partition: fastboot format:ext4 userdata
Clean cache and factory reset: fastboot -w
flash the GSI: fastboot flash system_a path/to/system.img
flash the GSI in other slot: flash system_b path/to/system.img
Test boot.
If it doesn't boot, flash this file in fastboot mode.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
View attachment 5371367View attachment 5371395View attachment 5371423View attachment 5371425View attachment 5371427View attachment 5371429View attachment 5371431View attachment 5371433
Click to expand...
Click to collapse
Be great to know who's working who no on this rom. Thank you

irmas5 said:
Be great to know who's working who no on this rom. Thank you
Click to expand...
Click to collapse
For now FP and calling is not working. Everything else is perfect. This rom is for those who want to test new theming etc.
I am working on a fix for fp and RIL.

Wait... Does it for Pixel 3 but not Pixel 2 XL?

123哆3 said:
Wait... Does it for Pixel 3 but not Pixel 2 XL?
Click to expand...
Click to collapse
This guide is for pixel 2xl.
the GSI is ported from pixel 3 android S beta 3.1, but it works on pixel 2xl and all A/B devices.

Dollscythe said:
For now FP and calling is not working. Everything else is perfect. This rom is for those who want to test new theming etc.
I am working on a fix for fp and RIL.
Click to expand...
Click to collapse
it's necessary resize system partition? i'm scared to brick phone.

irmas5 said:
it's necessary resize system partition? i'm scared to brick phone.
Click to expand...
Click to collapse
for android 12 and some GSI, yes.

Update! With GMS, overlay, and fingerprint sensor fixes. We are getting closer!
And the users that had unbootable slot error, it should be fixed too if you flash vbmeta. Make sure to follow the fixes section too.
EDIT: RIL is fine, SMS is fine, we can even accept and take calls. But there's no sound! Any devs can chime in and help?

Dollscythe said:
Update! With GMS, overlay, and fingerprint sensor fixes. We are getting closer!
And the users that had unbootable slot error, it should be fixed too if you flash vbmeta. Make sure to follow the fixes section too.
EDIT: RIL is fine, SMS is fine, we can even accept and take calls. But there's no sound! Any devs can chime in and help?
Click to expand...
Click to collapse
tryed repart and get a bootloop. deleting partition disconected phone from laptop, Tryed flash via deuces script. showing installed, restarting, but never not booting. stuck at google logo. Can you help me please?

irmas5 said:
tryed repart and get a bootloop. deleting partition disconected phone from laptop, Tryed flash via deuces script. showing installed, restarting, but never not booting. stuck at google logo. Can you help me please?
Click to expand...
Click to collapse
show me your new partition table
boot to twrp
Copy parted to /sbin.
adb push path/to/parted /sbin
Enter shell mode.
adb shell
Change permissions of parted.
chmod 777 /sbin/parted
then do parted /dev/block/sda

Dollscythe said:
show me your new partition table
boot to twrp
Copy parted to /sbin.
adb push path/to/parted /sbin
Enter shell mode.
adb shell
Change permissions of parted.
chmod 777 /sbin/parted
then do parted /dev/block/sda
Click to expand...
Click to collapse
PS C:\platform-tools> adb push "C:\Users\irmas\Desktop\Pixel 2 xl\parted"/sbin
2250 KB/s (470788 bytes in 0.204s)
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 2853MB 2684MB ext2 system_a
8 2853MB 5538MB 2684MB ext2 system_b
9 5538MB 5546MB 8389kB pstore
10 5546MB 5546MB 524kB aes_a
5546MB 62.5GB 57.0GB Free Space
(parted)

I fixed.

irmas5 said:
PS C:\platform-tools> adb push "C:\Users\irmas\Desktop\Pixel 2 xl\parted"/sbin
2250 KB/s (470788 bytes in 0.204s)
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 2853MB 2684MB ext2 system_a
8 2853MB 5538MB 2684MB ext2 system_b
9 5538MB 5546MB 8389kB pstore
10 5546MB 5546MB 524kB aes_a
5546MB 62.5GB 57.0GB Free Space
(parted)
Click to expand...
Click to collapse
You didnt finish the partitions.
there's supposed to be aes_b, and userdata, etc.
you didnt follow the tutorial properly

plus, from what you sent me, your system is still 2.6 GB. you didnt properly finish deleting the partitions with 'rm' command. you stopped at aes_b.

Dollscythe said:
plus, from what you sent me, your system is still 2.6 GB. you didnt properly finish deleting the partitions with 'rm' command. you stopped at aes_b.
Click to expand...
Click to collapse
I restarted again everything from begining and now goes well. Now flashed proton aosp and booting. now showing
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 3269MB 3100MB ext2 system_a
3269MB 3269MB 459kB Free Space
8 3269MB 6369MB 3100MB ext2 system_b
9 6369MB 6379MB 9953kB pstore
10 6379MB 6380MB 999kB aes_a
11 6380MB 6381MB 999kB aes_b
12 6381MB 6391MB 9998kB align_parti
6391MB 6391MB 69.6kB Free Space
13 6391MB 62.5GB 56.1GB ext4 userdata
62.5GB 62.5GB 12.3kB Free Space

73sydney said:
@Dollscythe
Appreciate the resize guide, especially as i like a full GApps install
But the ROM is impossible to download it seems...
Note: Im able to download other files at SF
Update: Finally found a working mirror - for anyone else try the Gigenet mirror (Chicago), by clicking "Problems Downloading"
Click to expand...
Click to collapse
since opengapps is back, this guide is perfect to flash the highest gapps package possible. i have 4GB system partition XD

134|taimen:/ # parted /dev/block/sda
Warning: Device /dev/block/sda has a logical sector size of 4096. Not all parts
of GNU Parted support this at the moment, and the working code is HIGHLY
EXPERIMENTAL.
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p free
p free
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
What caused this？？？？

make sure to push parted again and give it chmod perms (even if you did it before.)

This tutorial only applies to Taimen (2XL).
Can this operation not be performed in win10 environment