Wednesday 27 July 2016

Anyone made a GT-N8010 or GT-N8013 boot from SD?



I know it's a dead platform pretty much but here goes... I have a mangled GT-N8010. It's been fine for years, I even rooted it and installed nerdyblonde's blissrom image middle of last year. All of a sudden out of nowhere I get bootloop.

It's got TWRP on it and I notice that most of the partitions mount ro even though I have selected for them to be rw. Then I realise that they mount rw to start with then transition to ro due to filesystem errors. From dmesg:


Code:


<6>[  806.261839] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[  806.455283] c0 Atmel MXT1664S 3-004a: P: id[0]
<6>[  806.519815] c0 Atmel MXT1664S 3-004a: R: id[0] M[0]
<3>[  806.527889] c2 mmc0: mshci_check_sbc_status cmd response crc error
<3>[  806.527925] c2 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<6>[  806.712682] c2 mmc0: recovering eMMC has been done
<3>[  806.712698] c2 brq->sbc.opcode=23,brq->cmd.opcode=18.
<3>[  806.712706] c2 brq->sbc.error=-110,brq->cmd.error=0, brq->stop.error=0,brq->data.error=0.
<3>[  806.712747] c2 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[  806.712755] c2 mmcblk0: not retrying timeout
<3>[  806.712813] c2 end_request: I/O error, dev mmcblk0, sector 6008856
<3>[  806.712908] c2 CMD aborting case in MMC's block layer ret 0.
<3>[  806.712916] c2 mmcblk0: CMD18, ARG=0x5bb018.
<3>[  806.712921] c2 packed CMD type = 0.
<3>[  806.712926] c2 mmc0, request returns 4.
<2>[  806.713152] c1 EXT4-fs error (device mmcblk0p12): ext4_find_entry:934: inode #2: comm ls: reading directory lblock 0
<3>[  806.713166] c1 Aborting journal on device mmcblk0p12-8.
<2>[  806.713176] c1 EXT4-fs (mmcblk0p12): Remounting filesystem read-only
<6>[  807.261975] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[  808.262113] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[  809.262253] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[  810.262394] c0 binder: 1803:1803 transaction failed 29189, size 0-0


So my internal eMMC is broken. The broken sectors are all over the place too so I don't think I can partition around them with a custom PIT:


Code:


end_request: I/O error, dev mmcblk0, sector 180224
end_request: I/O error, dev mmcblk0, sector 209968
end_request: I/O error, dev mmcblk0, sector 1818496
end_request: I/O error, dev mmcblk0, sector 4685696
end_request: I/O error, dev mmcblk0, sector 5709696
end_request: I/O error, dev mmcblk0, sector 5726210
end_request: I/O error, dev mmcblk0, sector 6008856
end_request: I/O error, dev mmcblk0, sector 30769024


I think I have the latest 4.4.2 Samsung bootloader so what I can do from the bootloader is limited (basically just boot into odin/download mode or into TWRP - no fastboot. Obviously due to failed eMMC I get loads of NAND failures trying to do things with odin.

I would like to make use of the tablet for another 6 months or so, so has anyone ever had any success booting one of these from SD card?



No comments:

Post a Comment