Related
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
jbonlinea said:
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
Click to expand...
Click to collapse
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
I am using pixel experience 8.1 oreo rom in my redmi notr 4.and i have also install google canera mod.mgcmod5.i have done all the settings but ehen i am trying to take puctures its force closing and lagging..need solution..
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
After every OTA update do I need to re-flash everything?
ÀnkanKoley said:
After every OTA update do I need to re-flash everything?
Click to expand...
Click to collapse
If RedWolf succeeds OTA survival, then there is no need. But after OTA if RedWolf is replaced by stock recovery, then yes you'll have to flash everything once again. Refer RedWolf thread for more details on OTA survival.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
jbonlinea said:
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
Click to expand...
Click to collapse
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
What would broke on miui camera?
amnher said:
What would broke on miui camera?
Click to expand...
Click to collapse
The HDR mode.
ArK96 said:
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
Click to expand...
Click to collapse
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone
jbonlinea said:
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone pen
Click to expand...
Click to collapse
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
ArK96 said:
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
Click to expand...
Click to collapse
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
jbonlinea said:
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
Click to expand...
Click to collapse
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
ArK96 said:
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
Click to expand...
Click to collapse
Thank you very much !
jbonlinea said:
Thank you very much !
Click to expand...
Click to collapse
No problem.
ArK96 said:
No problem.
Click to expand...
Click to collapse
hum, :silly:
the link you sent for adb do not work
jbonlinea said:
hum, :silly:
the link you sent for adb do not work
Click to expand...
Click to collapse
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
ArK96 said:
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Click to expand...
Click to collapse
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
jbonlinea said:
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
Click to expand...
Click to collapse
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
ArK96 said:
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
Click to expand...
Click to collapse
Hi dude
I'm almost done but back to square 0, with blinking black screen at boot !
No crisis, I can still go to redwolf recovery, as well as fastboot.
How it happend ?
In magisk manager (on miui) I checked what modules were available in the download panel, and tried "Google Pixel 2 Experience" or something similar.
On reboot, the mi logo is displayed, then I have a black screen blinking on and off, without mi logo, just black, on and off
I thus wanted to unistal the mod with magisk module uninstaller, but the install fails and return that "magisk is not installed" and "magisk is required for this mod"
So I obviously couldn't try to uninstall the supposed failing module
I thus rebooted in redwold and installed magisk from redwolf (the included release), things went well
However, I still cant install magisk module uninstaller, getting the same error as above.
I took my chance and try to re-install magisk from the zip filed I downloaded, the install process was successfull, but I still can't install magisk mod uninstaller, and the black screen issue persist.
Lastly, I took my chance and try to re-install lazy flasher, the install process was successfull, but the black-screen issue persist.
To be honest, I'm a bit sctuck now.
What may be the right procedure to solve this problem ?
Am I screwed and do I have to reflash a whole rom ?
If so Should I do it from redwolf, and how ?
Or should I do it from the pc with fastboot, and how ?
Thanks for your directions
ps: i was interested by pixel 2 experience module as at it was written that it was compatible with mido and provides camera2api, which might have been a nice combo.
ps 2 : I also did installed dolby as you suggested, it worked but the demo crashed to app
ps 3 : I also did installed youtube vaccant, but I couldn't see any new app and my original youtube still had add and couldn't play in the back... not sure it reveals something on the effectiveness of magisk...
installing atm...
flash-all (minus -w) worked fine on my Wife's P3. Magisk 19.3 is working fine, and twrp-3.3.0-0-blueline installs (using ramdisk install method) and dycripts fine as long as you haven't done a full wipe since a couple of Google builds ago when a new install wouldn't decrypt.
public WiFi sign in issue not solved yet.
sliding_billy said:
flash-all (minus -w) worked fine on my Wife's P3. Magisk 19.3 is working fine, and twrp-3.3.0-0-blueline installs (using ramdisk install method) and dycripts fine as long as you haven't done a full wipe since a couple of Google builds ago when a new install wouldn't decrypt.
Click to expand...
Click to collapse
What is "using ramdisk install method" ?
fahmi182 said:
What is "using ramdisk install method" ?
Click to expand...
Click to collapse
That is the permanent TWRP install method that was mentioned a couple of months ago when TWRP said that they would no longer be doing the .zip installers soon. From the main screen in TWRP (after launching the fastboot boot .img), got to advanced and you will see a ramdisk install link. Use that to install the .img (make sure to put the .img on your phone before running it from fastboot) of TWRP permanently.
sliding_billy said:
That is the permanent TWRP install method that was mentioned a couple of months ago when TWRP said that they would no longer be doing the .zip installers soon. From the main screen in TWRP (after launching the fastboot boot .img), got to advanced and you will see a ramdisk install link. Use that to install the .img (make sure to put the .img on your phone before running it from fastboot) of TWRP permanently.
Click to expand...
Click to collapse
Have link for that?
fahmi182 said:
Have link for that?
Click to expand...
Click to collapse
It has been discussed on the P3 and P3XL TWRP forums, but here is the original article.
https://www.xda-developers.com/twrp-3-3-0-release/
No problem installing the July update and Magisk using my ol' pre-patch the boot image method. I've forgotten how to get the device certified in the Play Store now that you can't clear data for it anymore (it shows 0 storage used). I already have it hidden in Magisk. Does it just take some time to refresh the certified status?
CSX321 said:
No problem installing the July update and Magisk using my ol' pre-patch the boot image method. I've forgotten how to get the device certified in the Play Store now that you can't clear data for it anymore (it shows 0 storage used). I already have it hidden in Magisk. Does it just take some time to refresh the certified status?
Click to expand...
Click to collapse
The issue of not being able to clear Play Store cache and data (gray buttons) is likely caused by a Magisk module. It is for me on the 3XL, and in my case it is Edge Sense. Try disabling your modules and reboot. You should be able to clear data and re-enable your modules.
sliding_billy said:
The issue of not being able to clear Play Store cache and data (gray buttons) is likely caused by a Magisk module. It is for me on the 3XL, and in my case it is Edge Sense. Try disabling your modules and reboot. You should be able to clear data and re-enable your modules.
Click to expand...
Click to collapse
Ah, I'm using Edge Sense, too. Although since my earlier post I manually cleared the Play Store data with the package manager (pm clear com.android.vending). Now I guess I just have to wait for it to refresh the certified status (and my list of installed apps).
CSX321 said:
Ah, I'm using Edge Sense, too. Although since my earlier post I manually cleared the Play Store data with the package manager (pm clear com.android.vending). Now I guess I just have to wait for it to refresh the certified status (and my list of installed apps).
Click to expand...
Click to collapse
You can get the installed app list back (as well as any updates that aren't showing) by installing something from your library or just some random app. Delete if necessary of course. The certified status is just a matter of waiting. It'll show up randomly in a day or two most likely.
sliding_billy said:
That is the permanent TWRP install method that was mentioned a couple of months ago when TWRP said that they would no longer be doing the .zip installers soon. From the main screen in TWRP (after launching the fastboot boot .img), got to advanced and you will see a ramdisk install link. Use that to install the .img (make sure to put the .img on your phone before running it from fastboot) of TWRP permanently.
Click to expand...
Click to collapse
So use ramdisk method after. We can don't use fastboot direct into recovery?
Edemilorhea said:
So use ramdisk method after. We can don't use fastboot direct into recovery?
Click to expand...
Click to collapse
You still need to use the fastboot boot .img to even get into TWRP do the install with ramdisk. You do not need to permanently install TWRP though. You can still use fastboot to get into TWRP but leave stock recovery permanently installed. Many do that so they can sideload OTAs.
sliding_billy said:
You still need to use the fastboot boot .img to even get into TWRP do the install with ramdisk. You do not need to permanently install TWRP though. You can still use fastboot to get into TWRP but leave stock recovery permanently installed. Many do that so they can sideload OTAs.
Click to expand...
Click to collapse
If i install ramsisk, i can use magisk?
Twrp and magisk can in the phone at the same time?
Edemilorhea said:
If i install ramsisk, i can use magisk?
Twrp and magisk can in the phone at the same time?
Click to expand...
Click to collapse
Yes, the ramdisk is not something you are installing. It is simply the method that TWRP is using to install itself permanently. Of course, you can then use the permanent version of TWRP (or the fastboot .img version) to flash Magisk.
sliding_billy said:
Yes, the ramdisk is not something you are installing. It is simply the method that TWRP is using to install itself permanently. Of course, you can then use the permanent version of TWRP (or the fastboot .img version) to flash Magisk.
Click to expand...
Click to collapse
Sounds I still not use permanently Twrp, just use fastboot to into recovery enough.
I want to ask a few problems.
I use twrp flash root and magisk better than use patch boot.img?
If I root my phone and i will ota update in future. Just use magisk manager to uninstall magisk and restore factory boot.img?
And now google pay work on new one magisk?
Edemilorhea said:
Sounds I still not use permanently Twrp, just use fastboot to into recovery enough.
I want to ask a few problems.
I use twrp flash root and magisk better than use patch boot.img?
If I root my phone and i will ota update in future. Just use magisk manager to uninstall magisk and restore factory boot.img?
And now google pay work on new one magisk?
Click to expand...
Click to collapse
Using TWRP to root is much easier than patching boot.
If you take a monthly build, yes you will lose root. You don't need to uninstall anything though. Just run the TWRP .img and flash Magisk again. There are Magisk settings like app hides and such that are retained during the update since the are in user and not system. Uninstalling will cause you to have to redo that stuff.
Magisk does not in and of itself give you the ability to use Google Pay. There are a couple of threads on the Magisk page with a lot of information. I use the exact method spelled out in the OP of the thread that starts with [working] on both a Pixel 3 and Pixel 3 XL. There is always a game of cat and mouse with Google and certain methods, but this has been working for me for a few months.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
sliding_billy said:
Using TWRP to root is much easier than patching boot.
If you take a monthly build, yes you will lose root. You don't need to uninstall anything though. Just run the TWRP .img and flash Magisk again. There are Magisk settings like app hides and such that are retained during the update since the are in user and not system. Uninstalling will cause you to have to redo that stuff.
Magisk does not in and of itself give you the ability to use Google Pay. There are a couple of threads on the Magisk page with a lot of information. I use the exact method spelled out in the OP of the thread that starts with [working] on both a Pixel 3 and Pixel 3 XL. There is always a game of cat and mouse with Google and certain methods, but this has been working for me for a few months.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
Click to expand...
Click to collapse
OK And Want to know root and magisk is wrok on Q-BETA Too?
Edemilorhea said:
OK And Want to know root and magisk is wrok on Q-BETA Too?
Click to expand...
Click to collapse
Magisk is working with Q but TWRP is not yet, so you'd have to root with manually patched image. There are posts on the P3 and P3XL pages about how to manually patch to root. There does not seem to be an official solution for Google Pay yet. I don't see anything in Q that makes it worth me not waiting for all of the solutions to be created. They are on 4 of 6 test builds (public will likely coincide with Pixel 4 in the fall), so there is time.
sliding_billy said:
Magisk is working with Q but TWRP is not yet, so you'd have to root with manually patched image. There are posts on the P3 and P3XL pages about how to manually patch to root. There does not seem to be an official solution for Google Pay yet. I don't see anything in Q that makes it worth me not waiting for all of the solutions to be created. They are on 4 of 6 test builds (public will likely coincide with Pixel 4 in the fall), so there is time.
Click to expand...
Click to collapse
Really thanks your answer.
I think I still use PIE, and I will go to root my pixel 3 now, and to study how to Gpay work on Magisk 1.93 now
I saw a lot of person said to use SQL-Edit have to Gpay work on Rooted.
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
Disclaimer: I am not an android developer an I am not responsible for bricking your device. The forums contain instructions for unbricking and reflashing your device. You have been warned.
Ok folks I am new here. I spent countless hours trying to debloat the moto e5 play (android oreo 8.1 go). Many headaches and sleepless hours later I finally figured things out the painful way.
Firstly you need to flash twrp recovery. Please see the attached recovery img. There are many recovery images available on the internet but i have found that this one works for me. You must download the correct image/zip for your device or else you will end up in a bootloop. Also you must flash the recovery imag as follows:
Fastboot flash recovery recovery.img (using fastboot Tools).
Just create a folder and copy the image file in it and unzip your fastboot tools in the folder you created. Then open a command window in the folder and with your device in fastboot mode go ahead and flash the recovery.
Secondly You need to install either supersu or magisk to root. I prefered magisk and you can find and download the latest magisk on the internet as well as the updated magisk zip files. Any of the latest magisk 8.0 should work.
Thirdly you should install kingoroot (Not kingroot). Kingoroot seems to be the only one click root app that works on this device. Grant it superuser rights and start uninstalling google apps of your choice (again I will not attach the kingoroot I used. You can google it).
Please note that if you uninstall google completely some apps such as google contacts, calender and youtube will crash. You will see the updated date and time on your phone but you will be unable to save things in the calender as when google was installed. If you want you can uninstall google play services and reinstall a different version of google play services which is compatible with android oreo 8.1 go. then use kingoroot to uninstall calender and contacts and find a compatible version. You should install youtube vanced instead although at this time i am unable to get vanced sign in with microg to work.
You can also uninstall stock youtube and look for a compatible version. I tried installing xposed installer on the E5 bot it causes the device to bootloop no matter which version I tried. I installed TAI CHI xposed but I can't understand chinese so it didnt work for me. Only virtual xposed works but the Aurora store does'nt work.
If anyone else can get a working version of microg and xposed to work I would be so thankful. I have'nt found any custom roms for the E5 but i am always on the lookout.
PS: If you reflash your entire stock rom and you are unable to get a carrier signal and then download another rom from lolinet (I think that is the place I downloaded the stock ROM) and unzip on your pc. Unzip adb and fastboot into the folder where you unzipped the rom. Flash as follows:
fastboot erase modemst1
fastboot erase modemst2
fatboot flash NON-HLOS.bin
No need to reflash the whole ROM just these. That should work.
.
greetings friend
maybe you can help me my equipment is a moto e5 play xt1920-19 pettyl
although I have a recovery 3.3.1.0 that I downloaded from here on this forum.
but I have not been able to install custom rooms and I think it is the recovery.
when I make a backup of everything and
when I want to restore it, everything is lost and it starts only from the beginning as if it were formatted. and also and noticed that the internal memory is not read by the recovery.
Could you help me or at least guide me?
Rgodoy8080 said:
greetings friend
maybe you can help me my equipment is a moto e5 play xt1920-19 pettyl
although I have a recovery 3.3.1.0 that I downloaded from here on this forum.
but I have not been able to install custom rooms and I think it is the recovery.
when I make a backup of everything and
when I want to restore it, everything is lost and it starts only from the beginning as if it were formatted. and also and noticed that the internal memory is not read by the recovery.
Could you help me or at least
Click to expand...
Click to collapse
Strange. It works perfectly on my device. The only roms i flashed was magisk repo and viperfx and they both work very well. I am running android 8.1 go edition. I havent found any custom roms for the devicesuch as lineage OS etc. Development is very slow for this device. You may only be able to flash magisk modules. Also I assume you are using the original stock rom the device came with and it hasnt been altered with a rom from a similar spec device . There are many variants of the E5 play and you need to be sure your device hast the correct firmware.
Rgodoy8080 said:
greetings friend
maybe you can help me my equipment is a moto e5 play xt1920-19 pettyl
although I have a recovery 3.3.1.0 that I downloaded from here on this forum.
but I have not been able to install custom rooms and I think it is the recovery.
when I make a backup of everything and
when I want to restore it, everything is lost and it starts only from the beginning as if it were formatted. and also and noticed that the internal memory is not read by the recovery.
Could you help me or at least guide me?
Click to expand...
Click to collapse
What are you trying to flash? I havent seen any custom ROM OS for this model. You can modify by replacing google apps and install magisk and so on but there are no custom ROMs available for XT1920-19 at the moment.
Wondering if anyone else has run into this. Two days ago, the Magisk app prompted to upgrade, so I did. When I tapped to install, it says it did successfully, but when I tapped on "MManager" (the hidden Magisk app), it went into a loop prompting me to install again each time. I figured uninstalling completely and reinstalling would fix it, but that is not the case. The app is working fine now, but I cannot get Magisk to install. No matter what version Magisk app I use to patch the boot.img and fastboot flash it, it still says "Installed: N/A" inside of Magisk and I do not have root. I have tried version 25200 (stable), and canary builds 25201, 25203, and 25205. I believe I was previously on 25203 and was upgrading to 25205 when the install loop happened. I believe the issue is posted on the Magisk Github repo in the issue tracker here.
Is anyone else experiencing this? Are there any suggestions on how to resolve? My latest attempts have been failures. Dirty flashing the factory image, then fastboot flashing the patch boot.img. I fastboot flashed the vbmeta disable dm-verity and verification again, then flashed the patched boot.img. I attempted to fastboot boot the patched boot.img, to then potentially do a Direct Install but Magisk still shows not installed. And lastly, I've flash both boot_a and boot_b with the patched boot.img.
Any suggestions are welcome.
Well, your big mistake was not having Magisk unhide the app. Always do that before taking an update to Magisk.
That said, a clean install using Google's restore page is likely your only means of fixing this. Sucks because you have to set up again from square 1, but necessary in your case.
I had never had an issue with it in the past, always been able to upgrade while hidden.
There's no other solution? What exactly is wrong here?
Sunsparc said:
I had never had an issue with it in the past, always been able to upgrade while hidden.
There's no other solution? What exactly is wrong here?
Click to expand...
Click to collapse
I can't really speak as to "exactly" what is wrong, but I have a suggestion...
Make sure you don't have two instances of Magisk installed - one hidden and one not.
Delete all downloaded Magisk packages from /downloads, then re-download the version you're trying to install.
Unhide Magisk.
Force stop Magisk, clear data, uninstall.
Go back to downloads and install the one you've been trying to update to.
If that doesn't work...
Again, ensure you only have one instance of the Magisk app installed
Download the debug app - version checks are disabled in debug
Unhide Magisk
Install the debug app (should ask to update). If this does not work, try uninstalling Magisk (just the app from Android, don't use Uninstall inside the app)
Update the Magisk patch, reboot (this ensures the Magisk binary ignores version mismatch)
Install the version you're trying to update to
I think this may be where I'm having the issue. When I try to install certain versions, it's acting like it's already installed. When I check app drawer and Apps, it does not show any other Magisk installed. Is there a way I can verify? Or an adb command to dump out all installed apps and their com. names so I can manually comb through?
I figured it out!
I use Shelter to clone apps into work profile so I can use multiple instances. Once I disabled the Work Profile and reinstalled Magisk, everything is working properly now.