Related
Unofficial TWRP Recovery for LG Optimus L9.
{
"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"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Use Flashify / Rashr from the PlayStore to flash.
Screenshots::
Download links:
- P60/P765/P768:
twrp-3.0.2-0-p760.img
- P769:
twrp-3.0.2-0-p769.img
XDA:DevDB Information
TWRP 3.0 for LG Optimus L9, Tool/Utility for the LG Optimus L9 P760, P765, P768
Contributors
EdwinMoq
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-04-08
Last Updated 2016-04-08
Ohhh my God!!!!!! i can't believe it!!!! Man you are the master.
Really Really thanks for your great works!
Tested,and works perfect!!!
yeah dude awesome :* thanx it"s work great i test it now !!!
Great. This time I was using Rashr instead of Flashify. Can reboot to recovery without problems.
But I haven't got the cojones so far to check, whether the Power-Volume-Menu combo will brick the phone, as happening with the previous version. I will only get to know once the next build of CM13 arrives, and that again won't even work good enough to let me boot into recovery to restore the nandroid...
Can't access my exFAT formatted SD card. How do I fix it?
Casserole said:
Can't access my exFAT formatted SD card. How do I fix it?
Click to expand...
Click to collapse
Huh? I should be able to access any file system. Can you get the recovery.log by getting to Advanced --> Copy log and post it here?
Thank you for this gift but i want to install pa 4.4.4 and it display error 7. How can i resolve? thanks
satiryco said:
Thank you for this gift but i want to install pa 4.4.4 and it display error 7. How can i resolve? thanks
Click to expand...
Click to collapse
Check that the rom You're installing is made is made for your phone. The error 7 usually means that the user is trying to install on an incompatible device.
lecorbusier said:
But I haven't got the cojones so far to check, whether the Power-Volume-Menu combo will brick the phone, as happening with the previous version.
Click to expand...
Click to collapse
I didn't know that issue before today (yep, I bricked my phone). After fixing it and doing software reboots (through adb) I got everything working. Everything else is working perfectly. Thanks, Edwin. Got your TWRP 3.0.2 and CM13 running by now.
So is it even possible to flash back to stock after installing this?
bulletfreak said:
So is it even possible to flash back to stock after installing this?
Click to expand...
Click to collapse
Can't you flash stock using LGFlashTool? I don't see how to twrp would prevent you from doing so.
bulletfreak said:
So is it even possible to flash back to stock after installing this?
Click to expand...
Click to collapse
Yes... if before you do a rom (stock) backup with twrp
I was able to get to TWRP 3.0.2.0 at boot several times, unlike Twrp 2.8.
However, I got a rather serious brick later, with the P760 restarting every 3 seconds, and no access to TWRP and Fastboot. After unbricking, D/L mode still worked, and installing Twrp anew, I haven't tried that again, always rebooting into recovery.
For the Fastboot problem under Win8.1 and 10 it may help to deactivate all powersave settings for usb hubs and host controllers. I haven't tried that yet.
If TWRP's boot screen won't disappear, hit power twice, and you're in TWRPs lockscreen.
I have just rooted my Galaxy Note 2014, which has an official TWRP 3.0.2. I can tell that that one has more issues than this,despite being official.
Can i ask, please, if i want to switch from cwm to twrp, could o just flash this img? I want to flash your marsh rom afterwards
Thanks in advance
Sent from my LG-P760 using Tapatalk
besnaglista said:
Can i ask, please, if i want to switch from cwm to twrp, could o just flash this img? I want to flash your marsh rom afterwards
Thanks in advance
Sent from my LG-P760 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the img with Flashify or similar.
If Flashify don't work, install Rashr and reboot, for safety. For some people Fastboot don't work, so the option to flash via PC don't exist. This incurs extra circumstances, if something goes wrong.
I had an old version of twrp on my P760. To flash new one I replaced the old one in flashable zip with this new one, then flashed it on twrp like installing a rom. It successfully flashed. I'm sharing the flashable twrp 3.0.2-0 zip file if it helps. It should aslo work on P765 and P768. https://mega.nz/#!LAggTZbR!58cGt1xxGtIXo_AOSXf4w1RNHTm1I4WgTGDQBuq4Vts
Big thanks to @EdwinMoq
I have reverted to stock weeks ago, to use the phone as a mobile AP with a data SIM. So far, probably because of missing SIM, 5ghz wifi and gps don't work. The dead sensors in CM12/13 came back to life.
As Fastboot don't work with L9 & Win10, i had to root using Kingo Root. I don't like the Kingo superuser tool. Days ago, for the second time, the phone bricked while trying to install SuperSu. It's still in that state.
I was using Edwin's TWRP, which worked fine with CM12 & 13. The older Twrp from Artas had the habit to brick the phone while trying to access it at boot. Rebooting from Android to Twrp was no problem, however. If you go further back in time, there was only CWM. I was using CWM along with stock years ago, seems i have to get it again.
Boot to Recovery?
EdwinMoq said:
Yes, just flash the img with Flashify or similar.
Click to expand...
Click to collapse
How to acces with power offe device? Power+ Vol- combination does not work and I have to access using Advanced Reboot
This is my first post here, so please excuse me for my english, i'm from chile (spanish).
I'm gonna do a little tutorial to Install TWRP and root on Leeco X820....just received yesterday.
First we gonna need the official ROM 14S from here:
http://g3.letv.cn/188/43/59/letv-hd...3S-5.6.014S.zip?b=123456&platid=5&splatid=500
And the Pack that i prepared here:
https://dl.dropboxusercontent.com/u/105732967/twrp+root.rar
Now:
Step 1: Unzip the file twrp+root.rar and Put the file BETA-SuperSU-v2.72-20160510112018.zip on the internal memory,
put LE_X2_X820-CN-FN-FEXCNFN5601405103S-5.6.014S.zip file on the internal memory too (this 2 files)
Step 2: Power off the phone
step 3: Enter to Fastboot mode (turn on pressing volume down)(http://www.netded.com/uploads/allimg/160514/1_160514151201_1.png)
Step 4: on the folder that you created to unzip (example C:/twrp+root) press and hold SHIFT then right mouse click and go to "open command line window here" (or something like that in english)
step5: Connect your phone and wait to install the drivers
step6: on the command line write: "fastboot oem unlock"
step7: If that's ok then write: "fastboot flash recovery Le_X820_TWRP.img"
step8: If that's ok now you have the recovery twrp (chinese) installed (if this not work 1st time, do it again)
setp9: Reboot your phone on recovery mode (holding power button + volume up) (from fastboot, you don't reboot in normal mode)
step10: you gonna see the recovery in chinese, but don't worry, this recovery is the same that always and the options are on the same order: http://www.teamsuperluminal.org/wp-content/uploads/2016/02/twrp3_4.png
step11: go to install and flash the 14S rom (if you want), and if you want to keep your rom (probably 13S) just flash the SuperSU beta file.
If you want to Install a clean rom 14S with google play support (recomended), you have to wipe, then Flash the ROM 14s, and then flash this GAPPS (working fine) http://opengapps.org/ (just choose download ARM64+Android 6.0+ Pico version) and then flash the SuperSU beta file provided.
https://dl.dropboxusercontent.com/u/105732967/Screenshot_20160519-115831.jpg
https://dl.dropboxusercontent.com/u/105732967/Screenshot_20160519-100924.jpg
https://dl.dropboxusercontent.com/u/105732967/Screenshot_20160519-100944.jpg
https://dl.dropboxusercontent.com/u/105732967/Screenshot_20160519-112614.jpg
If you want to change the Language (in my case spanish), you can always use Morelocale (from playstore) with Root privileges
Greetings from Chile!!!!!
This is great but I have a problem . I did fastboot and it said "sending TWRP" okay and "writing Twrp okay"and all well to step 9. It boots to the recovery(LeEco recovery) that came on the phone. Can I bypass that ?
MadMicro said:
This is great but I have a problem . I did fastboot and it said "sending TWRP" okay and "writing Twrp okay"and all well to step 9. It boots to the recovery(LeEco recovery) that came on the phone. Can I bypass that ?
Click to expand...
Click to collapse
do it again, it works for me the 2nd time...and dont let the phone reboot in normal mode...reboot from bastboot into recovery from the fastboot mode pressing and holding On buttond and vol up
julianhrojas said:
do it again, it works for me the 2nd time...and dont let the phone reboot in normal mode...reboot from bastboot into recovery from the fastboot mode pressing and holding On buttond and vol up
Click to expand...
Click to collapse
Very much appreciated, Thanks
I did it again and got Twrp working. I did the wipes and flashed the Rom smoothly. I also flashed the gapps file but it said it was incompatible I then booted to system, shut down and tried and failed to get TWRP so I did whole fastboot twice again and booted TWRP and flashed the file that was “incompatible” with no errors. But I get a number(5-7)”incompatible ‘/cust’ ??? (invalid argument)” with all TWRP operations .
Before leaving I went to 3rd block on rt of TWRP home screen and then to world globe on rt and changed language to English and TWRP is now in English. I then went to bootloader and deleted/inactivated the stock LeEco recovery and can now boot to TWRP normally(power+volme up).
However although I do have the Google Play store app. I keep getting message to say google services has stopped. When I try to add a google account on settings or click on play store app it spends a long time “checking info” and after 1 hour its still checking info.Does anyone have a solution ?
MadMicro said:
Very much appreciated, Thanks
I did it again and got Twrp working. I did the wipes and flashed the Rom smoothly. I also flashed the gapps file but it said it was incompatible I then booted to system, shut down and tried and failed to get TWRP so I did whole fastboot twice again and booted TWRP and flashed the file that was “incompatible” with no errors. But I get a number(5-7)”incompatible ‘/cust’ ??? (invalid argument)” with all TWRP operations .
Before leaving I went to 3rd block on rt of TWRP home screen and then to world globe on rt and changed language to English and TWRP is now in English. I then went to bootloader and deleted/inactivated the stock LeEco recovery and can now boot to TWRP normally(power+volme up).
However although I do have the Google Play store app. I keep getting message to say google services has stopped. When I try to add a google account on settings or click on play store app it spends a long time “checking info” and after 1 hour its still checking info.Does anyone have a solution ?
Click to expand...
Click to collapse
Do.you have flashed the pico version of gapps arm64??...that zip clean and delete all the previous versions of play store and then install the newest. I had problems with playstore too but with the gapps pico flashed all runs fine for me
julianhrojas said:
Do.you have flashed the pico version of gapps arm64??...that zip clean and delete all the previous versions of play store and then install the newest. I had problems with playstore too but with the gapps pico flashed all runs fine for me
Click to expand...
Click to collapse
First it tells me pico version is incompatible then it installed it . I also tried the Arm64 mini version but same result. I get lots of "Com.letv.android.phonecontrol not working" and "Sorry google play services has stopped "
How do you delete apps ? In settings .app management I can disable or force stop but not uninstall. When I press and hold there no uninstall to drag to. When disabled they dissapear but come back when I do factory reset or wipe cache dalvic an data....weird. i have repeated everything a few times but nothing changes .
I havent put a sim card in yet
I have not setup a LeEco acount yet either,.....necessary ?
Even tho I have picked English I still get a lot of status messages in Chinese .
Help appreciated !!!
{
"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"
}
MadMicro said:
View attachment 3757709
Click to expand...
Click to collapse
I can do a backup of my system and upload it...if you want it you tell me...only if you know how restore a backup from twrp (you have to generate the code yo name the folder in backup)
Well I think I am at end of road anyhow.
I use TWRP to backup and restore my own phone (not le max 2) but maybe its best if you tell me steps
Please let me use your backup as my le max 2 is a brick at moment
Install google play store (x820)
1) - INSTALL GOOGLE PLAY STORE(X820) htt*://impressivedroid.com/guide-install-google-play-store-on-le-2-x620/
2) - open play market and input login and password
3) - go to TWRP and install GAPPS ARM64+Android 6.0+ Pico version
Work it fine, no errors.
Received mine today from Honorbuy. If I flash twrp, where can I get original Recovery to go back to Stock?
What Color has your device? Mine is Gold but looks like Rose..
If you dont change bootloader in TWRP it will always go back to stock. Why would you want to go back to stock?. I thought it is only useful for offline updates ?
MadMicro said:
If you dont change bootloader in TWRP it will always go back to stock. Why would you want to go back to stock?. I thought it is only useful for offline updates ?
Click to expand...
Click to collapse
If I would sell the Phone I set it back to stock.
Installed TWRP and SuperSU 2.72 Beta. Worked in first attempt. No update to 14s, because of Problems with Playstore. Will wait if its fixed
All working Great, Backups from Oneplus Two (Titanium Backup) restored, without problems
i have updated to 14s and playstore (open gapps pico) installed without problems
Can you change language to German in 14s?
Sent from my ONE A2003 using XDA Free mobile app
So, the OTA update released yesterday will kill your root and remove TWRP. I attempted to reflash TWRP in fastboot mode, but it does not work anymore. The result is that it starts LeEco recovery and then right half of the screen is just random color pattern. Anyone knows if there is an updated TWRP version?
Well, ok, I found it on Chinese forums, here it is:
app.box.com/s/w66pg1h8wo3fj1lrtlcdw2fs3hk1w40a
The ZIP contains all the necessary tools and SuperSU as well. Flash TWRP through fastboot as described in the first post, then SuperSU through TWRP. My TWRP and root are back, all good!
julianhrojas said:
i have updated to 14s and playstore (open gapps pico) installed without problems
Click to expand...
Click to collapse
Hi, my friend, and thanks for your help.
In new LeEco update of 14s, 237s, when I install Open Gapps there is a google play services error.
Dou you install in this new update and works properly?
I think that play services error was also in previous 14S (103s version). @mjoach has the solution in other thread. I have the 237s running and no problem with Play Store.
http://forum.xda-developers.com/le-max-2/how-to/fix-google-play-store-flashing-14s-t3383261
WORK IN PROGRESS: This all started in a quest to stay locked, but have root and Magisk running on my phone, and eventually unlocking to install a custom kernel which wouldn't trip SafetyNet.
I've had to compromise on staying locked as unlocking the boot loader was ultimately necessary. As of this update to the guide, I have root, Magisk, and system-less Xposed working with each other. SafetyNet, however, is partially broken.
This is my experience on my new ZTE Axon 7 unlocked U.S. variant (A2017U), running build B29.
I'm certain that most of my problems had to do with the write-protected /system partition, as well as the encryption of fstab (verity check encryption/SE Linux status). I finally got some things working by using the method that follows, and I've opened this thread for anyone wishing to learn from what I've done, and possibly sharing with us, better methods of achieving this:
-> Device needs to have its bootloader unlocked, or else you will get a boot-loop into EDL mode. Use your prefered method for this.
-> TWRP 3.0.2.0
-> Last working SuperSU v2.65, which should install in systemless mode (tenfar's patched boot.img doesn't work for me).
-> A way to disable fstab encryption. I got it done using both: a custom kernel called Kali Kernel (also check this post for a stripped down version of the kernel) and through DrakenFX's script available here.
-> Magisk Manager, and Magisk flashable zip versions available here (look under downloads, v2.5 and v9 respectively as of this writing): [url]http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
-> ADB shell (you can either use Terminal Emulator from the Play Store or ADB Shell on your computer.
After you have unlocked the bootloader, with any of the unlocking guides here on XDA (I used DrakenFX's zip, ultimately. God bless that dude!): Boot into TWRP, flash SuperSU v2.65 mentioned above.
Proceed to flash DrakenFX's boot loop patch.
Boot into the system.
Update SuperSU to the latest version through the Play Store (v2.79 as of this writing, should be automatic).
Open the SuperSU APK and update the SU binary at the prompt. Reboot the system.
Once booted back into the system: Open an ADB shell (either through terminal emulator, or through ADB shell on a computer) and type the following:
Code:
su
reboot disemmcwp
The phone will reboot.
Boot into TWRP and flash the Magisk v9 zip file.
Here, I would advise flashing the Kali kernel as well (if you're interested in passing SafetyNet validation, or even if you aren't as it worked for me this way). There is a stripped down version of the kernel available here (source post here).
Boot back into the system.
Once you're up, proceed to install the Magisk Manager.
If it is still showing up undetected then reinstall through the app, reboot into TWRP and flash the Magisk v9 .zip file as well, and reboot into the system.
Reboot system at the prompt.
A word of caution regarding Magisk's implementation of suHIDE: it can't be used with this method as it breaks root after a while, and apparently has no impact on a superuser system which is not a Magisk module. I am exploring Chainfire's suHIDE implementation in the coming days.
Hope it works for you all!
Edits: Updated guide to reflect my current research gains, and removed superfluous text. I will upload screenshots of my status as soon as I get back to my computer.
Updated screenshots to the current state.
{
"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"
}
Still no work for me. I can install it but when i reboot Magisk disapear. And i don't know why but magisk worked good before i do a factroy reset.
Alright, still working on streamlining my methods, and I've managed to get root, Magisk, and system-less Xposed playing nice together.
The next step was to try to not trip SafetyNet with this setup, and I've made some progress on that front. It involves installing the patched Kali kernel (as I've done so far) and suHIDE from Chainfire (next test, tomorrow).
I'll update the OP tomorrow, with screenshots!
Good for you!
Everything I try to install it didn't survive to reboot ðŸ™.
I make a fresh install and same. I don't know why. Last time I tried it worked.
I tried everything 😢
Znuf said:
Good for you!
Everything I try to install it didn't survive to reboot ðŸ™.
I make a fresh install and same. I don't know why. Last time I tried it worked.
I tried everything 😢
Click to expand...
Click to collapse
I've just updated the guide. Do you want to give it a shot and see whether it works for you?
It's exactly what I do many time, at least 10.
But it's never activated after boot. :sad:
If I found a way I'll post here
I found a way.
On unlocked phone.
Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk v9.
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9.
Reboot system.
This worked for me.
Znuf said:
I found a way.
On unlocked phone.
Install supersu 1.65
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk framwork
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9
Reboot system.
This worked for me. 😀
Click to expand...
Click to collapse
I have a couple of doubts about your procedure before testing it twice:
1. Are you sure you have to install SU v1.65? Why not SU v2.65?
2. you are referring to the magisk framwork, but I do not find it. Were you referring to Xposed framework maybe?
It would be easier if could provide some links to the download pages, just to match versions.
Thanks
I update my post. Sorry for the poor precision. It was late. ?
Znuf said:
I update my post. Sorry for the poor precision. It was late.
Click to expand...
Click to collapse
Thanks for the clarification, I understand that when you say install Magisk v9, you rever to install within the Magisk manager app, and then later, booting directly to TWRP flashing the Magisk v9 zip file.
I have been experimenting with Safetynet helper and I have found that it doesn't pass when the phone is unlocked. As soon as I unlock the bootloader, the safetynet helper reports a CTS profile doesn't match. Even when using the stock boot and stock system without any root!!!!
Any thought on this???
blue skies
So Android Pay is working with this method?
JKSurf said:
So Android Pay is working with this method?
Click to expand...
Click to collapse
Not for me.
I am still experimenting, there must be a way.
---------- Post added at 17:30 ---------- Previous post was at 17:23 ----------
Znuf said:
I found a way.
On unlocked phone.
Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk v9.
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9.
Reboot system.
This worked for me.
Click to expand...
Click to collapse
I have done exactly that with the B29 ROM with stock boot and system. For some reason Magisk manager keep asking for Magisk v9 even after the whole process has been completed. I have root thanks to SuperSU, but safetynet helper test doesn't pass.
A better question is if you can pass the SafetyNet check apps.
I posted this in the thread that started this one, but with the official TWRP you can flash recent versions of SuperSU, not just 2.65 anymore (that was a limitation of the unofficial).
I know this thread relates to getting Magisk working, but unless there's a specific module you're looking to use, I don't see a benefit to using it for systemless root over SuperSU. I had tried to install it before using unofficial TWRP and had problems, but I think those, like the inability to install SuperSU past 2.65 we're due to faults with the unofficial TWRP. Official TWRP should install Magisk just fine (haven't cared to try it).
That said, if Android Pay is you're concern SuperSU might be the way to go. I am running SuperSU 2.79, Xposed 86.2, suhide 0.55, and Root Switch 1.3.3.2 and am able to pass both of the popular SN test apps (SafetyNet Helper and SafetyNet Playground). I don't use AP to know if that functions, but Pokémon GO, which also relies on SafetyNet runs just fine.
Also, as far as kernel goes, if you want one that doesn't have all the extra stuff the Kali NetHunter kernel does, there's a stock kernel patched for SafetyNet, kcal, and exFAT in this post of the same thread.
If you don't care about Xposed, SuperSU and Root Switch should be all you need to pass.
And as I mentioned in the other thread, this will likely all be rendered useless by the Nougat update hopefully coming next month.
The method I posted as an update in the OP the other day closely follows @Znuf's method, and all the relevant files are linked in the OP. Still a bit busy to experiment more, but this is how far I had gotten with the method I had posted, and, in theory, should work with suHIDE. Even the Kali Kernel I have linked to is the patched one without the extra tools.
With suHIDE my config should be similar to @-Duir-'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.
I'll try this out and update it soon. Screenshots attached is my progress on the last update..
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
H0lmEd said:
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
Click to expand...
Click to collapse
The bootloop fixer script should work on all devices as it just disables forced encryption in your bootloader. Make backups and try it out. If you experience a problem just restore the backed-up boot partition.
I'm on 2017g no bootloop.
Erahgon said:
With suHIDE my config should be similar to @-Duir-'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.
Click to expand...
Click to collapse
suhide will only work with Xposed 86.2 (which is provided in the same post).
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.
Thanks
Oki said:
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.
Thanks
Click to expand...
Click to collapse
Yep, Xposed modules still work, all you're toggling is root and no reboot required to disable/enable root. It's worth clarifying that while modules will still work, root apps obviously won't while disabled. Also, while root is disabled, Xposed installer will say Xposed isn't installed - as long as Xposed installer is green when root is enabled you're good.
Hi,
I just updated my HW Mate 10 pro to the latest version which includes face recognition. It worked as expected until I rooted the phone with FHMate10Tool. I tried using another method called Magisk but I got an error when trying to apply it through TWRP so I couldnt proceed with this method.
Anyways, after rooting, I get an error saying that my facial features werent recognized, in simple words, front camera wont open, therefore, it wouldnt work.
I even tried to unroot but even after doing factory reset, I can't seem to make it work.
Any thoughts? Please see PS below:
{
"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"
}
Thanks for your help!
What your version and model? Mine work fine with magisk root.
maxkento said:
What your version and model? Mine work fine with magisk root.
Click to expand...
Click to collapse
Thanks for your reply.
Model: BLA-L29
Build Number: BLA-L29 8.0.0.135(C605)
EMUI Version: 8.0.0
The weird thing is that I ran a factory reset to remove any root stuff and I still cannot use the face unlock feature due to the error mentioned above.
I had the phone rooted and bootloader unlocked and worked until I rooted the phone.
jeinnerabdel said:
Thanks for your reply.
Model: BLA-L29
Build Number: BLA-L29 8.0.0.135(C605)
EMUI Version: 8.0.0
The weird thing is that I ran a factory reset to remove any root stuff and I still cannot use the face unlock feature due to the error mentioned above.
I had the phone rooted and bootloader unlocked and worked until I rooted the phone.
Click to expand...
Click to collapse
Is this the original firmware or you rebrand the rom?
Hi, I am on BLA-L29 800142(C432)stock & rooted phone with Magisk V16. Face unlock still running without any problems. Maybe it has something to do with the FH rooting tool?
maxkento said:
Is this the original firmware or you rebrand the rom?
Click to expand...
Click to collapse
Original firmware. OTA update.
How your stock camera? Does that work with the front facing?
jeinnerabdel said:
Thanks for your reply.
Model: BLA-L29
Build Number: BLA-L29 8.0.0.135(C605)
EMUI Version: 8.0.0
The weird thing is that I ran a factory reset to remove any root stuff and I still cannot use the face unlock feature due to the error mentioned above.
I had the phone rooted and bootloader unlocked and worked until I rooted the phone.
Click to expand...
Click to collapse
It's because of FH Root tool.
Download your stock ramdisk from here: https://mega.nz/#!BWxElaRA!lUb-u-jXaPSAN8OrbyG4tEKCWttvqPxMPOVBn6h1PRY
Then flash it using 'fastboot flash ramdisk RAMDISK_BLA-L29C605B135.img'
Then flash Magisk from TWRP.
Factory reset only resets /data, root is kept in your ramdisk (Well. App is kept in /data, but it's just an app.)
maxkento said:
How your stock camera? Does that work with the front facing?
Click to expand...
Click to collapse
Yes, both cameras work as expected. The only flaw is for the face recognition for unlock.
ante0 said:
It's because of FH Root tool.
Download your stock ramdisk from here: https://mega.nz/#!BWxElaRA!lUb-u-jXaPSAN8OrbyG4tEKCWttvqPxMPOVBn6h1PRY
Then flash it using 'fastboot flash ramdisk RAMDISK_BLA-L29C605B135.img'
Then flash Magisk from TWRP.
Factory reset only resets /data, root is kept in your ramdisk (Well. App is kept in /data, but it's just an app.)
Click to expand...
Click to collapse
Thanks for your help on this. I just flashed the ramdisk as you told me to. By any chance, do you have the URL to instructions to root with this method? Ive found a few but they dont seem to work for me.
Thanks once again!
jeinnerabdel said:
Thanks for your help on this. I just flashed the ramdisk as you told me to. By any chance, do you have the URL to instructions to root with this method? Ive found a few but they dont seem to work for me.
Thanks once again!
Click to expand...
Click to collapse
Flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Flash Magisk 16 in twrp: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or get the 16.4 beta: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
That's all there is to it
ante0 said:
Flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Flash Magisk 16 in twrp: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or get the 16.4 beta: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
That's all there is to it
Click to expand...
Click to collapse
I just confirmed that after adding the boot image you provided, I get an error stating that there's no boot image (error when trying to get into recovery mode). The good thing is that the phone can boot normally to Android, it just freaked the cr#p out of me!
jeinnerabdel said:
I just confirmed that after adding the boot image you provided, I get an error stating that there's no boot image (error when trying to get into recovery mode). The good thing is that the phone can boot normally to Android, it just freaked the cr#p out of me!
Click to expand...
Click to collapse
It's the stock ramdisk for your firmware, so it shouldn't cause any problems. However, if you have no recovery_ramdisk or it's incorrect it wouldn't be able to get to recovery.
Flash twrp using fastboot flash recovery_ramdisk twrp.img
ante0 said:
It's the stock ramdisk for your firmware, so it shouldn't cause any problems. However, if you have no recovery_ramdisk or it's incorrect it wouldn't be able to get to recovery.
Flash twrp using fastboot flash recovery_ramdisk twrp.img
Click to expand...
Click to collapse
Thanks! Yeah, apparently the ramdisk doesnt belong to this phone. I was able to install TWRP. I'm following the guides you provided as I type this. Let me go through these and I'll get back with you!
It works now! The problem I was having is that I tried installing the Magisk from TWRP as ZIP (which this time I couldnt find anywhere on the phone after copying it via graphical interface in android) so I just ran this command:
adb sideload Filepath\Magisk.zip
This installed Magisk on my home screen and I applied the patch from the app. I rebooted and voilá! it works now. It even had the previous configuration already applied, it recognized my face without even setting it up again.
As the phone was already rooted, Im not sure if this app really roots the phone as it didnt require a factory reset as other methods do, but the issue is now fixed!
Thank you for your support on this matter!
jeinnerabdel said:
It works now! The problem I was having is that I tried installing the Magisk from TWRP as ZIP (which this time I couldnt find anywhere on the phone after copying it via graphical interface in android) so I just ran this command:
adb sideload Filepath\Magisk.zip
This installed Magisk on my home screen and I applied the patch from the app. I rebooted and voilá! it works now. It even had the previous configuration already applied, it recognized my face without even setting it up again.
As the phone was already rooted, Im not sure if this app really roots the phone as it didnt require a factory reset as other methods do, but the issue is now fixed!
Thank you for your support on this matter!
Click to expand...
Click to collapse
It does not require a factory reset. That was only needed before when TWRP couldn't decrypt phone, and it can now thanks to zxz0o0 and Pretoriano80. Then you had to Format Data to flash as Magisk installs some things to /data (contrary to what I said earlier, but it does need to patch ramdisk to function ). SuperSU only places its apk in /data/ while the rest lives in ramdisk.
Hey guys. I've noticed that recently my advance power menu app has started acting weird it seems to be losing root access. The only way to get it to work, is to open the app, at which point it's granted root access. It will work once. Each subsequent time it requires being opened again before it will work. I'm on stock rooted us998 20H, with latest magisk.
Ballroomblitz said:
Hey guys. I've noticed that recently my advance power menu app has started acting weird it seems to be losing root access. The only way to get it to work, is to open the app, at which point it's granted root access. It will work once. Each subsequent time it requires being opened again before it will work. I'm on stock rooted us998 20H, with latest magisk.
Click to expand...
Click to collapse
Which Magisk are you on? You can update to later, past 18.x now that you are on last Oreo. Maybe that will help.
Also with stock Pie (which you are not on), we found couldn't use Advanced Power Menu, so had to go back to using Reboot Recovery app shortcut like in the old days. So, you can install that as backup method to get to TWRP. Install, give it root privileges, make shortcut on the desktop.
My Advanced Power Menu is still working fine with Magisk 18.1, but trying to help you find a solution...
ChazzMatt said:
Which Magisk are you on? You can update to later, past 18.x now that you are on last Oreo. Maybe that will help.
Also with stock Pie (which you are not on), we found couldn't use Advanced Power Menu, so had to go back to using Reboot Recovery app shortcut like in the old days. So, you can install that as backup method to get to TWRP. Install, give it root privileges, make shortcut on the desktop.
My Advanced Power Menu is still working fine with Magisk 18.1, but trying to help you find a solution...
Click to expand...
Click to collapse
I had updated to 20.4. that may be part of the problem. I'm going to downgrade to 20.1 and see if that has any effect.
Thanks.
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Ballroomblitz said:
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Click to expand...
Click to collapse
Try one other thing. In TWRP, flash the Magisk uninstaller and then install Magisk 19.3 in TWRP.
When you went back to 20.0 did you flash the uninstaller in TWRP first?
ChazzMatt said:
Try one other thing. In TWRP, flash the Magisk uninstaller and then install Magisk 19.3 in TWRP.
When you went back to 20.0 did you flash the uninstaller in TWRP first?
Click to expand...
Click to collapse
I did. I haven't tried 19.3 yet. I'll give that a try. Something else going on that I don't understand. When I try to download files from someone's Google drive I keep getting an error message that drive has stopped unexpectedly. Don't know if it's related. No problems downloading on my laptop. AIX files FYI.
Ballroomblitz said:
I did. I haven't tried 19.3 yet. I'll give that a try. Something else going on that I don't understand. When I try to download files from someone's Google drive I keep getting an error message that drive has stopped unexpectedly. Don't know if it's related. No problems downloading on my laptop. AIX files FYI.
Click to expand...
Click to collapse
Installed magisk uninstaller. Installed 19.3. APM still requires that I open it so it is granted root access before it works. Got to do it everytime for it to work. Still can't access files on drive either. Still wondering if I need to clean the phone and start over from scratch. I don't necessarily mind doing that. I've tried flashing us998 pie as well as vs996 pie and had issues with both. Now I just want things to work correctly on 20H. I did some kdz flashing after messing with the pie ROMs. I might have done some of that incorrectly.
Ballroomblitz said:
Installed magisk uninstaller. Installed 19.3. APM still requires that I open it so it is granted root access before it works. Got to do it everytime for it to work. Still can't access files on drive either. Still wondering if I need to clean the phone and start over from scratch. I don't necessarily mind doing that. I've tried flashing us998 pie as well as vs996 pie and had issues with both. Now I just want things to work correctly on 20H. I did some kdz flashing after messing with the pie ROMs. I might have done some of that incorrectly.
Click to expand...
Click to collapse
Any other thoughts on this @ChazzMatt?
Ballroomblitz said:
Any other thoughts on this @ChazzMatt?
Click to expand...
Click to collapse
Will answer tonight to give you range of options.
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Bawdy George said:
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Click to expand...
Click to collapse
That's a good point. I don't reboot to recovery much myself. No real reason to. Outside of the occasional backup I might run, getting to recovery isn't regularly needed. As I mentioned to Chazz, however, I'm a little anal about things running the way they're supposed to on my phone. When I push the power button, I like to know that I have the option right then to select recovery without issue. I didn't have a good reason that explains why it no longer works, and that bugs me.
Bawdy George said:
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Click to expand...
Click to collapse
Even easier way is Reboot Recovery app shortcut on desktop. Whereas, the Magisk Manager option is like 3 levels deep in that app.
We used this originally with Oreo, then I found the Advance Power Menu. But Advance Power Menu doesn't work with Pie, so for those KDZ I have to recommend this again:
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to system, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"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"
}
Ballroomblitz said:
That's a good point. I don't reboot to recovery much myself. No real reason to. Outside of the occasional backup I might run, getting to recovery isn't regularly needed. As I mentioned to Chazz, however, I'm a little anal about things running the way they're supposed to on my phone. When I push the power button, I like to know that I have the option right then to select recovery without issue. I didn't have a good reason that explains why it no longer works, and that bugs me.
Click to expand...
Click to collapse
Yeah, I can relate. I got my cheap used V30 with the express intention to tinker with it, and for the wired audio.
Ballroomblitz said:
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Click to expand...
Click to collapse
Here are three options -- each one successively more powerful but also harder.
Option 1
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. You should still have Oreo US998 20h system installed. You aren't wiping internal memory. You will need to reflash Magisk before rebooting.
If you are slightly OCD, you will also reflash the other two root files -- Encryption Disabler (Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip) and Root Check Disabler (AK3_RCTD_Remover.zip). You shouldn't NEED to do that -- as you are just factory resetting what you already have -- but I would rather do it and not need it, than not do it and then find out "Oh, for some reason you did need to do it". (You can find those two files in the Option 3 link.) Flash Magisk, then the Encryption Disabler, Root Check Disabler, then Magisk AGAIN. Then reboot.
Option 2.
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. Furthermore, wipe internal memory. You will be asked to confirm with YES. You will have no OS, so do NOT reboot from TWRP until you fix that. Before you use this option, you will need US998 Oreo 20e, 20f, 20g, 20g, 20h TWRP flashable zips + Magisk + Encryption Disabler + Root Check Disabler stored on microSD card ahead of time OR connect phone to PC while in TWRP mode and drag over all the files like with a flash drive. If you are depending on TWRP drag-and-drop to transfer files after wiping phone's internal memory, please test this functionality ahead of time. You don't want to wipe your internal memory and then find your phone TWRP can't see your PC via USB cable.
Flash all the TWRP flashable zips back-to-back, then flash Magisk, then the Encryption Disabler, Root Check Disabler, then Magisk AGAIN. Then reboot. You can "stack" them all to flash back-to-back in TWRP, then hit the install button and they will successively go through the list you create.
Option 3
Use Dev Patched LGUP to flash US998 20h Oreo KDZ in Refurbish mode. This will totally take you back to stock firmware, but you will still have unlocked bootloader. Then, follow this post instructions below to reinstall TWRP and root. It's basically Section 6 of WTF Instructions in a standalone post. IGNORE that it says it's for Pie. I wrote it for people who updated to Pie through KDZ and needed to reinstall TWRP. It will work for you on US998 20h Oreo.
INSTALL or REINSTALL TWRP on stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
ChazzMatt said:
Option 1
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. You should still have Oreo US998 20h system installed. You aren't wiping internal memory. You will need to reflash Magisk. If you are slightly OCD, you will reflash the other two root files also -- encyrption disabler and root check disabler. You shouldn't NEED to do that, but I would rather do it and not need it, than not do it and then find out "oh, for some reason you did need to do it".
Option 2.
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. Furthermore, wipe internal memory. You will be asked to confirm with YES. You will have no OS. So, before you do this, you will need US998 Oreo 20e, 20f, 20g, 20g, 20h TWRP flashable zips + Magisk + encryption disabler + root check disabler on microSD card ahead of time or connect phone to PC while in TWRP mode and drag over like a flash drive. If you are depending on TWRP drag and drop, test this functionality ahead of time. You don't want to wipe your internal memory and find your phone TWRP can't see your PC via USB cable.
Flash all the TWRP flashable zips back to back, then flash Magisk, then the encryption disabler, root check disabler, then Magisk again. Then reboot.
Option 3
Use Dev Patched LGUP to flash US998 20h Oreo KDZ in Refurbish mode. This will totally take you back to stock firmware, but you will still have unlocked bootloader. Follow this post to reinstall TWRP and root. It's basically Section 6 of WTF Instructions in a standalone thread. IGNORE that it says it's for Pie. I wrote it for people who updated to Pie through KDZ and needed to reinstall TWRP. It will work for you on US998 20h Oreo.
INSTALL or REINSTALL TWRP on stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Click to expand...
Click to collapse
Man! Don't know what to say, but thank you for taking the time to provide such an in-depth assist. I'll start picking away tomorrow, and let you know what happens.