![]() ![]() ![]() The boot path is stored in QFPROM (on the CPU) and it is something like /dev/block/sdb or /dev/block/sde. I spend lot of time try to figure out, but know nothingĩ008 bricks are not fixable on UFS NAND devices by booting from an SD card. # dd if=hyp.bin of=/dev/disk/by-partlabel/hypĭd: failed to open '/dev/disk/by-partlabel/hyp': No such file or directory I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Sector size (logical/physical): 512 bytes / 512 bytes sd 5:0:0:0: Assuming drive cache: write through scsi 5:0:0:0: Direct-Access Mass Storage Device PQ: 0 ANSI: 0 CCS usb-storage 1-1.3:1.0: USB Mass Storage device detected usb 1-1.3: new high-speed USB device number 13 using ehci-pci usb 1-1.3: new full-speed USB device number 12 using ehci-pci what have you done to get into the current 9008 aaa]$ sudo dmesg -c > /dev/null what have you done to get into the current 9008 state? did you unlocked the device by UsU or by the fastboot oem unlock command? If you know the firmware version you can identify here (click) what ARB it has. That means: what exact firmware was installed BEFORE you bricked it? Regardless of the above the thing is: you need to know the ARB of your current bootloader stack. So MAYBE you have really a bootloader stack of a h811 currently installed. There are users reported to be able to install a full h811 bootloader stack on it without bricking. To make it even more complicated the H810 itself is a special model. So what you see there means nothing at all. Its just a little text property which displays the model in Android settings. but.Īs you already found out: you CAN install a H811 system partition even on a H810.and even if not. So actually what wins is H810 as that is printed on your mainboard. You have a Frankenstein: check FAQ #21 here Omg why setting the size of your whole text to ultra big? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |