Related
So I bought 3 Nexus 7 (2013) for Christmas and was poking around the Play Store on my desktop the other day and noticed the one on my account is not showing up on My Devices.
It's stock, not rooted. I've cleared data for play services, and everything else I've read including uninstalling and reinstalling, force closing and restarting. I've installed apps directly from the Nexus but I want to be able to install from desktop as well.
I don't want to root because my main application for this tablet is Flickster which still is @ssaholic about supporting rooted devices.
Any ideas??
Nobody has an idea how to fix this issue? It's a pain as I'm often on PC would like to just send apps to tablet while I don't have it with me.
Wipe play store data, remove all google accounts, reboot, readd account, go to play store, wait a bit, could take an hour or so to see if it shows up.
If that does not work, and you are sure you tried everything else (adding/readding accounts, wiping cache and data of everything google-related, etc), root your device (yes you will have to root, but once the process is done, you can unroot, or use the xposed module that can hide root from apps, works on flickster too), (I'd also install TWRP and do a nandroid, or if you want to keep stock recovery, you can temporarily boot into twrp and do a nandroid too) install Titanium Backup, go into backups, and backup the app called Settings Storage 4.4.2 (similarly named), that will backup or old ID, then you can go into Settings > Manage Android id > Create New Random Android ID (it will also display your current ID, you might want to jot it down just in case before hitting generate), clear play store cache and data, delete all google accounts, reboot, readd account, goto play store and see if it worked (may take some time before it syncs and shows up though).
Another sure fire way (basically does what the above does, but starts fresh just to make sure) is to make a backup of what you don't want to lose with TB (yes you will have to root, but once the process is done, you can unroot, or use the xposed module that can hide root from apps, works on flickster too), install multirom, flash a new rom to secondary (it will get a new id), login with your google account on that rom, download an app or 2, wait a bit, see if it appears on the devices list in play store. If it does, then restore your data, swap secondary with primary, wipe the old rom, profit..if you use TB to backup restore as suggested it may ask you if you want to restore the old id, say 'ask me later' until you see that everything is working, that way you can always restore the old ID if you MUST, though if everything is accessible (things you purchased are there etc) you will want to eventually select, "keep new id".
I am on lineage-14.1-20180110-nightly-hammerhead
Obviously using Nexus 5 with latest FrancoKernal & Rooted with LineageOS SU - Add on
Also Latest TWRP 3.2.1
It Passes SafeyNET.
SO
My questions are :
1> Will The Automatic Updater Delete the Data (Photos, Music, etc ) ?
2> Will It change the settings ( App defaults, Ringtones, Notification settings, etc ) ? Using Google Apps n Services.
3> Will it remove Root ?
4> Will it remove the custom Kernal ( Franco in this case ) ?
5> Will it affect the SafetyNet Status of my device ?
Please don't suggest me to try n find out for myself.
Setting up the phone from scratch is what i am actively trying to Avoid. It works perfectly as of now.
Thanks in Advance for any helpful Info.
As far I know:
0. The LOS Updater downloads just the new build and boots into your recovery where you have to flash it. (not like the stock OTA updates)
1. No. (Except the Developer says you have to wipe data obviously.)
The new build should be installed in the system partition. Your "private data" (or internal SD) are located at data/media..
2.+3. Not necessary, but its recommended (I do it every time). here more
4. I don't use a custom kernel, so I don*t know for sure, but acording to this question you have to flash the kernel again.
If you want to test a new build, just do a full backup in your recovery. Assuming that u'r using TWRP us should know that a full backup in TWRP doesn't included your internal SD! Backup it separately! here more
If you wipe your data partition your "private data" (or internal SD) should be wiped too.
A factory reset excludes this!
Hoping that i dont made any mistakes :laugh:
chrisrevoltes said:
As far I know:
0. The LOS Updater downloads just the new build and boots into your recovery where you have to flash it. (not like the stock OTA updates)
1. No. (Except the Developer says you have to wipe data obviously.)
The new build should be installed in the system partition. Your "private data" (or internal SD) are located at data/media..
2.+3. Not necessary, but its recommended (I do it every time). here more
4. I don't use a custom kernel, so I don*t know for sure, but acording to this question you have to flash the kernel again.
If you want to test a new build, just do a full backup in your recovery. Assuming that u'r using TWRP us should know that a full backup in TWRP doesn't included your internal SD! Backup it separately! here more
If you wipe your data partition your "private data" (or internal SD) should be wiped too.
A factory reset excludes this!
Hoping that i dont made any mistakes :laugh:
Click to expand...
Click to collapse
Thanks for the info
mrinal46 said:
Thanks for the info
Click to expand...
Click to collapse
0 my devices perform automatic updates in twrp.
2 your settings survive. Installed gapps survive. No need to update in twrp they are self updating
3 addonsu survives.
5 yes, in cases magisk or SuperSU get removed by the update.
This is currently how i keep my Galaxy Active 2 working - connected and Samsung Pay working - across ROM flashes without having to reset it every time, because resetting sucks
Please note: At time of writing theres no known way to keep BP Monitor calibration data (ive tried backing up and restoring the relevant database), so you will lose that
Prerequisites:
Apps:
Android ID Changer: I use this (Free) https://play.google.com/store/apps/details?id=com.silverlab.app.deviceidchanger.free
Migrate (Free Backup App) -
Main app: https://play.google.com/store/apps/details?id=balti.migrate
Flasher Module: https://play.google.com/store/apps/details?id=balti.migrate.flasher
Helper Module: https://play.google.com/store/apps/details?id=balti.migrate.helper
MyAPK: https://play.google.com/store/apps/details?id=com.andatsoft.myapk.fwa
Steps:
Install all the above on the ROM you're currently on
Use MyAPK (set MyAPK to save somewhere easily navigable) to make a backup of the following apks:
Android ID Changer
Migrate Flasher Module
Migrate Helper Module
Store them safely (i always use PC, as well as sdcard) as you'll want to use these before restoring your apps, and later to restore your apps
Important: Open Magisk Manager and set MagiskHide for all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins), you do not have to select all sub-items under the main packages, just select the main packages
To prepare for a new ROM:
This largely only has to be done once....and then reused on subsequent new ROM flashes. I do things to make life easier for myself as in a bad week i can be testing 3 ROMS...
Note: The only steps you might want to do again are make a new Migrate backup (for new apps), and backup /data/adb, if you MagiskHide further apps in future
Steps:
Run Android ID Changer, copy Android ID to a text file or email (i store mine in both)
With a root capable file manager, or in custom recovery, backup /data/adb/magisk.db to a safe place (i always use PC, as well as sdcard))
Important Note: This assumes as mentioned above you have already used Magisk Manager to MagiskHide all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins)
Backup your apps and data with Migrate
Note: for most apps you want to tick all 3 boxes per app, but DO NOTbackup up App Data (middle column for both) of:
Samsung Health
Samsung Health Monitor
As we would have to wipe this anyway after ROM flash to get them working. Save yourself the drama and untick them in Migrate. Migrate is smart enough that it stores your selections between backups, so if you make a next Migrate backup it will automatically leave these de-selected in future backups.
Your Migrate backup will be in /sdcard/Migrate, i recommend backing this up to PC as well
On the New ROM:
After a new ROM and Magisk flash:
Setup ROM
Copy Android ID changer from wherever you backed it up, install and open it, copy and paste your original Android ID into the middle (Edit) field, then click Apply
Reboot the device
Enable MagiskHide (Don't hide Magisk Manager yet)
Test for SafetyNet, and if need be use whatever method is preferred for your ROM to achieve SafetyNet
Copy magisk.db from wherever you backed it up back to device
With a root enabled file manager (or from custom recovery), copy magisk.db to /data/adb
Reboot device (Do not skip this trying to be clever)
Open Magisk Manager, it should hopefully not complain that you've just dumped magisk.db back (Note: you will not see the list of MagiskHidden apps, as they are of course not installed yet, but MagiskHide now already knows to block root detection to them when you do install them - if Samsung Pay even gets a whiff of root, it wont work and you will have to reset some, if not all Gear/Watch Plugins, and reset your watch and start from scratch)
Hide Magisk App via Magisk Manager > Settings > Hide The Magisk App, name it anything but Magisk Manager, i call mine App
Copy the following apps from wherever you backed them up to device, and install them:
Migrate Flasher Module
Migrate Helper Module
Run Migrate Flasher
Descend into the backup folder (listed by date & time), and select all the zips inside it, and flash them (Of course if you moved Migrate folder off the device, restore it to /sdcard first)
At the end open Migrate Helper (which is already installed) and restore all the apps you wish - of course for our purposes, we want all the Samsung ones.... Note: Migrate will automatically select all backed up apps and data
At the finish of Migrate restore, leave the default options selected, which will remove the Migrate Helper, and reboot
On phone, open Gear App and press Connect
On watch, you may need to toggle BlueTooth off, and back on
You may need scan a few times and perhaps toggle bluetooth off and on, but it will give you the usual pairing prompt, both on the phone, and the watch, pair, and shortly you will have the watch reconnected, and Samsung Pay intactNext steps:
Open Samsung Health and sign in and restore
Open Samsung Health Monitor, and sign in
Set up ECG as normal
Re-Calibrate the Blood pressure monitor as normal
On any new ROM from now on, you can:
Make a new Migrate Backup, to include any new apps
Make a backup of /data/adb/magisk.db if you MagiskHide any new apps
Then refer to the On The New ROM steps above....
Please let me know if you find an error or issue folks
73sydney said:
This is currently how i keep my Galaxy Active 2 working - connected and Samsung Pay working - across ROM flashes without having to reset it every time, because resetting sucks
Please note: At time of writing theres no known way to keep BP Monitor calibration data (ive tried backing up and restoring the relevant database), so you will lose that
Prerequisites:
Apps:
Android ID Changer: I use this (Free) https://play.google.com/store/apps/details?id=com.silverlab.app.deviceidchanger.free
Migrate (Free Backup App) -
Main app: https://play.google.com/store/apps/details?id=balti.migrate
Flasher Module: https://play.google.com/store/apps/details?id=balti.migrate.flasher
Helper Module: https://play.google.com/store/apps/details?id=balti.migrate.helper
MyAPK: https://play.google.com/store/apps/details?id=com.andatsoft.myapk.fwa
Steps:
Install all the above on the ROM you're currently on
Use MyAPK (set MyAPK to save somewhere easily navigable) to make a backup of the following apks:
Android ID Changer
Migrate Flasher Module
Migrate Helper Module
Store them safely (i always use PC, as well as sdcard) as you'll want to use these before restoring your apps, and later to restore your apps
Important: Open Magisk Manager and set MagiskHide for all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins), you do not have to select all sub-items under the main packages, just select the main packages
To prepare for a new ROM:
This largely only has to be done once....and then reused on subsequent new ROM flashes. I do things to make life easier for myself as in a bad week i can be testing 3 ROMS...
Note: The only steps you might want to do again are make a new Migrate backup (for new apps), and backup /data/adb, if you MagiskHide further apps in future
Steps:
Run Android ID Changer, copy Android ID to a text file or email (i store mine in both)
With a root capable file manager, or in custom recovery, backup /data/adb/magisk.db to a safe place (i always use PC, as well as sdcard))
Important Note: This assumes as mentioned above you have already used Magisk Manager to MagiskHide all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins)
Backup your apps and data with Migrate
Note: for most apps you want to tick all 3 boxes per app, but DO NOTbackup up App Data (middle column for both) of:
Samsung Health
Samsung Health Monitor
As we would have to wipe this anyway after ROM flash to get them working. Save yourself the drama and untick them in Migrate. Migrate is smart enough that it stores your selections between backups, so if you make a next Migrate backup it will automatically leave these de-selected in future backups.
Your Migrate backup will be in /sdcard/Migrate, i recommend backing this up to PC as well
On the New ROM:
After a new ROM and Magisk flash:
Setup ROM
Copy Android ID changer from wherever you backed it up, install and open it, copy and paste your original Android ID into the middle (Edit) field, then click Apply
Reboot the device
Enable MagiskHide (Don't hide Magisk Manager yet)
Test for SafetyNet, and if need be use whatever method is preferred for your ROM to achieve SafetyNet
Copy magisk.db from wherever you backed it up back to device
With a root enabled file manager (or from custom recovery), copy magisk.db to /data/adb
Reboot device (Do not skip this trying to be clever)
Open Magisk Manager, it should hopefully not complain that you've just dumped magisk.db back (Note: you will not see the list of MagiskHidden apps, as they are of course not installed yet, but MagiskHide now already knows to block root detection to them when you do install them - if Samsung Pay even gets a whiff of root, it wont work and you will have to reset some, if not all Gear/Watch Plugins, and reset your watch and start from scratch)
Hide Magisk App via Magisk Manager > Settings > Hide The Magisk App, name it anything but Magisk Manager, i call mine App
Copy the following apps from wherever you backed them up to device, and install them:
Migrate Flasher Module
Migrate Helper Module
Run Migrate Flasher
Descend into the backup folder (listed by date & time), and select all the zips inside it, and flash them (Of course if you moved Migrate folder off the device, restore it to /sdcard first)
At the end open Migrate Helper (which is already installed) and restore all the apps you wish - of course for our purposes, we want all the Samsung ones.... Note: Migrate will automatically select all backed up apps and data
At the finish of Migrate restore, leave the default options selected, which will remove the Migrate Helper, and reboot
On phone, open Gear App and press Connect
On watch, you may need to toggle BlueTooth off, and back on
You may need scan a few times and perhaps toggle bluetooth off and on, but it will give you the usual pairing prompt, both on the phone, and the watch, pair, and shortly you will have the watch reconnected, and Samsung Pay intactNext steps:
Open Samsung Health and sign in and restore
Open Samsung Health Monitor, and sign in
Set up ECG as normal
Re-Calibrate the Blood pressure monitor as normal
On any new ROM from now on, you can:
Make a new Migrate Backup, to include any new apps
Make a backup of /data/adb/magisk.db if you MagiskHide any new apps
Then refer to the On The New ROM steps above....
Please let me know if you find an error or issue folks
Click to expand...
Click to collapse
My God! That's a lot of steps.
But you've written them down quite clearly.
This will certainly be helpful for those that like to flash ROMs frequently but don't want the hassle of setting up the watch again everytime you flash a new ROM on the phone. And of course, keeping Samsung Pay working successfully with root, while jumping across ROMs is quite impressive.
enigmaamit said:
My God! That's a lot of steps.
But you've written them down quite clearly.
This will certainly be helpful for those that like to flash ROMs frequently but don't want the hassle of setting up the watch again everytime you flash a new ROM on the phone. And of course, keeping Samsung Pay working successfully with root, while jumping across ROMs is quite impressive.
Click to expand...
Click to collapse
Once you have it set up the process is rather simple and i did have some help with the suggestion it might be tied to the Android ID....so i have to give @Dante63 some credit here (https://forum.xda-developers.com/t/galaxy-watch-features-ecg-bp.4051141/post-84652975)
Hehe If you want to see steps, and lots of words, visit the "My Magisk method for Google Pay SQLite Fix (Tested On P/Q/R)" link in my signature
Luckily at the moment that module isnt needed, but it had its fair share of downloads (23,000+) until recently when Google changed something on the backend again, and you can use Google Pay without it on a rooted device
Honest question: is SHealth so retarded that it doesn't save any backup in cloud, so that it could be restored afterwards?
w41ru5 said:
Honest question: is SHealth so retarded that it doesn't save any backup in cloud, so that it could be restored afterwards?
Click to expand...
Click to collapse
Samsung Health Does - All your steps etc are safe and can be restored after signing back in
Samsung Health Monitor (which calibrates and tests ECG/BP) does not.....
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Sqorpz said:
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Click to expand...
Click to collapse
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
If your device boots back to TWRP, it might be triggering Rescue Party. (click the 3rd button on the bottom of the screen to view the logs)
Fytdyh said:
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
Click to expand...
Click to collapse
I had installed twrp like this before and never had this type of error. But yes, the smart thing would definately be to always have backups. Lesson learned for next time!
Canny1913 said:
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
Click to expand...
Click to collapse
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Sqorpz said:
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Click to expand...
Click to collapse
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Canny1913 said:
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Click to expand...
Click to collapse
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Sqorpz said:
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Click to expand...
Click to collapse
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
T
Canny1913 said:
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
Click to expand...
Click to collapse
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Sqorpz said:
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Click to expand...
Click to collapse
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Canny1913 said:
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Click to expand...
Click to collapse
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Sqorpz said:
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Click to expand...
Click to collapse
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Canny1913 said:
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Click to expand...
Click to collapse
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Sqorpz said:
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Click to expand...
Click to collapse
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Canny1913 said:
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Click to expand...
Click to collapse
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Sqorpz said:
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Click to expand...
Click to collapse
Google One app can backup photos,SMS, phone call history and redownloads all of the apps (except apps that were installed from an apk file)
Pixel Experience actually bypasses the Google Photos storage limit so you can backup your entire gallery without problems.
For notes just use Google Keep, it syncs the notes to your Google account.
App data can be backed up by Titanium Backup or Migrate. (i suggest you test them before backing up your entire app data as suggested by Migrate developer)
I don't exactly recommend backing up Data as a whole since your only option is TWRP and TWRP loves to complain when it comes to backing up and restoring.
Thanks for the best wishes and i wish you all the best too. Have a good one.
Everytime I have to change my rom, My apks , music, books get wiped. Is there a possibiltiy to not wipe internal storage, just format , like it used to happen on a only devices?
Switching roms would require you to wipe, you may use some software to backup and restore your apps if you have root access. I don't flash roms now, but when I use to I used Titanium Backup for this, you can try it if it still works.
The OxygenOS @Funk Wizard? Lol
Bupreno said:
Everytime I have to change my rom, My apks , music, books get wiped. Is there a possibiltiy to not wipe internal storage, just format , like it used to happen on a only devices?
Click to expand...
Click to collapse
If you are going between custom ROMs of the same base version (meaning they all use the same OOS base like C.62), you do not have to do the wipe operation and can just dirty flash, but it's highly recommended to do a wipe so you don't have weird issues. If you do decide to dirty flash, at least do the dev the courtesy of holding off any bug reports until after you factory reset because if you have a weird problem nobody else is reporting, there's a pretty good chance it's because you dirty flashed.
If you're going between stock ROMs, that's a bit more complicated. I have successfully used Fastboot Enhance to upgrade, downgrade, and crossflash between different versions and it generally works as long as I'm not trying to downgrade or upgrade between Android 11 and 12 and I make sure to delete all the cow partitions in the partition screen before starting the flash. Trying to go from ColorOS 13 beta back to C.62 didn't work either but I have flashed between various C builds of OOS for different regions as well as ColorOS 12.1 and they've all worked.
That said, you should always do a full backup because things do go wrong. I have done it so many times on this phone that I have it down to a science now. I hook my phone up and use adb pull -a /sdcard to grab everything, do a system backup to Google Drive using the backup option in settings, back up my Signal messages, and when I'm on a stock ROM, I use the OnePlus backup to grab all my apps and settings. When I restore, I skip the initial Google account setup, I delete the Android folder from the adb pull folder and drag and drop the rest of it to the root of the storage, then I use the OnePlus backup to restore (if it's a stock ROM), then I log into my Google account and run that restore and the rest of the setup process, then I restore my Signal messages. Doing it in this order, I end up with the least amount of data loss. I don't even have to reconfigure my battery settings for my apps on the stock ROM doing it this way, it's all carried over, which saves me about 15 minutes of turning off optimizations for everything so my notifications work right.