Thanks all - I've figured out most of these steps, including how to install Magisk successfully - only new beta versions will install, and I've only tested the 20170520 build with Magisk 13.0 beta, but it worked entirely as intended. Below are the steps needed, and below that is my old post (hidden) for posterity in case it helps troubleshoot later if something breaks. Since this has now become a guide, I will put it into the Guide section and this thread can be deprecated.
This assumes you are starting at B25, but the instructions should work for any B version number, since MiFlash is going to force us to B19.
STEP 1: FLASHING FROM B25 TO B19 USING EDL MODE:
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, selected on the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then do the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP).
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time. You MUST flash the B19 FULL first to avoid this.
STEP 2: INSTALLING MAGISK 13.0 BETA WITH ROOT AND SAFETYNET PASS
1. Make sure you have a clean image with NO SU (PHH or MagiskSU or otherwise), and NO Magisk/Magisk Manager installed.
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 20170520 13.0 beta and Magisk 20170520 (here, and attached for convenience) (full beta thread here if needed), and copy them to your device.
4. Install Magisk Manager 20170520 13.0 beta via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 20170520 beta (here, and attached for convenience)
6. Reboot into stock, and open Magisk Manager 13.0. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Now if you check SafetyNet, it should pass.
Note that the temporary beta builds appear to only be available for a short time, so either use the files attached, or go ahead and try the latest beta build. The first build I tried, 20170520, worked. My guess is all beta builds or full builds after 20170520 will work with the instructions above, but feel free to test.
STEP 3: GET OTAS: I have not tested yet to ensure Magisk doesn't break, but you should be able to download OTA packages and flash them. Will update when I care to, or others can feel free to try it and report.
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Old Post (NOT CURRENT):
I unlocked my phone some time ago, but did not install TWRP or root so that I could get OTAs. I'm currently on A2017 B25 (fully up to date) and am stock otherwise. I was hoping I could get help with updated information since the guides and threads are usually old and the reply updates can be contradictory. Two questions:
1. Can someone confirm how to take my unlocked stock A2017U B25 Axon and (1) install TWRP and (2) install Magisk?
There have been a number of threads related to installing TWRP and Magisk, but all of them have question marks. The Phh Magisk guide is from 2016 so would be pre-Nougat. Then there's also a tutorial to build your own Magisk ROM, which seems like it's more complex than other people who just flash Magisk - though for them it seems like there are still problems, with it not being clear whether Magisk 10.2 or 12 is needed.
I assume I can flash TWRP using the toolkit, but it sounds like rooting via the toolkit is not going to be Magisk. I'd really like to have a root that can pass SafetyNet if needed so my device is fully functional - if there are other methods than Magisk, that'd be great too.
2. Can someone confirm what process I use to get future stock OTAs after I install TWRP and am Magisk rooted?
Do I just download the OTA file from this thread and flash it via TWRP, or do I need to go back to stock (such as with the toolkit) first?
-------------------------------------------------------------------------------------------------
UPDATE 2017/05/21:
I came very close to solving all problems. My steps are below in case anyone wants to try.
FLASHING FROM B25 TO B19 USING EDL MODE: See my explanations here: https://forum.xda-developers.com/showpost.php?p=72294934&postcount=11
INSTALLING MAGISK 12.0 WITH ROOT AND SAFETYNET PASS
I was able to get Magisk 12.0 to run on Unlocked A2017U B19, and it appears I pass every test and Pokemon Go (test app) runs. Starting from A2017U B19 clean wipe, these are the exact steps I did. They can probably be optimized.
HOWEVER, MAGISKSU ROOT DOES NOT GIVE PERMISSION TO APPS SO THE METHOD BELOW IS NOT A SUCCESS - it says "X is denied superuser rights," without prompting. I tried all options in Magisk and could not solve this problem. If you think you can solve this problem, please feel free to give it a shot below - you will pass all status tests in Magisk but I cannot get root to actually grant access. Any suggestions?
1. Install Magisk Manager app in Google Play.
2. Boot into TWRP, flashed Magisk 10.2. Reboot. (This appears to flash successfully in TWRP, then booting back into Android it does not appear Magisk is installed in Magisk Manager).
3. In Magisk Manager, download Magisk 12.0.
4. Boot into TWRP, install/flash Magisk 12.0.
5. Boot into OS, check Magisk Manager. Magisk is shown as installed, NO root is installed.
6. Download PHH Superuser ZIP from the main post here: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 (NOTE that I cannot tell which version this is. It appears to be r170 based on the changelog, but no version appears in the "superuser.zip" that I download.)
7. Boot into TWRP, install "superuser.zip".
8. Boot into OS, check Magisk Manager. Magisk shown installed, and Superuser is shown installed. SafetyNet FAILS.
9. Enable MagiskHide in Magisk Manager settings.
10. SafetyNet should PASS in Magisk Manager.
Note that I think step 2 is unnecessary, but I kept it in anyway since that's what I did exactly. Images below show the current state of things:
{
"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"
}
Magisk 12 works with custom roms but doesn't work with stock. 10.2 is what I use with stock, and I haven't heard anyone be successful with a later version. Let me know if you can't find a download.
To flash an OTA you don't have to downgrade. Just dirty flash the stock system and recovery of the version you are on and you can OTA without losing data. If you can be patient it's better to wait a few days for the twrp flashables from drakenFX. I don't think the thread you linked to is for your variant (U).
Good luck. Let us know if you get stuck.
I also am curious about this... having just scratched my head for like 2 hours as to why i cant boot into fastboot mode trying to install TWRP. so at this time as far as i can tell there is no way to flash twrp if you are on b25? the update packages in the EDL sub forum are all for b19
I would actually like to know which toolkit I should use to get root and keep my data on stock for A2017U
Sent from my ZTE A2017U using XDA-Developers Legacy app
B25 took away fastboot. Assuming you are unlocked, you can flash twrp in EDL mode using axon7tool, or I think, miflash. I'm sure the toolkit uses one or both of those.
StickMonster said:
B25 took away fastboot. Assuming you are unlocked, you can flash twrp in EDL mode using axon7tool, or I think, miflash. I'm sure the toolkit uses one or both of those.
Click to expand...
Click to collapse
Ok but how do i do that? which package do i download do i just put the TWRP zip file into miflash? whenever I use axon tool it tries to do it through the bootloader which of course doesnt exist anymore. also what is the deal with like 25 different miflash tools? I cant seem to find one that works for anything
That's interesting. I accidentally upgraded to B25 OTA a couple of days ago (well, not accidentally, but now I suppose that was a stupid idea). Is there a way to root the phone and unlock the bootloader now?
Cheers,
Mike
StickMonster said:
Magisk 12 works with custom roms but doesn't work with stock. 10.2 is what I use with stock, and I haven't heard anyone be successful with a later version. Let me know if you can't find a download.
To flash an OTA you don't have to downgrade. Just dirty flash the stock system and recovery of the version you are on and you can OTA without losing data. If you can be patient it's better to wait a few days for the twrp flashables from drakenFX. I don't think the thread you linked to is for your variant (U).
Good luck. Let us know if you get stuck.
Click to expand...
Click to collapse
Thanks! I haven't had time to get around to trying it, but thinking about doing so tomorrow.
Assuming that I don't have an issue getting TWRP via the Axon Toolkit I linked to above, do I just flash Magisk 10.2 via TWRP? It seems like the process goes wrong for 50% of the people who post here, so I'm expecting some crazy process. But maybe I'm worried about nothing.
Well, ran into trouble before I could do anything.
On B25, I cannot access Fastboot, so Axon7Toolkit and other methods fail. In the bootloader, I can choose to restart, go to recovery (no TWRP, so it's stock recovery), and there's still the option for Fastboot. However, selecting it just reboots into the bootloader.
I researched and read that it was removed in B25. So I looked for ways to get it back. I saw MiFlash, tried installing that to apply the EDL rollback to B19 (as outlined here), but MiFlash in Windows doesn't appear to recognize the EDL file, so I can't try to apply it.
When the device is booted into stock, ADB sees the device. Can I ADB sideload TWRP onto it despite not having fastboot? I wanted to check before I brick my device trying something dumb. Or see if anyone has other suggestions to get TWRP onto my stock A2017U B25 unlocked system.
ScaryBugThing said:
Well, ran into trouble before I could do anything.
On B25, I cannot access Fastboot, so Axon7Toolkit and other methods fail. In the bootloader, I can choose to restart, go to recovery (no TWRP, so it's stock recovery), and there's still the option for Fastboot. However, selecting it just reboots into the bootloader.
I researched and read that it was removed in B25. So I looked for ways to get it back. I saw MiFlash, tried installing that to apply the EDL rollback to B19 (as outlined here), but MiFlash in Windows doesn't appear to recognize the EDL file, so I can't try to apply it.
When the device is booted into stock, ADB sees the device. Can I ADB sideload TWRP onto it despite not having fastboot? I wanted to check before I brick my device trying something dumb. Or see if anyone has other suggestions to get TWRP onto my stock A2017U B25 unlocked system.
Click to expand...
Click to collapse
Have you tried the TWRP app from the Play Store? Pretty straight forward.
amphi66 said:
Have you tried the TWRP app from the Play Store? Pretty straight forward.
Click to expand...
Click to collapse
Thanks for the suggestion. It turns out the Miflash method DID work. I had to extract the EDL folder, and then in the app select the subfolder for the EDL type. In detail:
1. I first installed the MiFlash at the EDL thread
2. Installed the QUALCOMM drivers linked in the same thread
3. Downloaded "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread
4. Extracted the ZIP file
5. Opened MiFlash, selected on the named sub-folder from the ZIP
6. Connected my Axon 7, and held VOL-UP/VOL-DOWN/POWER until the screen went black and the red notification LED blinked very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirmed my device was shown
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then did the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)" in the same EDL thread (to get TWRP).
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time (since it was on B25 but had the B19 TWRP partial update, which caused problems).
My problem now is that I downloaded Magisk 10.2, and flash it in TWRP, but when I open Magisk Manager after booting, it shows no Magisk or SU is installed. Does anyone have an idea how to get Magisk 10.2 to stick? I have the option in Magisk Manager to download 12.0, but I hear that that does not work (and I don't want to have to restart this process) so I haven't tried it.
Edit: Also, Magisk Manager shows SafetyNet fails with a "CTS Profile Mismatch" error (though no SU is installed) - though Pokemon Go seems to run so I don't know what that means.
Edit 2: This is resolved, see first post.
I just bought an Axon 7 and it is on b25. Is there a way to downgrade or root? I bought this thinking it was still possible.
BoboBrazil said:
I just bought an Axon 7 and it is on b25. Is there a way to downgrade or root? I bought this thinking it was still possible.
Click to expand...
Click to collapse
Use MiFlash to apply B19 FULL, then apply the TWRP MiFlash file. It's in the Dev Thread (and the post right above you ).
ScaryBugThing said:
Use MiFlash to apply B19 FULL, then apply the TWRP MiFlash file. It's in the Dev Thread (and the post right above you ).
Click to expand...
Click to collapse
Will that erase internal storage?
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
Will that erase internal storage?
Sent from my ZTE A2017U using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say definitively, but when I did it all settings and data remained. All my installed apps, etc, everything were retained from B25.
ScaryBugThing said:
I can't say definitively, but when I did it all settings and data remained. All my installed apps, etc, everything were retained from B25.
Click to expand...
Click to collapse
I see, thanks for telling me. I'll give this a go pretty soon
Sent from my ZTE A2017U using XDA-Developers Legacy app
Sorry, in case it got lost in my old post: I downloaded Magisk 10.2, and flash it in TWRP, but when I open Magisk Manager after booting, it shows no Magisk or SU is installed. Does anyone have an idea how to get Magisk 10.2 to stick?
If anyone can answer this, I'd really appreciate it.
With help from here: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
I am running B25 whilst keeping TWRP and a bootloader.
How? Simple really, I just took the latest B25 zip from the above link of the system and installed it without the new B25 bootstack. I guess I was running B19 before so my bootstack will be the same from there.
So that means TWRP+Unlocked bootloader, it also means I can use SuperSU to root.
Downsides:
Magisk doesn't work, tried v12,11.6,11.1,10.2 and none work, no root access.
Now I am on B25 I can't use any prior stock rom , B19 stock or bad boyz rom (based on B15?) causes me to have major problems with my gsm signal turning on and off repeatably, I tried to fix it by installing different modems but failed.
BTW this is all A2017U, no idea if it will also work with other variants.
In case anyone is wondering, I updated the first post to show that I did succeed in getting a full pass on SafetyNet with Magisk and MagiskSU/PHH SU "root" installed, and I gave the full method there.
However, all apps are denied Superuser rights with no prompt, even if the Superuser app is set to prompt or allow all. Turning off MagiskHide also fails to give Superuser, so it appears MagiskSU/PHH Superuser is simply not installing correctly.
Just for kicks I also tried flashing SuperSU 2.79. It does work as root, and gives root to apps, but of course fails SafetyNet, and Pokemon Go (test app) fails.
Hi all - I think this is solved - i.e., Magisk is fully functional. See first post which has been updated with the details.
Related
{
"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"
}
Video about this tutorial please watching
https://www.youtube.com/watch?v=n-2XYEUNy1o
Hi guys,to make root in 5x in nougat is much easy
1 - Put your device in fastboot mode and Unlock your bootloader
https://www.youtube.com/watch?v=hwDwxy3Z7bQ (use this,or other video of you like )
2 - Download This Files
5x TWRP https://dl.twrp.me/bullhead/
ADB Tools http://files.androidpit.info/content/adb-tools_treiber.zip
SuperSU (Put in your memory this file to install in TWRP)
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
3 - Extract "ADB Tools" and open all folders like this "adb-tools_treiber\adb-tools_treiber\adb-tools"
4 - Put TWRP "https://dl.twrp.me/bullhead/" in this folder
5 - in Windows 8 or 8.1,10 select "file,in top" and select open prompt command,and select open prompt command in administrator
6 - in "CMD" put this code :
fastboot flash recovery twrp-3.0.2-1-bullhead.img
7 - push volume down button 2x and push power button
8 - in recovery mode go to install,and select SuperSU2.76 after install select reboot system
9 -waiting your phone turn on
10 - Enjoy <3
Flashed, supersu app is there, but I still don't have root access?
It's already been mentioned in another thread that this does not work, at least not if you're encrypted.
pkadavid said:
It's already been mentioned in another thread that this does not work, at least not if you're encrypted.
Click to expand...
Click to collapse
I was told that encryption doesn't matter with the new TWRP that was released yesterday. Is that not true? I haven't tried it yet. Waiting for the Android N factory images to start clean.
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Ryandos said:
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Click to expand...
Click to collapse
Do you mind sharing your steps? I followed Heisenberg's instructions however TWRP didn't stick, and SU didn't install. Thanks!
jsgraphicart said:
I was told that encryption doesn't matter with the new TWRP that was released yesterday. Is that not true? I haven't tried it yet. Waiting for the Android N factory images to start clean.
Click to expand...
Click to collapse
You can give it a try. Looks like people have had mixed results. TWRP hasn't stuck for me, and I couldn't install SU. I've seen a few other posts with the same result.
Is the SuperSU linked in this thread systemless root? If not, is systemless root available for the Nexus 5X? Chainfire creates so many threads I can't keep up with what's the latest and what's systemless and not systemless.
pkadavid said:
Do you mind sharing your steps? I followed Heisenberg's instructions however TWRP didn't stick, and SU didn't install. Thanks!
Click to expand...
Click to collapse
I decided to boot into TWRP instead of flashing it; instead of "fastboot flash recovery twrp.img", I just did "fastboot boot twrp-3.0.2-1-bullhead.img". This booted my 5x into TWRP without flashing it.
After that I flashed supersu-2.76.zip through twrp the usual way and rebooted. Obviously my twrp didn't stick but I'm not sure why or how this method succeeded in rooting.
Well, I did the same, did you flash supersu linked in the op?
Btw, twrp didn't stick for some reason first time I installed it(I unlocked bootloader, flashed twrp through fastboot, rebooted in twrp, and it worked. However, after I rebooted into the system, I couldn't boot back into twrp. It said 'no command'.)
Then I flashed it again with the same method, rebooted the system, and tried to boot back into twrp, and voila, now it did stick.
Weird.
Then I flashed supersu, the one linked in the op, and I've got supersu app, but as I said, no root access.
Ryandos said:
I decided to boot into TWRP instead of flashing it; instead of "fastboot flash recovery twrp.img", I just did "fastboot boot twrp-3.0.2-1-bullhead.img". This booted my 5x into TWRP without flashing it.
After that I flashed supersu-2.76.zip through twrp the usual way and rebooted. Obviously my twrp didn't stick but I'm not sure why or how this method succeeded in rooting.
Click to expand...
Click to collapse
I resolved the issue with these steps. Looks like something was messed up after I upgraded from 6.0.1 to 7 yesterday using the beta program. I noticed something was wrong because changes to the system UI via the stock settings (% in battery) didn't stick. A factory reset solved it.
1. factory reset (stock, encrypted)
2. install twrp -1 (it has stuck so far after two reboots) - https://dl.twrp.me/bullhead/
3. install su 2.76 (confirmed rooted) - http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:30 AM ---------- Previous post was at 12:24 AM ----------
jsgraphicart said:
Is the SuperSU linked in this thread systemless root? If not, is systemless root available for the Nexus 5X? Chainfire creates so many threads I can't keep up with what's the latest and what's systemless and not systemless.
Click to expand...
Click to collapse
It automatically installs systemless on newer versions of Android. Use the one below, and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------
Nightshadow931 said:
Well, I did the same, did you flash supersu linked in the op?
Btw, twrp didn't stick for some reason first time I installed it(I unlocked bootloader, flashed twrp through fastboot, rebooted in twrp, and it worked. However, after I rebooted into the system, I couldn't boot back into twrp. It said 'no command'.)
Then I flashed it again with the same method, rebooted the system, and tried to boot back into twrp, and voila, now it did stick.
Weird.
Then I flashed supersu, the one linked in the op, and I've got supersu app, but as I said, no root access.
Click to expand...
Click to collapse
Try the steps in my post above. I had the same thing happen. You'll have to do a factory reset.
Actually, seems like I have root access. Root checker says I do have it, the app I tried(quickboot) couldn't acquire root access at all. I guess it's because of the systemless root?
Only systemless root is available on 5X?
If you want Android Pay to work, then you need to do the following.
Flash Magisk.
Flash phh's SuperUser 17 (Magisk Version).
Install phh's SuperUser from the Play Store.
Then when you want to use Android Pay, temporarly disable root with Magisk Manager.
It would do you some good to read those thread's to see how things work. You can discuss Android Pay/magisk here.
Should go without saying you need to unlock and install twrp before you do any of this.
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
The1nonly1 said:
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
Click to expand...
Click to collapse
I can confirm that, I did completely the same.
Including flashing TWRP two times through fastboot, and it works now.
Ryandos said:
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Click to expand...
Click to collapse
The1nonly1 said:
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
Click to expand...
Click to collapse
I confirm this.
I'm using exactly same configuration (TWRP 3.0.2-1), flashed thru fastboot (fastboot flash recovery twrp-3.0.2-1-bullhead.img) and using SuperSU 2.76 systemless root
ikyeye said:
I confirm this.
I'm using exactly same configuration (TWRP 3.0.2-1), flashed thru fastboot (fastboot flash recovery twrp-3.0.2-1-bullhead.img) and using SuperSU 2.76 systemless root
Click to expand...
Click to collapse
So what's new? This is usual procedure to root every android version on a Nexus: flash latest TWRP recovery, latest supersu, done.
This worked perfectly on the first try! Thank you
Sent from my Nexus 5X using Tapatalk
So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.
Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,
Hello,
I have a big problem. I don't know what to do.
I wanted to make a clean install of OxygenOS 4.5.8 and so i downloaded it, did it on SD card together with Magisk and no_verity_op5.zip (because i read that this decrypt the data).
So i cleand data and installed no_verity_op5.zip via TWRP, but when i wanted to reboot it takes way to long (i waited 30minutes but it stays on boot circle)
After that i booted into TWRP and decided to made a factory reset and to install OxygonOS 4.5.8 in a clean version. But it was not possible anymore!
When i want to install the .zip it says Patching system image unconditionally... and it loads. after the blue is full it says:
writing static_nvbk image...
patching firmware images...
script succeeded: result was [1.000000]
And when i want to boot into system it says no OS installed.
I tried also to flash this rom or even any other custom rom through ADB Sideload but it does not work. Same like above..
What can i do? I do not know what to do
I hope my phone is not bricked.
Thank you for any suggestion.
Go to oneplus 5 official download page, download stock recovery and latest stock firmware and follow instructions on the download page.... But first with TWRP take a backup of all your data because restoring stock firmware will ERASE everything... Don't panic it will works
First off, don't panic! you're not bricked as long as you can reach your bootloader and recovery.
This happened to me as well and luckily the fix is easy!
You probably tried to flash the OxygenOS build from the Oneplus downloads right?
Somehow these won't flash properly through TWRP and you must therefore also flash the Oxygen recovery image listed in the downloads.
Here are some steps that'll fix your problem.
1 - Backup all of your private data from internal storage because flashing OxygenOS will WIPE/ENCRYPT all data on your device.
2 - Go to the Oneplus download center and download both the latest OxygenOS and it's appropriate recovery:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8
3 - Boot into your bootloader and flash the stock recovery you just downloaded. (fastboot flash recovery <recovery>.img)
4 - Boot into the Oxygen recovery and flash OxygenOS.
This should get you up and running again.
Once you get tired of OxygenOS simply reboot back into your bootloader and flash TWRP and any rom of your liking.
In the future if you want to flash OxygenOS from TWRP you have to grab a build from XDA I guess. I'm not entirely sure why flashing from within TWRP won't work with stock OOS but I believe it expects to be flashed from withing the stock recovery.
I'm pretty confident this will solve your problems.
Please backup your data first though, don't want anything to get messed up in there!
Good luck!
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
manuelbvb said:
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
Click to expand...
Click to collapse
It is possible to have both OxygenOS and TWRP for sure!
Only a clean flash from a non-encrypted state in TWRP seems to break stuff. You can use a modified OOS build from the forums.
TWRP can indeed backup your OOS install so that shouldn't be a problem.
The only exception seems to be flashing a clean install of OxygenOS (from Oneplus Download center) through TWRP.
Other than that everything works as expected.
Ok thank you.
So i will follow you instructions and i hope it will work.
And i think so.
And after it i will install TWRP again (because i need the backup tool), i will install magisk. will this work?
So i can use everything as in a custom rom, but cannot make a clean install? So official Oneplus OTA will work with TWRP or not?
Thank you soooo much!
Also, Magisk/root works just fine on OxygenOS.
Once you flashed OOS from the stock recovery and have everything set up simply boot into your bootloader and flash TWRP.
From there you flash Magisk and everything should be fine.
OTA's from Oneplus also install fine through TWRP as long as you go into Magisk and uninstall 'root' first. When OxygenOS tells you there's an update simply remove Magisk as I said above and it'll update fine.
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
manuelbvb said:
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
Click to expand...
Click to collapse
First off! YAY!! glad it worked out!
Be sure to use the TWRP build from the twrp.me website. The one listed on these forums are 'unofficial'. Not saying those are bad, but the official one has a pretty impressive track-record.
After flashing Magisk you are root-enabled so yeah, congrats you are now root! In order to pass safetynet you must enable 'magisk hide' in the magisk manager (the app that should now be installed on your phone).
If you do not have an app called 'magisk manager' then you can download this app from the magisk forums. It should however install itself while flashing the Magisk zip. So assuming you have it installed find the 'magisk hide' service and enable it.
From my experience you sometimes need to reboot in order for it to pass safetynet check.
Glad it all worked out for you!
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
manuelbvb said:
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
Click to expand...
Click to collapse
That's great to hear!
Enjoy and take care!
no os
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
xda___ said:
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
Click to expand...
Click to collapse
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Zocker1304 said:
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Click to expand...
Click to collapse
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
xda___ said:
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
Click to expand...
Click to collapse
Well just flash a different twrp via fastboot flash recovery *path to file*
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
a4abbas said:
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
Click to expand...
Click to collapse
Hello,
Here is a link that will help you out with this update process:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
a4abbas said:
I have OP6T OxygenOS 9.0.16 and I would like to update it to the latest 10.3.3 with root.
What should be my process of doing so? I have not been in touch with rooting for the past 3 years so I don't want to mess things up. Another note is that while I am on OxygenOS 9.0.16 I tried to root it which was failed, but now few banking and calling apps such as TextNow thinks that my phone is rooted and they can not run -- but my phone is not properly rooted according to root verification apps.
Please tell me how should I do the update to the latest version from this point and then I would like to unlock bootloader and install recovery and root it as well.
Please advice.
BTW my OP6T is global
Click to expand...
Click to collapse
Flash OOS full rom zip on both slots using TWRP also flash TWRP installer zip on both slots reboot recovery flash magisk reboot system. Easy peasy.
Example:
Boot recovery: fastboot boot twrp.img
flash OOS 10.3.3 full rom zip
flash TWRP installer zip, reboot recovery,
flash OOS 10.3.3 full rom zip, format data, wipe data,
flash TWRP installer zip
Reboot recovery, flash magisk,
reboot system.
Note: I use a USB stick. I flash magisk zip off my USB stick.
That's what I do when I use OOS on my 6t far as installation goes.
Edited
flash713 said:
Flash OOS full rom zip on both slots using TWRP also flash TWRP installer zip on both slots reboot recovery flash magisk reboot system. Easy peasy.
Example:
Boot recovery: fastboot boot twrp.img
flash OOS 10.3.3 full rom zip
flash TWRP installer zip, reboot recovery,
flash OOS 10.3.3 full rom zip, format data, wipe data,
flash TWRP installer zip
Reboot recovery, flash magisk,
reboot system.
Note: I use a USB stick. I flash magisk zip off my USB stick.
That's what I do when I use OOS on my 6t far as installation goes.
Edited
Click to expand...
Click to collapse
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Michalec said:
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Click to expand...
Click to collapse
10.3.3 is all that you need. 9.0.17 isn't the only way anymore.
Michalec said:
Are you sure there is no need to update to 9.0.17 and then 10.3.3?
I've asked once and someone said that 9.0.17 is neccessary before update to 10.3.x.
Also there is option to flash from system without losing magisk modules:
1. Flash manually from update center (do not reboot)
2. Enter magisk and flash to another slot (after OTA)
3. Flash TWRP installer like magisk module
4. Reboot
But I'm not sure if I remember it correctly.
Click to expand...
Click to collapse
I have a T-Mobile SIM unlock OnePlus 6t and I converted it to an international model so when my conversation was done I was on OOS 9.0.1.1 and I booted TWRP and installed 10.3.4 full rom on both slots and also recovery installer and all just like my previous posts stated and everything went fine. I used mauronofrio's TWRP the version just before the latest 3.4xx when I did this.
I always download quite a bit of various firmwares and also TWRP versions before I start flashing things just in case something goes wrong I already have other things maybe I can use and I don't have to stop and wait for some download to finish... And I'm quite sure you know this but definitely make a backup of everything beforehand to USB or transfer it to your pc just in case you end up needing it as a precaution.
Edit added:
I am assuming that you already unlocked your bootloader... I believe everyone knows to do that that's on XDA forums before you can do anything to any device .. I say this after reading post below me here. I guess I should have said that earlier but I just assume everyone knows that on the forums... My bad. ??
From fastboot on Linux PC:
sudo fastboot oem unlock (then hit enter on keyboard) use volume keys to move to unlock option and your Power button to select it and confirm. For more info see: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Super easy to unlock bootloader just remember it does wipe your device clean so move anything to want to PC or USB stick first...
I would think you could just update oxygenOS to latest then re-root no? Assuming your already bootloader unlocked which it seems like would be the case if you have an obsolete magisk installation.
Edit: re-reading your post maybe it is not unlocked as you failed to root. In this case just unlock then flash the latest fastboot image and then magisk as others have already stepped you through. You will lose data when you unlock so backup first.
So if I'm on 9.0.16 I could flash latest OOS directly from TWRP and then flash magisk? And no data loss? Of course I'm rooted with bootloader unlocked.
Oh dear this process is getting harder because recently I was busy doing other things it sounds way harder it actually is. Isnt there a way I pay someone on this forum so that user help me do this. Like download stuff links and proper version and follow me up with it because i want to do this without messing things up!
a4abbas said:
Oh dear this process is getting harder because recently I was busy doing other things it sounds way harder it actually is. Isnt there a way I pay someone on this forum so that user help me do this. Like download stuff links and proper version and follow me up with it because i want to do this without messing things up!
Click to expand...
Click to collapse
It is indeed a tough job. This A/B partition has had a lot of people bootloop/soft bricked their phones.
However, you need not pay anybody anything. If you are on stock, I would've recommended you upgrading it via Oxygen updater (a 3rd party app on the play store) and then using the latest recoveries (TWRP 3.4) and flashing it via Fastboot mode.
It is super easy.
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..