I flashed a CM ROM a couple weeks ago and ever since TWRP doesn't start out in it's typical directory... For example, I can put a file on root of my device when I connect it to my computer, but then I have to navigate through other folders to get to it in TWRP. Before flashing CM it would just go to the root of the storage. It's as though it now starts at the very root directory of the entire device. Is there a way to revert this?
Still looking for an answer to this if anyone has any ideas.
delete folder "0"
I have. But that's not my problem. When I load up TWRP I have to go to data/media/ just to get to the the root of the sdcard. Rather than it just starting there like it should.
Sent from my HTCONE using xda premium
I pulled this from the FAQ's on the TWRP page:
Android 4.2 has changed things with /data/media devices a little bit due to the multi-user support that came in 4.2. Each user is assigned a subfolder in /data/media. The main user gets /data/media/0 and subsequent users get /data/media/10 and /data/media/11 and so on. If you switch users in Android 4.2, the system will remount the /sdcard folder to point to the proper user's folder. TWRP has been updated to use the /data/media/0 folder starting in 2.3.2.0.
Another "feature" of 4.2 is that when you "update" to 4.2 it may attempt to upgrade your /data/media to multi-user. If you're running an older version of TWRP than 2.3.2.0 or newer, a factory reset may trigger multiple upgrades, causing your "sdcard" to get moved to /data/media/0 then /data/media/0/0 and then /data/media/0/0/0 and so on depending on how many times you "upgraded". This may cause backups to not be visible in TWRP. Also, there currently isn't a good way to go back to a 4.1 ROM after using a 4.2 ROM without having to manually move your files around.
Since I like to jump back and forth from 4.1 and 4.2, it seems to work best if you back your SD card up to your PC before you flash 4.2. This way if you decide to leave 4.2 and go back to 4.1, you could wipe the SD Card and then load it from your PC. Not idea but seems to be the workaround for now.
For now, it is best to decide if you are going to stay on 4.1 or 4.2 and not jump back and forth or you will eat up your space very quickly.
Hope this helps.
Related
Hello
My name is Alvin and I really want to help the people who are new to Android hacking/rooting/flashing/roming<made that up . This post may not be interesting or super helpful, but I want to help people with a question that's not usually mentioned.
Upgrading/Downgrading, that's the Technology world right now. It's important people know how to keep up by upgrading without having to lose all their data.
Upgrading/Downgrading Difficulty Level: 2
(Scale of 1, being Beginners, to 10, being a developer)
To upgrade a ROM without losing data, you must me under these certain circumstances,
The ROMS match. THAT'S IT. Well what do I mean by "Rom Matches"???
The /data has to be compatible with the newer ROM.
The ROMs that are not compatible with the same data.
NC Stock to any other ROMS
THE DATA MUST BE WIPED BOTH GOING FROM STOCK AND GOING BACK TO STOCK. THE DATA IS NOT COMPATIBLE.
The ROMs that ARE Compatible:
CM7<>CM7
CM7<>CM9
CM7<>CM10
Custom ROMs<> Any CM ROM.
Note: Downgrading the Android OS and keeping Data is fine, but some items may be broken or incompatible after being modified in a newer Android Version.
NOW you read all the circumstances and determined that your Nook Color is OK to upgrade+keeping /data partition, here are instructions if you don't already know them.
Open any type of Recovery. CWM or TWRP. SD or Emmc.
Go to Mounts and Storage at the bottom
Carefully select Format /system
Next, select format /cache
Now, we are leaving the /data alone.
Click Back or use the power button to do so.
Click Install Zip from SDCARD.
Find your .zip file that you want to flash to upgrade/downgrade your Nook.
When finished, you may apply GApps which is optional. GApps was formatted with /system. If you need to find gapps, go to: goo.im
Reboot and the New ROM should look like it was used before by you.
Note: The location of these instructions are based on C.W.M. All instructions are same on other recoveries.
If this post helped you, I would appreciate a thanks because it would make my day.
If this post provides any false information, typos or errors, please tell me so because this is a great learning experience for me.
If there are any questions, I will answer them withing 48 hours. Valid till 11/4/12. After that I'll check periodically.
P.S I love smiley faces.
Sources: Picture from neown.com
Hey -- I'm just about to try these steps. It seems really self-explanatory to me, I'm more than a beginner but not quite at developer. I'd say I'm like a 6 or 7 in your list.
However, the one thing I haven't tried yet is upgrading to a newer ROM. I flashed Nameless v2.0.2 for the HTC Desire C and now they're at version 5. I just did a FULL backup using CWM Touch for the Desire, and I'm about to do what you suggest. I have a custom lockring, battery icon and boot animation, I guess I'll just have to push those three things back on afterward? I think everything will go smoothly, I even have a separate SD card to flash from ^^
Anyway, I guess that's not really a question... I just want to make sure these steps apply to any ROM... but logically it seems like it would.
-AC
Hey, if i downgrade my rom (Android N) with only remove the system, and install the lower rom (Android M) is it will delete the installed application and the data too?
I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM10:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
Rebooted into webos:
resized my system partition from 400 to 600 mb.
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
CM10 still boots fine and my files show up in /sdcard0/. There is no sign of a folder called /sdcard/. Same story if I explore the device with a computer.
I should mention that I also moved my nandroid backup to my computer, off the touchpad to save space before I resized my partitions. I then moved it back into the folder. I wouldn't be opposed to wiping the thing and starting over to get 4.4 working.
Any ideas?
kspanks04 said:
I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
Click to expand...
Click to collapse
First, this issue that you observe has been discussed ad nauseam in various CM11 ROM development threads.
Second, you did not post which specific CM11 ROM you are planning to employ. So I assume it is Milaq's CM11 ROM (kernel 3.0+).
At any rate, what you are observing in an inability to directly access the /external_sd partition (on the TouchPad), which is accessible in previous CM builds, but is no longer directly accessible in Milaq's recent CM11 builds (Kernel 3.0.101) or in his recent CWM recoveries.
http://forum.xda-developers.com/showpost.php?p=49216229
• Milaq and others have suggested you can use ADB to mount the partition manually (sorry no instructions).
• Some have posted you can use Invisiblek's recovery (CWM 6.0.5.4 selinux datamedia) to flash Milaq's recent CM11 (Kernel 3.0+) ROM's
• You may be able to find a version of TWRP that can access the /external_sd partition.
On a related note, the new DataMedia storage paradigm which is the future of Android, has been designed into the newer CM11 and other KitKat ROM and recovery builds. Thus you need to increase the size of your /data partition.
You can use the Tailor app within WebOS to reduce the size of /media partition, then increase the /data partition size. And there are some scripts available that do similarly.
Best to read the specific ROM thread (including the OP) for more info on how DataMedia applies to the ROM build you are employing, and then be sure to read later posts in the thread regarding the inaccessibility of /external_sd: http://forum.xda-developers.com/showthread.php?t=2542353
It is possible that future builds of the CM11 ROM (kernel 3.0+) might provide access to /external_sd once again. Will see. Fingers crossed.
I tried invisiblek's cwm recovery and it did not provide access to /external_sd
(and there is confusion on the recoveries specific version number)
http://forum.xda-developers.com/showpost.php?p=49423381
There is another recovery on invisiblek's site: openrecovery-twrp-2.6.3.0-tenderloin.zip
Anyone have experience with that recovery version, ability to access /external_sd or "compatibility" with Milaq's newer CM11 ROM builds?
Yes sorry, Milaqs rom that you linked is the one I was working from. I don't have ten posts so that's why I'm posting here. I read through most of that forum and tried searching for my issue with no luck.
I went back and saw a couple posts that matched my problem with the following solution:
http://forum.xda-developers.com/showpost.php?p=49154585&postcount=471
When I get home I will try this although I didn't remember seeing that folder when I explored my device on Windows.
Thank you for the reply and sorry for the redundancy!
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
kspanks04 said:
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
Click to expand...
Click to collapse
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Here is another trick that worked for me. Recover a previous stored ROM that supported both sd1 and sd0. Use file manager to copy the files you want from sd1 to sd0. Then go back to the new ROM and you will have access to your files on sd0.
Merfy said:
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Click to expand...
Click to collapse
Ahhh thank you. I had tried this with a different file explorer in root. Es did the trick.
Now I need figure out how to fix these black screens that lock up after a good amount of inactivity.
Greeting HP Touchpad Expert: I need help.
I didn't mean to post this thread but I have same issue.. only I have this..
I also updated my CWM to http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.7-tenderloin.zip
in preparation for upgrading my CM09 to CM11 (Milanq 4.4 Kitkat). Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM9:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
I have not yet resize system partition.
Now, when I want reboot to CWM install the 4.4 rom all my folders were missing.
All I can see is
/sdcard/
-0/
-clockworkmod/
-clockworkmod/backup
Yes I have tried to ES File Explorer (R+W root) and following gabhroo123's notes above
I do not have
/data/media nor /data/media/0 folder
only empty /data folder.... I am able to write to copy older recovery-clockwork to /data but not "/" ...
When reboot to CWM 6.0.4.7 I still don't see any zip file.. (No files found message show).
Can someone at least point me the right URL or discussion xda-developers.com thread so I can read them.
I am not sure what I did wrong...
What extra steps I suppose to do ...because I have HP Touchpad with CWM 5.x.x + Android 4.0.1.x + CM 9 + mobo 0.35 ?
My planning steps were
#1) upgrade CWM to 6.0.4.7
#2) upgrade CM 11
#3) upgrade Gapps
Reference http://forum.xda-developers.com/showthread.php?t=2542353
([ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel])
I do see /sdcard/clockworkmod/backup/backupfolder.. in CM 9 and I did put CM 11 and Gapps in several place in
/media , /sdcard/media, /sdcard/cminstall etc.. but nothing.. kept saying file not found..
Should I downgrade CWM back to 5.x.x ? I do not see any install zip file at all ...how?
HELP!
Thank you
Hi All,
my first time using a forum and first time attempting to install a custom ROM so be nice . i have done some research around the net but I'm now more confused than before i have read that i need to install software to back up my current ROM but before that it needs to be rooted but before i can root it i should back up the current ROM (confusing...), i have also read that galaxy note 1 users have some serious bugs in the kernel so its very risky rooting it never mind putting a custom ROM on it, that the IEMI in the EFS partition will be wiped so that should be backed up after rooting but before flashing with a new ROM otherwise i wont be able to connect to my network i have searched the forum and found guides but nothing for my phone and nothing in as much layman's terms as i need.
Phone: Samsung galaxy note GT-N7000, last over the air update was 12 months ago for android v 4.1.2
base band version n7000xxlt3 kernel version 3.0.31-1103517 [email protected]#3 smp preempt tue jun 4 20:55:52 KST 2013 build number J2054k.N7000XXLT9
bought 2 years ago on t mobile currently running on giff-gaff
knowledge: some but evidently not enough tried to fix a bug on a tablet and didn't back it up first, bricked it and a year later its still in my draw
i have a lot of stuff on my phone, 2 years worth of stuff and while iv done the odd manual back up knowing im about to flatten it completely i want to back it up completely first, document videos pics contacts apps messages everything i can possibly back up i will
so what i need:
a total walk through precautions on what i should do and in what order i.e. backing up in general, backing up efs, rooting, backing up current rom, flashing a rom ect
what software i should use for the above?
the best 3 ROM's available for GT-N7000 or just peoples opinions will do I'm looking for something with added features and a a fresh look as I'm really bored of the phone now
sorry if this is already somewhere else and please feel free to make fun of the new guy as long as i can perform a successful flash my phone i will be happy!
Many thanks in advance
@ckershaw here is what you need to do. As you have a lot on your phone, connect it to pc and transfer all the data. Then look for Philz kernel and download kernel matching your build number XXLT9. Download the .zip file and put it on your external sd card. Reboot to recovery pressing volume up+power+home button and flash the .zip file there. It will give you custom cwm and root. You can now install titanium backup pro or such application to backup your user apps (don't backup and restore system apps). Once done, you can again reboot to recovery and take a backup of your whole rom (make sure you select EFS folder too to backup). Once you have the backup on your external SD card or trasnferred to pc. Perform full wipe (factory reset from philz recovery). Then go to mounts and storage and also wipe /system /cache /data and internal sd card. Once you are done, flash raw kernel (either r4 or r5) from external sd card and reboot recovery and flash the latest kit kat rom (any of your choice) along with Gapps. Raw kernel is only if you are trying to flash any kit kat rom, else philz kernel should suffice.
treacherous_hawk said:
@ckershaw here is what you need to do. As you have a lot on your phone, connect it to pc and transfer all the data. Then look for Philz kernel and download kernel matching your build number XXLT9. Download the .zip file and put it on your external sd card. Reboot to recovery pressing volume up+power+home button and flash the .zip file there. It will give you custom cwm and root. You can now install titanium backup pro or such application to backup your user apps (don't backup and restore system apps). Once done, you can again reboot to recovery and take a backup of your whole rom (make sure you select EFS folder too to backup). Once you have the backup on your external SD card or trasnferred to pc. Perform full wipe (factory reset from philz recovery). Then go to mounts and storage and also wipe /system /cache /data and internal sd card. Once you are done, flash raw kernel (either r4 or r5) from external sd card and reboot recovery and flash the latest kit kat rom (any of your choice) along with Gapps. Raw kernel is only if you are trying to flash any kit kat rom, else philz kernel should suffice.
Click to expand...
Click to collapse
hi thanks for the info!
when i say uber noob i do have lots of experience with phones and computers as its what i do for a living im also a quick learner so i figured it out myself last night, granted i was at it till 02:30 in the morning but i figured it out and that's almost exactly what i did, the only thing i did differently was i wiped it but i didn't 'Then go to mounts and storage and also wipe /system /cache /data and internal sd card' but all is working very well and it feels like i have a new phone i did have 1 annoying issue that was the Google keyboard crashed every 5 seconds so had to keep clearing the notifications for it but i solved that by disabling it and pushing a different one from the play store.
one thing i do need help with however is i made a manual backup of the phone but not sure if i got everything, i did a full backup with kies.. that was a mistake! as the phone isn't recognized as a Samsung device i cant restore the backup, i would like to try to manually extract the file but i have looked around and been told you can only recover calendar and contacts, i want to recover images, videos, sms, call logs all that sort of stuff.. any ideas? has anything been developed recently for that as all the posts i looked out although relevant are rather outdated its a .sbu file
Thanks
ckershaw said:
hi thanks for the info!
when i say uber noob i do have lots of experience with phones and computers as its what i do for a living im also a quick learner so i figured it out myself last night, granted i was at it till 02:30 in the morning but i figured it out and that's almost exactly what i did, the only thing i did differently was i wiped it but i didn't 'Then go to mounts and storage and also wipe /system /cache /data and internal sd card' but all is working very well and it feels like i have a new phone i did have 1 annoying issue that was the Google keyboard crashed every 5 seconds so had to keep clearing the notifications for it but i solved that by disabling it and pushing a different one from the play store.
one thing i do need help with however is i made a manual backup of the phone but not sure if i got everything, i did a full backup with kies.. that was a mistake! as the phone isn't recognized as a Samsung device i cant restore the backup, i would like to try to manually extract the file but i have looked around and been told you can only recover calendar and contacts, i want to recover images, videos, sms, call logs all that sort of stuff.. any ideas? has anything been developed recently for that as all the posts i looked out although relevant are rather outdated its a .sbu file
Thanks
Click to expand...
Click to collapse
If all your efforts are for naught, maybe I'd suggest that you flash a stock rom, restore all your stuff via Kies again, and this time backup them in your PC instead. Do not worry about deleting your media (Images, video, music) if you do a factory wipe reset from a custom recovery as they are not set to delete those files. to back up sms, call logs and contacts calendar n stuff, you can install superbackup app from playstore. Takes time n effort to restore but I think it's worth it. Good Luck bro:good:
Hi Guys,
thanks for all the help, been working great for a week with no bugs my question is now i have flashed it with the ROM the root access is now gone so i will need to root again the details are now
android version: 4.43
omni version: 4.4.3-20140608-n7000-nightly
Baseband n7000xxlt3
kernel: 3.0.64-OMNI-g5f47648 [email protected] #1 sun jun 8 07:00:23 CEST 2014
built number omni_n7000-userdebug 4.4.3 KTU84M 254 test-keys
what file will i need to do this, i couldnt use odin it dodnt work i found transfering the file to SD and running it that way worked best (cant remember do you have to wipe when you root this way)
Thanks
ckershaw said:
Hi Guys,
thanks for all the help, been working great for a week with no bugs my question is now i have flashed it with the ROM the root access is now gone so i will need to root again the details are now
android version: 4.43
omni version: 4.4.3-20140608-n7000-nightly
Baseband n7000xxlt3
kernel: 3.0.64-OMNI-g5f47648 [email protected] #1 sun jun 8 07:00:23 CEST 2014
built number omni_n7000-userdebug 4.4.3 KTU84M 254 test-keys
what file will i need to do this, i couldnt use odin it dodnt work i found transfering the file to SD and running it that way worked best (cant remember do you have to wipe when you root this way)
Thanks
Click to expand...
Click to collapse
Either find UpdateSuperSUv1.94.zip and flash it through recovery, or just try downloading supersu or superuser from playstore.
Jackwu696 said:
Either find UpdateSuperSUv1.94.zip and flash it through recovery, or just try downloading supersu or superuser from playstore.
Click to expand...
Click to collapse
Thanks,
last one i promise my battery has been draining in an average of 4 hours and my phone is constantly hot since putting this ROM on i have 3 battery's i charge externally via an external charger and that just about lasts me the day i have a power management app called battery doctor that is great and if it wasn't for that I'm sure it would only last half the amount, i have checked and Google+ keeps starting up every time i close it even if i force it to stop and it's used 96% of my battery today i have only actually used the phone for about 3 minutes today. ond its only been off charge for 3 hours is it OK to disable it what else wont work if i do. is there any reason its doing this surely that's not normal?
Thanks
ckershaw said:
Thanks,
last one i promise my battery has been draining in an average of 4 hours and my phone is constantly hot since putting this ROM on i have 3 battery's i charge externally via an external charger and that just about lasts me the day i have a power management app called battery doctor that is great and if it wasn't for that I'm sure it would only last half the amount, i have checked and Google+ keeps starting up every time i close it even if i force it to stop and it's used 96% of my battery today i have only actually used the phone for about 3 minutes today. ond its only been off charge for 3 hours is it OK to disable it what else wont work if i do. is there any reason its doing this surely that's not normal?
Thanks
Click to expand...
Click to collapse
My best suggestion would be to delete google+. Otherwise use Titanium Backup to freeze or greenify it. The best is still to delete it though.
Sent from my GT-N7000
I'm almost entirely new to messing around with stock firmware on a locked bootloader, its been unlocked for 2 years. I relocked it, TA keys are fine, I had TWRP, I was able to write to the system partition, I had external storage write permissions, and all of those things have dissapeared entirely. I was able to use an xposed module for getting external storage permission back.
-I can't install TWRP again because the installer on a locked bootloader requires the system to be remounted rw or already have access to a recovery.
-The xposed solution to the exteral sd isn't ideal, and again I need TWRP or to do it manually by mounting the system rw.
-FlashFire doesn't work regardless of what variation of options I give it.
-I pulled the kernel image out of the pre-rooted zip I initially used but it won't fastboot. It says USB debugging isn't enabled when I try it using flashtool, though it is on when the system is up. I was hoping that the rewrite permissions or possibly even TWRP would be available if I reflashed the kernel image. This won't work.
The reason for being on Lollipop is that for whatever reason, push notifications still really suck for me on Marshmallow, enough so that it isn't a workable option.
Having either TWRP or being able to remount the system rw would, from the look of it, lead to being able to fix the thing entirely.
The only workable solution I have right now is to flash stock Marshmallow, install TWRP which is rather easy on current MM, then reinstall the pre-made zip I already had for Lollipop. This is a huge pain given that I just put a lot of time into my setup and even just the settings I'm using in Xposed would in itself be difficult to restore as its quite a lot. Everything is backed up via Titanium.
Essentially, "Is there a workable solution to my problem that doesn't involve flashing MM, putting TWRP back, reflashing LP, then setting up what I know I need to all over again followed by the inevitable supprise down the line of still needing to re-do some of my apps that didn't quite go well? The goal is to get TWRP back, and this seems like it isn't going to happen if I can't write to the system.
??
Also, If I just pull /data entirely via adb, my laptop already uses ext4 for the filesystem, but it there a way in this scenario where I could absolutely ensure that I could do it, and then put it back while not screwing up file permissions assuming I did the whole falsh MM, install TWRP, flash LP thing?
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).