Develop Bugs

What could be causing bootloops on AT&T SGS3?

Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.

SlimJ87D said:
Hello,
I am from the i9300 forum. My GF has a SGH-i747. When she updated it to official Jelly bean using Kies, all seemed to go well but then when she booted up to her home screen the phone would reboot. It would continuously do this over and over again.
So we had to use KIES to do a complete format of the phone and reboot it. This deleted everything and made it factory brand new again. This is that option where you have to type in your serial number into kies to do the emergency firmware recovery.
Well a few months went by and today while my GF was using her phone it froze and rebooted. It is now stuck in the bootloop. I don't understand why this is happening. She doesn't have the phone rooted nor has she flashed anything on it. I'm not familiar with the SGH-i747 so I'm not sure if this is a common bug that has been addressed for fixed.
Please help, my GF needs her phone for work and she's a few miles away from me. Any help or advice would be appreciated.
Click to expand...
Click to collapse
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.

BWolf56 said:
Might've to get in recovery (hold vol up+home+power), clear cache, reboot.
If that doesn't work, back in recovery and factory reset, then reboot.
Click to expand...
Click to collapse
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Could Fix Permissions fix the problem? It seems that the phone boots up to the home screen. While loading files, something at this point is causing it to bootloop. It will freeze after a few seconds and then reboot and repeat the problem.
Something is definitely conflicting within the first 30 seconds of booting up to the home screen. Any ideas?

SlimJ87D said:
Yeah, I tried all that. I managed to back up her data so maybe we can restore her apps and information later. But this is similar to last time. I had her factory reset it, wipe cache, wipe dalvick, format system and format data.
We then followed by restoring her backup but the problem still persist. I might need to flash the stock ROM.
Click to expand...
Click to collapse
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.

