hello, i just updated my galaxy s3 mini to the latest CM release (20140629) and when my phone finished booting i started getting this error (Unfortunatelly, Themes provider has stopped.), i tried wiping cache and dalvik cache but it didnt work, could anyone help me out to fix this issue? Thanks in advance!
Are you able to do anything on the device or does the error keep coming back every second?
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.4
GXGOW said:
Are you able to do anything on the device or does the error keep coming back every second?
Click to expand...
Click to collapse
Yes, the error kept coming back every second, now i tried wiping system, data, cache and dalvik cache, flashed the rom and the gapps again and the device is working correctly now, thanks for the help
robert95 said:
Yes, the error kept coming back every second, now i tried wiping system, data, cache and dalvik cache, flashed the rom and the gapps again and the device is working correctly now, thanks for the help
Click to expand...
Click to collapse
No problem. I also had the same problem a few times, but with SystemUI. It's really annoying to restore from scratch again.
helps
My case is similar, but i dont solve the problem, i try all wipes any roms and the error continue.
Please help me solve this.
thanks
sfca said:
My case is similar, but i dont solve the problem, i try all wipes any roms and the error continue.
Please help me solve this.
thanks
Click to expand...
Click to collapse
Hello, T mobile GS4 owner here.
I just signed up because I'm having the same problem. I've been happily running Liquidsmooth for many months now, and my current version is from 6/21/14. I haven't had any problems flashing until now.
I've tried flashing the last 2 builds and keep getting the message "unfortunately themes provider has stopped".
It appears as soon as the phone boots up after flashing. It's right in the middle of the screen and won't allow me to do anything. Every time I click on OK, it comes back immediately. I have searched high and low for a way to fix this. So far I've tried reloading, rebooting, re-downloading starting again from scratch. I always clear the data and cache and do a factory reset. I have attempted flashing at least half a dozen times and always get the same annoying message.
Any help would be very much appreciated.
BTW, I'm also flashing the latest full version of GAPPS at the same time.
robert95 said:
hello, i just updated my galaxy s3 mini to the latest CM release (20140629) and when my phone finished booting i started getting this error (Unfortunatelly, Themes provider has stopped.), i tried wiping cache and dalvik cache but it didnt work, could anyone help me out to fix this issue? Thanks in advance!
Click to expand...
Click to collapse
Do complete wipe and install latest nightly or milestone release of cm 11 from novafusion.pl ..it should work fine!!
i try other roms and the problem continue..
in s3 mini its possible 4.4.4?
Themes Provider
Hi Guys!
I have the same problem of everyone...Anyone have a solution about this???
Best Regards,
Hugo
My Solution
robert95 said:
Yes, the error kept coming back every second, now i tried wiping system, data, cache and dalvik cache, flashed the rom and the gapps again and the device is working correctly now, thanks for the help
Click to expand...
Click to collapse
I selected ext4 file system and this problem went away. No more theme stopped working error.:laugh:
robert95 said:
Yes, the error kept coming back every second, now i tried wiping system, data, cache and dalvik cache, flashed the rom and the gapps again and the device is working correctly now, thanks for the help
Click to expand...
Click to collapse
Hey robert95, reinstalling is not the solution.
There is a culprit theme so lets find that out.
First connect phone to adb.
go to the layout just before which error come.
type in terminal
Code:
adb logcat
enter
tap to get error
you will get output something like this on terminal
Code:
.......
.......
.......
.......
--------- beginning of crash
xx-xx xx:xx:xx.xxx xxxx xxxx E AndroidRuntime: FATAL EXCEPTION: main
xx-xx xx:xx:xx.xxx xxxx xxxx E AndroidRuntime: Process: com.sonyericsson.advancedwidget.clock, PID: xxxx
xx-xx xx:xx:xx.xxx xxxx xxxx E AndroidRuntime: Theme: themes:{default=overlay:venus.theme, iconPack:com.elsalvador.xperiacm12theme, fontPkg:venus.theme, com.android.systemui=overlay:venus.theme, com.android.systemui.navbar=overlay:system}
.......
.......
.......
.......
.......
you get some app like venus.theme,com, elsalvador.xperiacm12theme
Uninstall those culprit and open themes again now there will be no error.
Happened with my s6.. emailed samsung and they said its a problem many are having and i would have to wait for the next update for it to be fixed. 4th update today and its still not working.
Brother when i go to my themes in samsung theme store at G930F it says Unfortunately theme store stopped. I cleared the data and i force stopped it 4 times but still problem is not solved. Can you help me plz....
Related
ok due to the massive number of people clogging the offical thread im starting this thread just to help some of our newer members get working. anyone with a proper working install can help as well. let the issues begin.
i have no data connection at all i have installed 1.6 from htc and then 4.1.99. I even went back and wiped and reinstalled both rebooted and still no connection (3g or 2g).
any ideas
when you signed into google did it work or say cant connect?
Ok here's a question. I was running 4.1.11 which was running fine. I downloaded the recovery image & flashed it thru the recovery console (home + power) and then tried to flash 4.1.99 & now when i try going into the recovery console, I get the Exclamation point with the phone on its side. If i let it power thru it loads up, but like its stock.
I even tried terminal emulation & can't even get the SU command to work.
Any suggestions besides, re-rooting?
This is what I did
Okay, let me start off by saying I have had none of the lag a lot of the people are reporting. So I figured I would post how I installed step by step just incase it helps someone.
Step 1: Download the HTC rom and Cyanogen rom.
Step 2: Reboot into recovery.
Step 3: Flash the HTC update from recovery and let it finish ( it will do the radio as well) the phone will reboot back into recovery by itself.
Step 4: Wipe.
Step 5: Flash the Cyanogen update.
Step 6: Enjoy.
Don't think it would make any diff but just incase, I came from JACxHEROSkiv2.2 and cm 1.4 recovery.
Hope this helps in any way.
yes the same thing happened to me. its very simple too. just fastboot cyanogens recovery.img
http://forum.xda-developers.com/showthread.php?p=3915123
heres fastboot stuff
http://forum.xda-developers.com/showthread.php?t=502010
then flash newest cyanogens like normal and wipe afterwards.
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Every time I try updating to 4.1.99 It stays on the g1 screen.
persiansown said:
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Click to expand...
Click to collapse
try wiping your ext3 however please note alot is going on first boot. i didnt have any issues with slow but i wiped my ext3 and data(wipe in recovery) slow downs are caused mostly by missing or incompatible issues. thats why wiping is recommended. try wiping ext3 and start from scratch. its worth it.
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
jeremycool said:
Every time I try updating to 4.1.99 It stays on the g1 screen.
Click to expand...
Click to collapse
did you flash the adp image first?
mormo said:
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
Click to expand...
Click to collapse
check your md5s on both and start from scratch.
Here's what I did:
1. Wipe.
2. Delete all your EXT partition stuff.
3. Reboot into recovery.
4. Flashed the HTC update from recovery. I did NOT reboot after this finished.
5. Flashed the Cyanogen update.
6. Rebooted and waited for the post flashing process to finish.
I had one single FC at the beginning but now it's all good.
If you are not clearing out your dalvik cache and all your other EXT stuff AND wiping, then it's only not working because you didn't do those things.
yes both ways work. however if you have issues try letting the radio install. ONLY if you have issues.
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
the reason some people have to let the radio flash is due to either a bad flash. corrupted install or some other reason. every new version come with a new radio and it will sometimes delete your recovery. this is because certain older setup are different and not very consistant. however things happen and some stuff gets messed up. every dream is the same and this software is the same. but you are the different part.
damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
damngood98 said:
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Click to expand...
Click to collapse
Not sure if it is your only option, but it might help. And no you will not need to flash anything afterwards.
jokersax11 said:
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
Click to expand...
Click to collapse
damn! gonna go bed and maybe pout for a bit tomorrow before i do another wipe. I hate wiping!
thanks for help joker!
damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
Look at it this way...
You moved into a new place and the last tenant was evicted. He left all his crap lying around (mostly trash and dirty laundry.)
Do you sweep the rooms and take out the trash and call it a day? Or do you clean the whole house first? Technically, taking the trash should be enough (laundry included) but you never know what else is hiding in the house (maybe he had a pet tarrantula and it's walking around unbeknown to you. Eventually, you'll run into it and force close yourself in shock.
Okay I have tried EVERYTHING! I tried uninstalling my CM9 Alpha 2 completely with Acme Uninstaller and then doing a fresh install. I tried wiping data, cache, davlik, and still nothing! I don't know what to do. I tried so many things and have been working on this for the past 5 or 6 hours today! Please SOMEONE ANYONE have any ideas? My Touchpad is fine for about 2 minutes and no matter what I am doing it freezes for a second or two, screen goes black for a second, and then it reboots. Please SOMEONE HELP! I am about to give up on Android and I didn't love ICS so much I would! Thanks for all the help!
Have you changed any of the DPI settings? in the build file?
Have you tried booting into recovery and performing a full wipe? Wipe data, cache, dalvik cache.
Sent from my Rocket in the Sky (SGH-i727) using XDA Premium.
I haven't tried changing the DPI Settings. As for wiping data, cache, and davlik cache I tried all that. When I wipe the davlik cache though in recovery I get this error:
E:unknown volume for path [/sd-ext]
Would that have anything to do with the rebooting? I don't ever recall having this error before. If so, how do I fix it???
Thanks for both suggestions!
Shound I uninstall everything and just start from scratch and put CM7 Alpha 3.5 and then update it the CM9 Alpha 2 or do you all think that would work???
I suppose the quickest answer would be to just to start again reload back to webos, then do the process again. I've never had any issues like your having and maybe instead of installing cm7 them cm9 just install straight to cm9. May of been a buggy install. Also maybe before that try redownloading another rom. May of just been a slightly messed up rom you installed.
alias4ever said:
I haven't tried changing the DPI Settings. As for wiping data, cache, and davlik cache I tried all that. When I wipe the davlik cache though in recovery I get this error:
E:unknown volume for path [/sd-ext]
Would that have anything to do with the rebooting? I don't ever recall having this error before. If so, how do I fix it???
Thanks for both suggestions!
Click to expand...
Click to collapse
The error is troubling. If it were me, I'd completely redo the CM7 to CM9 install process starting with the uninstall. And get a fresh download of the rom and gapps and every file that you have not used successfully once in an install.
anytime i try to install a rom the phone will get stuck at multiple "process has stopped working" notifications that just keep repeating. the only way to get anything to work is to go back to a stock rom. am i missing something? i have twrp 2.6.3.3 installed
almosttrae said:
anytime i try to install a rom the phone will get stuck at multiple "process has stopped working" notifications that just keep repeating. the only way to get anything to work is to go back to a stock rom. am i missing something? i have twrp 2.6.3.3 installed
Click to expand...
Click to collapse
Did you dirty flash it? When switching roms, ALWAYS wipe data/cache/dalvik before installing any rom. If you are at stock and switching to a non stock based rom, definitely wipe data/cache/dalvik, or else you will run into problems just like this.
almosttrae said:
anytime i try to install a rom the phone will get stuck at multiple "process has stopped working" notifications that just keep repeating. the only way to get anything to work is to go back to a stock rom. am i missing something? i have twrp 2.6.3.3 installed
Click to expand...
Click to collapse
Sounds like you are not wiping system, are you?
I always full wipe any ROM, you especially want to going to stock from aosp or vice versa.
Go Intl advance wipe and clear cache, dalvek, system, and data.
NEVER wipe internal
Sent from my VS980 4G
i forgot i started this thread but i fixed the problem a while back. and yea i always full wipe as well. i really dont know what the problem was. I just updated to the newest twrp and everything started installing fine. thanks anyway though guys
almosttrae said:
i forgot i started this thread but i fixed the problem a while back. and yea i always full wipe as well. i really dont know what the problem was. I just updated to the newest twrp and everything started installing fine. thanks anyway though guys
Click to expand...
Click to collapse
My bad. Didn't notice someone An Corp'd a dead thread haha. Glad you got it figured out
Sent from my VS980 4G
Hello Everybody, My phone is Samsung Galaxy Ace S5830 and I have an issue.I am the one who is changing rom constantly.I was using the rom named ''Xperiance-Ace-v4_Sky_Walker_Studios'' for a long time.Lately i loaded another rom, 2 hours after i used, The phone was closed by itself, I tried open phone again but it stayed at boot animation screen.After that, I thought that rom is spoilt, I tried other roms but they stayed at boot animation screen as well.I tried all of roms that i have but result was same.I thought that i should try the rom which i was using before all those problems started.So i flashed Xperiance-Ace-v4_Sky_Walker_Studios Rom.Bizarre but it worked.When it opened i have faced with some pop-up ''android upgrading 0/70'' when it finished (70/70) i was at homescreen and all of my apps that i downloaded when i was using this rom at old days was there.It was so weird, And all aplications started to stop itselves and i even havent touched any of them. Like ''Unfortunately Whatsapp has stopped'' ''Unfortunately contacts has stopped'' ''Unfortunately facebook has stopped'' finally they all stoped working and i tried open applications, No application opened even contacts.
Present state: Only one rom is working, Others staying at boot animation screen and the rom which is working actually not working, Only phone is opening, No application working
What is the Problem? What Should i do? I am waiting your answers, THANKS.
Talha10 said:
Hello Everybody, My phone is Samsung Galaxy Ace S5830 and I have an issue.I am the one who is changing rom constantly.I was using the rom named ''Xperiance-Ace-v4_Sky_Walker_Studios'' for a long time.Lately i loaded another rom, 2 hours after i used, The phone was closed by itself, I tried open phone again but it stayed at boot animation screen.After that, I thought that rom is spoilt, I tried other roms but they stayed at boot animation screen as well.I tried all of roms that i have but result was same.I thought that i should try the rom which i was using before all those problems started.So i flashed Xperiance-Ace-v4_Sky_Walker_Studios Rom.Bizarre but it worked.When it opened i have faced with some pop-up ''android upgrading 0/70'' when it finished (70/70) i was at homescreen and all of my apps that i downloaded when i was using this rom at old days was there.It was so weird, And all aplications started to stop itselves and i even havent touched any of them. Like ''Unfortunately Whatsapp has stopped'' ''Unfortunately contacts has stopped'' ''Unfortunately facebook has stopped'' finally they all stoped working and i tried open applications, No application opened even contacts.
Present state: Only one rom is working, Others staying at boot animation screen and the rom which is working actually not working, Only phone is opening, No application working
What is the Problem? What Should i do? I am waiting your answers, THANKS.
Click to expand...
Click to collapse
Are you do a full wipe, before flashing another custom rom?
I did Wipe data factory reset, Wipe cache partition, Advanced>Wipe Dalvik cache
Talha10 said:
I did Wipe data factory reset, Wipe cache partition, Advanced>Wipe Dalvik cache
Click to expand...
Click to collapse
I suggest you install the stock rom using odin. It seems you have some corrupted files. Before flashing the stock rom, do Format Data/ Factory Reset, Format Cache Partitions, Mount & Storage> Format /system, Wipe Dalvik Cache and Wipe Battery Stats. Once you have flashed the stock rom, go to recovery mod and do Wipe Data/ Factory Reset and Wipe Cache Partition (otherwise bootloop might occur). After that install root and CWM from the recovery mod. Now you can install any other custom rom without any problem. Do post your results. Hope I Helped
When i connect phone to the computer, connecting text under phone logo is occuring in kies, But not connecting
And neither in download mode nor not in download mod odin can't see the phone at all
Talha10 said:
When i connect phone to the computer, connecting text under phone logo is occuring in kies, But not connecting
And neither in download mode nor not in download mod odin can't see the phone at all
Click to expand...
Click to collapse
Uninstall kies, and then download driver for galaxy ace.
Maybe, there is something wrong with your recovery, what recovery do you use?
---------- Post added at 06:03 AM ---------- Previous post was at 06:00 AM ----------
Talha10 said:
When i connect phone to the computer, connecting text under phone logo is occuring in kies, But not connecting
And neither in download mode nor not in download mod odin can't see the phone at all
Click to expand...
Click to collapse
Uninstall kies, and then download driver for galaxy ace.
Maybe, there is something wrong with your recovery, what recovery do you use?
And, try redownload, and flash that rom again. Maybe, it's corrupted.
i unistalled and nothing happened.
And there is no problem about driver because pc is recognizing the phone which means it's was already updated.
ClockworkMod Recovery version is v4.0.0.9
And i flashed many times
Talha10 said:
i unistalled and nothing happened.
And there is no problem about driver because pc is recognizing the phone which means it's was already updated.
ClockworkMod Recovery version is v4.0.0.9
And i flashed many times
Click to expand...
Click to collapse
Try installing CWM 5 from the recovery mod. CWM 5 is much more stable than CWM 4. Once you have installed CWM 5, do Format Data/ Factory Reset, Format Cache Partitions, Mount & Storage> Format /system, Wipe Dalvik Cache and Wipe Battery Stats. Then try to flash any working rom with it. Here is the link,
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Do post your result. Hope I Helped
i did all of the things that you said but result is same
edit: Yeeeesss now i istalled Xperiance-Ace-v4_Sky_Walker_Studios but it wasnt like old instalations, Old applications didn't come.Rom was opened like new phone, There is no problem now, Everything in phone are opening.
But why could'nt i install other roms.Of course i can continue with this rom it's better than none i mean at least i can use phone without problem.It is perfect but if can we solve the problem for other roms it will be very perfect, By the way thank you for your helps
Talha10 said:
i did all of the things that you said but result is same
edit: Yeeeesss now i istalled Xperiance-Ace-v4_Sky_Walker_Studios but it wasnt like old instalations, Old applications didn't come.Rom was opened like new phone, There is no problem now, Everything in phone are opening.
But why could'nt i install other roms.Of course i can continue with this rom it's better than none i mean at least i can use phone without problem.It is perfect but if can we solve the problem for other roms it will be very perfect, By the way thank you for your helps
Click to expand...
Click to collapse
Bro, are you sure you can't install any other rom with CWM 5? Never forget to do Format Data/ Factory Reset, Format Cache Partitions, Mount & Storage> Format /system, Wipe Dalvik Cache and Wipe Battery Stats before you install any other rom. Also click the Thank button to thank us for our time. Do post the results. Hope I Helped
mahithm said:
Bro, are you sure you can't install any other rom with CWM 5? Never forget to do Format Data/ Factory Reset, Format Cache Partitions, Mount & Storage> Format /system, Wipe Dalvik Cache and Wipe Battery Stats before you install any other rom. Also click the Thank button to thank us for our time. Do post the results. Hope I Helped
Click to expand...
Click to collapse
Yes im sure i do all of them always
Update for the readers wh don't want to read the rest of the thread:
I solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
The remaining problem is:
But i still get the welcome screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the process i switched from OctOS to lineage and i still get the problem... what can that be???
quick info: TWRP is the most recent (3.0.3-1), firmware is the newest (4.0.3), Lineage is the nightly from Feb 14.
Original post:
Hello there fellow Oneplus users,
I've got some trouble with my 3T. I changed the OS to OctN some weeks ago. Everything was fine, i din't update the first 2 weeklys and when i wanted to update a few days ago (to OCT-N-WEEKLY-20170210-2251-oneplus3.zip) i tried but there was error 7... i don't remember exactly what i did then but when i booted i got the message "com.android.phone has stopped" and i couldn't get the message away (it appeared directly again after clicking ok) in the background the phone wanted to make a fresh setup. i tried a few things out, and the only thing that worked was wiping the cache, dalvik and data and then installing the rom, that was installed before (OCT-N-WEEKLY-20170121-0348-oneplus3.zip)
the next day i thought i could try it again (i hoped it was just coincidence), but make a backup via twrp before. but then same error... So i wanted to restore the backup. It went without errors in twrp, but the booting afterwards took about 15 minutes! After the boot: again the error message and in the background the "set up new phone" screen... even though i did a restore... so again wipe cache/dalvik/data via twrp and re install the old version of the OctOS
Next day after research: maybe i needed to update the firmware (4.0.2). downloaded it but i thought i would wait a little, because i don't have that much time to deal with those problem right now.
So today i decided to give it a try, rebooted to twrp, but then i thougt: "nah, i'll do it another day". So i really did NOTHING in TWRP -> reboot to system -> same old Error (com.android.phone has stopped) and data lost (new phone setup)
Ok: reboot to twrp, flashed the new firmware (no error) tried to flash the new OctOS -> error 7...
I also have the latest LineageOS rom (lineage-14.1-20170214-nightly-oneplus3-signed.zip) on the phone to try out: wiped Cache/Dalvik/Data install Lineage: same error 7...
same with the old OctOS: everything's fine...
Longstory short: what ever i do in twrp doesn't work expect a wiping and reinstalling the same OctOS that worked the last 3 or 4 weeks...
What am i missing? Or is there really something wrong with my phone?
Try to flash the new TWRP, firmware.
and flash the rom with full wipe
svandasek said:
Try to flash the new TWRP, firmware.
Click to expand...
Click to collapse
TWRP is the newest, and (as already mentioned in the text) firmware was renewed during the process without any success.
What do you mean by full wipe? More than Cache, Dalvik and Data?
But still, i have the feeling, that this error is something not very common... I think i might return to complete stock, if the problems continue.
So,
i solved 2 issues ("com.android.phone has stopped" was gone after wiping system, and the updating now works smoothly after i realized that the latest firmware is 4.0.3 and not 4.0.2)
But is Still get the Welcome Screen (like i wiped the data) everytime i reboot from twrp
It is not a ROM issue, because during the provess i switched from OctOS to lineage and i still get the problem... what can that be???
Nobody got any idea?
felixburk said:
Nobody got any idea?
Click to expand...
Click to collapse
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
GrandMasterB said:
It's a TWRP and f2fs problem. You either need to change your data partition to EXT4 and/or update your TWRP to 3.0.4-1
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Click to expand...
Click to collapse
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
felixburk said:
Thanks I'll try that out.
Might it help, if i don't set a password for the phone? Or is it not encryption related?
Click to expand...
Click to collapse
It's filesystem driver related and nothing to do with the encryption.