[Q] ex3, ex4 issue - Defy Q&A, Help & Troubleshooting

I now what ex3 and ex4 are. If we flash ex4 rom on ex3. It converts to ex4, When we do it vice versa, internal memory is 0. To solve it we have flash sbf. Is there anyway to fix it without flashing sbf??

All I know is that via the boot menu, it is possible to convert ext4 to ext3 without flashing any sbf. I tested this yesterday by downgrading from quarx latest nightly to wiui gb via a simple convert to ext3 from the boot menu, flash zip and wipe dalvik+cache. I have proper space in my system partition.
Sent from my MB526 using xda premium

thekguy said:
All I know is that via the boot menu, it is possible to convert ext4 to ext3 without flashing any sbf. I tested this yesterday by downgrading from quarx latest nightly to wiui gb via a simple convert to ext3 from the boot menu, flash zip and wipe dalvik+cache. I have proper space in my system partition.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
That's exactly what I forgot. Thanks man.

Related

Have I messed up my recovery partition?

I have recently repartitioned my NookColor's internal memory. I changed the partition from:
/data = 2GB & /emmc = 4GB
to:
/data = 5GB & /emmc =1GB
For some reason I now am unable to boot into my recovery console. I tried reflashing it via Rom Manager, but whenever it tries to go to recovery, it goes to the Stock NC rom's Factory Reset screen. My CWM no longer work. Did the repartition somehow messed up the recovery too?
Sent from my NookColor using xda premium
les02jen17 said:
I have recently repartitioned my NookColor's internal memory. I changed the partition from:
/data = 2GB & /emmc = 4GB
to:
/data = 5GB & /emmc =1GB
For some reason I now am unable to boot into my recovery console. I tried reflashing it via Rom Manager, but whenever it tries to go to recovery, it goes to the Stock NC rom's Factory Reset screen. My CWM no longer work. Did the repartition somehow messed up the recovery too?
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Did you try reinstalling CWR after repartitioning? I wouldn't think repartitioning would cause the problem... but it is possible.
First thing I'd try is installing CWR again... and see if it will boot into recovery then... if not... repartition back to 2 GB data.

[Q] can NOT install apps from Play store

i used CM10, after i flashed a CM7 and it stuck in red logo M,then i flashed CM10 new buil, after that i can not install apps from Play store
and how can i flash CM7 from CM10. i have flash normal, but it stuck at red logo M
ensure you're using ext3, flash cm7, factory reset from stock recovery, test. maybe install cm7 again.
If that doesn't work then flash the sbf. Sbf to cm7 only takes about 15 minutes.
I had the exact cm10 to cm7 issue. I've posted all the ways I've seen to fix it. I sbf'd after trying different things for an hour.
As for market apps not installing, sort of had that issue too. It wouldn't install old versions when I went to My Apps>All. Had to search Play for the latest versions. Happened with hacked and regular market. No real fix, but a dalvik/cache wipe plus a market cache wipe and I haven't had that problem since.
EXT3 ?
is what ?
kevins547 said:
EXT3 ?
is what ?
Click to expand...
Click to collapse
Ext3 and ext4 are different Linux file systems. By default (stock kernel) our file systems were mounted as either ext3. Custom kernels give us support for mounting /data, /cache, /sd-ext as ext4 (and ntfs/ext4 support on /sdcard -- no 4gb file size limit). Data on ext4 file systems should be better protected in case the phone freezes and you have to pull the battery.
Needless to say, if you're not sure if you're on ext3 or 4 and you didn't mess with the option in the bootmenu, you're formatted as ext3.

Broken /data/ partition MB525

