Someone has flashed the K7/KP2/3/KV to Android!

[boom1212]

In China,Someone has flashed the K7/KP2/3/KV to Android 4.4.2!

I send a New Kindle(K7) to him,and he done the work!So amazing!

when i get my K7 back,i compare the information when it boots, via serial,see the picture blow,the uboot has been modifyed by him.

OK,the left is the K7 which running Amazon OS 5.6.5 ,and the right,is the K7 running Android 4.4.2!

[Image violates Posting Guidelines for size - MODERATOR]

I find that the running Android one has a more boot process,it runs another "uboot-test" first,the kernel makes the kindle be recognized as "Android Bootloader Interface",so it can be flashed big system files.

Hit any key to stop autoboot:  0 
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   uboot-test
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    152020 Bytes = 148.5 kB
   Load Address: 88400000
   Entry Point:  88400000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...



U-Boot 2009.08-lab126 (12鏈30 2016 - 12:30:30)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   33 C, calibration data 0x5835065f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Bourbon PREEVT2 WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 062070C1526607OS
S/N: 90C6070652740A2Q
I2C:   ready
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
POST done in 1 ms
Battery voltage: 4160 mV

Entering fastboot mode...
USB speed: HIGH
Connected to USB host!

The Android 4.4.2 firmware download link is here ,download key is "t4ei"


Flashing!


Flash done!


So...the question is:
1.how to modify the uboot as above?
2.how to extract the uboot from my K7,if can do that ,i can share it for everyone.

[knc1]

We didn't have anything to do with that alteration.

You will have to get your support from your vendor.
There is no way we can guess what/where/how that vendor has populated their memory map of the device.

Start by requesting the full source code.
Under the terms of its license, that vendor must give you a copy on request.

[thatworkshop]

So you are saying that your KP2 is now running KitKat? legit?
What's working and what not?

[kaneorotar]

So it seems that with the correct u-boot flashed, any latest generation Kindle devices can enter fastboot mode and download the Android ROM and run it. Am I right?

I found some general article regarding u-boot:
https://boundarydevices.com/u-boot-u...-core-2gb-ddr/
https://boundarydevices.com/fastboot-on-i-mx/

But I suppose the 'memory map' in u-boot mentioned by knc1 is device specific so it is crucial for rebuilding the u-boot image?

Anyway, these are just some of my wild guesses. My apology if it doesn't help.

[knc1]

None of which changes the hard fact that the Kindles only have 256 Mbyte of RAM.
And that is the most that the board layout allows (the flash can be upgraded with the same board layout - not the ram).

You will note that the least amount of ram on the devices linked to is 1 Gbyte.

[kaneorotar]

Originally Posted by knc1

None of which changes the hard fact that the Kindles only have 256 Mbyte of RAM.
And that is the most that the board layout allows (the flash can be upgraded with the same board layout - not the ram).

You will note that the least amount of ram on the devices linked to is 1 Gbyte.

There is a build option which has 512 MB RAM in the first link:
i.MX6Solo 512MB nitrogen6s_config

According to Wikipedia, Voyage and KPW3 have 512MB RAM.
The difference is that these two devices have i.MX6 SoloLite rather than i.MX6 Solo, not sure if this is a big problem.

KT2, on the other hand, does have only 256 MB of RAM (again according to Wikipedia). But the guy who did the porting managed to make Android work on KT2. So I guess it is possible to modify the build configuration file (flash_header.s?) by specifying the details of RAM in the device.

I found this: http://www.radiumboards.com/i.MX_6So...uide_A0-02.pdf

Which is a device that has CPU and Memory that are quite similar to KT2 and has u-boot running. Maybe this can help?

[knc1]

Originally Posted by kaneorotar

- - - - -
Which is a device that has CPU and Memory that are quite similar to KT2 and has u-boot running. Maybe this can help?

"and has u-boot running" ? What do you mean ?
You think maybe the KT2 does not?

Where is it listed that device can fastboot install a file larger than its native ram ?
Which is the O.P. intent.

[kaneorotar]

Originally Posted by knc1

"and has u-boot running" ? What do you mean ?
You think maybe the KT2 does not?

Where is it listed that device can fastboot install a file larger than its native ram ?
Which is the O.P. intent.

Well, thanks for pointing it out for me. As you can see I do have little to almost no knowledge about the Android/Linux booting process.

I knew that KT2 should also have u-boot but I thought maybe building the u-boot our own could enable the fastboot capability and allow it to magically boot into Android.

I guess it's time for me to stop picking up random article from a simple Google search and posting it here. This is clearly not a simple problem, otherwise people would have solved it long time ago.

P.S. You seem to doubt the authenticity of this 'hack', but the guy who did it has been selling his service online for a few months. Quite a few people sent their Kindle to him and got them back with Android running. There are videos and pictures so I tend to believe it is true.

[knc1]

Originally Posted by kaneorotar

Well, thanks for pointing it out for me. As you can see I do have little to almost no knowledge about the Android/Linux booting process.

I knew that KT2 should also have u-boot but I thought maybe building the u-boot our own could enable the fastboot capability and allow it to magically boot into Android.

