Hi,
i managed to root the device using the S5E procedure
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806).
Everything worked fine.
Then i debloated using pm some apps (same list i used before on my S5e).
Unfortunately the S6 did not boot anymore. (bootloop)
So went to download mode, and reflashed the stock rom.
My BL still was unlocked (message on boot), but i had no "OEM Unlocking" option in Dev settings.
So i locked the BL again. Reflashed stock, unlocked BL, took my modified AP file i created on root before and flashed. But Odin "Failed". Don't remember exactly, but think was failed writing, as if the BL was locked.
No idea why. Do i have to recreate the modified AP file every time, even when staying on same version)
Now i'm back to stock, BL locked, "OEM Unlocking" disabled. I would say Factory new.
Should i proceed again to the S5e root method, or did i miss something?
Thanks
did you manage to find a solution ?
I followed these instructions to root my s6 wifi
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Only issue I have now is occasionally rebooting I would lose root and need to reflash the modified AP made with Magisk via Odin again. Not sure why.
Momotani-Hitoshi said:
I followed these instructions to root my s6 wifi
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Only issue I have now is occasionally rebooting I would lose root and need to reflash the modified AP made with Magisk via Odin again. Not sure why.
Click to expand...
Click to collapse
I'm not familiar with that method, but from reading the instructions it looks like Magisk is installed in recovery? You need to select to boot with Root each time, by booting into recovery first then selecting (I'm paraphrasing) "boot with root" or you'll just boot to stock.
I'm not sure why you've chosen to go down that route, but there's a much better solution for the S6 - Which is to install TWRP and a custom Kernel. It'll nullify any need of booting into recovery or creating any custom AP files.
https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
bartleby999 said:
I'm not familiar with that method, but from reading the instructions it looks like Magisk is installed in recovery? You need to select to boot with Root each time, by booting into recovery first then selecting (I'm paraphrasing) "boot with root" or you'll just boot to stock.
I'm not sure why you've chosen to go down that route, but there's a much better solution for the S6 - Which is to install TWRP and a custom Kernel. It'll nullify any need of booting into recovery or creating any custom AP files.
https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Click to expand...
Click to collapse
It boots into system just like how flashing via TWRP would. Lost root twice which I just reflash the AP in Odin again. Might be because I was playing with systemlesshost option in magisk app & adding secondary user profile in Android.
Patching the AP file with Magisk app, then flashing via Odin is basically the same task TWRP does via zip. (Modifies vbmeta.img, boot.img, and recovery.img) The instruction is for rooting without custom recovery.
I didn't use TWRP method because currently it does not support encryption with the newer SK1/SL3 CSC builds. Moving forward the maintainer for Tab S6 TWRP don't plan on fixing until Android-10 and isn't even sure it can be fixed.
Momotani-Hitoshi said:
It boots into system just like how flashing via TWRP would. Lost root twice which I just reflash the AP in Odin again. Might be because I was playing with systemlesshost option in magisk app & adding secondary user profile in Android.
Patching the AP file with Magisk app, then flashing via Odin is basically the same task TWRP does via zip. (Modifies vbmeta.img, boot.img, and recovery.img) The instruction is for rooting without custom recovery.
I didn't use TWRP method because currently it does not support encryption with the newer SK1/SL3 CSC builds. Moving forward the maintainer for Tab S6 TWRP don't plan on fixing until Android-10 and isn't even sure it can be fixed.
Click to expand...
Click to collapse
Oh ok. Never thought about encryption as I don't really need it. Just thought I'd point you towards that method in case you hadn't seen it.
Related
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??
I'm trying to get Magisk to work on a Samsung S2 Tablet SM-T713. I don't think it's relevant, but I'm running LineageOS 16.0 (the 4/5/19 nightly), and TWRP 3.2.3. I had enabled OEM Unlocking before I installed either of those.
I installed Magisk Manager 7.1.1on the tablet. I pulled the stock boot.img from a stock installation image (T713XXU2BRB2_T713OXA2BRA1, which was the same firmware I had before upgrading to LineageOS). I then used Magisk Manager 7.1.1 to create a patched boot.img. I then used TWRP to flash the patched boot image to the boot partition.
The result is that my tablet is now bricked at the initial boot screen (the one that says "Samsung Galaxy Tab S2") with an error in the corner that says "Set Warranty Bit: kernel".
I'm assuming that once the battery runs down I'll be able to boot into either recovery or Odin download mode and re-flash the boot image. Since having a non-removable battery makes trial and error very slow (since I need to let the battery run down before I can reboot), I'd really like to understand what I'm doing wrong before I try installing Magisk again.
All of the threads I've seen about people installing Magisk on the T713 are from last year. Is anyone still using that combination? Even if you're not, I'd appreciate any suggestions!
Thanks in advance for any help.
Dr. Drax said:
I'm trying to get Magisk to work on a Samsung S2 Tablet SM-T713. I don't think it's relevant, but I'm running LineageOS 16.0 (the 4/5/19 nightly), and TWRP 3.2.3. I had enabled OEM Unlocking before I installed either of those.
I installed Magisk Manager 7.1.1on the tablet. I pulled the stock boot.img from a stock installation image (T713XXU2BRB2_T713OXA2BRA1, which was the same firmware I had before upgrading to LineageOS). I then used Magisk Manager 7.1.1 to create a patched boot.img. I then used TWRP to flash the patched boot image to the boot partition.
The result is that my tablet is now bricked at the initial boot screen (the one that says "Samsung Galaxy Tab S2") with an error in the corner that says "Set Warranty Bit: kernel".
I'm assuming that once the battery runs down I'll be able to boot into either recovery or Odin download mode and re-flash the boot image. Since having a non-removable battery makes trial and error very slow (since I need to let the battery run down before I can reboot), I'd really like to understand what I'm doing wrong before I try installing Magisk again.
All of the threads I've seen about people installing Magisk on the T713 are from last year. Is anyone still using that combination? Even if you're not, I'd appreciate any suggestions!
Thanks in advance for any help.
Click to expand...
Click to collapse
any luck?
pointbob said:
any luck?
Click to expand...
Click to collapse
I wound up having to let the battery run out. Then I had to do finger acrobatics to hold down the buttons for download mode while I plugged in a USB cable attached to my computer. That allowed me to use Odin to install a stock boot image.
I ultimately figured out that the problem was that my data partition had automatically re-encrypted itself. I found I had to use TWRP to wipe my data partition, then immediately use TWRP to install Magisk so that my bootloader wouldn't force encryption. A reboot between those two steps screws things up.
Hey guys , i have been looking on the forum ,i already have a rooted s9+ but on 8.0, i want to go over to 9.0 but i cant find a guide how to and what i need for it , maby im oberlooking the threads but maby someone can hel me out ?
Wesley_NL said:
Hey guys , i have been looking on the forum ,i already have a rooted s9+ but on 8.0, i want to go over to 9.0 but i cant find a guide how to and what i need for it , maby im oberlooking the threads but maby someone can hel me out ?
Click to expand...
Click to collapse
Just use the method you used on Oreo.
spawnlives said:
Just use the method you used on Oreo.
Click to expand...
Click to collapse
though i forgot its been a while , and somehow i can remember little doing with odin3 i needed serval fiiles
Wesley_NL said:
though i forgot its been a while , and somehow i can remember little doing with odin3 i needed serval fiiles
Click to expand...
Click to collapse
Yes you will need Odin. If you are going to use magisk then either flash twrp or use the patch method. Either way require Odin.
Personally I use twrp. You can copy all files needed ( on to SD card ) and flash within twrp.
spawnlives said:
Yes you will need Odin. If you are going to use magisk then either flash twrp or use the patch method. Either way require Odin.
Personally I use twrp. You can copy all files needed ( on to SD card ) and flash within twrp.
Click to expand...
Click to collapse
yes that was my plan stay magisks with twrp ,
altough i dont remember i did this when i installed twrp on mines
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
Wesley_NL said:
yes that was my plan stay magisks with twrp ,
altough i dont remember i did this when i installed twrp on mines
HOW TO INSTALL:
0. Make sure you enabled developer settings by pressing the build number several times and have the OEM unlock enabled
1. Boot into download mode by pressing: bixby, volume down and power
2. Download the latest Odin version, open it
3. Download the recovery file from below and put it into the AP tab
4. Untick "auto reboot" in odin and flash the file
5. After flashing, boot into twrp. Make sure to NOT allow system to be modified till you disable dm-verity! (otherwise your phone will be stuck at bootloop). Alternatively flash my stock patched kernel to the boot partition (install, install img, check the kernel, check boot partition, done). Find the patch kernel here
6. To disable encryption you need to format data
Click to expand...
Click to collapse
Basically yes. I would first do a backup ( I know but the amount of people not doing it and then wanting to know how to retrieve the lost data ).
In download mode check kg/rmm state is NOT in prenormal state.
Step 5 - allowing system to be modified - that's up to you. I normally allow modifications.
Then format data reboot back into twrp.
Flash/install - no verity zip, rmm bypass zip, magisk .
Hey i have a problem, i downloaded latest rom but my bt wont save bt pairings, what can i do about it
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
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
If anyone can help that'll be great!
Phone Info:
Android Version: 10
Baseband Version: J600GDXSACVB1
Knox version: Knox 3.5 (idk if this is needed)
"OEM Unlocking" option in developer setting is enabled
"USB Debugging" is also enabled
ThatUnknownDude said:
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
Click to expand...
Click to collapse
TWRP =/= root. Root means you have SU access in Android system. Recovery mode is a separate environment; the difference between TWRP and stock recovery is that TWRP allows you to flash unsigned images.
If you just want to root your phone with Magisk, you can follow these instructions.
Otherwise, if you want to be able to flash custom ROMs, you can use this to patch your stock recovery to enable Fastbootd which will allow you to flash partitions directly instead of using Odin.
ThatUnknownDude said:
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
Click to expand...
Click to collapse
Yes, see the Magisk instructions I linked. Samsung likes to make things complicated, so when you've unlocked the bootloader, it still won't let you flash custom images until Vaultkeeper has been disabled.
Hmm ok thanks.. I saw the Magisk installation help page and I am getting stuck in this part:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Click to expand...
Click to collapse
I am long pressing volume up button in download mode however nothing is happening...
(Edit) Oh and KG State (which I assume is another word for RMM Lock) is just showing 'checking' and not 'prenormal' or anything...
I think TWRP may be the cause of the bootloop. I flashed a stock firmware of J600G to completely reset it (factory reset of sorts) and then flashed TWRP, and entered the recovery screen. After that the bootlooping issue started... is there any other good custom recoveries?
Hi TUD, fellow J600G user here, I'd recommend you to start off easy by installing TWRP 3.2.3.
Requirements -
Odin installed on your computer.
USB cable
TWRP tar file
To install TWRP -
1. Switch your phone off and hold volume up and down buttons at the same time while connecting your phone to the computer by cable.
2. Open Odin and go to options, switch off auto reboot, now click on AP and select your TWRP tar file.
3. Now after Odin says PASS disconnect the cable from your phone and hold Volume down + power button for 7 seconds and as soon as the screen goes black hold Volume up + power button. This will boot you into your newly installed TWRP.
When it comes to custom roms J6 has some limitations for a few good ones. In my opinion you can install EvolutionX 4.0 (made by @adi_ss) that is based on android 10 as its the easiest rom to install. All you have to do is follow the instructions given by the developer.
Happy Flashing.