Hey everyone.
I'll go straight to my problem.
My /data partition is broken. I can't mount it, just like if 1GB of space magically disappeared. Roms normally boot and work, but I can't install any apps. I remember that it happened after flashing modified SBF with Epsylon's CM9. Can't help it with flashing other roms (but I haven't tried stock Froyo yet, do you think it could help?) and I can't simply wipe as /data doesn't mount. Any suggestions on restoring the original partition layout?
Try flash SBF .... during flashing SBF file the partitions are formated so it may help

Cm7.2 based to stock based

I have a problem here
....
Is there any way to flash a stock based rom on existing cm 7 rom.... without flashing a stock firmware using odin...... I don't have a computer now as I am in vacation so I want to be that I don't brick my phone in my vacation.......
Sent from my GT-S5360 using Tapatalk 2
yes
goto cwm
mount system
flash hells fusion #50 kernel
restart to recovery
wipe system data cache
mount system data cache
flash rom zip
Tried before and got system mount error....... and after that cannot install any kernel or rom....... is there any fix to bipass system, data, catche mount errors
Sent from my GT-S5360 using Tapatalk 2
puli112 said:
Tried before and got system mount error....... and after that cannot install any kernel or rom....... is there any fix to bipass system, data, catche mount errors
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
If you already have cm7 install with percys kernel you can flash hells fusion #50 because it supports ext4 partitions
if you are talking about getting mount errors when flashing percys kernel for first time just wipe system data cache then you can mount
don't flash any other kernel as I cannot guarantee its support of ext4 and you may get mount errors and require odin

My attempt to convert a XT1033 converted to GPe to F2FS.

Hello folks,
Well, we all know that the stock Moto G filesystem is F2FS. But surprisingly, the Moto G GPe has a native Ext4 support. Since F2FS is supposed to have about a 30% better performance, I decided to try out the convert to F2FS feature in Philz recovery. So I formatted my system and cache to F2FS (since it didn't give me an option to wipe data and data/media to convert) and flashed a ROM. Currently, I seem to be facing a bootloop.
Anyway, has anyone else tried something like this? If yes, then please share your experience here.
Cheers.
It would be great if that would be possible,then you could jump from retail stock to GPe more easly. I have an XT1032 stock rom and i'd really like GPe,but my concerns are that would i be able to stock XT1032 again from GPe? You know,for F2FS and if i wanted to flash custom roms again to have better support. Any thoughts on my question? And look the first post,this is really interesting since if you'd want custom roms and you are on GPe,you wouldnt need to flash stock ROM to avoid bugs with custom roms and GPe
TWRP also include a format to f2fs <-> ext4 option:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
http://teamw.in/project/twrp2​
Wipe > Advanced Wipe > <Select Partition> > Repair or Change File System > Change File System
I will test this out tomorrow when I have some time.
U need a kernel support somewhat like this in nexus 5 for f2fs
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Stock kernel supports f2fs, GPE kernel does not. Development of a GPE kernel that supported f2fs would be ideal, assuming the GPE stock ROM also functions correctly with a f2fs formated USERDATA partition.
Has anyone even tried to flash boot.img from stock,and then converting in philz?
DeHuMaNiZeD said:
Has anyone even tried to flash boot.img from stock,and then converting in philz?
Click to expand...
Click to collapse
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
lost101 said:
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
Click to expand...
Click to collapse
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Sent from my Moto G using XDA Premium 4 mobile app
Using TWRP to reformat 'data' from f2fs to ext4 wipes SDCARD and didn't even change the format. Right now it appears if you plan on moving between GPE and non-GPE and possibly back again, keep a full firmware image for both.
EDIT: Actually it appears TWRP did format correctly. But the GPE kernel can't get past the Bootloader. Perhaps there are other partition table differences.
After another try..the following works fine.
Migrate to GPE:
1) In TWRP, wipe, and format 'Data' from f2fs to ext4 (this will wipe internal storage.)
2) Sideload / adb push GPE ROM or flash ROM and Kernel via fastboot.
3) Reboot​
Return to Motorola Stock:
1) In TWRP, wipe, and format 'Data' from ext4 to f2fs (this will wipe internal storage.)
2) Sideload / adb push Stock ROM or flash ROM and Kernel via fastboot.
3) Reboot​
rudi_j7 said:
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Click to expand...
Click to collapse
I re-read your OP. The GPE Kernel expects the 'userdata' partition to be ext4. Unless someone develops a custom kernel to support it; you will never be able to run the GPE ROM with an f2fs 'userdata.'
Because you set all partitions to F2FS. Only need to change /data to F2FS. Leave system and cache ext4. You would need a ROM with a patched fstab and then a kernel supporting f2fs for system and cache to be in F2FS as well. Plus major benefit is in /data, not system and cache. I tested full F2FS on my N4 and it was more a pain with less gain. /data is all that should be F2FS.
Sent from my Moto G using Tapatalk
You can get it by deleting the partition / data and change it later by f2fs with TWRP fastboot erase boot partition and flash the boot.img from the stock 4.4.4 rom motorola everything from GPE and I have it so it shows more fluid

Categories

Resources