Related
I am upgrading my OP3T from 5.0.1 to 5.0.3. My device is rooted using magisk and I have TWRP installed.
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?
EDIT - I read about Dirty flashing the version I want but I can't find 5.0.3 image on Oneplus website.
shantam2 said:
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?.
Click to expand...
Click to collapse
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
przemcio510 said:
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
Click to expand...
Click to collapse
Re-flashing magisk via TWRP will keep my data ?
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Can you elaborate more on this ?
After I upgrade (and it becomes unrooted). I immediately flash magisk via TWRP ?
I didn't get the part "flash the whole rom and don't exit" ?
Also, Will I lose any data in the process ?
shantam2 said:
Re-flashing magisk via TWRP will keep my data ?
Click to expand...
Click to collapse
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
przemcio510 said:
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
Click to expand...
Click to collapse
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
b4bass said:
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
Click to expand...
Click to collapse
If you flash the update downloaded as zip from downloads.oneplus.com via TWRP, then no, there will be no need to flash it again via fastboot and no need to install TWRP Manager.
Boot to TWRP
Flash 5.0.3 zip
Flash Magisk
Reboot & enjoy
OK thanks! I thought the recovery would go back to stock after flashing the rom
And guys, if other members help you with their posts, don't forget to thank them.
Unleashed by my rooted OP3T on 8.0
b4bass said:
OK thanks! I thought the recovery would go back to stock after flashing the rom
Click to expand...
Click to collapse
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
So magisk is patching bootloader? I thought it was it point not to
Though this method is saving me some serious time!
b4bass said:
So magisk is patching boot, I thought I was it point not to
Though this method is saving me some serious time!
Click to expand...
Click to collapse
Magisk makes a point of not touching the system partition but a lot of its magic is done by changing the boot image.
Sent from my OnePlus3T using XDA Labs
OK thx ! First time I replaced supersu to pet magisk. Will have to find more details on this subject
b4bass said:
So magisk is patching bootloader? I thought it was it point not to
Click to expand...
Click to collapse
Boot image is kernel and ramdisk. Boot image is not the same as bootloader!
I have an Mate 10 AL-L29. 4 days ago l tried to rebrand it to chinese model android 8.1, firmware 321. After rebrand l saw my emei is 0000000000. l did it some days ago and all was fine! Now if l make downgrade to a old firmware, my imei is fine, but if l do an upgrade to a new firmware, it doesn't matter ALP-L29 or ALP-AL00, my imei is gone! Right now l'm on the newest android 8.1- 325 firmware. All works good.....root, phone, google play etc..
The only problem is my Imei 000000000 , but MEID is ok.
Any solution guys? Thanks!
Try factory data reset.
badmania98 said:
Try factory data reset.
Click to expand...
Click to collapse
It was the first thing that l did... It isn't so simple....seems oeminfo don't do its job when l try to restore it. I have 2 backups of oeminfo, with twrp and with HwOta8_Mate10..
Root works on ALP-AL00 8.1.0.326(C00) , how? I tried Magisk but the device gets stuck on 'your device is booting'.
25Swagat said:
Root works on ALP-AL00 8.1.0.326(C00) , how? I tried Magisk but the device gets stuck on 'your device is booting'.
Click to expand...
Click to collapse
Try patching ramdisk.img from Manager but make sure Preserve AVB/DM-Verity is checked, then flash it from fastboot.
ante0 said:
Try patching ramdisk.img from Manager but make sure Preserve AVB/DM-Verity is checked, then flash it from fastboot.
Click to expand...
Click to collapse
Do you mean the stock ramdisk.img of the software I'm in? If so, then I did that and checked Preserve AVB/DM-Verity in Magisk, then flashed the patched ramdisk.img in fastboot. After rebooting, I opened Magisk but it says Magisk is not installed.
Also, after that didn't work, tried installing it from Magisk.zip but it only downloads but doesn't get installed.
25Swagat said:
Do you mean the stock ramdisk.img of the software I'm in? If so, then I did that and checked Preserve AVB/DM-Verity in Magisk, then flashed the patched ramdisk.img in fastboot. After rebooting, I opened Magisk but it says Magisk is not installed.
Also, after that didn't work, tried installing it from Magisk.zip but it only downloads but doesn't get installed.
Click to expand...
Click to collapse
You have to flash the zip from TWRP. It doesn't flash if you aren't rooted already.
ante0 said:
You have to flash the zip from TWRP. It doesn't flash if you aren't rooted already.
Click to expand...
Click to collapse
I can't boot into twrp after flashing patched ramdisk. Do I have to flash twrp again? Somehow, while trying to get into TWRP, I can't but after rebooting Magisk is installed and works but after rebooting it isn't installed. Never mind mate I got it to work. Thanks!
25Swagat said:
I can't boot into twrp after flashing patched ramdisk. Do I have to flash twrp again? Somehow, while trying to get into TWRP, I can't but after rebooting Magisk is installed and works but after rebooting it isn't installed. Never mind mate I got it to work. Thanks!
Click to expand...
Click to collapse
If it's working do explain how you did, in case others with the same problem see this
ante0 said:
If it's working do explain how you did, in case others with the same problem see this
Click to expand...
Click to collapse
I followed @Tecalote instructions posted at https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.
you mean magisk not working with this build?
mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs
avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!
Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV
avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.
jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems
gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?
jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again
Hello,
I attempted to root my Mi CC9 / 9 Lite and currently have a bootloop.
What I did:
-Flash TWRP from fastboot (success)
-Boot into TWRP (success)
-Wipe / Factory reset (success)
-Flashing Magisk v20 zip file (success)
-Then, reboot system sends me to TWRP again.
What I tried:
-The phone is not bricked. When I factory reset again from TWRP and boot to system, it boots up.
-Signing the boot image after flashing magisk using the zip file here (This did not work. Flashing the zip file returned a verification error)
Not quite sure how to root my phone at this point. Any help would be much appreciated. Thank you.
You need the Enable encryption zip...it will boot it up.. boot loop is cause from MIUI trying to encrypted and failing.
Flash the zip in this thread... go to the fstab zip that will help you
https://forum.xda-developers.com/mi-cc9/development/recovery-twrp-pyxis-unofficial-t3990493
[email protected] said:
You need the Enable encryption zip...it will boot it up.. boot loop is cause from MIUI trying to encrypted and failing.
Flash the zip in this thread... go to the fstab zip that will help you
https://forum.xda-developers.com/mi-cc9/development/recovery-twrp-pyxis-unofficial-t3990493
Click to expand...
Click to collapse
Where do I find it?
dupreme said:
Where do I find it?
Click to expand...
Click to collapse
Direct link from OP.
https://www.mediafire.com/folder/zqk7a9qj5ltyd/Mi 9 Lite (pyxis)
[email protected] said:
Direct link from OP.
https://www.mediafire.com/folder/zqk7a9qj5ltyd/Mi 9 Lite (pyxis)
Click to expand...
Click to collapse
Thank you. I tried flashing the fstab zip after flashing magisk and it did not change the situation. Shall I first flash the auto-decrypt TWRP img and then try again?
dupreme said:
Thank you. I tried flashing the fstab zip after flashing magisk and it did not change the situation. Shall I first flash the auto-decrypt TWRP img and then try again?
Click to expand...
Click to collapse
What I do is this: I Boot in recovery and format data then I go to advance wipe and select data and then repair and select ext4 and swipe and then reboot recovery and flash the MIUI rom and then I reboot the recovery and mount system and vendor and flash the zip and then reboot and wait for it... you know it will boot up because after it boots up the bootanimation increases it's light before the actual booting in the system and the rest you can figure out... hope this helps you out.
[email protected] said:
What I do is this: I Boot in recovery and format data then I go to advance wipe and select data and then repair and select ext4 and swipe and then reboot recovery and flash the MIUI rom and then I reboot the recovery and mount system and vendor and flash the zip and then reboot and wait for it... you know it will boot up because after it boots up the bootanimation increases it's light before the actual booting in the system and the rest you can figure out... hope this helps you out.
Click to expand...
Click to collapse
I'll try that. Thanks a lot. Do you use the auto-decrypt (the one you linked) TWRP in this, or just regular TWRP. I am using just the pyxis TWRP.
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
dupreme said:
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
Click to expand...
Click to collapse
After you unlock the bootloader I just put it in fastboot mode and fastboot boot "(whatever you have it called... I renamed it recovery) recovery.img and then press the volume up button and then I install the image through TWRP and reboot recovery and then follow the steps.
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
dupreme said:
I'll try that. Thanks a lot. Do you use the auto-decrypt (the one you linked) TWRP in this, or just regular TWRP. I am using just the pyxis TWRP.
Click to expand...
Click to collapse
I used the TWRP for the team win recovery project website.
---------- Post added at 04:25 PM ---------- Previous post was at 04:07 PM ----------
dupreme said:
Can anyone elaborate on what needs to be done? The previous responses did not explain how to ROOT the phone.
What I have just tried:
-flashed the TWRP img here
-did a wipe
-sent Magisk and the fstab zips to storage and flashed them (fstab first)
still gives bootloop to recovery. How to root this phone?
Thank you
Click to expand...
Click to collapse
Fstab zip is last because it's the encryption fix
[email protected] said:
After you unlock the bootloader I just put it in fastboot mode and fastboot boot "(whatever you have it called... I renamed it recovery) recovery.img and then press the volume up button and then I install the image through TWRP and reboot recovery and then follow the steps.
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
I used the TWRP for the team win recovery project website.
---------- Post added at 04:25 PM ---------- Previous post was at 04:07 PM ----------
Fstab zip is last because it's the encryption fix
Click to expand...
Click to collapse
I tried a combination of what you suggested and this guide and the phone booted up with root. However, opening the Magisk manager immediately says "your device needs additional setup" or something similar, and asks to flash a zip file. When I select flash, it says rebooting in 5 sec and stays in bootloop. Have you come across this?
use twrp by brigudav. It has also s built-in Magisk installer.
JimmyBondi said:
use twrp by brigudav. It has also s built-in Magisk installer.
Click to expand...
Click to collapse
Can you share a link? I could not find an XDA thread. Thank you.
dupreme said:
I tried a combination of what you suggested and this guide and the phone booted up with root. However, opening the Magisk manager immediately says "your device needs additional setup" or something similar, and asks to flash a zip file. When I select flash, it says rebooting in 5 sec and stays in bootloop. Have you come across this?
Click to expand...
Click to collapse
TBH no because as Soon as I got TWRP I flash another rom Mi Globe rom to be exact and use the method I posted.