Related
Everything I've seen so far has resulted in someone bricking their phones, including somehow deleting their IMEI numbers or somehow resulting in their BT/WiFi not working. There were so many threads that it's hard to remember which one is which.
I've decided it's time to unlock/root my phone but I don't want to make the same mistakes and somehow brick my phone. Why was it that the partition with the IMEI was written over? What about the other bricks? What is the best method to unlock/root right now?
Often times mixing firmware from other regions will cause issues. For example flashing the US version with the G or international versions. By firmware, I'm referring to other system components besides /system and kernel. Radio/baseband, BT firmware, etc.
The other issue has to do with the axon7backup program. For greatest safety, this really should only be used to backup and flash recovery while the bootloader is still locked only.
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
There is no way to fully brick a device with the Qualcomm 820 SoC. It is more or less complicated, but even deleting the bootloader it is possible to recover the device with the appropriate Qualcomm flashing tools.
Regarding "easy" bricks, you will be able to recover any brick by using tenfar's Axon7tools, and DrakenFX guides. Also Just keep on had a backup of your boot.bin, recovery.bin (both using Axon7Tool), and the full ZIP for your device model in a FAT formatted SDcard.
The recovery process is just to flash back the boot.bin, then recovery.bin (using the same tool Axon7tool) and then from the stock recovery reinstall the full zip and optionals OTA.
Cyrus D. said:
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
Click to expand...
Click to collapse
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
amphi66 said:
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
Click to expand...
Click to collapse
Sorry I'm new to all this, I'm doing something wrong here.
So just to be clear it's:
- Type in "SU", enter it, then type "reboot disemmcwp", in TWRP's terminal?
That results in "SU not found" for me.
or
- Type in "adb reboot disemmcwp" in a command window opened in the adb folder on my PC while TWRP is running adb sideload?
That resulted in "* daemon not running. starting it now on port 5037 * * daemon started successfully * error: closed"
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Cyrus D. said:
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Click to expand...
Click to collapse
The su binary only exists if you open a terminal in an android app because apps do not have root permission. TWRP and adb shell automatically have root privileges.
I hate to start the new thread but i really need some help please...
This is what I have done to my mi1.
1.Rooted by following these steps.
https://www.the***********.com/root-xiaomi-mi-a1-magisk-twrp-recovery/
2.My latest update is May OTA.
3.Already unlocked bootloader.
4.Magisk manager installed.
5.Tried to update July pack by following these steps but failed. Couldn’t install Magisk Manager after OTA update “Install to Second Slot” option is missing. So I chose not to install Magisk Manager.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
6.After reboot, the phone went to TWRP screen. I flashed magisk. After another reboot, My M1 showed this message “couldn’t update Installation problem”. Fortunately, the phone works fine so far.
Thanks for every single kind and helping comment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
already answered on another post but it seems you installed TWRP, erasing the stock recovery (mandatory for ota), not booted it, and modified system partition.
Download official Fastboot ROM, unpack it, remove "oem lock" command from "flash_all_except_storage.bat" file, run it. Then re-root with Magisk (boot TWRP, install Magisk).
Stock ROM: http://bigota.d.miui.com/V9.6.4.0.O...0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
The latest version of Magisk manager seem to have a bug with missing "install to second slot" option.
_mysiak_ said:
Download official Fastboot ROM, unpack it, remove "oem lock" command from "flash_all_except_storage.bat" file, run it. Then re-root with Magisk (boot TWRP, install Magisk).
Stock ROM: http://bigota.d.miui.com/V9.6.4.0.O...0.ODHMIFE_20180712.0000.00_8.0_735823083f.tgz
The latest version of Magisk manager seem to have a bug with missing "install to second slot" option.
Click to expand...
Click to collapse
Would you please explain "step-by-step" guide for the bold part?
Im such a newbie. Sorry for my ignorance.
nipunsdaddy said:
Would you please explain "step-by-step" guide for the bold part?
Im such a newbie. Sorry for my ignorance.
Click to expand...
Click to collapse
There are already few "step-by-step" procedures written on this forum, try to study them first so you understand what you're doing. I provided quick guide, for anything more detailed you'll need to search yourself
This works for me.
nipunsdaddy said:
I hate to start the new thread but i really need some help please...
This is what I have done to my mi1.
1.Rooted by following these steps.
2.My latest update is May OTA.
3.Already unlocked bootloader.
4.Magisk manager installed.
5.Tried to update July pack by following these steps but failed. Couldn’t install Magisk Manager after OTA update “Install to Second Slot” option is missing. So I chose not to install Magisk Manager.
6.After reboot, the phone went to TWRP screen. I flashed magisk. After another reboot, My M1 showed this message “couldn’t update Installation problem”. Fortunately, the phone works fine so far.
Thanks for every single kind and helping comment.
Click to expand...
Click to collapse
This is what I have done to my mi a1.
1.Rooted by Magisk
2.My latest update is April OTA.
3.Already unlocked bootloader.
4.Magisk manager installed.
5. I tried to find information about how to upgrade to 8.1 stock (July Security Patch), i dont find anything. So this is what i do thats works perfectly in mi a1.
.-Inside Magisk Manager find the option "Uninstall" this option will pop up a new window and you will choose the middle option "Restore Images"
.-Now, go to Configuration>System>System Upgrade or Update
.-You will see a new update (July Patch), push it in download..............now you can go to eat or buy something nice
.-When the update is finished the phone ask you if you want to restart, touch yes and wait, will take a bit to start, dont worry.
.-When the phone start well go to Magisk and you will see that you lose the Root-Magisk and you cant install it from the phone so you will need the help of the computer.
.-Hope you have the mi a1 drivers installed if you dont give me a beer i will show you how to install it. :good:
.-Download this drivegooglecom/file/d/1OcJcGem90nGj1ymMmzY29IGczIPP3Uk9/view this is a Script to help you By Aridane.
.-Unzip the folder in your music folder to find it quickly...
_mysiak_ said:
The latest version of Magisk manager seem to have a bug with missing "install to second slot" option.
Click to expand...
Click to collapse
Which version exactly has the bug?
dadnammit said:
Which version exactly has the bug?
Click to expand...
Click to collapse
I noticed it about 3 versions ago. No idea which one exactly.
I have found it... The last version that has the A/B slot install option is 5.7.0, and here is the commit on github about its removal.
https://github.com/topjohnwu/MagiskManager/commit/831112abd2d7fd3df0b1680d1c73c458512e7745
---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------
If you find yourself without the A/B install slot option while following the developer's OTA Installation instructions here (https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md), the following steps worked for me to recover from the problem...
* When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
* After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Updates).
* Once the installation has passed step 1 and is starting step 2, go to Magisk Manager → Install. IF THE "Install to Second Slot" OPTION IS NOT AVAILABLE, choose "Download Zip Only" and the zip will be stored to /sdcard/MagiskManager/ .
* Let the OTA finish its job. Reboot. You will not have root anymore.
* On a PC, install ADB and Fastboot (http://forum.xda-developers.com/showthread.php?p=48915118).
* On the PC, download TWRP recovery image for tissot (recovery-3.2.1-2-oreo.img): (https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472).
* Boot into fastboot mode (power off, then press and hold power and volume DOWN buttons simultaneously). Plug in USB cable to the PC.
* Open cmd on the PC, cd to the ADB/Fastboot directory, and run this to launch TWRP recovery:
fastboot boot recovery-3.2.1-2-oreo.img.img
* Phone will boot into TWRP. Tap Install and select the /sdcard/MagiskManager/Magisk-vXX.X.zip file. Select Zip signature verification. Swipe to confirm Flash. Tap Reboot System.
* Phone is now rooted again.
dadnammit said:
I have found it... The last version that has the A/B slot install option is 5.7.0, and here is the commit on github about its removal.
https://github.com/topjohnwu/MagiskManager/commit/831112abd2d7fd3df0b1680d1c73c458512e7745
---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------
If you find yourself without the A/B install slot option while following the developer's OTA Installation instructions here (https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md), the following steps worked for me to recover from the problem...
* When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
* After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Updates).
* Once the installation has passed step 1 and is starting step 2, go to Magisk Manager → Install. IF THE "Install to Second Slot" OPTION IS NOT AVAILABLE, choose "Download Zip Only" and the zip will be stored to /sdcard/MagiskManager/ .
* Let the OTA finish its job. Reboot. You will not have root anymore.
* On a PC, install ADB and Fastboot (http://forum.xda-developers.com/showthread.php?p=48915118).
* On the PC, download TWRP recovery image for tissot (recovery-3.2.1-2-oreo.img): (https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472).
* Boot into fastboot mode (power off, then press and hold power and volume DOWN buttons simultaneously). Plug in USB cable to the PC.
* Open cmd on the PC, cd to the ADB/Fastboot directory, and run this to launch TWRP recovery:
fastboot boot recovery-3.2.1-2-oreo.img.img
* Phone will boot into TWRP. Tap Install and select the /sdcard/MagiskManager/Magisk-vXX.X.zip file. Select Zip signature verification. Swipe to confirm Flash. Tap Reboot System.
* Phone is now rooted again.
Click to expand...
Click to collapse
I just followed your guide and everything worked at the beginning (Root Checker was positive and the phone was working) After I restarted though it just says though that the system process doesn't work and continous on restarting. Can someone please help me how to get my phone back to working? Thanks a lot!!
[D4v3|R4v3] said:
I just followed your guide and everything worked at the beginning (Root Checker was positive and the phone was working) After I restarted though it just says though that the system process doesn't work and continous on restarting. Can someone please help me how to get my phone back to working? Thanks a lot!!
Click to expand...
Click to collapse
maybe you can boot to recovery and then install this latest stock rom:
https://forum.xda-developers.com/mi-a1/development/rom-t3790268
then you can also boot to recovery and install magisk beta 16.7 and this awesome kernel:
https://forum.xda-developers.com/mi-a1/development/kernel-extreme-kernel-1-0-mi-a1-t3769702
good luck
I don't know why or how, but somehow I managed to get it back to working. Backed-up everything again, since I'm still not sure if it starts misbehaving again after a reboot. Will do an update to Magisk 16.7, but since it's my mom's phone I prefer not to temper with custom kernels. I still don't get though, what the initial source of the problem was
[D4v3|R4v3] said:
I just followed your guide and everything worked at the beginning (Root Checker was positive and the phone was working) After I restarted though it just says though that the system process doesn't work and continous on restarting. Can someone please help me how to get my phone back to working? Thanks a lot!!
Click to expand...
Click to collapse
Hmm. Not sure. If Magisk uninstalled itself correctly in the first step, the phone should reboot just fine after the OTA, but you should only have lost root. Sounds like something went wrong in the OTA perhaps. Sorry I can't be of more help.
dadnammit said:
I have found it... The last version that has the A/B slot install option is 5.7.0, and here is the commit on github about its removal.
https://github.com/topjohnwu/MagiskManager/commit/831112abd2d7fd3df0b1680d1c73c458512e7745
---------- Post added at 03:05 PM ---------- Previous post was at 02:54 PM ----------
If you find yourself without the A/B install slot option while following the developer's OTA Installation instructions here (https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md), the following steps worked for me to recover from the problem...
* When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
* After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Updates).
* Once the installation has passed step 1 and is starting step 2, go to Magisk Manager → Install. IF THE "Install to Second Slot" OPTION IS NOT AVAILABLE, choose "Download Zip Only" and the zip will be stored to /sdcard/MagiskManager/ .
* Let the OTA finish its job. Reboot. You will not have root anymore.
* On a PC, install ADB and Fastboot (http://forum.xda-developers.com/showthread.php?p=48915118).
* On the PC, download TWRP recovery image for tissot (recovery-3.2.1-2-oreo.img): (https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472).
* Boot into fastboot mode (power off, then press and hold power and volume DOWN buttons simultaneously). Plug in USB cable to the PC.
* Open cmd on the PC, cd to the ADB/Fastboot directory, and run this to launch TWRP recovery:
fastboot boot recovery-3.2.1-2-oreo.img.img
* Phone will boot into TWRP. Tap Install and select the /sdcard/MagiskManager/Magisk-vXX.X.zip file. Select Zip signature verification. Swipe to confirm Flash. Tap Reboot System.
* Phone is now rooted again.
Click to expand...
Click to collapse
do l lose all magisk modules installed before ota updates? i might try yr guide with Aug. update. wish me luck!!:fingers-crossed:
_mysiak_ said:
boot TWRP, install Magisk.
Click to expand...
Click to collapse
I could not have it booted into TWRP recovery (see below). Do you happen to know how to solve this problem? Thanks.
It looks fine on the PC screen when I Fastboot boot twrp.img. It showed things like, downloading 'boot.img'... OKAY, booting....OKAY, finished. But the connected phone simply showed no response and remained in the fastboot mode all the time!
feiafei said:
I could not have it booted into TWRP recovery (see below). Do you happen to know how to solve this problem? Thanks.
It looks fine on the PC screen when I Fastboot boot twrp.img. It showed things like, downloading 'boot.img'... OKAY, booting....OKAY, finished. But the connected phone simply showed no response and remained in the fastboot mode all the time!
Click to expand...
Click to collapse
Are you able to run any fastboot commands? For example "fastboot getvar all".
_mysiak_ said:
Are you able to run any fastboot commands? For example "fastboot getvar all".
Click to expand...
Click to collapse
Yes. It showed a long list on PC with the command "fastboot getvar all":
Version: 0.5,..., unlocked: yes,... version-bootloader: MSM8953_TISSOT2.0_20180814203737,... , product: tissot
When booting directly into the recovery mode, the phone showed "no command" error message.
The TWRP recovery file I was trying to use, with the command "fastboot boot ...", as mentioned in my last post : twrp-3.2.3-0-tissot.img
feiafei said:
Yes. It showed a long list on PC with the command "fastboot getvar all":
Version: 0.5,..., unlocked: yes,... version-bootloader: MSM8953_TISSOT2.0_20180814203737,... , product: tissot
When booting directly into the recovery mode, the phone showed "no command" error message.
The TWRP recovery file I was trying to use, with the command "fastboot boot ...", as mentioned in my last post : twrp-3.2.3-0-tissot.img
Click to expand...
Click to collapse
Try this recovery for Oreo https://forum.xda-developers.com/mi...ry-twrp-3-1-1-0-touch-recovery-t3688472/page1
I had issues with recovery images downloaded from the official TWRP web page, so I just stick to "unnoficial" ones found on XDA..
Well, August OTA security update released and still no A/B slot option available.
I'm now on Magisk Manager 5.8.3 (beta) and Magisk 16.7 (beta).
My instructions posted earlier worked fine again and saved me any serious troubles (https://forum.xda-developers.com/showthread.php?p=77122635#post77122635).
Hello, i want to root my device with SuperSU but i can't.
Now there is:
bootloader: unlocked
fastboot: working
recovery: TWRP 3.3.1-0
rom: stock B12
I try to root through axon7toolkit, device boot to fastboot, then app shows:
HTML:
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.326s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.348s
Tap 'Keep read-only'" on startup!
then app shows error "ADB recovery device is not connected". I manually select Recovery mode from fastboot. TWRP launch without "Keep read-only" option. I click mount, selecting all options and checking "Keep read-only" option. Then I click OK in axon7toolkit error message and TWRP make a script. After that device boot twice. SuperSU app says SU is not installed.
I try to click OK in axon7toolkit error without mounting with "Keep read-only" (just clicking OK when TWRP launch) but it's the same.
I try to root by install SuperSU v2.82 SR5 through TWRP, script working and says done, but after confirm there is the same as above.
I must flash special bootstack or maybe B12 is possibile to root?
EDIT:
I try to download terminal, then type
HTML:
adb shell reboot disemmcwp
then device was rebooting. After that I type in emulator
HTML:
su
and SuperSU asks for root permission. I allow that, but terminal no go to root mode and typing
HTML:
reboot disemmcwp
don't change anything.
ColorfulPoland said:
Hello, i want to root my device with SuperSU but i can't.
Now there is:
bootloader: unlocked
fastboot: working
recovery: TWRP 3.3.1-0
rom: stock B12
I try to root through axon7toolkit, device boot to fastboot, then app shows:
Checking ADB\Fastboot Connectivity...ADB device connected!Rebooting to bootloader...Checking Fastboot Connectivity...Fastboot device connected!Booting TWRP...downloading 'boot.img'...OKAY [ 0.326s]booting...FAILED (remote: unknown command)finished. total time: 0.348sTap 'Keep read-only'" on startup!
then app shows error "ADB recovery device is not connected". I manually select Recovery mode from fastboot. TWRP launch without "Keep read-only" option. I click mount, selecting all options and checking "Keep read-only" option. Then I click OK in axon7toolkit error message and TWRP make a script. After that device boot twice. SuperSU app says SU is not installed.
I try to click OK in axon7toolkit error without mounting with "Keep read-only" (just clicking OK when TWRP launch) but it's the same.
I try to root by install SuperSU v2.82 SR5 through TWRP, script working and says done, but after confirm there is the same as above.
I must flash special bootstack or maybe B12 is possibile to root?
EDIT:
I try to download terminal, then type adb shell reboot disemmcwp
then device was rebooting. After that I type in emulator su
and SuperSU asks for root permission. I allow that, but terminal no go to root mode and typing reboot disemmcwp
don't change anything.
Click to expand...
Click to collapse
i always just ask, why SuperSU?
Don't use "Keep read only" on TWRP, that's useful when you have DM-verity enabled but SuperSU, Magisk, or the no verity zip disable that. I don't know if this is your problem but it might as well be.
Also, issue "reboot disemmcwp" from the TWRP terminal or via adb in TWRP. it might do the trick
When I type the post, I use SuperSU because Magisk no work. Now I know Magisk works to 16.7 but now the problem is because I have a problem with "corrupted SD card" after flashing (I have read and many other people have this problem). I don't know how to fix it, because formating don't help, so I still be with SuperSU
When I go home I try use terminal from TWRP, thank for your help
EDIT:
TWRP not recognize my commends
ColorfulPoland said:
When I type the post, I use SuperSU because Magisk no work. Now I know Magisk works to 16.7 but now the problem is because I have a problem with "corrupted SD card" after flashing (I have read and many other people have this problem). I don't know how to fix it, because formating don't help, so I still be with SuperSU
When I go home I try use terminal from TWRP, thank for your help
EDIT:
TWRP not recognize my commends
Click to expand...
Click to collapse
lol. Try using Magisk, then get all of your stuff out of the SD card and format it. If your files aren't bigger than 4gb you can use fat32, otherwise try formatting it from the phone
Hello,
Yesterday I updated my OP8 Pro to OOS 11 by following this guide, everything was working fine and I kept the root.
I then updated one of my magisk modules (taichi) and after reboot I have an infinite boot animation.
Before, I went to the console in TWRP to uninstall the module, but there is no TWRP compatible with OOS 11.
So I don't know what to do.
Can someone help me please?
Thanks
zeldomar said:
Hello,
Yesterday I updated my OP8 Pro to OOS 11 by following this guide, everything was working fine and I kept the root.
I then updated one of my magisk modules (taichi) and after reboot I have an infinite boot animation.
Before, I went to the console in TWRP to uninstall the module, but there is no TWRP compatible with OOS 11.
So I don't know what to do.
Can someone help me please?
Thanks
Click to expand...
Click to collapse
You can try the following command whilst your device is on the boot logo:
adb wait-for-device shell magisk --remove-modules
If that does not work, take a patched boot.img for A11 and fastboot boot it first, if that works then remove the module and restart.
The latter worked for me when I had an issue earlier with a wonky magisk module.
Shredz98 said:
You can try the following command whilst your device is on the boot logo:
adb wait-for-device shell magisk --remove-modules
If that does not work, take a patched boot.img for A11 and fastboot boot it first, if that works then remove the module and restart.
The latter worked for me when I had an issue earlier with a wonky magisk module.
Click to expand...
Click to collapse
Thank you very much, it worked!
I used solution 2 with a boot.img extracted from the zip of OOS 11.
zeldomar said:
Thank you very much, it worked!
I used solution 2 with a boot.img extracted from the zip of OOS 11.
Click to expand...
Click to collapse
Glad it worked!
Shredz98 said:
Glad it worked!
Click to expand...
Click to collapse
By any chance, do you know how to uninstall a module in my case?
Because now that I am no longer root, and that Magisk is disabled, I no longer have access to the "modules" section in Magisk Manager.
Thank you!
zeldomar said:
By any chance, do you know how to uninstall a module in my case?
Click to expand...
Click to collapse
You can do so via ADB with a modded recovery, see here for more details
zeldomar said:
By any chance, do you know how to uninstall a module in my case?
Because now that I am no longer root, and that Magisk is disabled, I no longer have access to the "modules" section in Magisk Manager.
Thank you!
Click to expand...
Click to collapse
You can use Magisk Manager to path the boot.img you used and fastboot boot that to regain root and when you delete the module then fastboot flash the patched boot.img and voila root without the borked module
Or you can follow the patched recovery way which should work fine as well
Or just use the ADB commands while your phone is on
s3axel said:
You can do so via ADB with a modded recovery, see here for more details
Click to expand...
Click to collapse
Thanks, but there is no recovery for OOS 11
Shredz98 said:
You can use Magisk Manager to path the boot.img you used and fastboot boot that to regain root and when you delete the module then fastboot flash the patched boot.img and voila root without the borked module
Or you can follow the patched recovery way which should work fine as well
Or just use the ADB commands while your phone is on
Click to expand...
Click to collapse
Unfortunately, no solution works for the moment:
- if I boot (from fastboot) on a patched (so rooted) boot.img, I fall back on the infinite animation logo (I imagine that magisk is reactivated and that it tries to load the problematic module again)
- I can't find a patched OOS 11 recovery, do you have a link? what should I do with this recovery please?
- now that my phone is on, I can run the adb command "adb wait-for-device shell magisk --remove-modules", but I get the following error: "/ system / bin / sh: magisk: inaccessible or not found "
Thanks for your help.
Finally, the adb command during bootloop worked.
Thanks everyone!
Hi Folkz,
the rollout for 11.0.3.4. begins.
I've already downloaded 11.0.3.4 KB05BA (EU) via Oxygen Updater.
Here is a Link to a Post someone in official OPForums who provided a GDrive Link -> https://forums.oneplus.com/threads/...-the-oneplus-8t.1338403/page-34#post-22346201
I will install it now and then I give feedback (rooting etc.).
greetings rage
P.S. Please feel free to add OOS Update News for OP8T (all Variants) here in this Thread.
Okay... installed it already with no problems and root persists... looks great so far.
This is how I did the update:
1. Download FULL Update (e.g. via OxygenUpdater)
2. Install the update via "Settings->System->Systemupdates->Local Upgrade"
3. DO NOT REBOOT!!
4. Open Magisk Manager
5. Tap "Install" (Magisk) and select -> "Install to Inactive Slot (After OTA)" and install magisk to inactive slot
6. Reboot
7. Enjoy updated OOS with active root
greetings rage
Further Information:
* I used latest magisk canary version dc5e78e1 (21006) from here -> https://github.com/topjohnwu/magisk_files/tree/canary
* SafetyNet checks are sucessfull
I've already patched the boot.img with latest magisk canary, if you need it. -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
ChillDuder said:
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
Click to expand...
Click to collapse
...I think it's just for you. I tried it and "fastboot devices" and "fastboot reboot" works.
Hint: If you use Windows PowerShell, the command looks like this (if you start PowerShell in the same directory where fastboot.exe is located) ->
Code:
.\fastboot.exe devices
greetings rage
rage302 said:
Okay... installed it already with no problems and root persits... looks great so far.
This is how I did the update:
1. Download FULL Update (e.g. via OxygenUpdater)
2. Install the update via "Settings->System->Systemupdates->Local Upgrade"
3. DO NOT REBOOT!!
4. Open Magisk Manager
5. Tap "Install" (Magisk) and select -> "Install to Inactive Slot (After OTA)" and install magisk to inactive slot
6. Reboot
7. Enjoy updated OOS with active root
greetings rage
Click to expand...
Click to collapse
Like an idiot i rebooted before reinstalling Magisk. Patching boot images does not work anymore (fastboot locks on "fastboot mode" logo).
Any hint?
Scrambler77 said:
Like an idiot i rebooted before reinstalling Magisk. Patching boot images does not work anymore (fastboot locks on "fastboot mode" logo).
Any hint?
Click to expand...
Click to collapse
You can try to boot the other/untouched slot with this command in fastboot mode (if applicable):
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
...depending on which bootslot you are at the moment.
If this doesn't work you can try to boot my magisk_patched_boot.img form here -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
with this command:
Code:
fastboot boot magisk_patched.img
Or you can dump your own boot.img and patch it via magisk by your own (but I think you tried this already?)
If nothing helps you can use the Unbrick Tool from here -> https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180837
greetings rage
rage302 said:
You can try to boot the other/untouched slot with this command in fastboot mode (if applicable):
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
...depending on which bootslot you are at the moment.
If this doesn't work you can try to boot my magisk_patched_boot.img form here -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
with this command:
Code:
fastboot boot magisk_patched.img
Or you can dump your own boot.img and patch it via magisk by your own (but I think you tried this already?)
If nothing helps you can use the Unbrick Tool from here -> https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180837
greetings rage
Click to expand...
Click to collapse
Done it! Many thanks!
I couldn't get the OTA file for my variant. So, this is what I had to do to get it installed.
1. Open Magisk Manager -> Uninstall Magisk -> Restore Images
2. Don't reboot.
3. Take the OTA from Settings -> System -> System Updates
4. Don't reboot.
5. Open Magisk Manager -> Install Magisk -> Install To Inactive Slot
6. Reboot.
7. Your phone should be updated with Magisk still installed.
Next Update 11.0.4.5 is on it's way >
https://forums.oneplus.com/threads/oxygenos-11-0-4-5-for-the-oneplus-8t.1342473/
https://m.gsmarena.com/oxygenos_110...ls_out_with_11_different_fixes-news-46278.php
https://www.xda-developers.com/oneplus-8t-oxygenos-11-0-4-5-update/
Changelog
System
* Optimized the call stability
* Improved system power consumption performance to reduce heating
* Improved mis-touch prevention to offer better gaming experience
* Optimized fluidity with some mainstream games to reduce lagging risks
* Optimized user experience with Alert Slider by adding toast messages when switching among the 3 modes
* Fixed the issue that the status bar kept hovering on the screen in landscape mode
* Fixed the issue that NFC cannot be turned on in a small probability
Camera
* Optimized the imaging effect to bring you with better shooting experience
* Improved camera stability
Network
* Optimized mobile network connection to improve the network intensity with signal
* Fixed the small probability issue with network interruption while playing games
Click to expand...
Click to collapse
It is just a hot-fix update, so the changelog is nearly the same than 11.0.3.4.
Rollout for OOS 11.0.4.5 KB05BA (EU Version) begins.
Available via Oxygen Updater and here is the direct FULL OTA Link:
https://otafsg1.h2os.com/patch/amaz...gen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip (Source)
greetings rage
---UPDATE---
I've sucessfully upgraded to 11.0.4.5 KB05BA with keeping root and SafetyNet pass,
with my standard method -> https://forum.xda-developers.com/oneplus-8t/how-to/update-thread-t4188149#2
greetings rage
rage302 said:
Rollout for OOS 11.0.4.5 KB05BA (EU Version) begins.
Available via Oxygen Updater and here is the direct FULL OTA Link:
https://otafsg1.h2os.com/patch/amaz...gen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip (Source)
greetings rage
Click to expand...
Click to collapse
Lol, updated shortly before your post. First update post root and went flawlessly.
Sent from my OnePlus8T using XDA Labs
Is there a link for the AA version? I'm getting the "Installation problem" inherent with unlocked bootloaders
ChillDuder said:
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
Click to expand...
Click to collapse
This happened to me on first try.
Installed the Oneplus usb drivers
rebooted
All is well thereafter
blackknightavalon said:
Is there a link for the AA version? I'm getting the "Installation problem" inherent with unlocked bootloaders
Click to expand...
Click to collapse
It's on Oxygen Updater
Sent from my unknown using Tapatalk
Would be nice if OnePlus would release a Full OTA for us Global Model users, this Incremental mess is making things a pain.
@blackknightavalon and @Keinta15 I too am getting install failed. I'm betting I will need to MSMDownloadTool the phone, upgrade to 11.0.4.5 then Unlock Bootloader and root it.
card13 said:
Would be nice if OnePlus would release a Full OTA for us Global Model users, this Incremental mess is making things a pain.
@blackknightavalon and @Keinta15 I too am getting install failed. I'm betting I will need to MSMDownloadTool the phone, upgrade to 11.0.4.5 then Unlock Bootloader and root it.
Click to expand...
Click to collapse
If you're rooted you need to unroot before updating
Sent from my unknown using Tapatalk
@Keinta15 Right...? Which I have already done, then I get a Crashdump (dm-verity device corrupted force dump kernel_restart) and both slots no longer boot. All of which could be solved if there was full flash file and not a 300MB Incremental OTA.
card13 said:
@Keinta15 Right...? Which I have already done, then I get a Crashdump (dm-verity device corrupted force dump kernel_restart) and both slots no longer boot. All of which could be solved if there was full flash file and not a 300MB Incremental OTA.
Click to expand...
Click to collapse
Did you flash the 11.0.2.3 incremental in the past?
@g96818 I was able to flash 11.0.1.2 Incremental, 11.0.3.4 and 11.0.4.5 have both failed, with the exact same process I used to get 11.0.1.2 installed (unroot -> reboot -> install update -> boot patched boot img -> dd boot.img backup -> patch img -> boot to newly patched img -> direct install root).
****EDIT #1****
Looks like switching boot slots was a really bad idea and I irritated my phone. It's in a bootloop. "Boot reason: init_user0-failed unable to parse kernel log. For more debug information, adb pull /mnt/vendor/op2/rbr_log or pull op2.img".
***Edit #2****
Well that didn't go as planned. Tried to Factory Reset, still got install failed. Then locked the bootloader to see if it would installed and got stuck on DM-Verity Device Corrupted screen. Ended up using MSM to restore then update to 11.0.4.5. Good thing I was doing every couple days backups with SwiftBackup.