Today I flashed a rom and before rebooting, I wiped "internal storage" aka sdcard in twrp to get a completely clean start. After installing a few apps I noticed that the data in sdcard/android/obb and/or data/media/obb was not wiped. Is that a bug in twrp? Is it intended and if so, why? Are those file paths the same? Running latest twrp and cataclysm rom.
Related
So earlier today I was flashing my phone from a TW based rom over to a Android Open Source Project Rom, AOSP. And once booting after wiping multiple times and dalvik + Cache wipes, installed and opened to have no radio working. Also my internal storage was modded by the rom so it was in a "Emulated" folder and I have lost my backups... Any idea how to fix other than reverting to stock?
Hello I am having a problem with restoring backups from clockworkmod recovery. I am using Philz Touch recovery based on cwm 6.0.4.5. I was also having the same problem in the official cwm 6.0.4.5 recovery. What happens is that when I go to restore a recovery everything is fine until the data restoring part comes up. It starts restoring the data and then an error pops up and it stops restoring. I have tried restoring new backups from an android 4.3 and 4.4 rom and they both fail at restoring the data. What can I do to fix this? I am stumped.
jonny30bass said:
Hello I am having a problem with restoring backups from clockworkmod recovery. I am using Philz Touch recovery based on cwm 6.0.4.5. I was also having the same problem in the official cwm 6.0.4.5 recovery. What happens is that when I go to restore a recovery everything is fine until the data restoring part comes up. It starts restoring the data and then an error pops up and it stops restoring. I have tried restoring new backups from an android 4.3 and 4.4 rom and they both fail at restoring the data. What can I do to fix this? I am stumped.
Click to expand...
Click to collapse
Try to wipe system/data/cache/dalvik cache, then do format, after that make sure your storage are mounted then try restore again.
buhohitr said:
Try to wipe system/data/cache/dalvik cache, then do format, after that make sure your storage are mounted then try restore again.
Click to expand...
Click to collapse
It worked! First, I wiped everything, which I had been doing all along. Then I went to "Mounts and Storage" and formatted everything except for my external SD card (I feel like the last option in there that said "format /data and /data/media (/sdcard)" is what fixed my issue). Then I mounted /data and /storage/sdcard1. Then, I installed a new rom and made a backup to my external SD card instead of my internal SD card. Then I rebooted into system, and then I rebooted back to recovery and wiped everything to restored my backup from my external SD card. The restore actually worked and didn't give me an error when restoring the data. Thank you for your help! Can you let me know if /data needs to be mounted under the "Mounts and Storage" section of the recovery menu?
jonny30bass said:
It worked! First, I wiped everything, which I had been doing all along. Then I went to "Mounts and Storage" and formatted everything except for my external SD card (I feel like the last option in there that said "format /data and /data/media (/sdcard)" is what fixed my issue). Then I mounted /data and /storage/sdcard1. Then, I installed a new rom and made a backup to my external SD card instead of my internal SD card. Then I rebooted into system, and then I rebooted back to recovery and wiped everything to restored my backup from my external SD card. The restore actually worked and didn't give me an error when restoring the data. Thank you for your help! Can you let me know if /data needs to be mounted under the "Mounts and Storage" section of the recovery menu?
Click to expand...
Click to collapse
Just make sure everything is mounted, it should display "unmount" meaning it mounted. in any doubt, It won't hurt if you mounted them, versus if you mis the important one then you will run into issue.
I accidentally formatted and unmounted my system on my N7000 in CWM v6 .0 .5 .0 but i can still access my external storage in installing a zip somehow. I recently successfully installed Lollipop beta 5.0.1 cyanogen based on my Note but then i wanted to go back to slim wizz rom because i missed that tablet feature . After re-installing the slimwizz tablet rom i accidentally formatted and unmounted my system and the slim wizz doesn't boot up. When i turn my phone on it boot loops from the lollipop animation and stays as such. Before i did the Slimwizz i used twrp - installed the kernel for slim wizz , rebooted and from CWM i flashed the Slimwizz then somehow while formatting cache, data and internal storage (cause i really didn't have anything in there anyways) i accidentally unmounted my system in process
What can be done to re-mount my system, various storages and data back? Also i can still access TWRP by installing the kernel zip from my sd card but its not much help since my loads are still unmounted in TWRP
busawahk said:
I accidentally formatted and unmounted my system on my N7000 in CWM v6 .0 .5 .0 but i can still access my external storage in installing a zip somehow. I recently successfully installed Lollipop beta 5.0.1 cyanogen based on my Note but then i wanted to go back to slim wizz rom because i missed that tablet feature . After re-installing the slimwizz tablet rom i accidentally formatted and unmounted my system and the slim wizz doesn't boot up. When i turn my phone on it boot loops from the lollipop animation and stays as such. Before i did the Slimwizz i used twrp - installed the kernel for slim wizz , rebooted and from CWM i flashed the Slimwizz then somehow while formatting cache, data and internal storage (cause i really didn't have anything in there anyways) i accidentally unmounted my system in process
What can be done to re-mount my system, various storages and data back? Also i can still access TWRP by installing the kernel zip from my sd card but its not much help since my loads are still unmounted in TWRP
Click to expand...
Click to collapse
Hi. Thank you for using XDA Assist. I'm confident you'll find answers to your query here: http://forum.xda-developers.com/galaxy-note/help
Do remember to backup all data before modifying anything major on your phone. Good luck.
I install ResurrectionRemix M v5.7.2 and gapps 6.0 to my phone through TWRP. it was good. But later i decided to install AospExtended-v3.1 . I took the zip file into my USB Removable disk as my phone didn't have any external storage so that i could install it with the help of OTG cable!
I install AospExtended-v3.1 and gapps 7.1 successfully from TWRP recovery . when it is 'done' i tapped on 'Reboot to system'. I don't know why, my phone goes into bootloop though i installed various ROMS in this process but i wasn't face this problem before!
Anyway then i wiped all data and decided to go back to my previous ROM. I Installed ResurrectionRemix M v5.7.2 through TWRP. it was installed successfully and i thought now that looping problem will resolve, but after successful completion of installing ResurrectionRemix M v5.7.2 when i reboot to system there still the bootloop problem!
Then i though i should go back to my STOCK ROM. I download MIUI 6.7.5_5.0_global fastboot ROM and using miflash tool with proper ADB drivers installed i flash my phone. It was again completed successfully, then i thought this time the bootloop problem will resolve! But no! My phone still stuck into bootloop.
whatever installing process(TWRP/Fastboot) i followed, i am unable to solve this Strange bootloop issue! What should I do?
i am also facing this problem,wht i do i cant understand,pls anyone hlp me to take out from this situation
Try these.
1. Boot into twrp
2. Wipe System, Data, dalvik, cache ( Don't wipe system storage )
3. Connect USB disk
4. Copy desired ROM into internal storage using the file manager given in TWRP.
5. Flash ROM locating the zip in internal storage.
6. Wipe Cache/Dalvik.
Your phone should now boot successfully.
madhurajkumar said:
Try these.
1. Boot into twrp
2. Wipe System, Data, dalvik, cache ( Don't wipe system storage )
3. Connect USB disk
4. Copy desired ROM into internal storage using the file manager given in TWRP.
5. Flash ROM locating the zip in internal storage.
6. Wipe Cache/Dalvik.
Your phone should now boot successfully.
Click to expand...
Click to collapse
I tried this process, but this doesn't work!
try returning to stock MIUI
follow this thread
https://forum.xda-developers.com/mi-4i/help/solved-mi4i-continuous-reboot-issue-t3537896
Hello, forum!
My current Pixel 2 is using the stock google system but I haven't updated the OS since March, partly because it's rooted
and the update process is not as easy.
Now that google said it'd only support the phone till this December, I'm thinking to install lineageOS.
However according to its installation guide:
...
3. Now tap Wipe.
4. Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
...
It's surprising that it need clear internal storage?
p.s. I may also think about installing Resurrection Rom. Does it require 'formatting data' then?
Afaik you must back up everything before installing new ROM, because when you install custom ROM you will wipe and format system and it will erase everything in your internal storage
If its rooted try modded version of twrp to backup your internal data as well
armuttaqin said:
Afaik you must back up everything before installing new ROM, because when you install custom ROM you will wipe and format system and it will erase everything in your internal storage
Click to expand...
Click to collapse
No, it's not, nobody wipes /data/media during rom replacement only /data.
However if his bootloader is locked, bootloader unlock will wipe everything, so before switching from stock a backup is must.
Alright, guys. Thanks for the input. Guess I'll just backup the internal storage and do as told.