Phone became problematic and asking to decrypt data! - OnePlus 3T Questions & Answers

Everything was working great yesterday after I flashed the new 5.0 OOS through TWRP.
But this morning it was like my device suddenly decided to act funny. First it started FCing different apps all the time.
Then it got into a continuous restart loop.
Finally when it settled, I discovered all these problems:
- Home and recent buttons not working
- Developer options were empty
- Factory reset not working
- When I tried to reboot into recovery, I was asked for a password for decrypting data under a Mount title. I entered my pin and continued with some info for updating partition. I reflashed the stock 5.0 rom and the bluespark v.8.54 recovery, wiped cache, but nothing changed.
Any ideas?

Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?

thes3usa said:
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
Click to expand...
Click to collapse
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Everything looks fine now? Because when you said the device couldn't finalise the setup process, it may have been a corrupt flashable package. But since it's fixed now, that doesn't seem like the issue.
Sorry I was misinformed about the TWRP version, I thought there was only one version of TWRP by blu_spark that can be used. Turns out, there is another. Sorry about that.
Cheers!

Yee I hope the clean install did the trick.
Although 2 days ago everything was also running great before the catastrophic behavior.
And the worst part is that I have no clue what caused this. I didn't mess with root settings or new apps, had stock kernel installed and no new apps were installed recently.
Sent from my ONEPLUS A3003 using Tapatalk

Related

Cyanogenmod 13 no longer boots (but stock does)

This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Same issue here, was running resurrection remix, powered off to swap battery and stuck at starting apps. Went back to stock and it works.
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
My phone is functional again, I didn't notice originally but even with the stock flash I had no sound, sensors or camera. I ended up flashing the KDZ and reinstall RR and everything is normal again. Follow the step Surly33 posted and you should be fine.
Thanks a TON surly33 and Pantslessape !!!!
Struggled all day yesterday and half of today, trying to get it working again...
Wonder what was the problem?
I wonder if something changed in SuperSU 2.78 and we should stick with 2.76.
Thanks Surly33, I will try it and see how it goes.
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Worked like a charm
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
So happy that Xda developed me into someone who could help others! Cheers family!
Mogster2K said:
I flashed CM and GApps, and all seems to be working. Gonna try it with just the stock su for now. Thanks
Click to expand...
Click to collapse
Also, on SuperSU 2.78 with no issues
Surly33 said:
Also, on SuperSU 2.78 with no issues
Click to expand...
Click to collapse
i wonder what went wrong
Mogster2K said:
This just started a couple days ago. I rebooted the phone after SuperSU updated its binary, and the phone would not boot past the "starting apps" screen. I've tried everything I can think of - disabling systemless root and Xposed, upgrading CM 13, downgrading it, wiping everything and doing a fresh install, restoring stock 20i with TWRP and reinstalling CM... nothing works. It either hangs on the boot animation or the "starting apps" screen. I finally managed to get stock 20o loaded with the KDZ method and everything seems to work, but I would really like to have CM back. Can anyone help?
Click to expand...
Click to collapse
So I had this same problem happen to me. I happened to have a complete TWRP backup including all partitions from right after I unlocked the SIM and bootloader. I wiped everything including the SD Card then restored the backup and it's still having issues.
After restoring the backup I was able to get the SlimROM to boot but during the setup the phone locks up. I will try reinstalling Cyanogenmod to see if I encounter the same problem with that, but it doesn't seem like SuperSU 2.78 is the common denominator because I was running that version since it's release and only started having problems yesterday.
Meh Same here
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
shadow813 said:
Was running the nightly from 160920, had downloaded but not installed latest nightly 160930, before I had a chance to install it, phone locked up. Figured ok, maybe something I flashed? ( although last thing I flashed and or changed was on the 21st) so reflashed my previous backup of CM13 with just Cm13 installed, no extras or additions, and phone locked up again.
Stuck at the Starting apps screen.
Recharging my battery now and gonna reflash stock which Suuuuuuuuuuxxxxxxxxxxxxx :crying:
Meh dbl meh.
Anybody figure it out yet?
Click to expand...
Click to collapse
This happened to me when I flashed the CM 20160929 nightly on top of the 20160928 nightly. I was encrypted and I had been running SuperSU 2.78 since it released. Updating my phone to the 20o base fixed the problem and I took the opportunity to switch to the SlimROM6 port since CM decided they don't really want to get around to release a stable build of CM13 so that bug reports can be submitted. At least now I can toggle data on and off in the quicksettings pulldown. The downside is I have to re-setup all my accounts and stuff but on the upside I had been meaning to do this anyway as I encrypted and TWRP still can't decrypt properly (amongst other time zone bugs) to run backups and such.
I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
I was on Stock 20i before I initially installed CM 13. Maybe something changed in CM 13 so that it won't boot unless Stock 20o gets installed. I know there's more to it than just the boot and system images that custom ROMs use. (I count 57 separate partitions and I have no idea what most of them do.) The Stock 20o KDZ seems to contain 27 of them.
Click to expand...
Click to collapse
I think there was a boot loader compatibly issue with SuperSU and 20i. But, that is just a guess.
Surly33 said:
I had the same issue after updating the SuperSU binary following the flash of the latest nightly. Here is what I did to get CM13 back:
Flashed 20o kdz via LGUP - http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Booted Stock Rom - Set Developer options on and enable OEM unlocking and USB debugging
Added TWRP - http://forum.xda-developers.com/tmo...ck-guide-h811-20-o-bootloader-unlock-t3421589
Booted Stock Rom
Reboot to Recovery
Flashed CM13 via TWRP
Booted CM13
Enabled Developer options ensured OEM unlock and Usb debugging were enabled (Debugging was for Titanium Backup). Also, extended boot menu (for ease)
Reboot to Recovery flash additional items (SuperSU, Gapps, Xposed) Note: I flashed each one individually and booted (wanted to check each for functionality after this mess)
Let me know if you have questions, I'll be happy to try and help.
Cheers!
Click to expand...
Click to collapse
Haha, this happened to me like 3 weeks ago too. I ended up doing this after like 3 hours of messing around with the phone. I wish i would have just saw this instead of figuring it out on my own haha

