Question After installing TWRP for Android N Bluetooth Adaptive light - Nexus 6 Q&A, Help & Troubleshooting

So i was running great on developer preview 5. then i installed TWRP after months, just in case. you never know. after installing TWRP Bluetooth hangs it takes about ten minutes to turn on. i used wugfresh to install twrp. also my adaptive lighting goes bonkers, it'll start off way bright when i unlock my screen and take forever to go back to normal. i tried to clear data in bluetooth share app. also tried to do network reset. and restart and all three at once. no avail. i then just restored my phone to factory. everything works great. i then install TWRP from wugfresh and again have the problem. anyone have a good fix?

zmedhaug said:
So i was running great on developer preview 5. then i installed TWRP after months, just in case. you never know. after installing TWRP Bluetooth hangs it takes about ten minutes to turn on. i used wugfresh to install twrp. also my adaptive lighting goes bonkers, it'll start off way bright when i unlock my screen and take forever to go back to normal. i tried to clear data in bluetooth share app. also tried to do network reset. and restart and all three at once. no avail. i then just restored my phone to factory. everything works great. i then install TWRP from wugfresh and again have the problem. anyone have a good fix?
Click to expand...
Click to collapse
Installing TWRP shouldn't cause those issues but I would suggest installing TWRP using Fastboot. Instructions found here under the section titled "Fastboot Install Method (No Root Required):"

alryder said:
Installing TWRP shouldn't cause those issues but I would suggest installing TWRP using Fastboot. Instructions found here under the section titled "Fastboot Install Method (No Root Required):"
Click to expand...
Click to collapse
After wording it differently in Google, I have found that it's a known bug with no work around currently. It's random. Installing TWRP I think was a coincidence
Sent from my Nexus 6 using Tapatalk

Related

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.

[Q] Please help with Flashing Recovery on on Rooted VS980

I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
usafmunk said:
I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
Click to expand...
Click to collapse
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
mjones73 said:
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
Click to expand...
Click to collapse
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
usafmunk said:
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
Click to expand...
Click to collapse
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
usafmunk said:
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
Click to expand...
Click to collapse
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
TheOriginalKyle said:
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
Click to expand...
Click to collapse
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
usafmunk said:
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
Click to expand...
Click to collapse
Well new update: I was able to fix it! The problem was my own ignorance. I was following some Googl'd instructions to get the device into download mode that were incorrect. Once I saw the correct ones, I was able to get into Download Mode and revert to stock from there.

Stuck booting into TWRP

So I'm not sure what exactly went wrong, because it happened during the night. Today I got up, and my phone had booted into TWRP recovery. When I restart, it always goes back into recovery. No matter what I try, I can't get out of recovery.
I installed the Xposed Framework yesterday, and that worked just fine. It restarted just fine then, and nothing happened. I had a backup I had created before I added the framework, but restoring it doesn't help. I still boot into recovery.
Does anyone have any ideas on how to get out of recovery? I'm sure the backup I flashed works fine, because until I added Xposed I hadn't messed with anything involving root since I first rooted the phone weeks ago. Since that time, I've restarted the phone without any issues. I have no idea what exactly has happened here, since I was asleep when it did. TWRP is still installed, so I'm guessing it wasn't an OTA update that installed without permission.
Ok, I managed to get it booted, and here is what I followed:
http://forum.xda-developers.com/showthread.php?t=2451696
As concise as possible, install the USB drivers from the LG website, install Minimal ADB and Fastboot, and then open it and follow the directions of the previous thread exactly. I used copy/paste for the commands. If you can't find Minimal ADB, here is the link:
http://forum.xda-developers.com/showthread.php?t=2317790
I hope this solves the problem for anyone else who runs into it.

[HELP] Moto X won't boot to OS after strange happenings...

Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?
THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app
So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.
I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app
Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk
I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!
I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app
As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app

Beta 10 to 4.1.6 Rollback Nightmare. Help!

When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.
I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups
I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.
Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.
I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.

Categories

Resources