can I format the system partition and others without causing issues? I have loaded every rom and every kernel and seem to be having weird issues now.on every rom.
Thanks
stanglx said:
can I format the system partition and others without causing issues? I have loaded every rom and every kernel and seem to be having weird issues now.on every rom.
Thanks
Click to expand...
Click to collapse
You should be able to format system and then put a new rom on and be fine.
Related
Hi guys, this is my first post on this forum ( Actually I have benn here for a long time without account )
Alright, This is my problem, I usually flash back to stock by RUU, my Pico has over 100MB free space. A few days ago, I flashed the same RUU, but this time I have 70MB space only, I have cleaned all partitions by recovery and flash again, still.
Oh wait, I just use Disk Usage and check the storage, it's say there are some data(not system) on the internal storage, wow.
Does anyone have ideas?
My Pico cid is Taiwan(621), so I flash TW RUU.
Thanks
before flashing, did you wipe system partition too?
Affangta said:
before flashing, did you wipe system partition too?
Click to expand...
Click to collapse
yeah, I did, everything wiped before flash back by RUU, actually before this, I never wipe by myself but has no problems,
AA181891 said:
yeah, I did, everything wiped before flash back by RUU, actually before this, I never wipe by myself but has no problems,
Click to expand...
Click to collapse
why not sd-ext partition for apps?
Affangta said:
why not sd-ext partition for apps?
Click to expand...
Click to collapse
I know that and it's convenience, but this smartphone now is just my secondary phone.
And for a odd reason, I prefer not to creat a partition on my SD card, just like to keep it simple and clean.
Looks like I'm stubborn...
So guys, I think I'm in a real big problem. When I flash PAC Rom on my i9500 and reboot, it says "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I rebooted into TWRP recovery, Fixed Permissions, and the problem disappeared. However, after that, when I tried to install Apps from File Manager, it said Application Not Installed. I believe this has something to do with the partition thingy. Is there anyway I can overcome these problems?
The problem started when I wanted to install LiquidSmooth on my device. When I tried to do Nandroid backup through TWRP, it failed. Twice. So I used adb for the backup, but it was copying the whole block, 3-4GB+, was taking too much time, so I aborted it in the middle of the process. I then went to TWRP, and flashed LiquidSmooth without wiping (I forgot to wipe). The ROM didn't work, got stuck into Android is Upgrading, even after I wiped, still had the same problem. So I decided to restore my failed backup of the previous ROM (AICP). When rebooted, everything was crashing, System UIDs Inconsistent and stuff. Flashed PAC ROM, still the System UIDs problem, but fixed that with Fixing Permissions.
Is there anyway I can get my phone back to normal? Will I have to re-partition? What are the possible fixes?
Is there no one who can help me?
krtk6160 said:
Is there no one who can help me?
Click to expand...
Click to collapse
I think you partitioned your card as Logical make the partition as type primary.. then flash the ROM..
shubhojit89 said:
I think you partitioned your card as Logical make the partition as type primary.. then flash the ROM..
Click to expand...
Click to collapse
I had recently erased the SD card THROUGH the option available in the phone settings. But the System UIDS problem was there before I did this. I didn't change the partition type. And the SD card contained some android data and obb files. Might that be the problem?
Also, should I just put it into the SD card slot in my laptop and format with the Windows Utility?
krtk6160 said:
I had recently erased the SD card THROUGH the option available in the phone settings. But the System UIDS problem was there before I did this. I didn't change the partition type. And the SD card contained some android data and obb files. Might that be the problem?
Also, should I just put it into the SD card slot in my laptop and format with the Windows Utility?
Click to expand...
Click to collapse
I don't think android data and obb files are responsible for this system uid problem.. Yes format it using windows utility.. If still facing prob try flashing ROM using any other recovery .. Yes before flashing ROM you know the needed steps so I won't tell it again.. Do the steps manually..
Sent from my Explorer A310e using XDA Premium 4 mobile app
Does the data partition formatted to F2FS cause random reboots? I cant seem to narrow it down to anything else. Every nougat rom i tried so far seems to random reboot 3-4 times a day with clean installs. What file format is recommended for custom roms on this phone?
you need a custom kernel for that i think, i thin firekernel has support.
idk tho i dont have experience with it
I believe that ext4 is the stock filesystem type for the data partition, I've never changed it.
Actually, the stock ROM has the data partition formatted as F2FS. It's one of the factors in making the lower end processor seem as fast and snappy as it is.
You can check it in TWRP recovery. Go to advanced wipe and check the formatting for the data partition.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
Actually, the stock ROM has the data partition formatted as F2FS. It's one of the factors in making the lower end processor seem as fast and snappy as it is.
You can check it in TWRP recovery. Go to advanced wipe and check the formatting for the data partition.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hmm... Your right, a quick look at mount in the terminal confirms that. Sorry, my bad.
Now that we know that, I guess the F2FS file system type is probably not the cause of your issues.
acejavelin said:
Hmm... Your right, a quick look at mount in the terminal confirms that. Sorry, my bad.
Now that we know that, I guess the F2FS file system type is probably not the cause of your issues.
Click to expand...
Click to collapse
Yes. I've tried different combinations of partitions formatted to f2fs and it would only work using data as F2FS. Im using the newest aosp extended. Maybe this rom will fix my reboot problems. I am new to this phone coming from a falcon. I know one thing, i am not enjoying moto display. The screen seems to turn on when you dont want it to all the time. I miss my notification LED.
Hello,
Am running into a read only bug with my phone. It seems fine with standard MIUI as operating system without any modifications. Once I put on TWRP as recovery and root the filesystem becomes unreadable. The SD card itself was still working though on miui only. Upon using Havok or crDroid as rom the filesystem & sdcard are not readable. I've tried flashing without the SD card in the device and same thing. Just now I tried to format the SD card within crDroid and it made the card unreadable with 0 space.. even worse. Now I have to reformat it on a windows pc. So far.. this phone is a almost complete wash with this bug occurring.. i'm seeing only way to use it is through MIUI with card. Custom roms are just a complete no go with this happening. Can someone PLEASE help?
nevermind.. i figured it out by formatting the internal data within twrp. Everything is great now.. just need to get a camera app or port of the xiaomi camera.
Timmons said:
nevermind.. i figured it out by formatting the internal data within twrp. Everything is great now.. just need to get a camera app or port of the xiaomi camera.
Click to expand...
Click to collapse
My man, you solve your own problem, how about that, next time take time to read carefully the flashing details.
HidekiRyuga said:
My man, you solve your own problem, how about that, next time take time to read carefully the flashing details.
Click to expand...
Click to collapse
You don't need to be rude about it.
Neither of the twrp ports or the general flashing guide for the RN7P mention formatting the internal storage in their instructions.
Only wiping the cache, data, and sometimes system, which doesn't fix the problem at all.
I ran into this exact same problem and was stumped for 2 days because there was no information on this read only error in these forums, and I had some bad luck googling for help.
In fact, the only way I solved the issue is when Timmons saw my post in the crDroid thread and told me his solution.
Not everyone already has a deep understanding of twrp and flashing roms, and you can't expect people to know everything when stuff like this isn't mentioned at all.
Hey, I've been using a bunch of ROMs for a while, and recently this has become a problem.
Basically, when using Project Elixir or a MIUI ROM, everything works fine.
But, for example, when using crdroid, Evolution X or AncientROM, after rebooting the device, it just doesn't boot, it bootloops.
This might be related to something about Magisk, but not sure.
Also, this only happens after doing the setup.
Can anyone help, and is anyone else facing this problem?
wipe /data ? I'm almost sure that's the step yo're missing.
aurocha said:
wipe /data ? I'm almost sure that's the step yo're missing.
Click to expand...
Click to collapse
Before or after flashing?
Hahayes7 said:
Before or after flashing?
Click to expand...
Click to collapse
If you are changing ROMs you should format (note: format - not wipe) the data partition after flashing the new ROM. Of course this will also delete the contents of your internal storage, so you should backup your internal storage before formatting data.
DarthJabba9 said:
If you are changing ROMs you should format (note: format - not wipe) the data partition after flashing the new ROM. Of course this will also delete the contents of your internal storage, so you should backup your internal storage before formatting data.
Click to expand...
Click to collapse
I always use the instructions provided by the ROM developer, so I don't think I'm doing anything wrong...
DarthJabba9 said:
If you are changing ROMs you should format (note: format - not wipe) the data partition after flashing the new ROM. Of course this will also delete the contents of your internal storage, so you should backup your internal storage before formatting data.
Click to expand...
Click to collapse
Just tried it, didn't seem to work
Hahayes7 said:
Just tried it, didn't seem to work
Click to expand...
Click to collapse
Then it seems to me that the problem may be with something that you are installing after installing the ROM.
Perhaps start with a clean flash, setup the ROM, and do not install Magisk.