Related
Hallo,
i have a problem with updating cm 10.1 to 10.2 on my i9000. Like i say, i had allready cm 10.1 and prior to that 10.0 and helly bean. Till now everything was fine and every update was OK. I have allready root rights.
Now i tried to flash cm 10.2 like that;
1.
wipe data/factory reset
wipe cache partition
wipe dalvic cache
- flash cm-10.2-20130824-NIGHTLY-galaxysmtd.zip - 2 times
- flash gapps 10.2.x 20130813
- reboot system now
After reboot, i'm in the welcome modus - i choose German - then start - then i can choose the connection WLAN or skip with data. In this part i get allready an error massage "com.google.android.gsf.login" and "unfurnatly google account manager was shut down". After that i'm back again in the choose-connection area. After chosing WLAN or skip and use data, i always get the above mentioned message.
Restore 10.1 again
2.
like above, but extra mounts and storage - format /system
- Result like 1
3.
Just update from 10.1 to 10.2 with CWM, without wipe data/factory reset - wipe cache partition - wipe dalvic cache.
- Result 4.3 is on my mobile, but there ist still the error massage from above.
4.
like 3, but i deleted the Google account in 10.1. Just uodated to 10.2 without wiping.
- Result -> no error massages, but i can't add google account. I clik on add account - google -> but nothing happen.
I don't know what to do. Do somebody have any idea? Where is my oult?
one-dimon said:
wipe data/factory reset
wipe cache partition
wipe dalvic cache
- flash cm-10.2-20130824-NIGHTLY-galaxysmtd.zip - 2 times
- flash gapps 10.2.x 20130813
- reboot system now
Where is my foult?
Click to expand...
Click to collapse
Your foult is that you didn't read pawitp's opening post carefully. All steps untill gapps were fine, then after gapps you should have remained in CWM recovery and go to advanced restore and restore your /data from last nandroid backup from cm10.1, it works perfectly well.
I would advice you not to install 20130824 build anymore as it has some serious bugs (I run it in my i9000 and it works perfectly fine but some people had total re-formatting ofntheninternal SD card and data lost) but wait now for just short, any moment nightly 20130827 will be uploaded. The bugs are fixed there.
Then you can repeat proceeding once again as above and accomplish with /data restore. Then it should work fine again
Ok, i try it
Last question before i try, i have to restore just /data, wich backup do i have to do, full backup or just /data?
Thanx a lot
one-dimon said:
Last question before i try, i have to restore just /data, wich backup do i have to do, full backup or just /data?
Click to expand...
Click to collapse
OK, now the new nightly build is there, CM10.2 20130827
Do all your steps as above (download zip, go to recovery mode, wipe data/factory reset, wipe cache, wipe dalvik cache under "advanced", install 20130827 zip, stop here) now new:
if your last installed build is 10.2 you have already installed gapps for CM10.2 so you can skip re-installing them again
now go to "advanced restore" and choose your last nandroid backup of the CM10.1, where your google account was still working fine
choose now from your last nandroid file the option: "restore /data"
after restore is finished go back to main menu and reboot the system
Unless if you have formatted your SD card meanwhile, all your data will be back like they were in the CM10.1 (also your google account) and your new CM10.2 will work fine.
For thanking, it is common in this forum to click on "thanks" button left beyond all the posts which you find to be helpful
Hy, i tried what you said. I restored 10.1 before it
*
wipe data / factory reset - wipe cache - advanced .. wipe dalvic cache*- install 10.2
then - flash gapps for 10.2
then - restore just data
reboot system
*
4.3 is on my mobile, google account seems to be OK. But then i recognized, that my Contacts, Keep, Google+ and some other points doesn't synchronize. I've tried flash gapps again, then restore data -> error massage "google account closed"
*
My next step was to do above mentioned again - same error massage
*
So, i do it again. After wipe data / factory reset - wipe cache a.s.o. i had a look in my storage/sdcard0. It was full of old data, so i extra formated /system and formated /storage/sdcard0. After that i flashed 10.2 and gapps again and restored data. I receive the same sh.. error again and google account doesn't work.
*
Now i restored 10.1 again completely
*
Any idea?
one-dimon said:
....Now i restored 10.1 again completely....
Click to expand...
Click to collapse
Did you enable contacts sync in your accounts? Other thing you can do is to export all your contacts (in "people" ) as vfc data and after the upgrade import it from your SD card. I did that as I don't like google sync functions (for having few accounts) so I only enabled sync for the apps.
Other great thing is to use free app "SMS backup&restore" and "Call logs backup&restore" (by the same developer) from play store. The apps work for any android version and backup data is compatible to restore as well
Try to post in the development thread of nightly cm10.2 for i9000 or read through, I think also somebody else reported problems with google account, maybe it is solved why it happened.
BTW: for next flashing don't use nightly 20130827 anymore as the new 20130828 is out and it has many bug fixes
______________________________________
Sent from GT-P5110 powered by CM 10.2
Hy, i'm again. I try it with the newest cm, with the same result. I flashed exactly like the developer said. No error message, but play store, contacts and some other things don't work.
I would like to post in the development Center, but I am a to young forum member.
Maybe you could post for me my problem or the link to this posts?
one-dimon said:
Hy, i'm again. I try it with the newest cm, with the same result. I flashed exactly like the developer said. No error message, but play store, contacts and some other things don't work.
I would like to post in the development Center, but I am a to young forum member.
Maybe you could post for me my problem or the link to this posts?
Click to expand...
Click to collapse
Just one question: did you flash the gapps for 4.3 as well? Developer pawitp is a genious person and he doesn't mention it anymore in his first posts (he thinks that everybody knows it.....)
If you didn't, you can do it later as well, just download them and install zip in recovery mode..... Sorry if it doesn't work. Then would be better to wait untilmstable version is released. CM 10.2 works in my i9000 amazing, but another people report bugs.
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
*
Could you*post a question fpr me in the developement thread if this problem is known to the developers and if they have a resolution? Maybe they are allready working on it and solve the problem in next nightlys?
one-dimon said:
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
Click to expand...
Click to collapse
No, mate, if you meant CWM recovery. I would also use Titanium backup app for that, there can't go so wrong.
Could you*post a question fpr me in the developement thread if this problem is known to the developers and if they have a resolution? Maybe they are allready working on it and solve the problem in next nightlys?
Click to expand...
Click to collapse
you have no idea how little free time I have. But you're already on 5 posts, just five more and you will be able to post the questions in development threads. It is anyway better that you describe what the problem is. I think I saw in CM10.2 thread yesterday that the developer pawitp works on that.
EDIT: BTW, restoring /data from nandroid backup made with CM10.1x under CWM recovery -->advanced restore is possible without problems. But I think we have mentioned that already in last posts...
OK, I can understand you.
What do I have to do first: flash gapps or restore /data?
have you checked that dataprotection for these apps is not enabled?
one-dimon said:
OK, I can understand you.
What do I have to do first: flash gapps or restore /data?
Click to expand...
Click to collapse
I've posted your question and left link to this thread in the CM10.2 development topic. Hope somebody will answer soon.
If your Google account worked well in CM10.1x, I would say you should try this way:
download the newest CM10.2 nightly zip (20130830) directly here: http://get.cm/get/amd
download Google Apps zip for Android 4.3
run CWM recovery mode
try option "install zip" and don't install yet, just check if your zip files are visible for the CWM recovery in the folder where you saved them
return to main menu and wipe data/factory reset
wipe cache
wipe dalvik cache under "advanced"
install zip CM10.2 nightly
install GApps for 4.3
go to "advanced restore" and choose your last nandroid backup file made by CM10.1 build where your Google account worked well
now choose (from that nandroid backup file) the option "restore /data"
after your data are restored, go back to the main menu and reboot the system
Let me know if it worked. Please quote at least little bit of my text (click "reply" beyond my post) so I will get the notification that you've quoted me, otherwise I don't see when you answer
p.s. good point by @Marvi70 just one post before (this one) mine
Marvi70 said:
have you checked that dataprotection for these apps is not enabled?
Click to expand...
Click to collapse
What do you mean? How can I check it?
one-dimon said:
What do you mean? How can I check it?
Click to expand...
Click to collapse
in settings -> apps, in the app property of those apps check if dataprotection is enabled (no access to private data). When yes disable it.
Marvi70 said:
Datatings -> apps, in the app property of those apps check if dataprotection is enabled (no access to private data). When yes disable it.
Click to expand...
Click to collapse
OK, I checked all apps, also system apps. Data protection is disabled everywhere.
tetakpatak said:
I've posted your question and left link to this thread in the CM10.2 development topic. Hope somebody will answer soon.
If your Google account worked well in CM10.1x, I would say you should try this way:
download the newest CM10.2 nightly zip (20130830) directly here: http://get.cm/get/amd
download Google Apps zip for Android 4.3
run CWM recovery mode
try option "install zip" and don't install yet, just check if your zip files are visible for the CWM recovery in the folder where you saved them
return to main menu and wipe data/factory reset
wipe cache
wipe dalvik cache under "advanced"
install zip CM10.2 nightly
install GApps for 4.3
go to "advanced restore" and choose your last nandroid backup file made by CM10.1 build where your Google account worked well
now choose (from that nandroid backup file) the option "restore /data"
after your data are restored, go back to the main menu and reboot the system
Let me know if it worked. Please quote at least little bit of my text (click "reply" beyond my post) so I will get the notification that you've quoted me, otherwise I don't see when you answer
p.s. good point by @Marvi70 just one post before (this one) mine
Click to expand...
Click to collapse
Hy, i'm again. I've just tested to flash another ROM. It was slimbean. Everything works fine, there are no problems with gapps. I thing there is a bug in cm 10.2.
one-dimon said:
Hy, i'm again. I've just tested to flash another ROM. It was slimbean. Everything works fine, there are no problems with gapps. I thing there is a bug in cm 10.2.
Click to expand...
Click to collapse
Good to know, thanks for info! Congratulations also CM10.2 will soon be cool, the devs are now fixing the bugs on daily basis
tetakpatak said:
Good to know, thanks for info! Congratulations also CM10.2 will soon be cool, the devs are now fixing the bugs on daily basis
Click to expand...
Click to collapse
I hope so, i allready use cm a long time and i was a happy user till 10.1. I think if my prob. will be fixed, i'll switch to cm again
one-dimon said:
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
Click to expand...
Click to collapse
BTW, after your post about Titanium Backup I've tried indeed to restore data only from my old backup of Angry Birds app, it went perfectly well
Backup file was done with rooted Froyo 2.2 and restored in CyanogenMod 10.2
Before importing the data saved in different ROM, I used the settings exactly like described on the website of Titanium. I've checked again CM development posts about Titanium backup and they talk indeed about the one shouldn't restore whole apps.... but data only seems not to be a problem!
Big thanks, mate!
F2fs for zuk z1 is here.
This mod works only on cm 14.1 based roms.
The below file contains patched fstab.qcom so you can convert /data and /cache partition to f2fs.
Warning!!!!!!!
Converting /data to f2fs will wipe out entire data partition.
Make sure to backup your entire internal storage partition.
Me or xda will not be held responsible for any of your loss after proceeding with the below instructions.
Requirements:-
1) A rom based on cm 14.1 running Radioactive-kernel 3.20
2) Zuk z1
3)make sure you are on the stock boot image of your rom. If you flashed supersu, restore back to original boot image or dirty flash your rom
4) Proceeding with below instructions will reset your device. Make sure to keep rom zips on pc and backup internal storage.
I can't make it more clear that I'll not be held responsible for the losses due to hou not reading the entire instructions properly.
Instructions :-
1) Download the kernel attached below.
2) Download TWRP (Official 3.1.0-0) and flash it
3) Install the kernel zip i provided.
4) If you want to change only Cache partition to f2fs, boot into twrp, go to wipe, select advanced wipe, select Cache, change fs, select f2fs, swipe to confirm.The rom will be compatible with both ext4 (existing) and f2fs. So you can choose if you want only cache partition or both cache and data
5) If you want to convert data partition, boot to twrp, go to wipe, select advanced, wipe select data, change fs, select f2fs.
6) if you want supersu, make sure to flash it after flashing this kernel. Else your device might bootloop.
Enjoy faster read and write speeds.
Credits :-
All the devs on xda,
Especially @acuicultor and @OrdenKrieger who brought nougat to this device Nd team nuclear
i forgot from where I edited the fstab.
Plz pm me if i forgot anyone's name
Edit :-
Source code
https://github.com/Yrahate7/Radioactive-kernel-HAM
ADDICTEDYASH said:
F2fs for zuk z1 is here.
This mod works only on cm 14.1 based roms.
The below file contains patched fstab.qcom so you can convert /data and /cache partition to f2fs.
Warning!!!!!!!
Converting /data to f2fs will wipe out entire data partition.
Make sure to backup your entire internal storage partition.
Me or xda will not be held responsible for any of your loss after proceeding with the below instructions.
Requirements:-
1) A rom based om cm 14.1 running Radioactive-kernel 3.20
2) Zuk z1 [emoji14]
3)make sure you are on the stock boot image of your rom. If you flashed supersu, restore back to original boot image or dirty flash your rom
4) Proceeding with below instructions will reset your device. Make sure to keep rom zips on pc and backup internal storage.
I can't make it more clear that I'll not be held responsible for the losses due to hou not reading the entire instructions properly.
Instructions :-
1) Download the kernel attached below.
2) Download TWRP (Official 3.1.0-0) and flash it
3) Install the kernel zip i provided.
4) If you want to change only Cache partition to f2fs, boot into twrp, go to wipe, select advanced wipe, select Cache, change fs, select f2fs, swipe to confirm.The rom will be compatible with both ext4 (existing) and f2fs. So you can choose if you want only cache partition or both cache and data
5) If you want to convert data partition, boot to twrp, go to wipe, select advanced, wipe select data, change fs, select f2fs.
6) if you want supersu, make sure to flash it after flashing this kernel. Else your device might bootloop.
Enjoy faster read and write speeds.
Credits :-
All the devs on xda
Click to expand...
Click to collapse
Mate why you open a thread with Radioactive kernel on tittle? Also why you used my kernel without asking permission first? You should make a flashable zip with the modded fstab without my kernel inside. Please do it that way or i will report.
Sent from my Nuclear OnePlus3T
acuicultor said:
Mate why you open a thread with Radioactive kernel on tittle? Also why you used my kernel without asking permission first? You should make a flashable zip with the modded fstab without my kernel inside. Please do it that way or i will report.
Click to expand...
Click to collapse
Sorry man.
I wanted to make sure that you read it.
I'll change it right away.
And regarding the kernel, I've compiled my own kernel based on your source. It has a few mods which u didn't include.
Currently i didn't have a name. So much sorry about it. I i havent uploaded the source as i didn't have any new name.
ADDICTEDYASH said:
Sorry man.
I wanted to make sure that you read it.
I'll change it right away.
And regarding the kernel, I've compiled my own kernel based on your source. It has a few mods which u didn't include.
Currently i didn't have a name. So much sorry about it. I i havent uploaded the source as i didn't have any new name.
Click to expand...
Click to collapse
You know that you are breaking gpl? And why your zip looks exactly same like mine? I can help you if you need just pm me.
Sent from my Nuclear OnePlus3T
acuicultor said:
You know that you are breaking gpl? And why your zip looks exactly same like mine? I can help you if you need just pm me.
Click to expand...
Click to collapse
Yes i know that. But currently i don't have enough internet plan to upload it. I'll upload it asap as my exams are over. I. E. After 12th may
ADDICTEDYASH said:
Yes i know that. But currently i don't have enough internet plan to upload it. I'll upload it asap as my exams are over. I. E. After 12th may
Click to expand...
Click to collapse
You made a fork of Radioactive kernel, right? Then push to github your commits, that's not a lot of data consuming,then share the link here.
Sent from my Nuclear OnePlus3T
This thread is a clear violation of the GPL.
Please upload the source and contact me. I will re-open it then.
As for now thread closed.
Edit: Thread re-opened.
What is 12gb of "other" storage data that I can not seem to find [OP3T, 128GB]
Hello,
I just reflashed OxygenOS from Paranoid android after a clean wipe of data, system, cache etc. After set up, I realised there is 12gb of data being occupied under the "other" storage. I proceeded to factory wipe as well and I still have this 12gb of data.
I can not seem to figure out what this 12gb of data is. It is not the oem_logs. I do not have nandroid back ups. I do have around 4gb of titanium backup that I can account for. That means there is still 7gb of data that I can not seem to find.
Any help with figuring this out?
The only thing I could think of now was to wipe internal memory and flash the rom all over. Is that possible? I heard that wiping internal memory is a no no.
I have included some screenshots. If anyone needs more information, please ask.
(The massive app data is because this morning I finally gave in and redownloaded my spotify playlists. Spent 2 days trying to figure out this damn 12gb other data...)
Edit: Forgot to mention, I am on the latest OxygenOS stable. Rooted with latest Magisk and using TWRP 3.1.1-2
An update
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.
Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.
Any apk files you've downloaded, logs you've recorded all in that category. Even large flashable zip files and other firmware files are also under that category.
EatDahPewPew said:
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.
Click to expand...
Click to collapse
Twrp backups
If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.
Mr.RooT said:
Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.
Click to expand...
Click to collapse
Hey, Do you know what exactly I am looking for in there?
vighneshpillai90 said:
If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.
Click to expand...
Click to collapse
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?
EatDahPewPew said:
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?
Click to expand...
Click to collapse
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.
vighneshpillai90 said:
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.
Click to expand...
Click to collapse
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.
EatDahPewPew said:
Hey, Do you know what exactly I am looking for in there?
Click to expand...
Click to collapse
Every folder except emulated directory. Firstly I thought that these other folders are links to their original location, but when I deleted that folders, original folders weren't affected. But delete it at your own risk! It could be coincidence, that these folders weren't linked to original ones.
EatDahPewPew said:
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.
Click to expand...
Click to collapse
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:
vighneshpillai90 said:
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:
Click to expand...
Click to collapse
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.
other than media files and unrecognized file extension
like .zip .apk .flac and etc
EatDahPewPew said:
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.
Click to expand...
Click to collapse
Open the Blu-Spark thread, go to downloads, keep scrolling and you find the twrp among the kernels listed there (Latest is v8.52).
Hi to all!
It seems custom ROMs are not supports encryption of user data... Why?
After stock MIUI on Xiaomi Redmi 4X I try sevral custom ROMS, and from all of it I cannot encrypt user data partition.
Custom ROMs are (all latest official): Resurrection Remix, AOSP Extended and LineageOS 14.
My steps:
0) flash phone with stock recovery via MiFlash (to restore "innocent state");
1) install latest TWRP (v3.1.1);
2) wipe all partotions except SD card and insstall custom ROM from SD card;
3) new system initial setup without "ask password on boot";
4) go to Settings -> Security -> Encrypt User Data;
Phone performs reboot and data still not encrypted.
All three custom ROMs behave the same at this point.
If perform initial setup with "boot password prompt", user data is whown as encrypted in Security settings, but TWRP still not asks password on booting to recovery mode. And I can unpack backup archive produced by TWRP (it seems not encrypted).
So, my question: if I not produce mistake, it seems custom ROMs are not friendly with data encryption, why? And is it possible to fix it?
p.s.
Also I try to erase data with "fastboot format userdata" and configure phone again. It not helps to solve problem.
Hi. Perhaps anybody can bring some light into this encryption issues?
My situation is a little different:
I installed LineageOS 14.1 from TingyiChen. But did not format /data. So it is still encrypted. I did not try to restore an backup from data within twrp yet. But I have read that there can occure problems?
The official version of twrp (3.2.1.0) is not able to decrypt /data. But there is an inofficial version (3.1.1) that works with encrypted data? Please tell me what's the difference? Is it only the switch "TARGET_HW_DISK_ENCRYPTION "? Why did TingChen remove encryption feature two weeks ago in his github repo (Sorry, I'm not allowed to post links yet)?
Fingerprint unlock is not working after reboot anymore. I have read that this also is because of encrypted data. partition. Please tell me what's the problem here or point me to a thread which covers this topic. I was unable to find one yet.
If I do a backup of my data partition in twrp and format it to disable encryption. Can I then restore this backup or what do I need to do for disabling encryption without loosing my data?
Thank you for your answers.
Regards,
Oliver
olistudent said:
Hi. Perhaps anybody can bring some light into this encryption issues?
My situation is a little different:
I installed LineageOS 14.1 from TingyiChen. But did not format /data. So it is still encrypted. I did not try to restore an backup from data within twrp yet. But I have read that there can occure problems?
The official version of twrp (3.2.1.0) is not able to decrypt /data. But there is an inofficial version (3.1.1) that works with encrypted data? Please tell me what's the difference? Is it only the switch "TARGET_HW_DISK_ENCRYPTION "? Why did TingChen remove encryption feature two weeks ago in his github repo (Sorry, I'm not allowed to post links yet)?
Fingerprint unlock is not working after reboot anymore. I have read that this also is because of encrypted data. partition. Please tell me what's the problem here or point me to a thread which covers this topic. I was unable to find one yet.
If I do a backup of my data partition in twrp and format it to disable encryption. Can I then restore this backup or what do I need to do for disabling encryption without loosing my data?
Thank you for your answers.
Regards,
Oliver
Click to expand...
Click to collapse
Wipe Internal Data & perform Clean flash, you will have to dothis everytine you flash ROM. Some says Custom TWRP (redwolf port) Have solved the issue, but Better wipe Internal everytime you flash a ROM
---------- Post added at 08:10 PM ---------- Previous post was at 08:06 PM ----------
it's very easy for anyone with just a little bit of knowledge to get around any kind of security that TWRP might have. All they have to do is flash one of the other recoveries that's available that doesn't have password protection to get around it. You can Still flash a Custom Recovery by PC without prompting a pass again. And you're Internal is already Encrypted. Stay at MIUI with Unlocked bootloader if you're too much concerned with the security.... But an expert will use test points to Unlock that too...
We all know flashing ROMs got a lot more complicated with the advent of A/B partitions.
This is not my work, the aim here is only to highlight a process which simplifies the task.
Original post on the OnePlus 6 forum can be found here:
https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
It makes use of a script which copies the flashed firmware to both slots without having to reboot recovery and do it a second time. Also by not having to reboot recovery you avoid the issue where internal storage becomes unreadable.
Credit for this goes to:
LineageOS @erfanoabdi @filipepferraz @Prakyy @drpradsms
Download by prakky (hit the thanks button on his post below):
https://androidfilehost.com/?fid=8889791610682890605
The following posts detail it's usage which you follow at your own risk.
Clean Flashing a new ROM
Disable lockscreen security
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Format data; type 'yes' (backup as this wipes phone)
6) Boot System
Reboot recovery to flash additional zips.
Updating OOS base whilst on a custom ROM
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Boot System
Reboot recovery to flash additional zips.
Updating a custom ROM (nothing fancy here)
Boot TWRP 3.4+
1) Flash ROM
2) Flash TWRP installer
3) Boot System
Reboot recovery to flash additional zips.
Reverting to OOS
WARNING I've yet to test this!
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash Finalize.zip
3) Format data; type 'yes' (backup as this wipes phone)
4) Boot System
Note: this will revert you to stock recovery as well.
Tip:
Chain install the zips by selecting 'Add more Zips' after selecting the first zip.
Only 'Swipe to confirm Flash' once all zips have been queued.
I recommend numbering the zips in the order they need flashed.
Note: this issue is now resolved as of 09/08/20 as per https://forum.xda-developers.com/oneplus-6t/how-to/guide-rom-flashing-easy-t4143701/post83241857
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Deleted. Think maybe I'm getting altimeters. ?
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Edited first post to make it clearer this is your work.
mitchst2 said:
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Click to expand...
Click to collapse
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Prakyy said:
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Click to expand...
Click to collapse
Good question.
Is 'Android Development and Hacking / General' the right place? There are some all device guides with a lot of views in there.
https://forum.xda-developers.com/android/general
mitchst2 said:
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Click to expand...
Click to collapse
As of 09/08/20 build and this commit all is well with OMNI and TWRP again. No need to edit the ROM zip anymore.
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
brajesh.sharma87 said:
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
Click to expand...
Click to collapse
No when switching ROM formatting data will be necessary. Not used it myself but others recommend Migrate to restore apps and data.
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
brajesh.sharma87 said:
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
Click to expand...
Click to collapse
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
flash713 said:
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
Click to expand...
Click to collapse
I had to mandatory format data when I wanted to move from evolution x to aospa.
brajesh.sharma87 said:
I had to mandatory format data when I wanted to move from evolution x to aospa.
Click to expand...
Click to collapse
And I've also had to format data before as well but not lately. Could it be because I format both slots coming from OOS or because I use Canary Magisk or the recovery I use.. No idea but next time you are on EvoX backup system, data and boot and try and restore it using that recovery that comes with EvoX and see what happens. These last few weeks I've stayed on AOSiP and PixeN and I flashed Omni once I think but restoring from AOSPA to Pixen was flawless for me and also restoring Pixen to Pixen was also fine, which I do because I always mess around with sound mods.... I'm on AOSiP now and soon as I get more charge on my phone I'm going to try and restore to something I have a backup already made on one of my USB drives and I'll edit this post and report what the outcome is...