Recent update with layers theme active = Possible Factory Reset - OnePlus 5T Questions & Answers

Not sure if this has been discussed or even an issue before, as I've done updates in the past with layers theming active and haven't had any problems.
Did the newest update this morning, systemui keeps crashing and the theme WON'T DISABLE. Looking like a factory reset is upon me. If anyone has any ideas, please speak up. Phone isn't rooted or bootloader unlocked.

siralsmooth said:
Not sure if this has been discussed or even an issue before, as I've done updates in the past with layers theming active and haven't had any problems.
Did the newest update this morning, systemui keeps crashing and the theme WON'T DISABLE. Looking like a factory reset is upon me. If anyone has any ideas, please speak up. Phone isn't rooted or bootloader unlocked.
Click to expand...
Click to collapse
Flash over recovery the substratum rescue/legacy zip, wipe cache and see if that works.

Morningbender23 said:
Flash over recovery the substratum rescue/legacy zip, wipe cache and see if that works.
Click to expand...
Click to collapse
Is that flash able with stock recovery or do you need to boot twrp, or was that recovery a rooted only option?

Related

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

[Q] 4.3 roms will boot but wont reboot

I've tried most of the 4.3 ROMs available. Installed 100% clean with a factory reset and/or wipe system, data, cache & dalvik. After the initial boot if I try to reboot, the phone gets stuck on the first "note2" screen. 4.2.2 ROMs flash boot and reboot fine. I've tried a factory reset after flashing a 4.3 but it still gets stuck. I tried devil kernel... Stuck. I'm using the latest twerp recovery. Please tell me where I fail! Thanks
mrtoast said:
I've tried most of the 4.3 ROMs available. Installed 100% clean with a factory reset and/or wipe system, data, cache & dalvik. After the initial boot if I try to reboot, the phone gets stuck on the first "note2" screen. 4.2.2 ROMs flash boot and reboot fine. I've tried a factory reset after flashing a 4.3 but it still gets stuck. I tried devil kernel... Stuck. I'm using the latest twerp recovery. Please tell me where I fail! Thanks
Click to expand...
Click to collapse
Sorry I made a duplicate thread. I think I've tried more trouble shooting than the other thread. Its your call moderator.
mrtoast said:
Sorry I made a duplicate thread. I think I've tried more trouble shooting than the other thread. Its your call moderator.
Click to expand...
Click to collapse
Maybe try flashing just the rom without any gapps. see if it'll boot for you after a couple reboots. also when u download the files check them again their MD5's so you can confirm that you have a good download.
Clockwordmod superuser app was the key! After the first boot, I ran the app and even though it always wanted to be updated (even after it went through its process) 4.3 ROMs would reboot! I tried probam and pacrom. Each time I flashed new, I had to re update the su or else no reboot. Thanks for your help!

[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:

H815 Bootloop after battery died

Hey,
So im currently on holiday and dont get back home until the 13th aug.
I was on my phone last night until i ran out of battery and the phone inevitably died. I charge it this morning and the phone is stuck on the boot animation and has a slowly flashing blue led. I do get past the lg bootloader unlocked screen too and the android boot animation runs fine, just never completes. My phone is running bootloader unlocked, twrp recovery and the imperium rom. My model is h815 and s/n is 512 prefix. The battery was running pretty bad so it might be that. Either way it is stuck in bootloop and i am not sure how to approach it. I also have some internal storage that would need backing up if possible.
Cheers for any help
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
Thats interesting, never thought of that. I should be able to backup any files etc from the internal storage using adb right?
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
MattheewHun said:
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
Click to expand...
Click to collapse
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
jet399 said:
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
Click to expand...
Click to collapse
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
htr5 said:
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
Click to expand...
Click to collapse
Yeah i saw that post and was reluctant to do so as im on my holiday. Dont want to lose my pics either, even when im very sure twrp is installed correctly as i use the quick boot app to go into recovery quite often.

Power off automatically after updating to OB8

I updated from OB7 to OB8 but when I finished updating the phone shows me power off message then boots recovery evey time. I had magisk installed with flash kernel 4.13 before updating.
zaidshb said:
I updated from OB7 to OB8 but when I finished updating the phone shows me power off message then boots recovery evey time. I had magisk installed with flash kernel 4.13 before updating.
Click to expand...
Click to collapse
Did you have Submitted installed and forgot to uninstall the overlays? Also did you full wipe or at the very least wipe Dalvik and Cache?
showofdeth6969 said:
Did you have Submitted installed and forgot to uninstall the overlays? Also did you full wipe or at the very least wipe Dalvik and Cache?
Click to expand...
Click to collapse
Do I have to uninstall substratum themes? Yes I didn't do that, but I did wipe caches. Do I have to wipe system as well?
zaidshb said:
Do I have to uninstall substratum themes? Yes I didn't do that, but I did wipe caches. Do I have to wipe system as well?
Click to expand...
Click to collapse
You need to remove all Substratum themes/overlays or you'll likely have problems. Completely uninstall the overlays if you haven't already and do so I'm the future. It's easy to forget but you need to get into the habit of doing so before you update your OS.
Doesn't happen all the time in my experience but can cause problems like yours often enough.
showofdeth6969 said:
You need to remove all Substratum themes/overlays or you'll likely have problems. Completely uninstall the overlays if you haven't already and do so I'm the future. It's easy to forget but you need to get into the habit of doing so before you update your OS.
Doesn't happen all the time in my experience but can cause problems like yours often enough.
Click to expand...
Click to collapse
I've done that and updated successfully. Thanks for the help.
zaidshb said:
I've done that and updated successfully. Thanks for the help.
Click to expand...
Click to collapse
It's always a good idea to start from scratch if you have problems but if for whatever reason that's not ideal then in TWRP tap install and scroll down to the substratum folder and select "SubstratumRescue.zip". Flash that and it will allow to to boot up again.

Categories

Resources