Related
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
As far as I'm aware the rom should be pre rooted and all you'll need to do is install supersu from googleplay and then update the su binaries from within the supersu app.
Set it to option 4 (apps and abd) and go about installing supersu first as the app from googleplay and if no joy then as a flashable zip file.
Beamed in by telepathy.
amitrider04 said:
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
Click to expand...
Click to collapse
Did you try to flash the addonsu.zip from LineageOS website?
You must flash it to get root access in LineageOS 14.1
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Flash a stock firmware and start over.
Beamed in by telepathy.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
Are you sure you flashed the correct addonsu???
As far as i remember, the s3 doesn't have 64x, flash the normal arm version (arm32x).
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
flash supersu.zip 2.79 with twrp it worked for me
Thanks it also worked for me:laugh:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Zwolly said:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Click to expand...
Click to collapse
It works, you will get an error in recovery, but when you boot, you will get root access normally, i don't why the error happens, but it's harmless anyway.
Root fix
I'm not sure if you have fixed it yet but just in case if this helps the way I got around this is by simply downloading the latest super su zip from the official site and manually flashing via twrp kinda sucks but it works the first boot took a little though so if you try this and it takes forever for your device to not just wait because it can take up to 15 min the first time. So basically as long as you have twrp you are rooted technically it's just based on the rom wether they chose to support it if not the zip always works but you need the app too.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
S3 has arm32. So neither x86 not x64 would work. You should've flashed addonsu.zip for 32.
Sent from my Pixel XL using Tapatalk
The below works for Nougat ROMs. I didn't have a chance to try with Oreo yet, sorry.
The ability to encrypt a device doesn’t depend on the presence of the stock recovery nor no-verity-opt-encrypt being flashed or not. It simple needs an unrooted boot.img at the moment the encryption is attempt. You do however need no-verity-opt-encrypt flashed to allow a custom ROM to boot. So the desired state to allow encryption from within a custom ROM is to have the stock boot.img with only no-verity-opt-encrypt applied to it.
The simplest sequence to archive a fully encrypted device with a custom ROM is the following:
- Flash (I recommend Dr. Ketan) ROM as always, but DISABLE ANY ROOTING in the installer
- Encrypt the device from the settings menu
- Flash the ROM one more time, this time WITH MAGISK ROOT. It will display a warning about /data not being mountable as it is now encrypted. That is ok as everything we need is already in place
If you didn’t choose fast encryption (which I recommend for security), download Trimmer (fstrim) from Play Store, tick all partitions and click Trim Now. This will free up all the sectors overwritten by the encryption process on the flash controller and makes your device work super smooth like before encryption.
This obviously only works that simple with ROMs that offer the ability to initially flash without root and if you’ve been on stock or a rootless ROM before. If that’s not the case you have the following options:
- Flash Magisk Uninstaller after initial ROM flash. You may have to reflash no-verity-opt-encrypt in TWRP again, in case it fails to boot now.
- Flash the stock book.img back in Odin and apply no-verity-opt-encrypt in TWRP. Use 7-Zip to create a tar only containing the stock BOOT.IMG and flash it in Odin using the AP slot.
- Flash back a TWRP backup taken of the boot partition before installing a root ROM, but after flashing no-verity-opt-encrypt.
Updating your ROM works no different then usual also. Just dirty flash over if it's the same ROM unless the release notes explicitly mention to factory reset. You don't need /data writable for a ROM update.
Enjoy your fully encrypted and rooted device.
Thank you, I'll try this when I'm at home. Nice recommendation with the trimmer tool, too!
Chainfire root & encryption [N950F]
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Encryption in oreo rom
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
halloweltkk said:
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
Click to expand...
Click to collapse
I haven't tried it with Oreo yet. But I'll probably give it a spin with Oreo within the next month. Sorry for that, will add a note to the guide.
little-endian said:
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Click to expand...
Click to collapse
Sorry for the late reply. I have no S7 to try, but believe using Magisk instead of SuperSu should work. Magisk has means to work with devices with forced encryption. AFAIK with an encrypted device it will put things to the cache partition first and on the next boot move things to the final location. I'm not aware of a similar mechanism in SuperSu.
I would try to unroot with Supersu, flash TWRP and give Magisk a spin. Keeping the stock ROM should be ok, however it will likely fail SafetyNet after plain Magisk Root. In that case try the universal SafetyNet fix also available as module within the Magisk app. If it fails to boot after Magisk root, try flashing the no verify opt encryption patch, but I don't think you need it.
I tried it in O5 as well and cannot get it to work. Just soft reboot as mentioned. No magisk just the ROM with stock kernel and still fails. Any advice?
will this work on s8?
Worked for me on S9 (GF-960F)! Thanks!
Had to use the Magisk Uninstaller first though, as I've alrady rooted.
Has anyone had any luck with this on Oreo? I've been trying to get my N960F simultaneously rooted and encrypted, but haven't had any luck with any method I've tried thus far. I can root it just fine, or encrypt it, but I've not found a way to do both at the same time without it resulting in "Verification failed" and a reset loop.
no-verity-opt-encrypt unable to find boot block location
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
sllorent said:
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
Click to expand...
Click to collapse
Maybe it's too late to answer to you, but this could be usefull for someone else.
I had same problem, "Unable to find boot block location", with same TWRP 3.2.3.
To solve this problem i downgrade TWRP 3.2.3 to TWRP 3.1.0-1 - Nougat that i found here https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627.
Than i followed the step to root, but i used Magisk 17.3 instaead SuperSu (Magisk 18.0 gave me some problem). Now i have root permissions with Magisk
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
sllorent said:
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
Click to expand...
Click to collapse
I don't know, sorry. How can i check that?
Inviato dal mio SM-T819 utilizzando Tapatalk
Android root + encryption possible at all ???
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Any thoughts on this? And other ideas on Android / third party encryption apps? Encrypting containers with EDS would be an alternative (recommended by Veracrypt) since full disc encryption is still not available for Android (why btw.? nobody seems to care...) - but I am not sure if one could run / move apps into the container (like contacts, sms, e-mail-apps etc.)...
Cheers!
no ideas - nobody ??
no ideas - nobody ??
Finally, rooted with Magisk and encrypted data note8 exynos
Followed these threads
https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
https://forum.xda-developers.com/note-fe/how-to/exynos-8890-sm-n935f-ds-twrp-root-t3771767
Tested with stock Nougat and TWRP-3.2.1.0-greatlte (with twrp-3.2.3-0 fail)
got these combinations working
Samsung_S7+Oreo+Magisk+Xposed+root+encryption
LG_V30+OreoAOSP+Magisk+Xposed+root+encryption(+BThandsfree)
also according to TWRP and the threads it was impossible. the TWPR might not be able to read files, i don't care as long as i have encrypted system. I can flash from the system.
Wouldn't like 3rd party solution as i want Secure Boot and type password during the boot.
Encryption and root is a must. But it's getting difficult more and more nowadays. ROM threads don't list limitations since KNOX was ever introduced, and that sucks. Instead of "knox will be tripped, warning boot screen will be showm, TWRP won't read filesystem, BT handsfree won't work, encryption won't work" you get "no limitations". Have to read full threads to discover the truth.
Hope Note9 and S10 will be ok.
No encryption working on my N960FD
I tried to install it while updating to DrKetan p09 and it doesnt work.
Is it possible for somebody to help me ?
I ve done a clean install and unrooted the no-verity-encrypt flash (The phone didn't even unlocked with pin )
xdaparanoia said:
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Cheers!
Click to expand...
Click to collapse
Is this true??
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...
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Thanks in advance guys
Fcleon said:
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Click to expand...
Click to collapse
Yes, that's the correct place to get the TWRP image file from. You've backed up so that's good. Make sure the PC you're using has USB 2.0 ports. If it only has USB 3.0 ports you'll need an external USB 2.0 hub for this to work. fastboot boot the TWRP image file and backup using TWRP. I backup system image, vendor image, boot & data. You don't need System or Vendor. Flash Magisk and install the Magisk manager apk. I use AdAway for blocking ads which requires root. You don't need to flash dm-verity, DFE or diskquota disabler. Nor do you need to worry about security.
Fcleon said:
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Thanks in advance guys
Click to expand...
Click to collapse
i am on 3.3.3-1 unofficial, the touch issues fixed in this one
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
download link
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw
- Magisk disables Dm Varity itself while flashing
- but for DFE you need to flash saperate Disable Force Encryption - Treble.zip
i replied similar question(s) and more YESTERDAY at https://forum.xda-developers.com/showpost.php?p=80170044&postcount=3
if you can manage some time, Please do read ~ its about rooting to custom rom flashing
edit: https://www.youtube.com/watch?v=BsHtfLh6azw plz see
YasuHamed said:
i am on 3.3.3-1 unofficial, the touch issues fixed in this one
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
download link
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw
- Magisk disables Dm Varity itself while flashing
- but for DFE you need to flash saperate Disable Force Encryption - Treble.zip
i replied similar question(s) and more YESTERDAY at https://forum.xda-developers.com/showpost.php?p=80170044&postcount=3
if you can manage some time, Please do read ~ its about rooting to custom rom flashing
edit: https://www.youtube.com/watch?v=BsHtfLh6azw plz see
Click to expand...
Click to collapse
Ok but in my situation and for the things that I am gonna do, do you really think I need to disable DFE and the other things?, disabling all this things are for what reason?
guhvanoh said:
Yes, that's the correct place to get the TWRP image file from. You've backed up so that's good. Make sure the PC you're using has USB 2.0 ports. If it only has USB 3.0 ports you'll need an external USB 2.0 hub for this to work. fastboot boot the TWRP image file and backup using TWRP. I backup system image, vendor image, boot & data. You don't need System or Vendor. Flash Magisk and install the Magisk manager apk. I use AdAway for blocking ads which requires root. You don't need to flash dm-verity, DFE or diskquota disabler. Nor do you need to worry about security.
Click to expand...
Click to collapse
Alright then, I have another question, I am right now on 10.3.7 when Xiaomi releases a new version how do I update it, after rooting, normal OTA or I need to do another process?
Fcleon said:
Ok but in my situation and for the things that I am gonna do, do you really think I need to disable DFE and the other things?, disabling all this things are for what reason?
Click to expand...
Click to collapse
now the question is SHOULD you be disabling DFE and if yes why? if no WHY ?
Google has been putting great efforts recently to keep users data secured !
force encryption encrypts data (internal storage) for the user . however it consumes battery and later if you are trying to flash roms , there are high chances you will be locked out! because twrp cannot READ that encryption. hence after installing rom, if you go back to twrp! and try to access internal STORAGE, twrp will give your error that unable to Mount storage!
now at the time CLEAN FLASHING if you had flashed DFE, it will DISABLE GOOGLE Encryption and twrp will able to access your data
YasuHamed said:
now the question is SHOULD you be disabling DFE and if yes why? if no WHY ?
Google has been putting great efforts recently to keep users data secured !
force encryption encrypts data (internal storage) for the user . however it consumes battery and later if you are trying to flash roms , there are high chances you will be locked out! because twrp cannot READ that encryption. hence after installing rom, if you go back to twrp! and try to access internal STORAGE, twrp will give your error that unable to Mount storage!
now at the time CLEAN FLASHING if you had flashed DFE, it will DISABLE GOOGLE Encryption and twrp will able to access your data
Click to expand...
Click to collapse
Alright so in theory is better to disable force encryption to improve battery and to have the option to install a custom ROM, although at the moment I do like MIUI. And what about disk quota disabler ? What is the reason to disable that?
And if I disable FDE I have to permanent install TWRP ? Because since I just want magisk for the moment I wanted to just use TWRP temporarily and like for making my phone kinda more secure if someone steals it from it
Fcleon said:
Alright so in theory is better to disable force encryption to improve battery and to have the option to install a custom ROM, although at the moment I do like MIUI. And what about disk quota disabler ? What is the reason to disable that?
And if I disable FDE I have to permanent install TWRP ? Because since I just want magisk for the moment I wanted to just use TWRP temporarily and like for making my phone kinda more secure if someone steals it from it
Click to expand...
Click to collapse
1. for disk quota disable or not and why please read more on this subject at https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389. (mainly to make storage stats faster, disk quota is used and to obsolete them you disable it)
2. Twrp is the flasher! and you can flash any modes, roms (designed for the device in your hand!) hence you don't have to keep it flashed! you can call the twrp from fastboot command from pc when you want to!
Thanks everyone I finally unlocked the bootloader, and then used fastboot boot TWRP, backup up everything, then flashed magisk, and then FDE, I can say that the device feels much faster, maybe is the placebo effect but anyway I like it.
The last question that I have is what happens when Pocophone releases a new stable version?, should I just use TWRP and flash the ota file? and i guess flash magisk again and fde again right?
Fcleon said:
Thanks everyone I finally unlocked the bootloader, and then used fastboot boot TWRP, backup up everything, then flashed magisk, and then FDE, I can say that the device feels much faster, maybe is the placebo effect but anyway I like it.
The last question that I have is what happens when Pocophone releases a new stable version?, should I just use TWRP and flash the ota file? and i guess flash magisk again and fde again right?
Click to expand...
Click to collapse
What I always do when updating is:
1. fastboot boot twrp
2. uninstall magisk
3. install full rom (not ota)
4. install magisk
5. reboot
6. install magisk manager
7. install modules
I have a Alcatel U3 4055T phone (same as TCL 4055T) and I have tried all the simple methods (PC/APK …Kingroot, kingoroot etc) of rooting it with NO SUCCESS. It has Android 6.0, Baseband MT6737M, 3G/LTE. Now I have thought of trying rooting it manually, I have read online and figured out that I might need do as follows:
(1( UNLOCK the boot-loader
(2) FLASH a custom Recovery (TWRP)
(3) EXTRACT Boot image from the phone
(4) PATCH the image in (3) with Magisk
(5) FLASH the patched image back to the phone
I have just successfully unlocked the boot-loader BUT I can find any version of TWRP or any other custom recovery to FLASH into my phone. I have tried all suitable TWRP(s) that I could find online with no success.
PLEASE help me out in rooting my phone … any help from the members and admins will be highly appreciated.
This is to inform that I have successfully rooted this phone using Magisk and now I can enjoy all those apps which require root. I wish to thank the makers of Magisk ... this was simple and straightforward . BUT I I still have stock recovery.
Hello friend can you share the details, I just installed Magisk but cant find any option to root.
sorh said:
Hello friend can you share the details, I just installed Magisk but cant find any option to root.
Click to expand...
Click to collapse
What is the model number of your phone??
sorh said:
Hello friend can you share the details, I just installed Magisk but cant find any option to root.
Click to expand...
Click to collapse
Well … the method I had used only applies to devices with MTK chips. The Best part is that the device only gets rooted after boot && running a script. Means if you wish to keep it un-rooted (for some reasons) you can also do that. The package contains 2 apks and one of them is “magisk” … and other is “mtk-easy-su” install both , you only have to run the later and it will execute magnisk. You can also tic the box for automatically root at boot. Here is the package: https://offlinemodapk.com/mediatek-easy-root-apk/#more-3134
To run those kinds of application, you need the Magisk Manager app if you have a rooted device. By enabling the magisk hide on the app, you would able to run whatever application you need, which cannot work on rooted devices. Becric