Hi guys, I have a little problem.
Yesterday, for decrypting my OP3T, I did a "fastboot format userdata", then I went into TWRP (3.2.0-0) and installed a new ROM. (Did a full wipe before installing that)
But today I noticed a strange thing, I saw that System is occupying about 24 GB.
I checked with a file manager (Solid) and he shows me that Internal Memory has only 30 GB of capacity. (When my OP3T is 64 GB)
What I have to do for fix this? Thanks.
Format data to ext4 and then back to f2fs or vice versa
valimakik said:
Format data to ext4 and then back to f2f2 or wiseversa
Click to expand...
Click to collapse
Thank you very much.
I resolved the problem.
Glad to help
Related
I've flashed custom roms many times, but I have a couple questions regarding Texas ICS p10.
Currently running:
MeDroid 4.1.
BlackRose with System 220MB Cache 16MB Data 200MB
Amon’s RA recovery
Here's a checklist of what I should do:
Backup everything.
Update Blackrose to system 210 / cache 8 / userdata 218.
Wipe everything / factory reset 3 times
What do I need to do regarding formatting/partitioning the sdcard? ext4? setting dalvik cache to use sdext or data partition? In Amon's RA recovery, I have a "partition sdcard" option, with options to
- Partition SD
- Repair SD:ext
- SD:ext2 to ext3
- SD:ext3 to ext4
Do I need to do anything to get a2sd working other than rebooting a couple times?
Flash Texas' p10.
Flash google apps.
Restore.
Done.
Thanks in advance.
Sounds like you got it
if you are ext4 from medroid, you should be fine--not sure, but ext3 may work too
your current partition sizes are ok
see this on a2sd
http://forum.xda-developers.com/showpost.php?p=21222591&postcount=1374
i think you only rin a2sd install one time
i went to p10 and tiamets kernel and had some issues, restored back to p9 and lost my app links--even a sdcard reformat didn't work with p9 so went back to a medroid nandroid
haven't had time figure it out
medroid 6.1 is pretty stable for me
Ken
How can I check if the sdcard is formatted as 4ext?
Isn't it dangerous having a cache partition of only 8 MB?
Sent from my Nexus One using Tapatalk
maybe gparted or a partition tool program
i am having sdcard issues atm so can't test--terminal em can check, forget command, but sometimes it wasn't accurate for me
i don't know that 8mb is dangerous--some larger apps may not work right--depends how rom handles them. cm7 handles them well--miui doesn't--or so folks say
Don't know about 8MB cache, but it's kinda vurnerable to have only 210MB system partition now. If you have any plan to switch to other ics rom, i.e. MeDroidMod, you'll only have a little size left, or even nothing left. I repartizied back to 220/16/200, which is acceptable for any rom.
Sent from my Nexus One
Ok, so I followed the checklist I listed above. p10 stalls at the blue X boot logo for 10 minutes now. Anyone know why it's doing this? I'm going to go do a full wipe/repartition/reinstall again. I left my hboot alone, as suggested twice.
Actually, I opened blackrose and it automatically installed the latest blackrose, which put my phone in recovery and apparently wiped the rom??? Anyway, now I couldn't change hboot partitions anyway, so I proceeded with the rest of the checklist...
Have a 220/16/200 partition?
Boot into recovery, if you have 4ext recovery, you can format everything except sdcard, then flash p10 & gapps.
Sent from my Nexus One
Yeah, I have that partition. I just wiped everything, repartitioned the sdcard and reflashed... currently 8 minutes in the boot animation...
Not sure what to do from here.
Installed latest medroid 1.3.2a and it just keeps booting back into recovery.... hrm.
Do I need to flash a boot img as described here?
http://forum.xda-developers.com/showthread.php?p=22731102#post22731102
Ok, it installed. Updating blackrose, which took out my ROM for some reason, reverted to the default hboot as far as I can tell. I put the 220 version back on wiped and reflashed and it booted just fine.
Ended up using Medroid 1.3.2a instead of TexasIce p10. Even though p10 has HWA, it has bugs (browser rendering on zoom takes 2 seconds, sometimes longer) and isn't as fast as Medroid in general.
just got 1.3.2a and is running great
samuaz is loading HWA version now, but may have same issues as T's
First boot on ICS may take a while ! Just chill out ^^
After installing custom recovery and rooting my (OP3T) in DiskInfo (https://play.google.com/store/apps/details?id=me.kuder.diskinfo) I noticed that the file-system for System is ext4 (same for Cache), but at the same time Data (userdata) is still in f2fs (see the print screen)?
During the TWRP installation and root I did not format or re-flashed the ROM (I am still on OxygenOS 3.5.3. as it was after OTA update from OxygenOS 3.5.3.).
So I am thinking its either the custom recovery installation that caused file-system change or it is so by default.
Could you please check your OP3T and see what DiskInfo (https://play.google.com/store/apps/details?id=me.kuder.diskinfo) reports in regard of file-system.
jemeljsh said:
After installing custom recovery and rooting my (OP3T) in DiskInfo (https://play.google.com/store/apps/details?id=me.kuder.diskinfo) I noticed that the file-system for System is ext4 (same for Cache), but at the same time Data (userdata) is still in f2fs (see the print screen)?
During the TWRP installation and root I did not format or re-flashed the ROM (I am still on OxygenOS 3.5.3. as it was after OTA update from OxygenOS 3.5.3.).
So I am thinking its either the custom recovery installation that caused file-system change or it is so by default.
Could you please check your OP3T and see what DiskInfo (https://play.google.com/store/apps/details?id=me.kuder.diskinfo) reports in regard of file-system.
Click to expand...
Click to collapse
Pure stock updated to latest, just had the device a few hours and love it.
LMcR92 said:
Pure stock updated to latest, just had the device a few hours and love it.
Click to expand...
Click to collapse
Everything's the same, except in your case we cant see "Internal Storage - System" and its file-system. Probably because yours is without root.
jemeljsh said:
Seems the same, except in your case we cant see Internal Storage - System. Probably because yours is without root.
Click to expand...
Click to collapse
I'm planning on getting root and kernel on ASAP.
LMcR92 said:
I'm planning on getting root and kernel on ASAP.
Click to expand...
Click to collapse
Any news?
Userdata (the main storage) is f2fs, modem and sde23 are vfat, rest is ext4. From what I know, this is supposed to be so.
I have TWRP installed and phone is rooted.
Mine are all EXT4.
Running stock 3.5.3
TWRP, Rooted, running tyranus kernel, and xposed.
Everything seems perfect so I'm not sure why mines different.
I'll back everything up and format data in TWRP
OK I'm good now
Does anyone have encountered this issue?? It's really damn annoying... Thanks for any help
I did have it and it is very annoying, I installed TWRP Blue Spark and it solved the issue. I will look for it and if I find it I will share it with you.
What version of TWRP are you using? 3.0.3-1, 3.0.4 and 3.0.4-1 have all been working well so far.
Anova's Origin said:
What version of TWRP are you using? 3.0.3-1, 3.0.4 and 3.0.4-1 have all been working well so far.
Click to expand...
Click to collapse
This happens if yu are f2fs formatted and swipe in allow for modifications when booting in §TWRP. If you don't swipe, you can still flash roms. Not sure what's changing anyway...I formatted ext4 and have no issues right now.
iam using f2fs with latest twrp (3.0.4.x) and no such issues.
but i was losing apps randomly after booting into recovery, on older TWRP versions.
Installed TWRP 3.0.4 and everything seems back to normal. Thanks for ur help guys.
Now my next problem is 4g reception in France..
Cheers thanks a lot
PS: how do I know if I'm using f2fs or ext4?
I believe there was an option somewhere in TWRP to view all your partitions and their file formats. By default, only the data partition is formatted in f2fs, everything else should be ext4 (and maybe fat?)
Edit: If you select Wipe in TWRP, then advanced wipe, and select the Data partition, you can click partition options to see what the file format is (don't swipe right if you don't want to wipe it). Aside from data, every other partition should be ext4 by default.
There's also apps like disk info that can tell you the file system used as well.
piffa_ said:
Installed TWRP 3.0.4 and everything seems back to normal. Thanks for ur help guys.
Now my next problem is 4g reception in France..
Cheers thanks a lot
PS: how do I know if I'm using f2fs or ext4?
Click to expand...
Click to collapse
there is a app on playstore disk info
and there is new twrp avaliable 3.0.4.1
So yeah, my phone memory turned to 32gb from 128gb after I used the force wipe data from the oneplus3t toolkit can there be a way to fix this?
Boot to twrp recovery and repair filesystem in wipe tab.
ppajdek said:
Boot to twrp recovery and repair filesystem in wipe tab.
Click to expand...
Click to collapse
Thanks for the reply, tried it and still gives me 32gb of internal storage. Do I need to format/wipe the internal storage or the system?
Fixed bro, changed the file system from f2fs to ext4.
Long story short, I've been trying to get into my internal storage via TWRP but its saying that there are 0MB in the internal storage and that there is nothing in the sdcard folder
I've tried formatting it, hasn't worked
I've tried changing the format to FAT and then back to EXT4
then after that didn't work i tried the same but with EXT2 , it showed the amount of storage but still didn't let me see what was inside of the sdcard folder, whenever i'd go in there its just completely empty
Can I please have some help with this, I've been stuck on this for a couple hours now
Ouch! Please don't say that you just formatted userdata (/data).
You've just killed all your data on your phone.
No, I'm not that experienced with TWRP and I don't know which versions under which circumstances it can mount userdata.
I use custom recoveries and just presume that I can't mount userdata in them.
In the normal system (which mounts and decrypts) I use normal tools to sync or backup.
Renate said:
Ouch! Please don't say that you just formatted userdata (/data).
You've just killed all your data on your phone.
No, I'm not that experienced with TWRP and I don't know which versions under which circumstances it can mount userdata.
I use custom recoveries and just presume that I can't mount userdata in them.
In the normal system (which mounts and decrypts) I use normal tools to sync or backup.
Click to expand...
Click to collapse
I didn't format data it self i meant that i factory reset it, sorry i should of been a lot more clear on that
Oh, ok.
Well, in any case, if it's encrypted you need to mount it not with a simple "mount" command but something fancier using dm.
They don't try to make it easy to do.
Unless you're destroyed your system and you're trying to recover your data, whatever you're trying to do is best done in the normal system.
never mind i found a fix for it
well not really a fix just a way around it
thanks for the help ^^
SoftieIsVibing said:
never mind i found a fix for it
well not really a fix just a way around it
thanks for the help ^^
Click to expand...
Click to collapse
I had the same issue so I flashed a raw firmware after taking full system backup. Now TWRP is working fine.