Related
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot
Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.
prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot
Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!
Hello,
I have Oneplus 3 A3000 running on OOS 4.0.1 (Android 7.0). I also have official OP3 twrp recovery version 3.0.3-0 installed and root was done using supersu free v2.82.. It also has dm verity prompt which comes up during boot time because it is oem unlocked.
I want to know exact procedure to go to complete stock rom + stock recovery along with links to download stock recovery and rom. I saw different versions of stock recovery for different OOS. I don't care about device data as everything is on cloud and nothing on is on device. App list also I can get from google account history. Only thing I care is not to corrupt any system partitions. I also saw few posts that go into boot loop if incorrectly unrooted. I would not want that either.
Your help is greatly appreciated. Virtual beer for you ???. I am software engineer so even though I am noob in terms of hacking my android, I can follow the instructions properly.
Thanks again.
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
reyscott said:
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
Click to expand...
Click to collapse
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
mit2nil said:
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
Click to expand...
Click to collapse
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
reyscott said:
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
Click to expand...
Click to collapse
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
mit2nil said:
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
Click to expand...
Click to collapse
flash stock oos thats it.. you may leave the bootloader unlocked. better that way..
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
mit2nil said:
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
Click to expand...
Click to collapse
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
reyscott said:
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
Click to expand...
Click to collapse
Thank you so much.
mit2nil said:
Thank you so much.
Click to expand...
Click to collapse
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
tnsmani said:
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
Click to expand...
Click to collapse
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
mit2nil said:
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
Click to expand...
Click to collapse
Never mind. It booted to setup screen after few minutes. I guess I was in too much hurry.
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
danxtian said:
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
Click to expand...
Click to collapse
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
There is a zip floating around XDA which I am not able to locate immediately. It may be on siankatabg's thread on dm verity. Simply flash it.
There is also another method I read about where you flash the 4.0.2 firmware, use the enable verity command on adb, boot the phone and then flash the current firmware.
Both methods are mentioned here in XDA. Search for it.
EDIT: One of them here: https://forum.xda-developers.com/showpost.php?p=72273041&postcount=215
See also the OP of the same thread for the other method.
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
i remember having the dm verity but i forgot what i did to make it disappear.. after that time ive been running OOS rooted with twrp until i decided to go back to stock locked
So, I stopped doing anything as I got busy with my life. Here comes the 4.1.7 OTA and my DM verity was gone. So, it seems like if you go to stock and if still dm verity exists, try to do ota update or go to one ota back for flashing.
Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/
@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
I'm letting people know that with 14 they can keep stock recovery and take OTAs
ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now
Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.
lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5
Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3
Now where can we obtain a copy of the stock boot.img?
almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.
Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs
Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.
I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.
I am upgrading my OP3T from 5.0.1 to 5.0.3. My device is rooted using magisk and I have TWRP installed.
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?
EDIT - I read about Dirty flashing the version I want but I can't find 5.0.3 image on Oneplus website.
shantam2 said:
The system updates says -
"Root is detected, system will begin dowloading the full package. Your device will be un-rooted once the upgrade is completed."
Now my questions are
1. How to install the upgrade (5.0.3) without unrooting it ?
2. As it says it'll un-root my device, does it also mean it'll wipe my data as well ?.
Click to expand...
Click to collapse
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
przemcio510 said:
1. You can't.
2. No, but you can re-root it using TWRP (which will need to be reflashed via fastboot).
Click to expand...
Click to collapse
Re-flashing magisk via TWRP will keep my data ?
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
It's the same as with all previous updates.
Go to TWRP, flash the whole rom,.don't exit,.flash latest Magisk,.done.
Everything will be as before, with the new system installed
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Can you elaborate more on this ?
After I upgrade (and it becomes unrooted). I immediately flash magisk via TWRP ?
I didn't get the part "flash the whole rom and don't exit" ?
Also, Will I lose any data in the process ?
shantam2 said:
Re-flashing magisk via TWRP will keep my data ?
Click to expand...
Click to collapse
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
przemcio510 said:
Nothing will be lost even if you don't flash Magisk, so yes.
And Rastaviper meant that when you flash the update via TWRP, you don't reboot, but right after flashing the ROM you flash Magisk and then reboot, this way you will stay rooted.
Click to expand...
Click to collapse
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
b4bass said:
So no need to fastboot flash recovery?
Correct me if I'm wrong, so you dl the zip, you flash it, you then flash magisk zip? Then what? You boot up and install twrp manager in order to change recovery?
Click to expand...
Click to collapse
If you flash the update downloaded as zip from downloads.oneplus.com via TWRP, then no, there will be no need to flash it again via fastboot and no need to install TWRP Manager.
Boot to TWRP
Flash 5.0.3 zip
Flash Magisk
Reboot & enjoy
OK thanks! I thought the recovery would go back to stock after flashing the rom
And guys, if other members help you with their posts, don't forget to thank them.
Unleashed by my rooted OP3T on 8.0
b4bass said:
OK thanks! I thought the recovery would go back to stock after flashing the rom
Click to expand...
Click to collapse
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That only happens if you reboot the phone while on the stock boot image. If you use a patched boot image, or a custom kernel, or Magisk, then the stock recovery doesn't overwrite the current recovery.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
So magisk is patching bootloader? I thought it was it point not to
Though this method is saving me some serious time!
b4bass said:
So magisk is patching boot, I thought I was it point not to
Though this method is saving me some serious time!
Click to expand...
Click to collapse
Magisk makes a point of not touching the system partition but a lot of its magic is done by changing the boot image.
Sent from my OnePlus3T using XDA Labs
OK thx ! First time I replaced supersu to pet magisk. Will have to find more details on this subject
b4bass said:
So magisk is patching bootloader? I thought it was it point not to
Click to expand...
Click to collapse
Boot image is kernel and ramdisk. Boot image is not the same as bootloader!
How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!
EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device
Ah! Will do this immediately when I get home.
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!
droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!
HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk
HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.