Develop Bugs

[TWRP][any G4][BL LOCKED] TWRP-in-FIsH for all LOCKED G4 devices

TWRP on locked devices is impossible right?
Oh no wait there are hacks up to KK which work but I couldn't find anything for LL (sorry if I missed something) and so nothing for the G4
Here is where the FIsH steps in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIsH: [F]luffy [i]ncredible [s]teadfasterX [H]ijack​
FIsH is different from Safestrap or other hijacks because it should be understood as a kind of framework for any boot image you want to boot.
FIsH will not harm the Android boot chain!
It is NOT multirom
It is NOT efidroid
It is NOT Safestrap
It is NOT twrp.
.... but FIsH can boot any of the above. U got it? FIsH is the hack to boot whatever you want.
Will FIsH void your warranty? Not more or less then rooting your device.
Will FIsH unlock your bootloader? No read again.
Is there a risk with FIsH? For example could it soft-brick my device? Well.. absolutely! Safe is the death only. There are always risks especially for untested devices. I do all I can to keep this risk as low as possible and I provided a way to get out of bootloops but again you will get no guarantees here and elsewhere.
.. and it is more then just a hack for the G4 (any model) it is a hack for ALL devices of ANY vendor! wtf? yes.
Sure you have to met the pre-requirements and there has to be done some things to get it ported but those are straight forward.
Go to IRC channel #androidfish if u can't wait but I will publish a public porting guide when it is ready.
Are there plans to make more out of it for the G4? Absolutely. I'm currently working on an "efidroid in FIsH" version which will let you flash & boot (hopefully) any custom ROM u like.
ALL DETAILS ABOUT HOW FIsH WORKS HAVE BEEN RELEASED IN ANOTHER THREAD (check my signature).
So going back to topic. This is:
TWRP in FIsH for the LG G4 (any model) - Bootloader LOCKED
Do you have a bootloader unlocked device?
If the answer is YES: you don't need it
Do you have a bootloader locked device and want TWRP?
If the answer to BOTH is YES. you need it. you can't install TWRP on a locked device.. up to now. FIsH allows you to do so.
If your question is: Can this ENABLE root for my device?
NO! you actually NEED root to activate TWRP for your device with this method.
Important: Here are the pre-requirements you have to met!
If you can't get them:
Close this page and FORGET it (until the day you may met those reqs)!
Requirements!
root by SuperSU >=v2.76 (greater or equal v2.76) (atm this means you have to downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!)
you have to be able to disable SELinux in your booted Android (which should be the case when you have a full rooted device)
Those above are hard facts so it may never work with MM. That also means if MM can get fully rooted by SuperSU and you can use "setenforce 0" the method should work there as well!
Before you think about downgrading to LL read about ANTI-ROLLBACK protection some LG devices and MM versions may have!
Anti-Rollback means you CAN NOT downgrade - it would brick your device.
I will NOT provide downgrading guides there are plenty of them so search and read.
If you can not meet ALL of the above 2 requirements lay down and cry. For the others: calm down and read on!
You can test requirement 2 (disable SELinux) by:
adb shell
su
setenforce 0
getenforce
-> you should see "Permissive" as a result. If you see "Enforcing" or error messages you may doing something wrong or it just do not work for you.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader.
That means with TWRPinFIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = soft brick. for this u need "efidroid in FIsH" - coming soon)
Install a custom Kernel (this will modify boot = soft brick)
Install a custom recovery (this will modify recovery = may soft brick)
In short: nothing which modifies boot or recovery partitions.
You can of course flash everything which is modifying /system /data only (e.g. xposed,...)
That means you could install even a custom ROM which works with the stock kernel so with unmodified boot image. Let's say the creator of imperium or genisys provide a release without the containing boot image. You could flash it..
State / Roadmap
FULL takeover/hijack of boot -> DONE (the modifications required are not voiding the Android boot signing chain!)
replace RAM disk -> DONE
boot own RAM disk (TWRP!) -> DONE (atm TWRP 2.8.7-0) <-- TWRP-in-FIsH v1.0 private BETA
Upgrade bundled TWRP to latest version -> DONE (TWRP 3.1.0-0) <-- TWRP-in-FIsH v1.0 final release
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Go to the DOWNLOADS tab in this thread.
TWRP-in-FIsH is now integrated into my TWRP build server and so whenever a new change happens in TWRP you will get the same automatically on next build. This way it is much easier to release new TWRP versions made for FIsH.
From now on you will find nightlies (untested automatic builds) here:
Jenkins build status
Nightlies download server
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRPinFIsH*.tgz (tar xzf TWRP-in-FIsH*.tgz since v2.0)
cd openFIsH (cd android_FIsH since v2.0)
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Android / no PC)
Requirements:
TWRP-in-FIsH v4.2 or higher!
BusyBox pre-installed (e.g.: with this app )
You can just install any newer version over an old one.
Thanks to @ReeS86 starting from v4.2 on TWRP-in-FIsH has an enhanced installer which can run without any PC - directly on your Android device!
It would be nice if you could give him a thx click (here) for his contribution !
Bring TWRP-in-FIsH to your Android device
Example-1 with any PC (windows, linux, ...): adb push TWRP-in-FIsH.tgz /sdcard (replace TWRP-in-FIsH.tgz this with the real file name)
Example-2 within an Android Terminal:
cd /sdcard
wget http://full-URL-to-file (replace full-URL-to-file with the real direct download link)
Example-3 with just a browser: well just download it.. but remember where it gets saved!
extract it
Example from within Android Terminal:
cd /sdcard (or the folder where you have downloaded TWRP-in-FIsH)
tar xzf TWRP-in-FIsH.tgz (replace TWRP-in-FIsH.tgz this with the real file name)
run the installer (but do it correctly)
Example from within Android Terminal:
su
cd /sdcard/android_FIsH
sh ./install.sh (using sh is absolutely important otherwise it will fail)
done
Installation (Windows)
If none of the above methods is working for you: use FWUL
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
FIsH helpers
If you just want to reboot directly from within Android check out these:
Thanks to @sdembiske who has onboarded the developer @AntaresOne we have an option to reboot into FIsH very comfortable now!
Check it out here: QuickReboot App
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
reboot back to Android and catch the fish log (IMPORTANT!):
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
Upload it to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support there only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that TWRPinFIsH is a brutal hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
System IMAGE backup:
Using this new option is a bulletproof method to backup and restore in TWRP-in-FIsH because you have to keep in mind that FIsH is a giant and brutal hack and even when a usual backup & restore is proven to work fine I would recommend to use both backup methods - if you can.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
@sdembiske reports success using the internal storage as target for the backup but if you do this keep in mind that you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
When you find a stock based ROM which is not modifying boot you can flash it. But ensure that it does not modify anything on boot!!! You could ask the devs of imperium etc if they can provide such a zip..
SYSTEM partition (since v2.0: may be not a restriction on your device model!):
when you boot into TWRPinFIsH you may see an error message regarding the fact that /system cannot be mounted.
you can mount /system manually without a problem - BUT - it will work only if you do NOT select "mount system read-only". It has to be unchecked to work.
after you have mounted /system manually and you want to take a backup you may see "0 bytes". Just press refresh and the size will be updated. If not: Do you have mounted it correctly (see above).
FIRMWARE partition (since v2.0: may be not a restriction on your device model!):
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
You may heave seen/heard that this works in the official / usual TWRP for the G4 for unlocked devices. Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Installing more than 1 ZIP at a time (may be not a restriction on your device model!):
It is not possible to install more than 1 ZIP at the same time. TWRP gives you the option to install multiple ZIP files but the problem is you have to re-mount /system after each ZIP flashing. This is due to a problem with mounting /system readonly and most ZIPs will exactly try to do this when they finished their work - leaving you with an unmounted /system.
This will be not the case for every ZIP combination - so it is possible that you can flash some ZIPs at the same time while others not.
atm I believe you have to live with it.
Credits (without them - no TWRP-in-FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH!
TeamWin for TWRP of course!
@cray_Doze, @dssmex and @KeiranFTW for their hijack implementations which given me many input (e.g. https://forum.xda-developers.com/showthread.php?t=2608408)
@Aaahh for his great first steps to a G4 hijack -> His work had given me the motivation back to continue when I was about to stop all this
@dibbled for creating the android FIsH logo
steadfasterX for being steadfast!
@jasonlindholm for your donation it was highly appreciated!
XDA:DevDB Information
TWRP-in-FIsH_LGG4, Tool/Utility for the LG G4
Contributors
steadfasterX, Aaahh, TheMadScientist420, KeiranFTW, cray_Doze, dssmex, TeamWin, ChainFire, the_naxhoo, SimoxTav, Rees86, uio88, sdembiske, jasonlindholm, ... and all new other contributors who gave me feedback for this!
Source Code: https://github.com/Carbon-Fusion/android_FIsH
Version Information
Status: Stable
Current Stable Version: 4.2
Stable Release Date: 2017-06-21
Current Beta Version: 5.0
Beta Release Date: 2017-12-19
Created 2017-03-14
Last Updated 2017-12-19

List of confirmed devices (as of 2017-06-04)
If you own a device missing on this list - let me know and I will add it here.
F500L Korean variant - locked (Thanks @Syntist)
H810 - locked (Thanks @shane87)
H812 - locked (Thanks @ReeS86)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test with PURE stock and without touching the boot chain so its similar to locked devices.)
H815 EUR - locked (Thanks @uio88)
H815P - locked (Thanks @KnightOdin)
H815T - locked (Thanks @the_naxhoo)
H815L - locked (Thanks @foxyfoxyblah)
H818P - locked (Thanks @SimoxTav, @alitavas)
LS991 Sprint - locked (Thanks @TheMadScientist420)
VS986 - locked (Thanks @g_ding84)
List of confirmed flashing experiences (as of 2017-05-19)
If you tested a ZIP missing or unknown on this list - let me know and I will add/update it here. Write the exact version tested would be helpful as well.
Xposed - confirmed to work (tested: Xposed version 87 (SDK 21). THANKS for your report @g_ding84, @the_naxhoo, @KnightOdin, @shane87)
Viper4Android - confirmed to work (tested: Viper4Android 5.4 stock zip with Dolby Atmos. THANKS for your report @g_ding84 , @the_naxhoo, @SimoxTav)
SuperSU - confirmed to work (tested: v2.79. Thanks for reporting @g_ding84)
A.R.I.S.E - confirmed to work (tested: v.2.94 -> Am3d Eq, Viper4arise, Viper4Android Xhifi, Esira. Thanks for your report @alitavas
Android O emoji package - confirmed to work (thanks for your report @alitavas)
Editing system/build.prop - confirmed to work --> read carefully HOW (thanks for the howto & report @sdembiske )
Xtreme music 9.2 - confirmed to work (thanks for your report @jason_l367)
ANY OTHER ZIP - unknown ----> Please report back if you have flashed one missing here

Releases
TWRP-in-FIsH v5 (5.0)
Released: 2017-12-19
Download: Go to the Downloads tab
Changelog for FIsH: previously used version <---> this version
Changelog for TWRP-in-FIsH device tree: previously used version <---> this version
Changelog for:
- TWRP v3.2.0-0
- TWRP v3.2.1-0
Summary changelog (read the above FULL changelogs for details!):
new TWRP version
all important fixes from the main TWRP releases like corrected time and EFS backup, added Bootloader backups etc.
Many enhancements and fixes in FIsH, e.g. enhanced and fixes issues in the installer and qseecomd (device encryption) added to the brand new exclude service option
Everything is better now
Old releases:
TWRP-in-FIsH v4 (4.2)
Released: 2017-06-21
Download: Go to the Downloads tab
Changelog for FIsH: previously used version <---> this version
Changelog for TWRP-in-FIsH device tree: previously used version <---> this version
Changelog for TWRP: v3.1.1-0
Summary changelog (read the above FULL changelogs for details!):
Installer is now able to detect and run from within Android* (read the NOTES in the OP - topic "Installation (Android / no PC)"!)
Added the option to backup /system as an IMAGE* (read the following HINT!)
Using this new option is a bulletproof method to backup and restore in TWRP-in-FIsH because you have to keep in mind that FIsH is a giant and brutal hack and even when a usual backup & restore is proven to work fine I would recommend to use both backup methods - if you can.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
@sdembiske reports success using the internal storage as target for the backup but keep in mind that if you do this you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
Everything is better now
(.... TWRP updated, many FIsH improvements, added an option to backup /system as image,... read ALL the above changelogs!)
TWRP-in-FIsH-v3_LGG4_LL
Released: 2017-04-16
Download: here
Changelog: on github
Summary:
Big speed improvements
adding model detection as property (ro.product.detection -> should be "success")
fixing unify detection
adding all known devices to unification
- these both above will fix issues where your device was not detected correctly in TWRP and fails to install a ZIP which requires this!
Installer:
./install.sh --check will give you the option to check if TWRP-in-FIsH works for your or not - without changing anything on your device.
TWRP-in-FIsH-v2.0_LGG4_LL
(as far as im able to remember.. i have changed so many things inside..)
Released: 2017-03-24
Changelog: on github
Summary:
TWRP-in-FIsH now has a meaningful package name (TWRP-in-FIsH-v2.0-BETA1_LGG4_LL.tgz) which reflects all required information
The installer is checking for the SDK level now instead of the Android release version! This means ANY Lollipop version will work without modifications of the installer
new: completely overworked WIDE parts of FIsH
In order to be more easy portable all variables users may need to adjust are moved to FIsH.porting
while FIsH.me contains global variables for FIsH a user/dev normally would NOT change.
The log has been enriched with some more useful information
The stopping of android services is now more aggressive
Apropos aggressive: now we use fuser to kill ALL processes before trying to unmount a disk (excluding init and ourself)
Another porting stuff was added: we extract the FISHFOOD but WITHOUT a possibly existing file </init>. When you prepare your own ramdisk it may or may not contain a file /init but we do not want to overwrite the current running /init by just cpio yet.
The reason is: it makes a difference in the Linux world to use cp or mv or cpio > to overwrite!
The short version: using mv is the best choice here. So we extract first without /init (if there is one) and then extract /init ONLY but to a different directory. Afterwards we use mv to overwrite the current /init with either an extracted /init or your own init name configured by the new FOODBIN variable.
Unfortunately this has not that positive effect I hoped but I leave it there because it is the way it should be done nevertheless.
Now FIsH also:
- checks the exec bit before it tries to start it! Im still thinking of adding a reboot if not.. but this could cause bootloops.. on the other hand doing nothing will leave the device in a unusuable state.. well it should more or less never happen though but..
- save the current SELinux mode
- trying to restore the saved SELinux mode when something goes wrong (at the end this will make no sense but it doesnt hurt)
- umounts when a mount point is mounted ONLY
Besides that FIsH now comes with callmeFIsH - a caller script which gets executed at very first.
The only task callmeFIsH has is to prepare the whole FIsH to get started out of /system and then starting FIsH from /res. After this it immediately exists to not keep open tasks on /system.
Also new are some parts of the installer e.g. starting adb server first and then wait for a connected device before continue the installation.
The installer is keeping track of an older FIsH install and removes the previous one before as well
The installer also now giving a hint that you may have to change to PTP mode on your G4 to get detected
For completeness: Same TWRP version inside so nothing changed here..
During these changes I have renamed the package folder from openFIsH to android_FIsH. Please keep this in mind when you extract the FIsH
So after you extract the BETA package you have to do
"cd android_FIsH"
instead.
TWRPinFIsH_v1.0
Released: 2017-03-18
Changelog:
first public release
.

As current. To further op. When released remeber bl is still locked do not modify recovery and or boot partitions. Will throw secure boot errors done tried and found out. Was able to restore orig boot and recovery images.
On ls991.
So lets get our flash on. I wanna see some good clean flashing and no hits below the bootloader

TheMadScientist420 said:
As current. To further op. When released remeber bl is still locked do not modify recovery and or boot partitions. Will throw secure boot errors done tried and found out. Was able to restore orig boot and recovery images.
On ls991.
So lets get our flash on. I wanna see some good clean flashing and no hits below the bootloader
Click to expand...
Click to collapse
Well .. Correct. For me it is totally clear but this will be not for the average user maybe.. I will add it to the OP. Thx
Sent from my LG-H815 using XDA Labs

Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!

Jkmoran said:
Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!
Click to expand...
Click to collapse
2 posts up.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Jkmoran said:
Thanks for all your effort with this development. So, i understand that we can boot into TWRP and we can backup and restore our system, right? But we can also flash roms, mods or kernels without unlock BL?
Again, thanks for your time on this project, this are really big news for our device!
Click to expand...
Click to collapse
Yes and no. I flashed viper 4 android. But because of signed bl. Any recovery or modified boot image will not work just yet. Still a wip.

Reserved. I hope to install this in my H815p soon...

TheMadScientist420 said:
2 posts up.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Yes and no. I flashed viper 4 android. But because of signed bl. Any recovery or modified boot image will not work just yet. Still a wip.
Click to expand...
Click to collapse
Hey i just want to say thanks for acknowledging thqt i helped you more than what happens in the sprint thread. I have a post 2400 views where i tore my g4 down 3 days after purchase to show a thermal paste mod. 2400 views and 1 thanks. Id thank u properly but unfort ive hit my 8 thanks a day limit
---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------
Newmak said:
Reserved. I hope to install this in my H815p soon...
Click to expand...
Click to collapse
It will come in due time. The third release was sent out in one day. Progress is moving rite along my friend.
Some of us have been waiting since day one. I have about 15 months. Or nov 15 we are all anxious for offic release. And please make sure to give the man his cr3dit where due. Took time out of his day to do a team view session to test on mine at like 5 am this mornin. Some of the greatest minds have not been able to do this. And now look. Lol all the nay sayers
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
Newmak said:
Reserved. I hope to install this in my H815p soon...
Click to expand...
Click to collapse
sorry i didnt actually answer ure ?
this should work on all g4s and possibly many other lgs and or devices

I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.

tmihai20 said:
I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.
Click to expand...
Click to collapse
No read the OP again (wait for efidroid-in-FIsH).

tmihai20 said:
I have only one question. Will this TWRP be able to modify boot partition as well? Isn't that the whole point of the locked bootloader? If it will be able to modify any partition, it is a big, big win for us.
Click to expand...
Click to collapse
Lol op and about 4 or 5 posts up. Same ? Just asked.
Either was locked bl or not this is a majpr victory for the g4. They said it couldnt be done and

Hopefully You could port this also to G Flex 2?

dadaa1 said:
Hopefully You could port this also to G Flex 2?
Click to expand...
Click to collapse
he has stated should work on any android device running loli as long as u meet the prequisites
root and kernal set to permissive if he doesnt some one probly could adapt it from here no prob once its offic released
---------- Post added at 06:36 AM ---------- Previous post was at 06:04 AM ----------
dont know how much feed back uve been gettin but figured id chime in again
so after all night playing lol still sick as a dog cant sleep about 4 hours on 2 days feel high and drunk lol
ive do have to mount system everytime i load twrp to backup restore or flash but i flashed viper flashed xposed again just to check it out
bricked about 10 times and have restored perfectly everytime.
bricks my own fault trying and testing most def incompatible mods and fixes but so far through every brick recovery is holding strong and steady havnt installed the beta 3 yet
should i is much changed from there?

TheMadScientist420 said:
he has stated should work on any android device running loli as long as u meet the prequisites
root and kernal set to permissive if he doesnt some one probly could adapt it from here no prob once its offic released
---------- Post added at 06:36 AM ---------- Previous post was at 06:04 AM ----------
dont know how much feed back uve been gettin but figured id chime in again
so after all night playing lol still sick as a dog cant sleep about 4 hours on 2 days feel high and drunk lol
ive do have to mount system everytime i load twrp to backup restore or flash but i flashed viper flashed xposed again just to check it out
bricked about 10 times and have restored perfectly everytime.
bricks my own fault trying and testing most def incompatible mods and fixes but so far through every brick recovery is holding strong and steady havnt installed the beta 3 yet
should i is much changed from there?
Click to expand...
Click to collapse
Thanks for ur ongoing support here. please always go to IRC if possible:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,http://webchat.freenode.net/?channels=androidfish)
Whenever you have to choose a channel it is: #androidfish
When you be asked for a server network choose: freenode
.

Just wanted to let you know the current device list.
If you own a device missing in this list send me a PM with subject FIsH !
Please do not write me if your device is shown here already!
List of confirmed devices (as of 2017-03-15)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test without touching the boot chain so its similar to locked devices.)
LS991 Sprint - locked (Thanks @TheMadScientist420)
H815T - locked (Thanks @the_naxhoo)
H818P - locked (Thanks @SimoxTav)
H812 - locked (Thanks @ReeS86)

steadfasterX said:
Just wanted to let you know the current device list.
If you own a device missing in this list send me a PM with subject FIsH !
Please do not write me if your device is shown here already!
List of confirmed devices (as of 2017-03-15)
H815 International - unlocked (Thanks @steadfasterX yea its mine and i have no locked device to test with That's why i needed ur help. but i test without touching the boot chain so its similar to locked devices.)
LS991 Sprint - locked (Thanks @TheMadScientist420)
H815T - locked (Thanks @the_naxhoo)
H818P - locked (Thanks @SimoxTav)
H812 - locked (Thanks @ReeS86)
Click to expand...
Click to collapse
Nice work Waiting my Flex 2 LGH955 to arrive from warranty, I hope this can be ported to "LG Damed" locked flex 2 also

With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?

nikomedes said:
With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?
Click to expand...
Click to collapse
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader.
That means with TWRPinFIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = soft brick. for this u need "efidroid in FIsH" - coming soon)
Install a custom Kernel (this will modify boot = soft brick)
Install a custom recovery (this will modify recovery = may soft brick)
In short: nothing which modifies boot or recovery partitions.
You can of course flash everything which is modifying /system /data only (e.g. xposed,...)

nikomedes said:
With efidroid in FIsH, will we able to install any custom rom such as android 7.0 based roms?
Click to expand...
Click to collapse
Yes, with Efidroid you should be able to flash Custom ROM.
You can search about efidroid if you want to know more.
and thank you very much @steadfasterX , Good job bro ! :good:

Problem updating Huawei Mediapad M2-A01LV100R001C100B006 4G SIM Unlocked - NL

Hi,
Goal is to upgrade my M2, I believe it has a modem because it is able to receive SMS, 4G network, etc...
One thing is missing, calling functionality, dialer stuff ... is this hardware or firmware (or driver not installed)?
Can somebody please confirm or know how these things work?
So I want to upgrade because, I just want to be up to date, new android!
No updates are available if I try the official via EMUI Update way... online at Huawei nothing is available either (they refer to EMUI). It says most current version.
But then I read people from other European countries do have updates installed, 'same' model ... WTF?!?
Version / model : M2-A01L / 2GB
* Everything is still factory.
* EMUI : 3.1
* Android : 5.1.1
* Custom version : CUSTC100D002
* Bootloader version : V100R001C00B000_FASTBOOT
* Kernel version : M2-A01LV100R001C100B006_BOOT
* AP : M2-A01LV100R001C100B006_SYSTEM
* CP Version / baseband : 21.600.20.00.010(balong)
* Cust Version : Cversion:C100 DVersion002
So first things first reading different posts and tutorials about updating:
* https://forum.xda-developers.com/mediapad-m2/how-to/guide-official-updates-m2-tablet-root-t3589363
* https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
Im already stuck at the official steps:
1 - On tablet created folder : InternalStorage/HwOUC placed M2-A01LV100R001C100B007.zip and rename in update.zip
2 - Turn off , Reboot device (not connected to laptop) , should automatically install update above. Nothing happens.
So lets try bootloader maybe I can choose to update from folder or something. Nope, just 3 options, (reboot:wipe cache:factory)
Strange... Im wondering
1 - If they disabled something so updating is not possible at all?
2 - Other possibility in the forum, update.app in dload... people mention the process got stuck on 2%. Can you get back to original, it just fails or do you need to do a factory reset to get a working tablet again?
3 - What steps to take to make sure you can always... yes, always get back to your factory firmware when updating.
4 - Then I was reading about simply download to a full firmware (not an update)
HUAWEI_MediaPad+M2+10.0_M2-A01L_Firmware_Android+5.1.1_EMUI+3.1_V100R001C100B010CUSTC100D001_Germany_Spain_Belgium.zip
Not Netherlands... Im not 100% confident this is the way to go. Last part of the filename D001_German... mine is D002, so, aaargh
I hope you can guide me and help me updating. I dont know much about this, is it really chipset, hardware or just software (compilation) stuff...

jesperrekuh said:
Hi,
Im already stuck at the official steps:
1 - On tablet created folder : InternalStorage/HwOUC placed M2-A01LV100R001C100B007.zip and rename in update.zip
2 - Turn off , Reboot device (not connected to laptop) , should automatically install update above. Nothing happens.
So lets try bootloader maybe I can choose to update from folder or something. Nope, just 3 options, (reboot:wipe cache:factory)
Click to expand...
Click to collapse
Making progress ... step:
0 - Back to factory settings, yes wipe that thing and let's see... then:
1 -
a - Unpacked M2-A01LV100R001C100B007.zip placed in internal storage/dload. Settings > Update > menu > local update. Package found, rebooting, installing, SUCCESS, rebooting again.
b - Open Settings > About Tablet > look at buildnr... A01LV100R001C100B006 didn't change, huh. repeated steps above...
Lets's see what happens if go to OTA-M2-A01LV100R001C100B010.zip, same steps... and after updating process. nothing changed, still the same ... A01LV100R001C100B006 ...
So somehow the manual local update looks into dload folder > changes the boot procedure to update > then looks into a factory prepped setting > updates to its original and no version change.
Edit:
Placed file 007 in internal storage > dload , powered off , then I did :
Vol + UP and Vol - Down and PowerOn buttons, waited until I got the installing EMUI screen.
Nope, nothing changed.

YESSSSS , SUCCESS :good: read!!! (and above)
- Tablet (bought in the Netherlands) - Huawei M2 10" - A01L :
* Custom version : CUSTC100D002
* Bootloader version : V100R001C00B000_FASTBOOT
* Kernel version : M2-A01LV100R001C100B006_BOOT
* AP : M2-A01LV100R001C100B006_SYSTEM
This is what I did :
- Factory reset, tried to update B006 -> B007 -> B010, nothing seemed to be changed although it said success ...
- Not rooted, no TWRP, not Developer or Manufacturer mode... just basic.
Then downloaded rom in this topic :
https://forum.xda-developers.com/mediapad-m2/development/rom-m2-a01l-lte-premium-stock-t3624094
Huawei 10 - M2 A01L - B010 LTE file
- sdcard in tablet (not internal storage)
- create folder dload
- unzip file (above) and place the contents of the extracted file and its subfolder dload into this.
- the folder contained file UPDATE.APP and hw folder. Total size 3.3GB.
- Power down
- Unplug all cables
- Check if you have sufficient power >50%
- VolUp + and VolDown - and PowerOn, wait until EMUI Install screen, takes around 15-20seconds.
- Install starts until finished, 15minutes. Slow progress.
- Looks like it hangs on 99% but wait for success
Et voila, from B006 -> B010 and yes, including dialer... made a phonecall...
Next is rooting...

As I was saying... ROOTING, success again.. what ... a .... day !!!
My Steps :
0. Did above... don't forget
1. Follow these steps and pay 4 credits : Steps to Unlock, Recovery and Root
- Manufacturer mode to get the unlock code, back to hiSuite mode
- Command line tools for windows : ADB and fastboot
- Follow the exact procedure , step 18.
2. Troubles finding the files you need:
- TWRP for Android 5.1.1 More information can be found link here
- SuperSu

Enabling call on M2-801L
jesperrekuh said:
As I was saying... ROOTING, success again.. what ... a .... day !!!
My Steps :
0. Did above... don't forget
1. Follow these steps and pay 4 credits : Steps to Unlock, Recovery and Root
- Manufacturer mode to get the unlock code, back to hiSuite mode
- Command line tools for windows : ADB and fastboot
- Follow the exact procedure , step 18.
2. Troubles finding the files you need:
- TWRP for Android 5.1.1 More information can be found link here
- SuperSu
Click to expand...
Click to collapse
I read your post with interest. I was trying to do exactly the same thing i.e. enable the calling features on my M2-801L.
Eventually got my tablet fully working and your post helped a lot!!
So thanks for posting the info.

Honor 7X with installed TWRP bricked by OTA update ... any help?

Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:

ZB2016 said:
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
Click to expand...
Click to collapse
Restoring the backup is the only solution it seems.

Yes ... hmmm ... backup ... that was what I intended to do that morning when the BAMMMM happened. I really had a bad start with the 7X ...
So in case someone has a backup of a clean or nearly clean system partition, please send me a PN. Tnx in advance!

Normal make a Backup in Twrp before modify the System Partition.
Make not an Official Ota Update with Rooted and Twrp installed Rom

Its not the phones mistake that you mess up and wakeup and take the phone for a spin in half sleep
and bamm, i really dont know what that meant. i would say go to the honor care center and get it to them to work.
the procedure which i know of is tough and things like bamm happening might worsen things like TWRP not starting at all.
i have seen people bricking their phones but its never the phones fault.
i would never recommend doing a "BAMM" thing doing and flashing all the stuff randomly cz i dont think magisk is supported fully yet to our phone and you flashed it without asking anyone.
the other russian forums are flashing chinese stock firmware which is the only original firmware available, but the task to change the settings to work for other variant is a huge stock which i gave link to a few people but for you i wont recommend that cz obviously your situation is totally different so go to the honor center and explain them and they would help you.
good luck! next time verify and be careful before flashing anything at random cause its not the phones fault.

Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.

ZB2016 said:
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
Click to expand...
Click to collapse
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release

sid21 said:
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
Click to expand...
Click to collapse
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!

ZB2016 said:
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
Click to expand...
Click to collapse
I am in contact with the user who posted the article and tested it himself and requested a proper one in english language but he is busy so it hasnt proceeded.. But soon he ll be free to write one up for me so i will post it on XDA..

I'm in a very similar boat. The Magisk v15 update bricked my L24. I had another one available and have made back ups through twrp to restore on the bricked one. It actually boots, but all I get is a black screen with the menu, home, and back buttons now. Holding power gives me the options to restart and power off. Hope they release the stock rom soon, or custom roms be available soon.

root your son's 7x, make a boot and system backup and restore that in your phone.
reboot

Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread

Sudeep Duhoon said:
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Click to expand...
Click to collapse
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.

sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Back to life ... at least about 80%. Rooting leads to corrupt system partition (unable to boot afterwards) and bootloader can only be reached while a USB cable is connected (unusual behaviour). Nevertheless ... got it running. SID ... you are my hero of the day. Will PM you regarding comments for your thread.

ZB2016 said:
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
Click to expand...
Click to collapse
i think i have to write a guide now. this was the first but more can come soon enough. may be today i'll write a guide to backup your phone (all 48 partitions) and then root so you always have all the necessary files to restore it back to life.

sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Plz give link of custom rom for honor 7x

dhananjay 007 said:
Plz give link of custom rom for honor 7x
Click to expand...
Click to collapse
Who made custom rom for the phone?

sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I have honor 7x.

dhananjay 007 said:
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
I have honor 7x.
Click to expand...
Click to collapse
So why are you even asking me for a custom rom?
If you know no one has made yet

UPDATE ... got it back to life, at least partly. The only thing is, that constantly the android adaptions of Huawei is making it unnecessary complex or is stopping progress at all. This is the log of my actual tasks. Key to progress was the unlocking of the system fs, which has some inconsistencies in the file system. In general, it gives me a 7X, that boots and I can install apps via HiSuite. Nevertheless I have no idea how to deal with Gapps. If I install opengapps, I will not be able to register an account - just hangs for a long period and then comes back (are there any logs written on the device to analyze a bit deeper?). Gapps without an account maks no sense. So I tried it without opengapps but with installing play services via HiSuite, granting rights, rebooting twice, installing Playstore, granting rights, rebooting twice, but starting Playstore after this procedure just tells me, that gms has to be installed (which in fact is already).
Any hint?
- prep like described by SID21 including HiSuite-Installation
- optional: download Nova Launcher, Firefox and Total Commander from "apkmirror.com"
- boot into TWRP
- mount system r/w
- format data
- wipe all partitions besides external SD
- mount vendor
- install image VENDOR.IMG
- reboot to bootloader​- USB-connect to PC
- kill HiSuite in case it comes up
- Start MultiTools
- Click on "Unbrick" in upper list
- enter Path to prepared folder in grey field
- Validate: at least 4 checked boxes
- Click on Box labeled "Unbrick"
- Validate messages: "Completed", "All images are flashed successfully"
- Click "Recovery" in upper list
- in frame labeled "Flash custom Recovery/eRecovery":
- Click Button labelde "Select image" and navigate to file twrp_Honor_7x.img and select
- Click button "Flash Recovery"
- in Popup window select "Restart from fastboot" and unplug the phone from USB​- Stop Multitools
- Wait for first restart, phone comes up
- Adapt phone settings:
- Security & Privacy/Additional Settings:
- set "Unknown sources"
- set "Allow HiSuite to use HDB"​ - About phone:
- Click 7 times in a row on "Build number" to activate developer options​ - Developer options:
- Activate "USB debugging"
- optional: Activate "Allow ADB debugging in charge only mode"​ - WiFi:
- connect to your WiFi network​- USB-connect phone
- Phone popup: set "Allow access to device data?" to "Yes, allow access"
- Phone popup: set "Allow connection in HDB mode?" to "Yes, allow access"
- Phone popup: set "Allow USB debugging?" to "Ok"
- PC HiSuite Popup to inform about installation of services to manage device
- optional: PC HiSuite Apps:
- Install a proper Launcher (e.g. Nova Launcher) and make it the default launcher
- Install a proper file manager (e.g. Total Commander)
- install a browser (e.g. firefox)
- Download opengapps from opengapps.org and save to sd card​- USB-disconnect phone
- Restart phone into TWRP
- do not get access to system partition
- Mount: Validate: system is not mounted at all
- Advanced/Terminal:
- enter "ls -l /dev/block/platform/hi_mci.0/by-name/system"
- validate: the filesystem points to /dev/block/mmcblk0p44
- ONLY DO THE FOLLOWING IF YOU KNOW WHAT YOU ARE DOING!!!
- enter "resize2fs /dev/block/mmcblk0p44"
- Validate Message: The Filesystem is now 1200128 blocks long.
- enter "e2fsck /dev/block/mmcblk0p44"
- Validate message: system clean, ...​ - Mount:
- check "system"
- uncheck "Mount system partition read-only" and swype in next screen to get access to system
- check "system"​ - Install:
- Select storage: Micro SDCard
- install SuperSU (I've chosen 2.82)
- Wipe Cache/Dalvik​ - Reboot:
- reboot to system
- do not install TWRP app​- Reboot takes long time
- During boot animation another reboot occurs
- Boot animations gets finalized, phones comes up normally

[Recovery][P20][Unofficial]TWRP 3.2.1-0 [16/04/2018]

Disclaimer​This software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation​
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_p20_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features​
Internal storage decryption = working (If decryption with pin/password fails, remove the security (pin, pass, fingerprint) before booting to TWRP and it should decrypt just fine )
MTP and OTG connection = working
Backup&Restore = working
Note: This was tested only by few P20 owners,so if you test it,please report back!There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_p20_0.1.img - Decryption support (you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk not available for backup./vendor not available for backup (use /vendor_image instead)

Reserved

Works like a charm! Even decryptin! Thanks so much for your work! P20.

Amazing Work
Works without hiccups on my EML-L29 with demo fw. Thank you so much!

Works perfectly on EML L29! Thank you very much! Now let's try phh AOSP, :fingers-crossed:

ectoplasma22 said:
Works perfectly on EML L29! Thank you very much! Now let's try phh AOSP, :fingers-crossed:
Click to expand...
Click to collapse
I don't know if it will work on that, is tested only on EMUI.

Work perfectly on P20 Normal and i am on pphusson rom
Big thanks

Pretoriano80 said:
Reserved
Click to expand...
Click to collapse
What is the chance of this work on P20 Pro ? :fingers-crossed:

otonieru said:
What is the chance of this work on P20 Pro ? :fingers-crossed:
Click to expand...
Click to collapse
It's working already, but i didn't created a thread yet, i was waiting for more feedback from testers.

Dumb question - Does the bootloader need unlocking first?

CurtisAndroid5 said:
Dumb question - Does the bootloader need unlocking first?
Click to expand...
Click to collapse
yes

Works fine on P20 Pro (CLT-L09)
Thank you!

Yes you need to unlock the bootloader to flash

should i try on a p20 lite ?

Beantje said:
should i try on a p20 lite ?
Click to expand...
Click to collapse
It won't work, i guess!

Pretoriano80 said:
It won't work, i guess!
Click to expand...
Click to collapse
im gona try

Seems to work fine on my P20, thank you.

Re-uploaded 0.1 with some small fixes. More partitions are available to install as image (check Install - > Install image).

I'm running into trouble when trying to resize the system partition.
Failed to unmount '/system' (Device or resource busy)
...
Repairing System before resizing.
Repairing System using e2fsck...
/sbin/e2fsck -fp /dev/block/sdd59 process ended with
ERROR: 8
Unable to repair System.
I guess the inability to unmount causes this. Does anyone have suggestions as to why it's happening and how to fix it?
Tried searching, but couldn't find anything useful so far.
Found some TWRP bug reports for different devices about this, maybe that's a possible direction to look into.

After some more investigation it seems that the the aptouch_daemon for TWRP is running from the system partition.
395 root 18092 S /system/vendor/bin/aptouch_daemon
When i kill the process, the command: e2fsck -fp /dev/block/sdd59 during resizing seems to work. The touch interface goes dead at that point, so can't test if the resize would work as i can't select it. The openrecoveryscripts only allow wiping of partitions it seems.
I did find multiple locations where the aptouch_deamon executable is stored:
/system/vendor/bin
/vendor/bin
I checked if it were links, but they don't appear to be.
There are some aptouch_daemon.rc files, that say to start from /system/vendor/bin/aptouch_deamon. I have changed the ones i found to remove the system directory, but on rebooting it stills loads the executable from /system/...
That's the stuff i figured out, which seems the main cause for the issue with the system partition. I'm not familiar with the code or build mechanism, so hopefully this gives you some information and an idea to fix it @Pretoriano80
If there is a git specific for this build, i'm willing to check if i can help with fixing this. Just not sure if i'm able to figure the system out quickly.

How To Guide [Guide] Xiaomi Mi Pad 5 MIUI12/13 ROOT Step-by-step - Pass SafetyNet, Widevine L1

Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5​EEA 13.0.3​Global 13.0.1​​​Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader

Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01

Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.

Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01

Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.

Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.

Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!

Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.

thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks

Can i update ota to 13.0.2 after rooted? Just update and root again?

Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2

How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?

Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5

Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...

Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?

thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.

vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img

kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks

Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?

cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet