Related
Thought I'd share how I upgraded my T-Mobile Galaxy S6 to Nougat (G920TUVU5FQE1 ) with root, deep sleep and SafetyNet bypass.
*** Read all step before starting as you will need to download and copy several files to your phone first ***
NOTE: This method will trip Knox!
Reboot into Download Mode
Flash G920TUVU5FQE1_G920TTMB5FQE1_G920TUVU5FQE1_HOME.tar.md5 with Odin (I used v3.10.6)
Download from Android File Host | Google Drive.
Reboot into Download Mode
Flash TWRP img.tar with Odin
Flash Magisk zip with TWRP and reboot to system
Install Magisk Manager (and enable Magisk Hide in Magisk Manager settings)
NOTE: The steps below will re-enable Deep Sleep
Install Flashify
Flash stock recovery.img with Flashify
Download from Android File Host | Google Drive.
Wipe cache (twice for good measure) and reboot
(Optional) Flash TWRP img using Flashify and reboot to system
Enjoy Nougat with root and SafetyNet bypass on your G920T! :good:
You do know that Google pulled Magisk from the Play Store....
The Sickness said:
You do know that Google pulled Magisk from the Play Store......
Click to expand...
Click to collapse
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
KaneHusky said:
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
Click to expand...
Click to collapse
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
The Sickness said:
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
Click to expand...
Click to collapse
Uh... I linked to the main Magisk thread on XDA, not Google Play.
KaneHusky said:
Uh... I linked to the main Magisk thread on XDA, not Google Play.
Click to expand...
Click to collapse
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
The Sickness said:
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
Click to expand...
Click to collapse
Wow. Ok, dude. Do you see an edit anywhere for my post? No. I specifically linked to the XDA thread because I know it was taken off Google Play. :good:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
BigDaddy38 said:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
Click to expand...
Click to collapse
It's pulled straight from Smart Switch so everything is 100% stock.
KaneHusky said:
It's pulled straight from Smart Switch so everything is 100% stock.
Click to expand...
Click to collapse
Sweet gonna give it a shot, Thankyou!!!!
i have no idea where to find magisk manager any help would be appreciated
BigDaddy38 said:
i have no idea where to find magisk manager any help would be appreciated
Click to expand...
Click to collapse
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
KaneHusky said:
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
Click to expand...
Click to collapse
Your right i found it, the link didnt work earlier when i tried thankyou
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
EncryptedCurse said:
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
Click to expand...
Click to collapse
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
crashff said:
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
Click to expand...
Click to collapse
Yeah, to fix deep sleep not working after the first TWRP flash.
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
BigDaddy38 said:
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
Click to expand...
Click to collapse
Read my rom thread and kernel thread.
KaneHusky said:
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
Click to expand...
Click to collapse
Everything was working fine last night, but I seem to have lost root during some point today. Magisk Manager still says that Magisk is installed, but that I am "not rooted." Any ideas? Should I try to reflash Magisk or will that trip SafetyNet?
Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....
Try installing it in recovery
I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.
Yes. It's happening to me too. Does it work if I flash this update with twrp?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.
Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.
I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?
madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )
Hey ppl, just installed it on my 3t, but when I try to install magisk, it says successful in TWRP, but when I boot up into system, it says not rooted. BUT the system partition is full and I can read it, but not write... There is some weird issue. Can anyone follow my problem?:silly:
Overall nice, what OnePlus did
Pic
svandasek said:
Pic
Click to expand...
Click to collapse
Reflashing the Magisk zip solves the issue I suppose. It fixed it for me on some other ROMs too.
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
Reflashing the Magisk zip solves the issue I suppose. It fixed it for me on some other ROMs too.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
I was trying, even tried to flash oos in between so that boot.img is stock again... No chance, tried SuperSU , and it says root isn't installed correctly on device.
svandasek said:
I was trying, even tried to flash oos in between so that boot.img is stock again... No chance, tried SuperSU , and it says root isn't installed correctly on device.
Click to expand...
Click to collapse
You probably didn't have magisk manager installed, check it? If that's the case download apk from Magisk thread and installing should deal with the issue.
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Thanks, I was testing.
---------- Post added at 03:53 AM ---------- Previous post was at 03:16 AM ----------
สุรินทร์ พลโธา said:
Thanks, I was testing.
Click to expand...
Click to collapse
From testing hours than typical usage, better 0.2 overview and notifications improved. The battery cannot be dictated at this time.
I can't install from twrp, too. Same error.
=。= said:
I can't install from twrp, too. Same error.
Click to expand...
Click to collapse
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
I installed through an app system. I tested it now, it's better to use a stable battery enough to say it's saving
aNGERY said:
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Click to expand...
Click to collapse
After activating magisk modules my device is not booting. continuously booting to twrp and showing Rescueparty. i had tried magisk untinstaller but nothing happen.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
I'm wondering if there is any advantage to installing the update twice, so that it's on both slots?
This Walkthrough works with me perfectly
Updating from open beta 5 to open Beta 6 successfully
Rooted 20.1 & Twrp 72 no issues
Thanks a lot
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
null0seven said:
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
Click to expand...
Click to collapse
This works like a charm. Just did it to install it to the other slot being slot a. I'm ocd so I like both slots flashed. Easy solution to not being able to flash it in twrp. I'm kind of curious why it won't flash in twrp though. Maybe something to do with the security patch
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Account login in settings:
I was able to flash in TWRP using version -74, downloading OB6 using oxygen updater
Gordietm said:
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Click to expand...
Click to collapse
Not up at the top but yes can add in through settings.View attachment 4883201
Aporzio said:
Not up at the top but yes can add in through settings.
Click to expand...
Click to collapse
So why do I have in the main settings and others don't?
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
Not really sure
If anybody wants official download link for OB6 Global:
https://otafsg1.h2os.com/patch/amaz...13.W.17_OTA_017_all_1911152150_5b8908ba7b.zip
ZoiraP said:
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
Click to expand...
Click to collapse
this is the first one i couldn't flash in TWRP
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
I updated from twrp and got the same popup in my settings. Also, xXx has been affected, the debloat doesn't work properly on ob6. Hopefully things will get figured out soon.
Open Beta 14 is out
Changelog
System
• Fix the problem that some software voice input cannot be recognized
• Fix the problem of the disappearance of contacts in the address book on some devices
• More clock style options now available in ambient display (Settings -- Customization --Clock style)
• Improved system stability and fixed general issues
• Updated Android security patch to 2020.05
Phone
• Now you can view call recording in call history (move to the call history, click the three-dot menu on the upper right to access the call recording)
we need the full rom zip
i6rb said:
we need the full rom zip
Click to expand...
Click to collapse
http://otafsg1.h2os.com/patch/amazo...35_OTA_035_all_2005122203_dfb6c8f59826ca0.zip
just intalled from the stable, works fine, no data lost
I can't get Magisk to work, anyone else? Tried both the normal release and canary.
What are the correct steps to flash from one beta to another, when you are rooted, and would like to keep root?? Thanks.
Went to download and it says beta 13
Tr4il said:
I can't get Magisk to work, anyone else? Tried both the normal release and canary.
Click to expand...
Click to collapse
Works for me. I downloaded the zip from oxegyn updater, flashed it in TWRP, wiped dalvik, flashed TWRP (not sure if necessary), wiped dalvik, flashed magisk, changed partition to B, restarted to recovery again, flashed magisk again and rebooted. All as fine. Dirty install too.
mexiken said:
What are the correct steps to flash from one beta to another, when you are rooted, and would like to keep root?? Thanks.
Click to expand...
Click to collapse
carnivalrejectq said:
Works for me. I downloaded the zip from oxegyn updater, flashed it in TWRP, wiped dalvik, flashed TWRP (not sure if necessary), wiped dalvik, flashed magisk, changed partition to B, restarted to recovery again, flashed magisk again and rebooted. All as fine. Dirty install too.
Click to expand...
Click to collapse
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
lbcoach3347 said:
Went to download and it says beta 13
Click to expand...
Click to collapse
The file name contains a "13" but it is not beta 13.
Sent from my OnePlus7Pro using XDA Labs
lollyjay said:
The file name contains a "13" but it is not beta 13.
Click to expand...
Click to collapse
Will this wipe everything it just update to 14 from 13
Greatness83 said:
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
Click to expand...
Click to collapse
I actually make both slots identical.
Local install of OS
Install Magisk after OTA
Reboot
Local install of the OS (might fail the first time, do it again)
Flash TWRP in Magisk
Direct install of Magisk
OTA install of Magisk.
Reboot
Now both slots are bootable with the same OS and rooted.
Greatness83 said:
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
Click to expand...
Click to collapse
that screwed me up once, now i flash twrp from magisk, then reboot to recovery and flash magisk
lbcoach3347 said:
Will this wipe everything it just update to 14 from 13
Click to expand...
Click to collapse
Just update.
Sent from my OnePlus7Pro using XDA Labs
Did OnePlus pull the update? No longer shows up for me
Pubg automatically closing without any notification on oxygen os beta Latest and even previous beta.. Any fix ??
Please help
It looks like the "clock style" is the first step toward the incoming AOD
Greatness83 said:
Did OnePlus pull the update? No longer shows up for me
Click to expand...
Click to collapse
Yes. I don't know the reason why but hope it's nothing too bad cause I already installed it.
https://www.xda-developers.com/onep...-ambient-display-clocks-may-2020-patches/?r=2
tnmsrkr said:
Pubg automatically closing without any notification on oxygen os beta Latest and even previous beta.. Any fix ??
Please help
Click to expand...
Click to collapse
Happening with me too here.
Found a fix ?
[Pulled back] OnePlus 7 and OnePlus 7T series OxygenOS Open Beta 14
Shortly after this article was published,
OnePlus has pulled back all the builds.(OxygenOS Open Beta 14)
The reason for this is unknown,
but a reasonable guess could be that there may be a showstopper bug present on them.
original link:
https://www.xda-developers.com/oneplus-7-oneplus-7t-series-oxygenos-open-beta-14-4-ambient-display-clocks-may-2020-patches/?r=2