Blackscreen after magisk update

Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
EuEra said:
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
Click to expand...
Click to collapse
That solved my issue, didn't realize that I really bricked my device. Sadly it wiped my data also!
Thanks for your advice!
I've experienced this about 3 times over the last 4 months, and had to restore a full backup each time. Basically afraid to do anything with Magisk at this point. This really needs to be fixed.
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
I did that when i switched from official to open beta, and everything went fine, then i installed a module, rebooted and got blackscreen again
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
It's not the kernel, the black screen has occurred twice when just installing a module with no modifications to /boot.
dre-z said:
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
Click to expand...
Click to collapse
Fix for me was to boot twrp, manually wipe system, data, caches etc (NOT internal storage box), then clean install the OS in twrp. Keeps your data and encryption then.
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Didgeridoohan said:
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Click to expand...
Click to collapse
Nope, I've had this happen with multiple modules, including App Systemizer, ad-free YouTube, and OP3/T channel bonding enabler. Based on the file size changes in magisk.img, I legitimately think that the linked GitHub issue is the root cause. I think the only consistent repro is to flash different versions of modules while rebooting repeatedly.
Problem might be corrupted magisk.img during resize.
vemacs said:
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
Click to expand...
Click to collapse
I had the same issue when trying to install xposed 87.1 through MagiskManager (black screen and repeated vibration).
On my J5 I just removed the battery and booted into twrp, then I uninstalled magisk with the uninstall-zip, wiped dalvik an cache, rebooted once and everything works.
I reinstalled magisk in twrp and installed xposed 87.0 through the material xposed-installer and everything works.
No data loss.
The issue on GitHub was closed with a comment saying that it's likely fixed in latest Magisk (13.1). FWIW I haven't seen it occur after running 13 beta for a while.
My op3 was bricked again today after the update. Funny thing is, this time I had not installed any module. So the problem doesn't seem to be fixed.
pls someone should help me i tried to root my android v10 infinix note8i with magisk patch boot img file using adb fastboot when i tranfer the file and reboot the phone is not booting and not gettig into recovery mode, just blank screen when a turn on pls help me out with solution
same but my problem is kind of stupid because someone rooted my phone in another way and magisk says it is installed and needs updating but it is actually not and the biggest problem is when i unroot my phone the stupid rmm locks gets enabled and boom i can't open twrp recovery because it is not an offical binary so i got stuck there i flashed a stock rom got it fixed but i still can't do it

Flashing nightmare