BWolf56 said:
Debloated stock ROM might be a good idea. When restoring, you might be bringing the problem right back. It should be very minimal (the needed stuff that you can't simply re-download or re-setup) to avoid issues coming back.
Click to expand...
Click to collapse
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.

SlimJ87D said:
I edited my post above about fixing permissions.
But this is very similar to what happen last time. I had wiped factory reset, wipe cache, wipe dalvick, format data and system, installed fresh new ROM and that boot looped too.
It took KIES emergency firmware recovery (where you have to type in your serial number) to fix the problem, but everything was deleted even the internal SD card.
Click to expand...
Click to collapse
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.

BWolf56 said:
I doubt fixing permissions will change much but could try it.
From the way you describe it, it sounds like a app or some bad data. Is she using a external SD? If so, try booting without it. If not, my guess is that there's a rogue app or something corrupted her data.
Click to expand...
Click to collapse
Thanks. Yes she's using an external SD card. I will have to get a hold of her phone and see what's going on. The first time it happened was because we upgraded to Jellybean. it happened right after so I don't think it was a rogue app. This time she just pulled her phone out of her purse and noticed it boot looping. Something sounds wrong with her phone... I think we might need to send it back for warranty repair.

Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Now that I put fresh rom and cleared everything her phone was working. But the moment I rooted the phone itboddly didn't come with SU, so upon installing SU nothing could access SU for some odd reason. So I found out you need a SU for Jelly Bean, upon installing this version of SU is when everything went to he'll and the same boot loop came back.
Sent from my GT-I9300 using xda app-developers app

SlimJ87D said:
Okay I need help. I have discovered the problem and it is the SUPERUSER app. When Superuser was updated it caused my GFs phone a boot loop.
Click to expand...
Click to collapse
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?

Alexandre-P said:
What rooting method did you use to root your girlfriend's phone?
If I'm not wrong, most of the rooting method -- if not all -- for the SGH-i747 involve the SuperSU app instead of the Superuser app. And I believe most of the custom ROM, if you switched ROM, come with SuperSU pre-installed. If you try to install Superuser (without removing SuperSU), might that be the cause of your trouble?
Click to expand...
Click to collapse
Perhaps, I will try and fix the problem again. We just got back from a movie. Thank you.

if everything doesn't work
here's what you should do
first go look for AT&T 4.1.1 stock rom
download ODIN
go to recovery by vol up + power + home
clear cache, data and dalvik
flash stock rom thru odin.
that should fix soft brick

Help with Rebooting wiping storage

Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse

re: rebooting into Google Edition Rom
razorj7 said:
Hello everyone,
I would post this in the development thread but I can't since I am a ne user. Anyway..
I am currently on InFamous switching between the 2.4 TW version and the Google Edition v2.0.
My problem is every time I reboot my phone, it gets stuck on the Samsung Galaxy S4 boot image. Then when I go to recovery the Internal storage shows 0 MB available, and I can't fix permissions or wipe anything without having to format data first. The only way to boot my phone again, is to format data, wipe everything, and reinstall the ROM which is very annoying and time consuming.
PLEASE HELP!!
Thanks in advance
-Jesse
Click to expand...
Click to collapse
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!

Misterjunky said:
Have you tried this:
Before doing anything, be sure to back up the internal sdcard to a folder on your computer if you have anything you
want to save on the internal sdcard. Also be sure that the Google Edition zip file rom is on your "external" sdcard.
When the phone is flashed and ready to use go into settings>accounts tab>backup and reset>"Factory data reset".
Click on the factory data reset.
After doing that reboot into cwm or twrp which ever you are using and do a full wipe as you usually do but don't
forget to include "Factory reset".
Then flash the Google Edition rom as you normally have done and it should fix the problem you are having hopefully.
Good luck!
Click to expand...
Click to collapse
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.

razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
Have you tried holding the power button, home key and the volume up key all at the same time to boot in recovery? If not do a battery pull and do it when turning the phone back on
Sent from my SGH-M919 using xda premium

razorj7 said:
Unfortunately, this did not work =(. Again, as soon s I reboot, I get stuck on the Samsung screen and have to pull out the battery. Then, in recovery my Internal storage has 0 MB aeven though the folders are empty.
Click to expand...
Click to collapse
If you already tried to Odin flash the STOCK rom and formatted your internal sdcard and you still find "0 MB"
in your internal storage then it must be a hardware issue and if I were you I would return/exchange the phone.
Good luck!

It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.

teshxx said:
It's not a hardware issue. It's a bug in twrp. Whenever you do "format data" it corrupts the data partition. Use PhilZ Touch recovery. His recovery includes the fix. Try it.
Click to expand...
Click to collapse
Thanks, I'll try that. How do I get rid of the bug after writing the new recovery? Format data?
Thanks!

Hello, any progress please? I have exactly the same issue.

I found here http://forum.xda-developers.com/showthread.php?t=2265588&page=23 this solution:
I wanted to clean my internal SD card before flashing Omega ROM, so I used Format Data option from Wipe section in TWRP.
After that I lost almost two days trying to fix my phone. Flashed stock ROM, TWRP and Omega ROM endless times without success after that.
My phone became randomly unbootable on reboot or power on! It was stuck on i9505 logo that is shown before boot animation forever. It was same for both stock and Omega ROM, with or without external micro SD.
After endless tries, I figured out that my phone works fine if I do factory reset and wipe from original recovery. Worked fine before and after flashing TWRP.
I tired to Format Data from TWRP again and my phone again was stuck on boot.
So I did everything once more. Flashed stock, did factory reset and wipe from original recovery and then installed TWRP and in the end I flashed Omega without wiping anything.
Everything works just fine now and I will not try to use Format data option from TWRP on this device in near time! Please fix this.
First I used TWRP 2.5.0.1 and then 2.5.0.2, but it is same in both of them.
Click to expand...
Click to collapse
Now I'm downloading stock rom so I'll try it in next 2 hours.

bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.

TheAxman said:
bet you guys previously flashed a aosp rom, I could be wrong, but it sounds as if you did.
Click to expand...
Click to collapse
It says so in the OP... going between TW and Google Edition 2.0.. Out of curiosity though, what difference would that make? I have flashed and have backups of two versions of TW and quite a few AOSP variants... I can move between them seamlessly and haven't encountered any such problems as the OP. I use TWRP as well.

It was TWRP problem. I have flashed the stock ROM with stock recovery. I have done full wipe and my phone works well again. This is bug in TWRP. Don't push "format data" button!

[Q] which TWRP?

Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.

redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3

buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.

redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.

buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.

redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.

buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?

redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/

Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore

buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?

redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.

Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)

buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.

redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.

Cool. I can try that when I get home. Do you have a link handy for the stock recovery?

redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.

buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:

CM13 Not Starting - Accidentally Wiped TWRP

I've gone and screwed up again. I managed to root and install TWRP from Lollilop. Before flashing with CM13, I wiped everything except the external SD and I believe I wiped TWRP and SuperSU in the process. So then I was like, no biggie, let's root and get TWRP back on. I rooted via ADB but now when I power the phone up, it's stuck in an endless CM boot screen.
How can I resolve this. Go back to stock and start over? I really want to avoid any further screw ups hence why I am posting here.
Thanks!

Can anyone offer some pointers? I'm truly at loss and I don't want to brick the phone.

dmg14 said:
I've gone and screwed up again. I managed to root and install TWRP from Lollilop. Before flashing with CM13, I wiped everything except the external SD and I believe I wiped TWRP and SuperSU in the process. So then I was like, no biggie, let's root and get TWRP back on. I rooted via ADB but now when I power the phone up, it's stuck in an endless CM boot screen.
How can I resolve this. Go back to stock and start over? I really want to avoid any further screw ups hence why I am posting here.
Thanks!
Click to expand...
Click to collapse
dmg14 said:
Can anyone offer some pointers? I'm truly at loss and I don't want to brick the phone.
Click to expand...
Click to collapse
Yeah, sure.
So how about telling me first how you managed to wipe TWRP? I'm pretty sure there is no option under "wipe" to wipe the recovery partition?
And CM13 is rooted, all you need to do is enable it in settings, you can install SuperSU optionally if you wish to manage superuser access with it.
So like, confirm that you actually wiped recovery (still don't get it how? you used dd command?), try to enter TWRP with hardware key combination. If successful get a new CM13 zip and reflash.

NatusVincere said:
Yeah, sure.
So how about telling me first how you managed to wipe TWRP? I'm pretty sure there is no option under "wipe" to wipe the recovery partition?
And CM13 is rooted, all you need to do is enable it in settings, you can install SuperSU optionally if you wish to manage superuser access with it.
So like, confirm that you actually wiped recovery (still don't get it how? you used dd command?), try to enter TWRP with hardware key combination. If successful get a new CM13 zip and reflash.
Click to expand...
Click to collapse
Under the wipe settings of TWRP, I checked all the boxes except external SD. Then after installing CM13, the phone didn't power on unless I pulled the battery before turning it on. Also, recovery mode doesn't boot into TWRP is simply says Factory Reset? Which is the stock recovery I believe.
This is the first time that TWRP doesn't work after wiping the phone and installing CM.

No.. It is not stock. If you installed cm then you had twrp. Just click yes when asked to wipe and you will go to twrp.
Sent from my LG-D855 using Tapatalk

NatusVincere said:
No.. It is not stock. If you installed cm then you had twrp. Just click yes when asked to wipe and you will go to twrp.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
That worked. Thank you! I re-flashed CM13 and all is good.

Think I borked my 5t

Here's where I am. Have twrp. tried to go back to stock. I messed something up. Now when I reboot to bootloader it says something about a script and "running open recovery script" is at the top. It instantly reboots to 1plus logo and back to twrp. I can get to bootloader but not recovery. Any advice before I rma it? Thanks if you can help.

Do not try to re lock bootloader

So can you get to TWRP or not? You state you can't get to recovery? Can you useADB?

azsl1326 said:
So can you get to TWRP or not? You state you can't get to recovery? Can you useADB?
Click to expand...
Click to collapse
I flashed blue twrp now and i can get to recovery. But now any rom I load, even stock oos, I can't get any wifi. The codex twrp was messing things up. But like I said, now wifi won't connect no matter what I try. What a mess.

fracman said:
I flashed blue twrp now and i can get to recovery. But now any rom I load, even stock oos, I can't get any wifi. The codex twrp was messing things up. But like I said, now wifi won't connect no matter what I try. What a mess.
Click to expand...
Click to collapse
Have you tried Formatting the data partition? You might try that then do a system reset and then reinstall whatever ROM you want. Note, it will wipe all the data on your internal sd card, so you should transfer important files to a pc. You will also have to reinstall recovery via ADB.

azsl1326 said:
Have you tried Formatting the data partition? You might try that then do a system reset and then reinstall whatever ROM you want. Note, it will wipe all the data on your internal sd card, so you should transfer important files to a pc. You will also have to reinstall recovery via ADB.
Click to expand...
Click to collapse
What is the process to do this? I will definitely try it. What does formatting do? Thanks for your help

Formatting will completely ERASE your internal storage partition, so you will LOSE all personal files that are stored here. You need to backup your data first to your pc, etc.
Boot into TWRP and select 'WIPE'. Then select the button on the lower right, 'Format Data'. You will be presented with a warning screen where you will have to type 'Yes' to confirm you understand that you are deleting all personal files. Type 'Yes' and it will format this partition. Personally, I then go back and perform a factory reset after formatting the Data partition. I then reboot back into recovery and transfer over the files that I need from my PC.
Hopefully this will fix the issue for you.

azsl1326 said:
Formatting will completely ERASE your internal storage partition, so you will LOSE all personal files that are stored here. You need to backup your data first to your pc, etc.
Boot into TWRP and select 'WIPE'. Then select the button on the lower right, 'Format Data'. You will be presented with a warning screen where you will have to type 'Yes' to confirm you understand that you are deleting all personal files. Type 'Yes' and it will format this partition. Personally, I then go back and perform a factory reset after formatting the Data partition. I then reboot back into recovery and transfer over the files that I need from my PC.
Hopefully this will fix the issue for you.
Click to expand...
Click to collapse
I formatted. Loaded liquid remix. Booted and factory reset. Booted into recovery and then back to system. No wifi. There is nothing in my ip address on phone. I don't get this.

fracman said:
I formatted. Loaded liquid remix. Booted and factory reset. Booted into recovery and then back to system. No wifi. There is nothing in my ip address on phone. I don't get this.
Click to expand...
Click to collapse
Hmm..... Not sure then. I remember reading someone else was having a similar issue. It might have actually been in the liquid forum. Have you checked there?

azsl1326 said:
Hmm..... Not sure then. I remember reading someone else was having a similar issue. It might have actually been in the liquid forum. Have you checked there?
Click to expand...
Click to collapse
It kinda sux I can't even get it on stock. Posted in LR thread. We will see. Thanks for the help.

fracman said:
It kinda sux I can't even get it on stock. Posted in LR thread. We will see. Thanks for the help.
Click to expand...
Click to collapse
Read thru here and see if any if this helps.
https://forum.xda-developers.com/oneplus-5t/help/wifi-issues-rolling-to-stock-oos-t3730017

azsl1326 said:
Read thru here and see if any if this helps.
https://forum.xda-developers.com/oneplus-5t/help/wifi-issues-rolling-to-stock-oos-t3730017
Click to expand...
Click to collapse
Notta. I think something is messed up with it.

The way I fix the wifi bug. Flash oos And codeworks universal twrp. Then flash stock boot.Img in twrp then flash mgsik 15.2 then flash a custom kernel (I'm currently on new kernel v1.08. That's how I fixed my wifi bug. )
Don't know of that helps but that's how I fixed it.

Have you tried following the instructions for roll back here:
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074