[RECOVERY][prague][OFFICIAL][3.5.2]TWRP for Huawei P8 Lite 2017

Search This thread

DarkJoker360

Recognized Developer / Recognized Contributor
Oct 20, 2015
2,624
3,657
18
Aradeo
Official TWRP for Huawei P8 Lite 2017

Working
Code:
[CENTER]* Touchscreen
* Adb
* Backup
* Wipe
* File manager
* MTP
[/CENTER]

Not Working
Code:
[CENTER]You tell me
[/CENTER]

Installation
Code:
[CENTER]* put you phone in fastboot mode and type
"fastboot flash recovery_ramdisk <grab_here_the_img>"
* reboot
[/CENTER]

Download

Please support my work, it's very important! Thanks
DONATIONS

Regards !​
 
Last edited:

DunoCZ

Senior Member
Feb 21, 2016
174
46
Adoptable storage is not working, show sdcard but empty. (I wouldn't recommend putting something to SD card because it will on 99% overwrite existing stuff).
 

jsubiros

New member
May 21, 2009
1
0
I am doing with my p8 lite and the result is all the time same error: partition lenght

i have tried fastboot flash recovery file.img and fastboot flash recovery_ramdisk file.img this last says ok, but then when i reboot appear all the same

Is there any solution ????
Thanks.
 

DunoCZ

Senior Member
Feb 21, 2016
174
46
Nice job dude! Keep rocking :)
(Anyway this twrp won't recongnize my adoptable storage so....)

DMESG output
Code:
[  395.228881s][pid:249,cpu0,mmcqd/1]mmcqd/1 rw time:7228125 ms,write time:0 ms,read time:7228125 ms
[  395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 workload < 1%, duty 7228125, period 335947444373, req_cnt=4
[  395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 Read Throughput=21650 kB/s, size: 151552 bytes, time:7 ms
[  395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  395.244384s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[  395.324401s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[  395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  395.704528s][pid:325,cpu5,recovery]hisi_vibrator_enable,value=80
[  395.784545s][2020:08:10 14:22:16][pid:0,cpu5,in irq]hisi_vibrator_timer_func called
[  395.925598s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  395.925628s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  395.926483s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[  396.006622s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[  396.088073s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  396.088104s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[  396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[  396.088928s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80

Mount output when it's working
Code:
/dev/block/dm-0 on /external_sd type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/dm-0 on /sdcard type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
 
Last edited:

haky 86

Recognized Contributor
  • Oct 5, 2012
    3,447
    7,480
    Hama (Syria)
    DMESG output
    Code:
    [  395.228881s][pid:249,cpu0,mmcqd/1]mmcqd/1 rw time:7228125 ms,write time:0 ms,read time:7228125 ms
    [  395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 workload < 1%, duty 7228125, period 335947444373, req_cnt=4
    [  395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 Read Throughput=21650 kB/s, size: 151552 bytes, time:7 ms
    [  395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  395.244384s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
    [  395.324401s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
    [  395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  395.704528s][pid:325,cpu5,recovery]hisi_vibrator_enable,value=80
    [  395.784545s][2020:08:10 14:22:16][pid:0,cpu5,in irq]hisi_vibrator_timer_func called
    [  395.925598s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  395.925628s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  395.926483s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
    [  396.006622s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
    [  396.088073s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  396.088104s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
    [  396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
    [  396.088928s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80

    Mount output when it's working
    Code:
    /dev/block/dm-0 on /external_sd type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
    /dev/block/dm-0 on /sdcard type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)

    ofc, wrong file system, should be VFAT not F2FS
     

    DunoCZ

    Senior Member
    Feb 21, 2016
    174
    46
    well I see this : FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem

    it's mean wrong file system lol
    You never used adopted storage right?
    Here is output of fdisk.
    Code:
    :/ $ su
    :/ # fdisk -l /dev/block/mmcblk1
    Found valid GPT with protective MBR; using GPT
    
    Disk /dev/block/mmcblk1: 60456960 sectors,  848M
    Logical sector size: 512
    Disk identifier (GUID): d8cd974c-9971-4801-aa06-39559b5fa3c1Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 60456926
    
    Number  Start (sector)    End (sector)  Size Name
         1            2048           34815 16.0M android_meta
         2           34816        60456926 28.8G android_expand
    :/ #
    And even shrp have in fstab vfat for /external_sd, so it's not sdcard related problem, it's TWRP's partition support problem. And also SHRP mounts /dev/block/dm-0 not /dev/block/mmcblk1p1.
     
    Last edited:

    haky 86

    Recognized Contributor
  • Oct 5, 2012
    3,447
    7,480
    Hama (Syria)
    You never used adopted storage right?
    Here is output of fdisk.
    Code:
    :/ $ su
    :/ # fdisk -l /dev/block/mmcblk1
    Found valid GPT with protective MBR; using GPT
    
    Disk /dev/block/mmcblk1: 60456960 sectors,  848M
    Logical sector size: 512
    Disk identifier (GUID): d8cd974c-9971-4801-aa06-39559b5fa3c1Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 60456926
    
    Number  Start (sector)    End (sector)  Size Name
         1            2048           34815 16.0M android_meta
         2           34816        60456926 28.8G android_expand
    :/ #
    And even shrp have in fstab vfat for /external_sd, so it's not sdcard related problem, it's TWRP's partition support problem...

    exactly it has been disabled even on official berkeley twrp.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 11
      Official TWRP for Huawei P8 Lite 2017

      Working
      Code:
      [CENTER]* Touchscreen
      * Adb
      * Backup
      * Wipe
      * File manager
      * MTP
      [/CENTER]

      Not Working
      Code:
      [CENTER]You tell me
      [/CENTER]

      Installation
      Code:
      [CENTER]* put you phone in fastboot mode and type
      "fastboot flash recovery_ramdisk <grab_here_the_img>"
      * reboot
      [/CENTER]

      Download

      Please support my work, it's very important! Thanks
      DONATIONS

      Regards !​
      4
      New TWRP Update !

      * Fixed Adb
      * Re-enabled OTG Usb wipes

      Also I submitted for Official mantainership.

      NOTE: P10 Lite won't receive supports since I broke it, just use P8 Lite 2017 stuff.​
      3
      Hello from now the recovery is official !
      Grab latest builds from official website and enjoy :)
      1
      Use DC unlocker, you can buy credits via Google Pay... First Downgrade to Android 7 ... Then unlock bootloader

      You don't need to downgrade.

      ---------- Post added at 06:07 ---------- Previous post was at 06:05 ----------

      I got a FAILED remote: partition lenght get error, when flashing

      Do you know why?
      Yep you are probably flashing ramdisk_recovery and not recovery_ramdisk. This happens to me almost every time.