So here are a few things I have been through in the past 48 hours:
I flashed a custom ROM (FreedomOS) for the 3T. Could not get OK Google to work and it is essential to me especially when driving. Other people had mentioned every custom ROM was like this at the moment so I made the switch back to factory. This is where the hell begins. I wanted to try out Magisk so I could play Pokemon GO and use Android Pay, and I thought "oh what a perfect time to do just that". 4 hours of work and the SafetyNet was still tripping, only to find out I needed Magisk 13.0, which is incompatible with the OP3T boot image. Now, that could have been because I installed SuperSU prior and that patches the boot image but I had been through enough to the point of just going stock with SuperSU only. So about 10 dirty flashes later and a few hours of waiting for TWRP to load (F2FS can suck my @#$*), I find out that if you don't want to lost your data partition, there is only one very specific way to install SuperSU.
1) Wipe system and caches
2)Install OOS full rom
3)Boot into OS
4)Reflash TWRP (because OOS removes it)
5)Flash SuperSU
6)Boot into OS again
7)THEN, and only THEN can you install additional things such as ARISE or custom fonts
It appears after you flash the factory ROM through TWRP, TWRP loses all commands. So anything flashed after that doesn't actually do anything. I thought maybe it was because the new recovery is there and so maybe TWRP just needed to be reflashed before the OS was even booted, that however, resulted in a beautiful slew of corrupted fonts, no root access and broken hardware keys (even the power button). So please, learn from this XDA users, as I have the hard way. Now I'm off to go change F2FS to EXT4, fun stuff.
EDIT: On top of everything I just said, it seems none of the SuperSU zips are working now. Does not affect my phone whatsoever. It's almost like it isn't mounting /system...
EDIT 2: Great. Rooting now bootloops me and the logcat is saying AtCmdFwd service errors and BindNDK sensor server unavailable. I'm going back to FreedomOS and will just suffer from never having OK Google again.
EDIT 3: FreedomOS no longer even starts booting. Stuck at bootloader logo. Guess I'm flashing stock OOS unrooted for now. Going to have to deal with ugly default fonts and crappy audio
Try blusparks twrp for OnePlus 3t.. that fixed a lot of my issues with flashing, instead of supersu try magisk instead.
Install twrp - OOS - Magisk - Kernel - what ever else.. but see if it boots. If not, try holding the power button for 12-15 seconds until the screen goes black but the notification led turn red.. plug your phone into the computer and do a unbrick from there with the msm tool.. once it all boots, flash a custom rom over the stock rom and then factory reset from there, I'm just throwing ideas out there.
1. Factory reset.
2. Install official OOS.
3. Reboot to recovery.
4. Install TWRP.
5. Install Magisk, custom kernel, debloater etc.
6. Reboot to OOS.
When upgrading to newer OOS version, skip factory reset. I never wipe caches and everything works. If safety net fails, check that hide is enabled on Magisk settings. If still failing, use Universal SafetyNet Fix.
Forget SuperSu, Magisk does same thing. And with Magisk you can play PoGo. Forget EXT4, it doesn't give you anything, it's going to be history.
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Solved
xKroniK13x said:
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Click to expand...
Click to collapse
Ok, I will eventually try blu_sparks TWRP (that was the plan anyways), but I am back in working order. So Magisk did not bootloop my device, and v13 works on OOS. It wasn't working on FreedomOS but it even passes SafetyNet on OOS. I have ARISE and Dolby installed and couldn't be more satisfied. Did not have to wipe /data, it's like the whole thing never even happened. I will likely change to EXT4 as soon as I get the chance to backup my data partition, I haven't seen any benefit to F2FS whatsoever. Appreciate the tips, XDA rocks!
EDIT: Still takes forever to boot blu_spark TWRP but eh, I'll keep it. Will update when switch to EXT4, only reason to switch
I do the flashing in a rude way
1. Flash OOS from TWRP.
2. Flash magisk, arise, etc..
3. Reboot
4. Boot into recovery, flash any custom kernel etc..
Changing to ext4 is not required, if you are on OOS. f2fs is way better in performance over ext4 for the stock/freedom.
Sent from my OnePlus 3T using Tapatalk

Flash oxygen os 5.0.5 on OP3T with magisk using TWRP ??

Hello friends..(I am a noob )
Actually I was running on Oreo 8.1 lineage os 15.1 but then I wanted to flash oxygen os 5.0.5 stable ROM I searched for the thread on XDA and then followed it..
Here is what happened:-
1---First I clean flashed the ROM (oxygen os) using TWRP 3.2.3-0 successfully..
But then when I tried flashing magisk 17.1 my phone RESTARTED in between of magisk installation process...??
2--Then I tried it using Blu spark recovery
The same issue occured..
3-- then I tried flashing firmware 1st then OOS
Same issue occurred now my phone vibrated vigorously..
4--when I tried to just flash OOS
It again restarted...
5--Now I want to know how can I flash oxygen os with magisk using TWRP recovery ????
I had tried this process using magisk 14.3, 16,17,17.1
But none worked
Plz help me..
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Click to expand...
Click to collapse
Happening in between..??
Mayank7 said:
Happening in between..??
Click to expand...
Click to collapse
Can u pls elaborate..
How did u flash OOS using Blu spark ??
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
deetailed said:
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
Click to expand...
Click to collapse
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
OP said something about a clean flash, so he probably already cleared his data. So it shouldn't be a big deal if he does it again.
When changing from LOS to OOS you should always clear data anyway.
I think you might not be wiping everything before flashing. If you have a computer, I would follow this steps (assuming that you already backed up all your photos, documents, etc):
1- Download the factory image to your PC
2- Wipe EVERYTHING in twrp (through the advanced option)
3- Reboot to recovery
4- Connect your phone to the PC and send the factory image zip to the phone just like with any other usb drive.
5- Flash the file through twrp and inmeadiately flash latest magisk
6- Reboot to recovery and do a factory reset through twrp.
7- Reboot and be happy.
One or more of those steps might be unnecesary, but I always do it like that and it always works...
Have fun!

Help getting from LineageOS 14.1 to OxagenOS 5.08 (Something wrong with flash mem?)

Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...
As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs

Categories

Resources