[Макс Меломан]

Here it is…
Tell me only one thing. How are You planning to flash it.

Attachments:

You must be logged in to view attached files.

[Макс Меломан]

Finally I figured it out that the problem with missing eMMC is semi hardware/software issue.
The main reason is incorrect behavior of so-called MMC sdhci-acpi host controller driver (kernel: drivers/mmc/host/sdhci-acpi.c)
MMC host controller serves as an operating buffer between NAND flash and host processor. Sometimes it happens that it ‘sticks’ in incorrect state and that results in incorrect I/O operations.
In the very case with Tbook 10 it gives incorrect output information about phisical size of NAND flash to BIOS when the system starts up. It gives to BIOS NAND flash physical size as big as 8GB of unallocated memory instead of 64GB and also makes impossible for eMMC to be correctly recognized by BIOS.
That’s why:
– UEFI can’t detect eMMC
– map -r in EFI Shell doesn’t show any mmcblk acpi device
– when You try to install original (not costomized) Windows 10 from WINPE bootable USB it shows You only 8GB of unallocated memory
This problem was recognized by Intel with its BayTrail platform and now with CherryTrail platform.
But the situation isn’t so bad as it seems. There are several methods to get MMC Controller back to the normal state.
The are soft reset and hard reset methods. To speak about soft reset methods they all about kernel programming and there are many patches but I am not familiar with kernel at all.
So I kindly ask someone with appropriate knowledge to advise me how to hard/soft reset MMC Interface Controller.

P.S. FYI (taken from another forum):
eMMC is a shortcut for embedded MMC.
MMC was a standard that came out before the SD standard came out.
Just google for MMC cards and SD cards and you will notice that MMC have some extra connections.
As hardly anyone used those extra signals, SD became more and more the standard as it was cheaper and easier to use (less signal lines).
So, the 3ds eMMC is basically an MMC card in a chip housing. This means that it has to be interfaced as an MMC card.
The Nand memory chips used in the chip aren’t directly accessible. The MMC controller is used for it’s interfacing.
The 3ds boots from the eMMC. What I was saying is that the 3ds might have an option to boot from it’s sd card as well.
Usually, this second boot option is used for recovery and can for instance be used for initial programming of the eMMC.

So, the eMMC controller isn’t containing scripts. It’s usually a small arm processor that simply takes care of the interfacing between the
MMC protocol and the flash memory chips. The gateway bricks were caused by intenionally locking the eMMC.
The methods to do this are clearly documented in the MMC protocol. They are intended to protect the contents of the device.

So, whenever the eMMC is locked or the nand contents are corrupt, if you could boot the 3ds from another device, you could undo the eMMC problem.
The controller isn’t blanked. It’s simply put in a locked state that requires a passkey to return to normal.
The recovery method used is called “force erase” It allows to remove the lock without the passkey but erases the device so that it’s previous protected contents are gone.

Attachments:

You must be logged in to view attached files.

[Макс Меломан]

Martin Boni wrote:

Hey guys, I rooted my tBook 10…

When completed I had root access. Just thought I would share

Thank You for sharing. It worked for me like a charm. Nice work.

P.S. You can use recovery.img (attached below from here http://bbs.teclast.com/thread-748443-1-1.html) instead of TWRP-X80-pro.img as it has touchscreen fuction and do not need OTG and mouse.

https://drive.google.com/open?id=0BxR2a98hqEyVSG5mVE9UZVAyWUU

 

[Author]

Posts