Related
Well I have no problem flashing stock rom back, but everytime I flash TWRP it seems to just want to go in a bootloop. I have G928R4 USC on 7.0, every time I restart the phone it just bootloops. I can access TWRP but when I reboot it pulls that crap -_- Please help. Thank you
Tokumei no said:
Well I have no problem flashing stock rom back, but everytime I flash TWRP it seems to just want to go in a bootloop. I have G928R4 USC on 7.0, every time I restart the phone it just bootloops. I can access TWRP but when I reboot it pulls that crap -_- Please help. Thank you
Click to expand...
Click to collapse
You use the latest twrp??
dizio said:
You use the latest twrp??
Click to expand...
Click to collapse
Yes on the latest twrp. Idk what the issue is.
Would it be because I'm on 7.0? Idk if that's a thing but I would assume it wouldn't be the case.
https://twrp.me/devices/samsunggalaxys6edgeplus.html
Are you using the one for your device from here?
There are 2 variants of the SM-G928R4
kdogguk said:
https://twrp.me/devices/samsunggalaxys6edgeplus.html
Are you using the one for your device from here?
There are 2 variants of the SM-G928R4
Click to expand...
Click to collapse
Yes I'm sure I'm using the right one for my device. I have never had this issue before.
Went back to twrp 3.0.2.0 and it's fine, I guess it was just the latest release that was the issue.
Wu
Root
Tokumei no said:
Well I have no problem flashing stock rom back, but everytime I flash TWRP it seems to just want to go in a bootloop. I have G928R4 USC on 7.0, every time I restart the phone it just bootloops. I can access TWRP but when I reboot it pulls that crap -_- Please help. Thank you
Click to expand...
Click to collapse
Root it first
unbelievable i did a hard reset , then clear cache , before was random reboot , now it became worse and constant boot loop ,does replugging the battery solve this issue ?
i have ALE-21 runing b958 unlocked bootloader
with twrp 3xx every time i boot into recovery and start touch the first screen of twrp device restart
and that happens for alot of twrp v
any solutions
The_username said:
i have ALE-21 runing b958 unlocked bootloader
with twrp 3xx every time i boot into recovery and start touch the first screen of twrp device restart
and that happens for alot of twrp v
any solutions
Click to expand...
Click to collapse
That used to happen to me. My phone vibration was broken, but a few days ago it started working again and twrp also started working, so I wonder, does your phone vibration work?
Lemon476 said:
That used to happen to me. My phone vibration was broken, but a few days ago it started working again and twrp also started working, so I wonder, does your phone vibration work?
Click to expand...
Click to collapse
not working
The_username said:
not working
Click to expand...
Click to collapse
That's it then. For some reason, TWRP doesn't seem to work if vibration doesn't work.
Lemon476 said:
That's it then. For some reason, TWRP doesn't seem to work if vibration doesn't work.
Click to expand...
Click to collapse
so there is no possible solution for twrp to work without vibration
The_username said:
so there is no possible solution for twrp to work without vibration
Click to expand...
Click to collapse
I don't really know, sorry, my phone vibration just started working on his own, and so TWRP did. Try asking OpenKirin team on their thread why TWRP doesn't work if vibration doesn't, this is all I can tell you
The_username said:
i have ALE-21 runing b958 unlocked bootloader
with twrp 3xx every time i boot into recovery and start touch the first screen of twrp device restart
and that happens for alot of twrp v
any solutions
Click to expand...
Click to collapse
Where did you get b958 ROM?
What emui version does it have?
Did you mis spell it ?
Never heard about b958.
miststudent2011 said:
Where did you get b958 ROM?
What emui version does it have?
Did you mis spell it ?
Never heard about b958.
Click to expand...
Click to collapse
b895 miss spelled
So I updated without going back in and seeing that Verizon is not working on 9.0.10. I'm stuck signal-less. My question is, can I flash 9.0.7-8( can't remember Wich one came before, I got the international phone, no mclearan.) Also in the process of downloading the open beta. Can I flash these without doing a data wipe?
Same problem here!! Wtf!
Yeah I'll stick with 9.0.7 before they fix this in 9.0.11. why even rush into updating your phone when it's working fine beforehand
YEAH NO GUYS. DONT GO BACK. BOOTLOOP.
However, the open beta gave me service back.
zakkyzombie said:
YEAH NO GUYS. DONT GO BACK. BOOTLOOP.
However, the open beta gave me service back.
Click to expand...
Click to collapse
Yah debating if I should load beta or wait for fix. I need phone for office calls tomorrow.
Artnig said:
Yeah I'll stick with 9.0.7 before they fix this in 9.0.11. why even rush into updating your phone when it's working fine beforehand
Click to expand...
Click to collapse
See I tell myself that, but then I see a update and I'm like "hmm...wonder what's new" and there I go doing it. That's how I missed a jailbreak when I did have a iPhone. S8 on Verizon before this and root and shid wasn't a thing, so I updated freely. Now I have to be careful ??
coolguy said:
Yah debating if I should load beta or wait for fix. I need phone for office calls tomorrow.
Click to expand...
Click to collapse
I'd stay till it's stable. I've seen some reports of the beta not fixing it.
zakkyzombie said:
I'd stay till it's stable. I've seen some reports of the beta not fixing it.
Click to expand...
Click to collapse
Loaded beta. Fixed the issue.
Beta fixes issue for me so far, but kinda sucks they missed that I got notification for update so did it and noticed that right away lol
I took the 9.0.10 update on Verizon without issue. No signal loss or anything. Wonder what could be the issue with those losing signal???
Hopefully not major issue but u were lucky one lol I've seen few already with same issue as me but hopefully if it is prob they will fix next update
Glad I saw this thread, I was driving myself crazy trying to figure out why my signal wasn't working
Yeah, going Open Beta didn't fix my signal loss issue. I really don't want to jump through the hoops to do a factory reset and set my phone back up, though, so I'll just run off my TMO work SIM and wait for a fix.
Wipe the cache.
I updated with the full OTA flashed to both slots.
No issues on Verizon.
I'm glad I read the warnings. Thank guys who brave enough to try.
Sent from my OnePlus 6T using Tapatalk
chrisliphart said:
Yeah, going Open Beta didn't fix my signal loss issue. I really don't want to jump through the hoops to do a factory reset and set my phone back up, though, so I'll just run off my TMO work SIM and wait for a fix.
Click to expand...
Click to collapse
Hmm doing beta update fixed mine.
I'm on TMobile with McLaren edition, no issues on 9.0.10
chrisliphart said:
Yeah, going Open Beta didn't fix my signal loss issue. I really don't want to jump through the hoops to do a factory reset and set my phone back up, though, so I'll just run off my TMO work SIM and wait for a fix.
Click to expand...
Click to collapse
You try to flash on both slots?
well, for everyone's reference, i tried to update twrp to official 3.x.x-0 and then updated to the newest oos 9.0.10 on both slots. and i flashed magisk on each. somehow i missed the memo about it borking my vzw service. that being said, i tried to restore my backup of oos 9.0.7 and next thing i knew, i was stuck booting with the red "device is corrupted" message which then booted into twrp with my files locked encrypted. not wanting to lose my data, i decided to fastboot boot twrp 3.x.x-0 (newest, official). this allowed me to see my files again, so i am now copying internal to my *computer. my next step will be to use msm download tool to flash back to oos 9.0.5. wish me luck.
edit- fastboot booting the twrp let me back everything up to my pc. then i used msm tool to flash 9.0.5 successfully. did update to 9.0.7 and now am copying data back. took quite some time, but until i see fixes for vzw, i wont be doing that update. lol.
The main point, though, is signal/service are both back to normal. Victory is mine! lol.
First I've heard of flashing both slots.
zakkyzombie said:
You try to flash on both slots?
Click to expand...
Click to collapse
I updated to 9.0.10 and now my connection drops. This is the first I've heard of flashing both slots. Can you direct me to a guide for this?
Just got my new phone yesterday. Been out of the modding game for a while. I went from t mobile to international sim unlocked. Have TWRP installed 3.2.3 blue 9.91 and magisk 19. Everything went smooth. I installed some modules and didn't pass safety net. Disabled modules rebooted still didn't pass. I Uninstaller magisk 19 so I can flash 18 because I read there is a safety net fix for v18 but when I go into TWRP my files are random names. What exactly do I need to do to get everything running good with safety net and how do I prevent safety net from failing? Also which TWRP should I flash so I don't have this problem. At the end of the day I just want to be on stable OOS with magisk and safety net passing. Thanks for all the help in advanced.
Sent from my [device_name] using XDA-Developers Legacy app
This may help.
Start with this post for TWRP : https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
SEARCH for flashing with Android 9.xx, onePlus 6 & Our 6T have TWO slots A & B and a whole bunch of partitions, things are 'different' from the old methods and require relearning to successfully flash recovery, ROMS, keeping root and encryption, etc;
It took me a couple of attempts and the MSMTool but I think I have some grasp of what the process' are now, we live we learn, we search.
All Devs have my utmost respect and thanks for their hard work, efforts and sharing of the spoils.
THANKS DEVS
itsmix said:
Start with this post for TWRP : https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
SEARCH for flashing with Android 9.xx, onePlus 6 & Our 6T have TWO slots A & B and a whole bunch of partitions, things are 'different' from the old methods and require relearning to successfully flash recovery, ROMS, keeping root and encryption, etc;
It took me a couple of attempts and the MSMTool but I think I have some grasp of what the process' are now, we live we learn, we search.
All Devs have my utmost respect and thanks for their hard work, efforts and sharing of the spoils.
THANKS DEVS
Click to expand...
Click to collapse
I followed a video on YouTube but I guess I need to flash a newer TWRP and magisk again. Thanks for the reply. The devs are killing it with this phone!!
Sent from my [device_name] using XDA-Developers Legacy app
Before all that, open Magisk Manager, then menu(top left 3 lines), toggle Magisk Hide. Also make sure you hiding every single item with Google in the name.(show system apps)
schmeggy929 said:
Before all that, open Magisk Manager, then menu(top left 3 lines), toggle Magisk Hide. Also make sure you hiding every single item with Google in the name.(show system apps)
Click to expand...
Click to collapse
I was just about to flash anew twrp. Downloaded everything on my pc and then turned off my phone now it is stuck on The bootloader is unlocked screen. What do I do? Also windows tells me that the device I connected has malfunctioned
Edit: Ok so I got out of that screen by holding Volume up and the power botton. Then it shut off and booted normal. I can't hide magisk because as of right now magisk is not installed but the manager is. So I'm trying to flash twrp and then flash Magisk 18.1 stable instead of v19. Do I just fastboot twrp and then flash twrp and then restart twrp back into recovery correct? And then flash magisk?
i7vSa7vi7y said:
I was just about to flash anew twrp. Downloaded everything on my pc and then turned off my phone now it is stuck on The bootloader is unlocked screen. What do I do? Also windows tells me that the device I connected has malfunctioned
Edit: Ok so I got out of that screen by holding Volume up and the power botton. Then it shut off and booted normal. I can't hide magisk because as of right now magisk is not installed but the manager is. So I'm trying to flash twrp and then flash Magisk 18.1 stable instead of v19. Do I just fastboot twrp and then flash twrp and then restart twrp back into recovery correct? And then flash magisk?
Click to expand...
Click to collapse
yes you can fastboot TWRP and then Flash the latest TWRP. reboot back to TWRP and flash 18.1, I recommend v19 though, but try that first.
schmeggy929 said:
yes you can fastboot TWRP and then Flash the latest TWRP. reboot back to TWRP and flash 18.1, I recommend v19 though, but try that first.
Click to expand...
Click to collapse
Ok I did flash v19. Everything went smooth. Now Im going to create a backup. So how can I keep safteynet in good standing?
i7vSa7vi7y said:
Ok I did flash v19. Everything went smooth. Now Im going to create a backup. So how can I keep safteynet in good standing?
Click to expand...
Click to collapse
OK as I stated, go to Magisk hide from Menu under Superuser, hit 3 dots top right and show system apps. Check everything that has Google in the name. Then go into Settings and toggle Magisk Hide off then on again. And then test Safety Net.
Thanks I hid everything google man it was kinda a pain lol thank you all. Anything I should be aware of to lose safetynet?
i7vSa7vi7y said:
Thanks I hid everything google man it was kinda a pain lol thank you all. Anything I should be aware of to lose safetynet?
Click to expand...
Click to collapse
Flash the modules you like then reboot and toggle Magisk Hide, it's usually something you have to do after every reboot. If it fails SafetyNet just remove module.
schmeggy929 said:
Flash the modules you like then reboot and toggle Magisk Hide, it's usually something you have to do after every reboot. If it fails SafetyNet just remove module.
Click to expand...
Click to collapse
Thanks for all your help I'm happy now. I got some nice good modules. Didn't pass safety but as soon as I toggled hide Magik it passed. Thank you once again and much appreciated to the devs. Cannot thank you guys enough.
Sent from my [device_name] using XDA-Developers Legacy app
When I used v18.x, SafetyNet would initially pass but after some time, usually a few hours, if I check again it would fail, even if nothing changed in that time. Toggling Magisk Hide off then back on would get it to pass, but I found myself obsessively checking several times a day & it got really annoying. I reverted to v.17.3 and don't have this issue. Only problem is Google Pay no longer works. I read that the latest Magisk fixes the GPay issue, but I don't want to deal with the SafetyNet issue just for that. Rather do without GPay.
Once I get the OOS update, I'm gonna completely uninstall Magisk & XPosed, run the update then try v.19. Hoping everything will work as it should, SafetyNet passes consistently & GPay works.
sharksfan7 said:
When I used v18.x, SafetyNet would initially pass but after some time, usually a few hours, if I check again it would fail, even if nothing changed in that time. Toggling Magisk Hide off then back on would get it to pass, but I found myself obsessively checking several times a day & it got really annoying. I reverted to v.17.3 and don't have this issue. Only problem is Google Pay no longer works. I read that the latest Magisk fixes the GPay issue, but I don't want to deal with the SafetyNet issue just for that. Rather do without GPay.
Once I get the OOS update, I'm gonna completely uninstall Magisk & XPosed, run the update then try v.19. Hoping everything will work as it should, SafetyNet passes consistently & GPay works.
Click to expand...
Click to collapse
Yeah every now and then I have to reset. Kinda annoying but not to big of a hassle
Sent from my [device_name] using XDA-Developers Legacy app
schmeggy929 said:
Before all that, open Magisk Manager, then menu(top left 3 lines), toggle Magisk Hide. Also make sure you hiding every single item with Google in the name.(show system apps)
Click to expand...
Click to collapse
So now that I have magisk and safety net is good I'm rooted I have TWRP and I'm on Oxygen Os 9.0.11. This is a T Mobile 6T but flashed to the international. How do I install Ota? Do I need to update a certain way or disable anything prior? I'm only interested in stable builds.
Sent from my OnePlus 6T using XDA-Developers Legacy app
i7vSa7vi7y said:
So now that I have magisk and safety net is good I'm rooted I have TWRP and I'm on Oxygen Os 9.0.11. This is a T Mobile 6T but flashed to the international. How do I install Ota? Do I need to update a certain way or disable anything prior? I'm only interested in stable builds.
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Follow the thread here. https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I have IN2023 latest OTA oxygen OS 11.0.1.1.INI11BA.
After rooting on magisk canary (as well as beta) I can neither enable gestures nor hide the Navbar (in system buttons and gestures). (see picture)
Hold powerbutton to open the menu also doesn't work (it simple turns the power off, changing to google assistant does work)
How to solve this, did I do something wrong or is it a bug?
henk-jan said:
I have IN2023 latest OTA oxygen OS 11.0.1.1.INI11BA.
After rooting on magisk canary (as well as beta) I can neither enable gestures nor hide the Navbar (in system buttons and gestures). (see picture)
Hold powerbutton to open the menu also doesn't work (it simple turns the power off, changing to google assistant does work)
How to solve this, did I do something wrong or is it a bug?
Click to expand...
Click to collapse
What modules have you got installed??
I noticed my center clock mod broke gestures too.
Also if you have frozen or uninstalled the OnePlus launcher this too breaks gestures.
Chances are it's a mod that broke it or freezing the OOS launcher..
But then again it's only just came out so who knows what's going on at the moment
dladz said:
What modules have you got installed??
I noticed my center clock mod broke gestures too.
Also if you have frozen or uninstalled the OnePlus launcher this too breaks gestures.
Chances are it's a mod that broke it or freezing the OOS launcher..
But then again it's only just came out so who knows what's going on at the moment
Click to expand...
Click to collapse
Thanks for the reply. The centre clock mod works fine. I use nova launcher and indeed freezing the OOS launcher when switching to it
It all happens before any mod is installed.
Your answer sugests there's a bug in Magisk comparing to the latest OTA
henk-jan said:
Thanks for the reply. The centre clock mod works fine. I use nova launcher and indeed freezing the OOS launcher when switching to it
It all happens before any mod is installed.
Your answer sugests there's a bug in Magisk comparing to the latest OTA
Click to expand...
Click to collapse
In regards to the centre clock mod no it's due to the apks used not being the most up to date.
In regards to your issue, the only way to find out what it is is to remove modules then try again. If it goes away then install one at a time, obviously unfreeze the OOS launcher too
dladz said:
In regards to the centre clock mod no it's due to the apks used not being the most up to date.
In regards to your issue, the only way to find out what it is is to remove modules then try again. If it goes away then install one at a time, obviously unfreeze the OOS launcher too
Click to expand...
Click to collapse
Maybe you've been to quick: I wrote it happens before any mod is set. It doesn't happen without root. (and everything else is the same)
As long as I'm the only one I have to start from scratch, otherwise I'll wait till a solution is found. (I guess from John Wu)
Regards, Henk-Jan
henk-jan said:
Maybe you've been to quick: I wrote it happens before any mod is set. It doesn't happen without root. (and everything else is the same)
As long as I'm the only one I have to start from scratch, otherwise I'll wait till a solution is found. (I guess from John Wu)
Regards, Henk-Jan
Click to expand...
Click to collapse
Oh really??
So you're not running any modules, and no other mods or changes?
Then youre alone with this problem..
It's possible that some modules were left behind before the update. Beyond that I'm not sure buddy, mines working fine unless I make the aforementioned changes.
dladz said:
Oh really??
So you're not running any modules, and no other mods or changes?
Then youre alone with this problem..
It's possible that some modules were left behind before the update. Beyond that I'm not sure buddy, mines working fine unless I make the aforementioned changes.
Click to expand...
Click to collapse
Thanks, then I'll start from scratch
henk-jan said:
Thanks, then I'll start from scratch
Click to expand...
Click to collapse
Bit of a long shot but try this
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation have this command ready and run via ADB.
adb wait-for-device shell magisk --remove-modules
3. Reboot, cycle the gestures to nav bar and see if it works.
That'll eliminate any left over modules, just incase, even if they're disabled from magisk they can still be left behind, have seen this a few times.
solved
dladz said:
Bit of a long shot but try this
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation have this command ready and run via ADB.
adb wait-for-device shell magisk --remove-modules
3. Reboot, cycle the gestures to nav bar and see if it works.
That'll eliminate any left over modules, just incase, even if they're disabled from magisk they can still be left behind, have seen this a few times.
Click to expand...
Click to collapse
I feel so stupid
Going to bed I just realised I completely forgot the CC mod. I removed all mods except this one
Now I did the problem is solved.
Thanks for all the help and pointing to the right direction!
henk-jan said:
I feel so stupid
Going to bed I just realised I completely forgot the CC mod. I removed all mods except this one
Now I did the problem is solved.
Thanks for all the help and pointing to the right direction!
Click to expand...
Click to collapse
No worries man. Hit the thanks button.:good:
Glad you're sorted