Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.
Please describe in steps what you did.
AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!
Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?
ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb
AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.
I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.
Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!
Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver
I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3
Related
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Unlock bootloader.
Use ADB side load to flash stock rom.
Lock back bootloader. Voila!
Hope it helps. Thanks!
i tired
I tired but after the OTA update i get the dm message again
K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
this
cpt.macp said:
this
Click to expand...
Click to collapse
I will try Tomorrow
cpt.macp said:
this
Click to expand...
Click to collapse
When i do this a have to unlock the bootloader so i have 1 message again ...
K3v1990 said:
When i do this a have to unlock the bootloader so i have 1 message again ...
Click to expand...
Click to collapse
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
ill go try that, thanks
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
for full restet u mean Factory restet in the settings?
Edit: found it
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Official Recovery ( Oxygen OS ) - https://www.androidfilehost.com/?fid=24591000424943319
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
It worked thank you very much
When dm-varity warning is there, i flash openbeta 7 firmware &modem . Problem solved! Never see this warning. Phone works fine.when i flash openbeta 8 firmware &modem,i wil get back the dam-varity warning
LELBOT said:
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - https://docs.google.com/uc?id=0BzS3n...xport=download
Official Recovery ( Oxygen OS ) - http://oneplusroms.s3.amazonaws.com/...BmI3Z1Dri5Q=
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
Click to expand...
Click to collapse
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
m_reyna_16 said:
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
Click to expand...
Click to collapse
Yes, it will work.
For the new recovery, it supports f2fs decryption and u have flash it to follow the steps.
These methods will work.
Dm-verity
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
cryptofer said:
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
Click to expand...
Click to collapse
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
Hi,
to be synthetic:
From TWRP recovery, change filesystem to Ext4 for both Data and Cache, then full wipe everything (System too);
Go back to OxygenOS v3.2.8;
Be sure to replace TWRP with Stock Recovery (download from 3.2.8 official thread);
Lock bootloader (both from Developer Options and Fastboot);
Sideload via recovery OxygenOS v4.0;
Consider to factory reset for a clean installation.
For more clarifications, I'm at your disposal
https://www.androidfilehost.com/?fid=457095661767116249
flash it
Test by me
millicent said:
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
cryptofer said:
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
Click to expand...
Click to collapse
I haven't tried it yet but I read a few reports already about systemless root with magisk being able to preserve Android pay
Sent from my ONEPLUS A3000 using Tapatalk
Hello,
As the title pretty much explains, I want to know how to prevent stock recovery replacing twrp when we flash the nougat oos zip? Even when I flash twrp image in recovery after oos nougat installation, the damn thing still overwrites twrp and I need to use a laptop to flash twrp again.
abhibnl said:
Hello,
As the title pretty much explains, I want to know how to prevent stock recovery replacing twrp when we flash the nougat oos zip? Even when I flash twrp image in recovery after oos nougat installation, the damn thing still overwrites twrp and I need to use a laptop to flash twrp again.
Click to expand...
Click to collapse
To keep twrp
1.flash stock oos
2.flash twrp
3.reboot to recovery - most imp step
4.reboot to system
JumboMan said:
To keep twrp
1.flash stock oos
2.flash twrp
3.reboot to recovery - most imp step
4.reboot to system
Click to expand...
Click to collapse
Did the same but unfortunatley, it booted straight into the rom rather than recovery.
abhibnl said:
Did the same but unfortunatley, it booted straight into the rom rather than recovery.
Click to expand...
Click to collapse
That "bootloader unlocked" warning is pretty useful. When it shows up, press a volume buttton (any) and you'll get a list of options. Choose recovery there to make sure it doesn't try to go directly into system.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
That "bootloader unlocked" warning is pretty useful. When it shows up, press a volume buttton (any) and you'll get a list of options. Choose recovery there to make sure it doesn't try to go directly into system.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
I can vouch for the usefulness of the warning screen. Quite accidentally I found that option while trying to install 4.0.2 and TWRP and in the process trying to avoid dm_verity. It is really useful because sometimes, despite your choosing to boot into recovery, the phone stubbornly boots into system.
i know its a old threat but i have the same problem, and tested all the steps above and still is my OP3T booting into stock recovery after i installed TWRP. do you guys maybe have a new solution for the problem ?
PIPT said:
i know its a old threat but i have the same problem, and tested all the steps above and still is my OP3T booting into stock recovery after i installed TWRP. do you guys maybe have a new solution for the problem ?
Click to expand...
Click to collapse
Another method is to flash Magisk immediately after TWRP before booting into system. Then boot into system.
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!
Step to expose what happens to me:
after brick my oneplus 3 by flash a wrong zip I got back to the stock rom, but when I try to install twrp only stays 1 time. When I reboot the system and try again to enter TWRP it appears the stock recovery of oneplus. Any idea why this happens and how to fix it?
BlackDeath XVI said:
Step to expose what happens to me:
after brick my oneplus 3 by flash a wrong zip I got back to the stock rom, but when I try to install twrp only stays 1 time. When I reboot the system and try again to enter TWRP it appears the stock recovery of oneplus. Any idea why this happens and how to fix it?
Click to expand...
Click to collapse
Flash the recovery by adb. This should make it stick.
zelendel said:
Flash the recovery by adb. This should make it stick.
Click to expand...
Click to collapse
I flash it with adb 3 times and still stock when i reboot the phone
BlackDeath XVI said:
I flash it with adb 3 times and still stock when i reboot the phone
Click to expand...
Click to collapse
Immediately after flashing TWRP, without booting, flash SuperSu or Magisk and then boot to system.
tnsmani said:
Immediately after flashing TWRP, without booting, flash SuperSu or Magisk and then boot to system.
Click to expand...
Click to collapse
What is the diference for do twrp permanently installing magisk?? Ty very much for you help
BlackDeath XVI said:
What is the diference for do twrp permanently installing magisk?? Ty very much for you help
Click to expand...
Click to collapse
Your question is not very clear. If you are asking how TWRP stays permanent if Magisk is flashed, I think that since Magisk modifies the boot image, it prevents the ROM from overwriting TWRP with stock recovery.
tnsmani said:
Your question is not very clear. If you are asking how TWRP stays permanent if Magisk is flashed, I think that since Magisk modifies the boot image, it prevents the ROM from overwriting TWRP with stock recovery.
Click to expand...
Click to collapse
ty yes that my question jajaja
I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.