We do have a custom copy of u-boot posted for the series 5 devices that includes fastboot.

But it **is not** modified to do 'read-back & verify' what it writes to flash, not is it modified to flash a file larger than available ram.

For the purposes it was posted for, those features where not needed.

Keep in mind that the series 5 devices have two (2) u-boot setups installed normally -
The tiny one, that runs in the SoC internal ram -
The large one (bist), the runs in the external ram.

You aren't automagically going to run Android.
You need to build an **ANDROID** kernel that includes the **AMAZON** hardware drivers.
**NOT** a small project (you will find several threads here where people have started to make that cross-breed kernel).

Originally Posted by kaneorotar

I guess it's time for me to stop picking up random article from a simple Google search and posting it here. This is clearly not a simple problem, otherwise people would have solved it long time ago.

We have addressed the problem here, numerous times.

Originally Posted by kaneorotar

P.S. You seem to doubt the authenticity of this 'hack', but the guy who did it has been selling his service online for a few months. Quite a few people sent their Kindle to him and got them back with Android running. There are videos and pictures so I tend to believe it is true.

I don't doubt that someone did it.
I just want to see them release the sources as required by the license.

The people at this site do not support Dorkan, because they abuse the terms of the Open Source, software licenses.

You can't expect the people here to support an un-released version of the Open Source kernel for Android nor the Open Source Android itself.

Everything you find here (done by our members, not just passers-by) is Open Source and the sources are published in public repositories.

When the Chinese learn to do the same, we might even help them.

But the fact is, there is very little experience in running an Open Source project among the Chinese.

So twobob and I set up a site for the purpose of collaborating with a Chinese manufacturer.
We would run the site and be technical advisors (for free) until the first completed project was marketed, and then turn operations over to the (then trained) Chinese manufacturer.

Part way through, the manufacturer bailed out.
But the site is still there and if this person who is abusing Open Source for profit wants to change their ways - the site is available:
https://gunshi.org

[boom1212]

Originally Posted by kaneorotar

So it seems that with the correct u-boot flashed, any latest generation Kindle devices can enter fastboot mode and download the Android ROM and run it. Am I right?

I found some general article regarding u-boot:
https://boundarydevices.com/u-boot-u...-core-2gb-ddr/
https://boundarydevices.com/fastboot-on-i-mx/

But I suppose the 'memory map' in u-boot mentioned by knc1 is device specific so it is crucial for rebuilding the u-boot image?

Anyway, these are just some of my wild guesses. My apology if it doesn't help.

it looks interesting! but idon't know how to do it with the following, so i think is there any easier ways to get the u-boot, which has been modified in my device, if we extract it as the file "xxx.bin", we can use the command such as"fastboot flash bootloader xxx.bin" to reach our object.

[bt4wang]

Originally Posted by boom1212

it looks interesting! but idon't know how to do it with the following, so i think is there any easier ways to get the u-boot, which has been modified in my device, if we extract it as the file "xxx.bin", we can use the command such as"fastboot flash bootloader xxx.bin" to reach our object.

In the zip file you pasted above, there is a file named 'loader.bin'. If you open it with any HEX editor, you will find some interesting stuff.



Now we need a brave man to flash this file to his pw2.

[boom1212]

Originally Posted by bt4wang

In the zip file you pasted above, there is a file named 'loader.bin'. If you open it with any HEX editor, you will find some interesting stuff.

Attachment 144639

Now we need a brave man to flash this file to his pw2.

Yes.I have noticed it ,just the boot process i have posted(the first picture),
it has another kernel prefer to boot first,which is named "uboot-test",and this kernel makes kindle to be recognized as "Android Bootloader Interface",and this kernel is 148.5KB ,the same as the file i post above named "loader.bin".
While the original kernel is named "Linux-3.0.35-lab126",it's about 2.3MB.
So,i guess that, the modified u-boot has two kernel totally, "uboot-test" boots first, and "Linux-3.0.35-lab126" boots later.
If we just only flash the "loader.bin" to bootloader, it will make Kindle to be brick! Notice it!
And the question is:
1.where should the "loader.bin" be flashed?
2.and the man how to make the "uboot-test" kernel boots earlier than the original one("Linux-3.0.35-lab126") ?
3.how can i extract the "modified u-boot" from my device directly?

Hit any key to stop autoboot:  0 
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   uboot-test
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    152020 Bytes = 148.5 kB
   Load Address: 88400000
   Entry Point:  88400000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[knc1]

You MUST have the sources at hand and work from them!!!
Really, you need the sources.
So get the sources from the author of your install, they are Open Source and by the terms of there license, must be available to you.

Hey, Kindles are not the first embedded system I have ever worked with. Some of us actually do this shit as a day job.

[Rizla]

The author may not be willing to release the sources. Is it possible to derive the necessary files from the user's install?

[knc1]

Originally Posted by Rizla

The author may not be willing to release the sources.
Is it possible to derive the necessary files from the user's install?

Willingness is not relevant, only the license terms.

Test it yourself:
Run a stop sign while driving, see if the police officer who stops you considers your willingness to stop when writing your ticket.

That can not be answered without having the device in-hand.