Related
TWRP for Huawei P10 Lite
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
Code:
[CENTER][URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P10%20Lite/Pie/TWRP/"]TWRP[/URL]
[/CENTER]
Credits:
@Pretoriano80
@haky 86
@OldDroid
@DarkDroidDev
Please support my work, it's very important! Thanks
DONATIONS
Regards !
Reserved
sorry for this request here, but please say me, will your stuff like this recovery and roms for p10 lite work on p8 lite 2017 because when im not wrong ive read some stuff work on different huawei phones with same chipsets etc, is it true?Big thanx, keep up your great work, have a nice day. Greeetz!!!
Great .. after testing on WAS-LX1A
i dunno why you're telling that mtp/backups doesn't work !
For me Backups work and internal storage / SD shown on windows normally
*Edit
Can't copy files
Thanks for your precious work .
-CALIBAN666- said:
sorry for this request here, but please say me, will your stuff like this recovery and roms for p10 lite work on p8 lite 2017 because when im not wrong ive read some stuff work on different huawei phones with same chipsets etc, is it true?Big thanx, keep up your great work, have a nice day. Greeetz!!!
Click to expand...
Click to collapse
I've installed RR and Bootleggers ROM's on P8 Lite 2017 and it works. All ROM's and Recoveries for hi6250 based devices (Kirin 655, 658, 659) will work on each other.
Hi, when trying to install your Android AOSP 9 pie ROM with this TWRP recovery... I get message
E3004: This package is for "hi6250" devices; this is a "warsaw"
please help?
GizmoTheGreen said:
Hi, when trying to install your Android AOSP 9 pie ROM with this TWRP recovery... I get message
E3004: This package is for "hi6250" devices; this is a "warsaw"
please help?
Click to expand...
Click to collapse
It could work if you edit the updater-script. In your rom zip open the updater-script file with text editor (Rom.zip/META-INF/com/google/android) and delete the first lines which are for the device verification including the ones giving the error output. This leads to no device check while flashing. :fingers-crossed: . For me it was really helpful in some cases.
NeoPreacher said:
It could work if you edit the updater-script. In your rom zip open the updater-script file with text editor (Rom.zip/META-INF/com/google/android) and delete the first lines which are for the device verification including the ones giving the error output. This leads to no device check while flashing. :fingers-crossed: . For me it was really helpful in some cases.
Click to expand...
Click to collapse
You would think when the same guy dev both Recovery and ROMS they would have that fixed? ^^;;
GizmoTheGreen said:
You would think when the same guy dev both Recovery and ROMS they would have that fixed? ^^;;
Click to expand...
Click to collapse
yeah, this is going to happen soon !
@DarkJoker360
How could I know if my device is hi6250 or warsaw?
chiduja said:
@DarkJoker360
How could I know if my device is hi6250 or warsaw?
Click to expand...
Click to collapse
hi6250 is the device chipset marking which matches multiple devices, warsaw is especially this device as in my case WAS-LX1A (WAS is warsaw). every warsaw is a hi6250 but not every hi6250 is a warsaw.
NeoPreacher said:
hi6250 is the device chipset marking which matches multiple devices, warsaw is especially this device as in my case WAS-LX1A (WAS is warsaw). every warsaw is a hi6250 but not every hi6250 is a warsaw.
Click to expand...
Click to collapse
Thank you, I asked it because I not capable of flash custom ROMs on my P10 Lite WAS-LX3 the problem is: after the clean installation of AOSP 9.0 mi phone get stuck in: your device is booting now... And then go to eRecovery not to TWRP and don't boot on system. I don't know what I have to do.
chiduja said:
Thank you, I asked it because I not capable of flash custom ROMs on my P10 Lite WAS-LX3 the problem is: after the clean installation of AOSP 9.0 mi phone get stuck in: your device is booting now... And then go to eRecovery not to TWRP and don't boot on system. I don't know what I have to do.
Click to expand...
Click to collapse
i had and still have the same results when trying to flash aosp. did you also decrypt your device before flashing any rom? could also be helpful in some cases.
NeoPreacher said:
i had and still have the same results when trying to flash aosp. did you also decrypt your device before flashing any rom? could also be helpful in some cases.
Click to expand...
Click to collapse
The first time that I tried to do the flashing I had to put my patron, but I've never did the decrypt, It's ****ty I tried a lot of "Solutions" but It doesn't worked.
ok alright the problembis that i tried to use "warsaw" codename instead of "hi6250" but it is not working for some reason, it is a flashing issue, and probably i have to revert my changes...
EDIT: before reverting my changes I wanted to try with LineageOS 16.0
Hi
Is there a prerequisite to use this recovery, I'm still using twrp 3.1.1-2 made by KingofMezi so still emui 5.0 but that recovery doesn't allow data backup because of the encryption. So I tried to flash yours it was ok in the command window but when I try to boot in recovery I get an error. I tried flashing again, downloading again and flashing but still doesn't work any idea?
I didn't want to upgrade the rom without a proper backup but none of the recoveries have been working.
Hi! Does someone try to install on a p20 lite?
@DarkJoker360 thanks for your work! Looks amazing.
I've never flashed TWRP before so I am bit nervous of bricking my phone!
I finally managed to unlock my bootloader by downgrading to EMUI 5.1.1, Android 7.0 (...). Will your TWRP work from this version? Is there any benefit/drawback of updating my phone to EMUI 8.0.0/Android 8.0.0 before flashing your TWRP?
P10Lite:
Model: WAS-LX1A
Build: WAS-LX1AC432B209
EMIU: 5.1.1
Android: 7.0
diy_solomun said:
@DarkJoker360 thanks for your work! Looks amazing.
I've never flashed TWRP before so I am bit nervous of bricking my phone!
I finally managed to unlock my bootloader by downgrading to EMUI 5.1.1, Android 7.0 (...). Will your TWRP work from this version? Is there any benefit/drawback of updating my phone to EMUI 8.0.0/Android 8.0.0 before flashing your TWRP?
P10Lite:
Model: WAS-LX1A
Build: WAS-LX1AC432B209
EMIU: 5.1.1
Android: 7.0
Click to expand...
Click to collapse
I asked myself the same question and tried to flash twrp on android 7.0 but it didn't work. I tried to upgrade to android 8 via erecovery but it failed. So i managed to upgrade it to B366 Emui 8 with dload (https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946) but i still could not flash twrp. So i entered erecovery mode again (press power, volume up & down for a few seconds) and with android 8 i could recover it to the official 8.0.0.376. After this step the flashing of twrp was finally successful. Thanks to darkjoker!!
New TWRP update is up !
Changelog
Code:
[CENTER]* Synced with latest TWRP source code
* FIxed flashing errors[/CENTER]
DONATIONS
Check OP for more info and download !
Hi,
Has anyone been successful in flashing the Android 10 GSI? Especially if you are using the Chinese RN8. Would like to hear how you've done it.
Thanks in advance.
Edit:
Managed to do it using resources from the Redmi Note 8 Discussions Telegram Channel. Just do a search for it and you'd likely find it.
Currently running PE Android 10 Unofficial. Some bugs but as this is a secondary phone not a big deal to me.
Same question here. I can see in phhusson's Github documentation that Redmi Note 8 is one of the devices which has successfully booted his AOSP GSI and I can't see any indepth guide and discussion on how it can be done here in XDA.
Some do claim that they were able to run it while here I am trying to make it work with no success. Be it AOSP 9 GSI or 10 it just won't work at all. I followed the GSI installation tutorial for the Mi 8 here with the same old results. The Redmi logo just keeps on bootlooping after following all instructions.
If there's anyone who were really able to boot these GSIs to their Ginkgos, do leave a reply here on what worked for you so that we can also give it a try. Much appreciated.
Hey,
I've try to flash GSI (phh-treble 10 V208) But the phone direct reboot in TWRP after that.... I wipe everything except vendor and flash gsi throught system but nothing work...
Also I have 8T (Willow) but it should works the same as Ginko... Any helps ?
I'm still waiting to get my ginkgo, but I found this, could it help?
HijoProdigo said:
I'm still waiting to get my ginkgo, but I found this, could it help?
Click to expand...
Click to collapse
Will definitely let you know how this goes
Lyves said:
Will definitely let you know how this goes
Click to expand...
Click to collapse
Stay safe over there! Just saw the news...
HijoProdigo said:
Stay safe over there! Just saw the news...
Click to expand...
Click to collapse
Thanks man. I'm miles away from the scene hence why I'm safe.
Going back, I still can't figure out how to make those GSIs work. I'll ask those on the Telegram group where that link originated from so that I can check whether someone was really able to make it work.
Good idea, I'm checking it too. Just got my RN8, and once I get back home I'll unlock it and give it a try.
Important! On this device run only Arm64 AB gsi rom!!!
https://t.me/ginkgo_dev/45
Vendor and kernel to flash gsi.
Giving a bump here as I've managed to do this. See OP for info.
Uwai yan said:
https://t.me/ginkgo_dev/45
Vendor and kernel to flash gsi.
Click to expand...
Click to collapse
Even trying that, I can't boot the Android 10 gsis :crying:
These days, I find many people asked how to enable fingerprint on Mi 8 PRO(runs GSI), so I'd write this thread to let you konw. I only test the phh's AOSP v217 with MIUI 12 20.5.21 vendor. If you want to use other GSI or other vendor you can also test whether fingerprint works on it by following these steps. However, these instructions may only works on Android 10.
I assume you are familiar enough how to flash GSI on Mi 8 pro. If you just a rookie, I recommand you to read this passage.(Of course, don't forget follow the instructions what I writed).
Follow these steps:
Step 1: Flash the MIUI 12 rom(20.5.21) by this TWRP.
Step 2: Find the GSI. ATTENTION: The GSI needs to be ARM64-AB!!! . I will recommand the phh's AOSP GSI v217(Because I only test it). Of course, you can chose other GSIs you like and test whether the fingerprint works on it.
Step 3: Flash it by the TWRP.
That's all. Hope you enjoy it!
Did the partition layout change with MIUI 12?
The Mi 8 Pro (equuleus) used to be a A only GSI image. I would like to try this... even if I replaced my Mi 8 Pro recently with a OnePlus 7 pro... mainly due to the fingerprint!!!
nealed said:
Did the partition layout change with MIUI 12?
The Mi 8 Pro (equuleus) used to be a A only GSI image. I would like to try this... even if I replaced my Mi 8 Pro recently with a OnePlus 7 pro... mainly due to the fingerprint!!!
Click to expand...
Click to collapse
I saw it on phh's AOSP wiki on github. That's what he said:
Why should I use GSI for A/B devices to some A-only devices? : On Android 9, Google changed the requirements and all devices shipped with Android 9 must use "system-as-root". Before this change, only A/B devices were system-as-root and GSI name was separated by A-only and A/B. For this historical reasons, you have to use GSI for A/B on the devices shipped with Android 9+.
If I try to flash the arm64-a Android 10 GSI then it can't boot and just go to the fastboot mode. However, if I flash Android 10 arm64-ab rom, it will succeed to boot. So I think we should use arm64-ab rom instead of arm64-a rom(at least on Android 10 we should do it).
Arm64-ab-floss OR Arm64-ab-go OR Arm64-ab-vanilla?
Sent from my MI 8 Pro using Tapatalk
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
Kimsimth said:
I saw it on phh's AOSP wiki on github. That's what he said:
Why should I use GSI for A/B devices to some A-only devices? : On Android 9, Google changed the requirements and all devices shipped with Android 9 must use "system-as-root". Before this change, only A/B devices were system-as-root and GSI name was separated by A-only and A/B. For this historical reasons, you have to use GSI for A/B on the devices shipped with Android 9+.
If I try to flash the arm64-a Android 10 GSI then it can't boot and just go to the fastboot mode. However, if I flash Android 10 arm64-ab rom, it will succeed to boot. So I think we should use arm64-ab rom instead of arm64-a rom(at least on Android 10 we should do it).
Click to expand...
Click to collapse
Arm64-ab-floss OR Arm64-ab-go OR Arm64-ab-vanilla?
Sent from my MI 8 Pro using Tapatalk
Jord5s said:
Arm64-ab-floss OR Arm64-ab-go OR Arm64-ab-vanilla?
Sent from my MI 8 Pro using Tapatalk
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
Arm64-ab-floss OR Arm64-ab-go OR Arm64-ab-vanilla?
Sent from my MI 8 Pro using Tapatalk
Click to expand...
Click to collapse
It up to you. You should chose the one you prefer. If you dont know what differences of them, just search it on Google. And all of them can succeed to boot.
Kimsimth said:
It up to you. You should chose the one you prefer. If you dont know what differences of them, just search it on Google. And all of them can succeed to boot.
Click to expand...
Click to collapse
Why must you flash MIUI12 first? I am running MIUI 11.0.5 Android 10...
Sent from my MI 8 Pro using Tapatalk
Jord5s said:
Why must you flash MIUI12 first? I am running MIUI 11.0.5 Android 10...
Sent from my MI 8 Pro using Tapatalk
Click to expand...
Click to collapse
Just because the fingerprint only works on MIUI 12 vendor. Just backup your data and flash the MIUI 12 rom.
Thanks for the guide !
you forget to mention we must had advance wipe the system partition -will mostly go into fastboot if not-
plus, anyone was able to pass safetynet ? my banks apps not working at all even after using magiskhide props
even whatsapp tells me this is an unofficial ROM
Aldwarii said:
Thanks for the guide !
you forget to mention we must had advance wipe the system partition -will mostly go into fastboot if not-
Click to expand...
Click to collapse
That I mentioned this thread
Aldwarii said:
plus, anyone was able to pass safetynet ? my banks apps not working at all even after using magiskhide props
even whatsapp tells me this is an unofficial ROM
Click to expand...
Click to collapse
U can do this by uninstall root. By click phh settings->Securize then you will rid out of root. However, you can use "MagiskHide Props Config" module to pass the safetynet.
1.) Install the "MagiskHide Props Config" module
2.) Reboot
3.) Run a terminal app and type:
su
props
4.) Set the fingerprint with the following keys (pressing enter after each):
1 -> f ->Any way u want(but I recommend you to chose the Xiaomi option), just follow the instruction of it.
5.)reboot.
And dont forget to uninstall the edxposed module first if you install it before.
Kimsimth;82980891
U can do this by uninstall root. By click phh settings->Securize then you will rid out of root. However said:
su
props[/B]
4.) Set the fingerprint with the following keys (pressing enter after each):
1 -> f ->Any way u want(but I recommend you to chose the Xiaomi option), just follow the instruction of it.
5.)reboot.
And dont forget to uninstall the edxposed module first if you install it before.
Click to expand...
Click to collapse
I need my root, so I can't uninstall it
I applied a factory reset, with internal storage wipe to ensure everything been deleted, then installed Magiskhide props and set the proper fingerprint "xiaomi mi 8 android 10"
hided google play services and store and framework in the MagiskHide
and now, wow ! it worked
but there is still 2 applications that haven't worked
1) STCpay
2) Alinma internet
may you please try these 2 bank applications to indicate if the issue only with me or not please ?
Aldwarii said:
I need my root, so I can't uninstall it
I applied a factory reset, with internal storage wipe to ensure everything been deleted, then installed Magiskhide props and set the proper fingerprint "xiaomi mi 8 android 10"
hided google play services and store and framework in the MagiskHide
and now, wow ! it worked
but there is still 2 applications that haven't worked
1) STCpay
2) Alinma internet
may you please try these 2 bank applications to indicate if the issue only with me or not please ?
Click to expand...
Click to collapse
The Alinma internet can be opened like this. However, the stc pay still cant be opened. You can read this passage "Time attack-based bypass script (Deprecated)" and follow it to make the app work I think. Good luck.
Btw I use the Lineage 17.1 rom now.
Kimsimth said:
The Alinma internet can be opened like this. However, the stc pay still cant be opened. You can read this passage "Time attack-based bypass script (Deprecated)" and follow it to make the app work I think. Good luck.
Btw I use the Lineage 17.1 rom now.
Click to expand...
Click to collapse
Tried that, but didn't get any benefit, even the worked apps had crashed after reboot :/
this GSI stuff is just a headache, no safetynet pass, android auto not working, device get very hot, battery drained faster -better than MIUI12 though- with no additional features upon MIUI at all
I think I will give the lineageOS a try tonight
Thank you my friend for you support all the way "big heart"
I don't know if anyone else uses this device anymore, but worth a shot! I've lost root on my UK MediaPad M5 SHT-W09 9.1.0.335 (C432E3R1P2).
I'm trying to get hold of the full FW download so that I can re-patch the ramdisk with Magisk. I can't find it anywhere, though, not even through Hawawei Firmare Finder - the latest SHT-W09 FW from there is 9.0.1.160, all later ones are SHT-LGRP2. Even then, the best matches for a FullOTA are 9.1.0.333 and 9.1.0.336 (only OTA for 335).
Is it "safe" to use the ramdisk image from what's on Firmware Finder? 333 or 336?
Or do I need to get hold of the 335 FullOTA for SHT-W09?
Thank you!
Needed too..
You can scan the huawei firmwares by yourself to get the exhaustive list. With something similar to :
Huawei firmware scanner
I ran a scan for you it should be finished in a few hours. You will be able to access it in the cameron.html link in this this thread (the data will auto-update once the server will be done) :
Huawei mediapad firmwares
emiliewgnr said:
You can scan the huawei firmwares by yourself to get the exhaustive list. With something similar to :
Huawei firmware scanner
I ran a scan for you it should be finished in a few hours. You will be able to access it in the cameron.html link in this this thread (the data will auto-update once the server will be done) :
Huawei mediapad firmwares
Click to expand...
Click to collapse
Amazing, thank you!
mroshaw said:
I don't know if anyone else uses this device anymore, but worth a shot! I've lost root on my UK MediaPad M5 SHT-W09 9.1.0.335 (C432E3R1P2).
I'm trying to get hold of the full FW download so that I can re-patch the ramdisk with Magisk. I can't find it anywhere, though, not even through Hawawei Firmare Finder - the latest SHT-W09 FW from there is 9.0.1.160, all later ones are SHT-LGRP2. Even then, the best matches for a FullOTA are 9.1.0.333 and 9.1.0.336 (only OTA for 335).
Is it "safe" to use the ramdisk image from what's on Firmware Finder? 333 or 336?
Or do I need to get hold of the 335 FullOTA for SHT-W09?
Thank you!
Click to expand...
Click to collapse
I see the FULL package for all of those versions via Firmware Finder. SHT-W09. Mind you, they changed the naming convention for this model's firmware.
sarichter said:
I see the FULL package for all of those versions via Firmware Finder. SHT-W09. Mind you, they changed the naming convention for this model's firmware.
Click to expand...
Click to collapse
Hi - Could you clarify this, please ?
I can see SHT-LGRP2-OVS and SHT-LGRP3-OVS versions of 9.1.0.335.
Are either/both of these compatible with SHT-W09 ?
Could you flash the full firmware rather than just the ramdisk ?
What about local variants (eg. C432 etc.) ?
Thank you.
emiliewgnr said:
You can scan the huawei firmwares by yourself to get the exhaustive list. With something similar to :
Huawei firmware scanner
Click to expand...
Click to collapse
mroshaw said:
Amazing, thank you!
Click to expand...
Click to collapse
Which firmware/ramdisk did you use ?
Thank you.
Just pick the SHT-LGRP2-OVS 9.1.0.335 (approved + full).
For magisk only flash the patched recovery_ramdisk (or stock to get back).
Also the system.img is useful to get back to stock from e.g. phhusson's GSIs Android 11 which is great BTW.
Stupid question, I lost root recently on my M5 and am trying to get it back. I have a US M5 so I'm still on Android 8.0.
When flashing the patched ramdisk image do you use the command "fastboot flash ramdisk Magisk_patched.img" or "Fastboot flash boot Magisk_patched.img".
Thanks,
Rick
emiliewgnr said:
Just pick the SHT-LGRP2-OVS 9.1.0.335 (approved + full).
For magisk only flash the patched recovery_ramdisk (or stock to get back).
Also the system.img is useful to get back to stock from e.g. phhusson's GSIs Android 11 which is great BTW.
Click to expand...
Click to collapse
oh cool, i was actually wondering if the M5 is still compatible with GSI roms so how is Android 10 and 11 GSI working on it? any experiences you can share would be great! my gf's M5 is currently on Android 9 GSI and its been running great.
jbmc83 said:
oh cool, i was actually wondering if the M5 is still compatible with GSI roms so how is Android 10 and 11 GSI working on it? any experiences you can share would be great! my gf's M5 is currently on Android 9 GSI and its been running great.
Click to expand...
Click to collapse
Both Android 10 and 11 GSIs work well for me. Some of the 11 ones are getting too large for the M5's system partition, although this can usually be overcome by deleting unneccessary VNDK files from the image.
See this comment by CAOS GSI developer eremitein.
yatsura2k said:
Both Android 10 and 11 GSIs work well for me. Some of the 11 ones are getting too large for the M5's system partition, although this can usually be overcome by deleting unneccessary VNDK files from the image.
See this comment by CAOS GSI developer eremitein.
Click to expand...
Click to collapse
very nice info, thx for that! encountered anything that isnt working on the M5 with 10 or 11?
jbmc83 said:
very nice info, thx for that! encountered anything that isnt working on the M5 with 10 or 11?
Click to expand...
Click to collapse
I use Android 10 (HavocOS 3.12) for daily use - everything works fine.
Magisk works and it passes SafetyNet with the 'Universal SafetyNet Fix' module.
I tried phhusson's Phh-Treble 11 for a couple of days and everything seemed OK, but I'm waiting for it to come out of 'pre-release' before moving off HavocOS 3.12; the latest 11-based builds of that are far too large, even after removing redundant VNDKs.
It is worth noting that I have a WiFi-only M5 (SHT-W09) and so can't comment on whether the telephony parts of Android 10 or 11 work correctly.
Did someone succeed in installing Android 12 Beta 5 GSI on his Lenovo P2 (Kuntao) ?
I was just curious to install it in order to test it and see what's new.
I tried every method I found but each time my phone goes into boot loop when rebooting after having flashed the GSI.
u using which vendor?
Astridxx said:
u using which vendor?
Click to expand...
Click to collapse
I tried with vendor installed (Android 11) :
coming from lineage-18.1-20210919-nightly-kuntao-signed.zip,
then the one coming from Havoc-OS-v4.8-20210821-kuntao-Unofficial.zip,
then the one coming from dotOS-R-v5.1.3-kuntao-UNOFFICIAL-20210825-0359.zip.
I think i must make a mistake somewhere.
I also tried installing an Android 11 GSI with the same result as for Android 12.
As the Lenovo P2 doesn't have a vbmeta partition I edited the boot.img in order to disable Android Verified Boot (AVB).
cocopipou said:
I tried with vendor installed (Android 11) :
coming from lineage-18.1-20210919-nightly-kuntao-signed.zip,
then the one coming from Havoc-OS-v4.8-20210821-kuntao-Unofficial.zip,
then the one coming from dotOS-R-v5.1.3-kuntao-UNOFFICIAL-20210825-0359.zip.
I think i must make a mistake somewhere.
I also tried installing an Android 11 GSI with the same result as for Android 12.
As the Lenovo P2 doesn't have a vbmeta partition I edited the boot.img in order to disable Android Verified Boot (AVB).
Click to expand...
Click to collapse
A11 or A10 vendor does not support treble
Try with this vendor: https://t.me/lenovodownloads/1026
Astridxx said:
A11 or A10 vendor does not support treble
Try with this vendor: https://t.me/lenovodownloads/1026
Click to expand...
Click to collapse
I tried yesterday by using your versions of vendor but I got same result : my phone refuses to boot.
I will then wait till the first GSI after the official release of Android 12 or till someone proposes a custom rom based on Android 12.
Bump!