So, i;ve repartitioned my phone, and tried to install cm11...all good...., ..but with cm12.1 it seems it have a problem.
I tried, reflash/full wipe/format system , data ( preload i cant format ..it gives me this error )
formatting /preload....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
When im installing cm12..at the end i get this error : warning: no file_contexts detected filesystem ext4 for /dev/block/mmcblk0p12 ..but at the end it says that the script was succesfully installed
I thinks ..i get bootloop because of the repartition...how do i fix this ? ..can someone help me ?
The error indicates, that /preload partition is not having a proper ext4 filesystem. This is strange, as imo CM doesn't need this partition.
Try to flash a different recovery like TWRP (Link in CM12.1 Thread) and format /preload in there.
Afterwards I would wipe /system and /data and then flash CM12.1.
disclaimer: formatting /data or sdcard0 will result in loosing all your data, so backup your data before doing so.
fireburner-de said:
Did you format /system /data and sdcard0 after re partitioning? Don't forget to flash a ROM or Kernel after formatting /system, because formatting deletes your recovery.
disclaimer: formatting /data and sdcard0 will result in loosing all your data, so backup your data before doing so.
Click to expand...
Click to collapse
well..i did ...sdcard0 trough windows i think... is it because of that?..i thinks its fat32
Sorry, pls read my edited post. That may be more helpful.
But I would not suggest formatting sdcard0 through windows. I would suggest formatting it inside the recovery with vfat (fat32).
But that shouldn't be the cause of this problem.
well, i did format it with twrp ..doesnt show me any error..but i still get a bootloop
Okay, so the first problem is solved.
I then would suggest wiping /system /data /cache out of TWRP and then flash CM12.1 again.
diclaimer: wiping /data will delete your App data
welll..i did...still doesnt work..bootloop/.
Booting up CM12.1 for the first time may take some minutes. Are you sure you got a bootloop`?
i waited 10 minutes...
Did you try again, wiping all above mentioned and reflashing CM12.1?
disclaimer: formatting /data or sdcard0 will result in loosing all your data, so backup your data before doing so.
ill try it right now
same thing
ultravy said:
Use this guide for repartition by @gsstudios , and format your partitions correctly (ext4 cache, data, sys & vfat/fat32 sdcard0 your internal storage) . worked for me 1 gb system, 3 gb data!
Click to expand...
Click to collapse
Did you try formatting again like ultravy suggested?
yes
i have used the modified preload pit files I9100_6GB data - 45mb preload.pit
still bootloop
detected filesystem ext4 for /dev/block/mmcblk0p9
detected filesystem ext4 for /dev/block/mmcblk0p10
Patginking system image unconditionally...
Script succeeded: result was [0.20000]
How big is your /system partition with that PIT?
Else I don't know what's wrong here.
8gb system
Are you sure? Because that would lead to like 2-3GB left on sdcard0, when /system is 8 and /data 6. Stck /system is 512MB and suggested when repitting is 1GB or 1.5GB.
its working now..please close this topic
Thank you !
Related
i will keep it simple ..Custom recovery is unable to take a nandroid backup if i have a2sd on ext4 partition that same run nandroid-mobile.sh via adb...please fix it or tell me how to.. i m new to android but m good with C and Linux
i had same as your problem , every time when i try to include .android and ext files with my backup it gives me error message , but after i installed a new rom everything went fine!!
For me mounting of ext in recovery helped as well.
The_ERROR said:
For me mounting of ext in recovery helped as well.
Click to expand...
Click to collapse
And doing this, did you managed to restore the backup successfully ??
Well this thing happens with BOTH megatron and void roms...when i boot into custom recovery /cache is the only one mounted and i tried unmounting it before trying a nand+ext+.android_secure backup...doesn't work my sd card is like 3 gb free and ext4 a2sd has only 130Mb of apps in it..
Guys I had made a simple nandroid backup after rootingand installing custom recovr and before installing void. Now if I restore the nandroid backup, will I still have the custom recovery or not?
Sent from my LG-P500 using Tapatalk
lekhwani said:
Guys I had made a simple nandroid backup after rootingand installing custom recovr and before installing void. Now if I restore the nandroid backup, will I still have the custom recovery or not?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
u made nandroid after instaling custom recovery :|
how can u lose it?? i dnt think so ..
i cant mount the sd-ext partition from the custom recovery.. it says:
E:Can't mount /dev/block/mmcblk0p2
even nadroid back up with ext ends: run nandroid-mobile.sh via adb
any solution??
Boot in recovery mode.
Connect phone to pc.
Mount ext partition via adb.(after that in Custom recovery mount menu you will found ext partition mounted)
Do nandroid
sugaritos said:
i cant mount the sd-ext partition from the custom recovery.. it says:
E:Can't mount /dev/block/mmcblk0p2
even nadroid back up with ext ends: run nandroid-mobile.sh via adb
any solution??
Click to expand...
Click to collapse
//Edit: First try to create backup ONLY of system, without any other option. If this will be work, you probably done same mistake as I did.
Same as me. I didn't do wipe of EXT after creating of ext-part and I had same symptoms. Backup all your data with Titanium Backup, backup data on SDcard, delete ext, create ext2 again, convert ext2 on one, that you want, do wipe of it. Than it should be working (I had).
anotherloony said:
Boot in recovery mode.
Connect phone to pc.
Mount ext partition via adb.(after that in Custom recovery mount menu you will found ext partition mounted)
Do nandroid
Click to expand...
Click to collapse
i tried via adb but it keeps saying the same thing:
mounting /dev/block/mmcblk0p2 on /sd-ext failed: invalid argument
i dont know if i am doing it right..
The_ERROR said:
//Edit: First try to create backup ONLY of system, without any other option. If this will be work, you probably done same mistake as I did.
Same as me. I didn't do wipe of EXT after creating of ext-part and I had same symptoms. Backup all your data with Titanium Backup, backup data on SDcard, delete ext, create ext2 again, convert ext2 on one, that you want, do wipe of it. Than it should be working (I had).
Click to expand...
Click to collapse
thankss!! i will try it..
i read somewhere that ext4 has problems and is better or recommended the ext2 even though it is slow..
sugaritos said:
thankss!! i will try it..
i read somewhere that ext4 has problems and is better or recommended the ext2 even though it is slow..
Click to expand...
Click to collapse
ext2 is faster, because it haven't journal. But it on some I/O output error is not possible to recover it by itself. Ext3 have journal - is slower, but in case of problem will (can) repair itself. ext4 is better ext3.
under partition section - http://forum.xda-developers.com/showpost.php?p=10377391&postcount=4
At the time I made the recovery kernel sources were not out so I couldnt add ext3 & ext4 support to recovery. I'll try to update it as time allows.
mount -t ext4 /dev/block/mmcblk0p2 /sd-ext
be shure /se-ext exists
drellisdee said:
At the time I made the recovery kernel sources were not out so I couldnt add ext3 & ext4 support to recovery. I'll try to update it as time allows.
Click to expand...
Click to collapse
i know that.. but in ext4 i couldnt take a nandroid +ext backup because the ext4 partition could not be mounted. in ext2 and ext3 i managed to do nandroid backup +ext and mount the ext partition only through adb..
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
YouArePoop said:
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
Click to expand...
Click to collapse
which version of CWM have you got?
3.0.2.4, which I've used for a while now, always tries to back up my 6GB ext2 debian partition unless I remember to change cards first. no way I leave room in the vfat partition to back up that much data.
I'll put it up on 4shared if you want it.
mihir287 said:
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
Click to expand...
Click to collapse
Guess when I get home I'll copy the contents to computer, reformat, and copy back. Hopefully link2sd will notice the formatting has changed and reset itself
Sent from my LG-VM670 using XDA App
Doesn't work with extra either. Version 3.2.0.1 I believe it was.
Guess it doesn't really matter, can just use titanium since its all app stuff on there anyways...
Sent from my LG-VM670 using XDA App
i use CWM to back up my 512MB ext2 partition for my data2ext all the time (with the rest of the backup) and it seems to have no problem, and just to check i just mounted the partition in mounts and storage and it mounts fine. I know some recoveries ive used in the past on other phones would have problems with partitions that were not in 64-128-256-512-1024 MB, etc. format because of block size issue errors that i would get (when mounting or trying to set block size to 4096). I also found that when partitoning/formatting to ext2/3/4 some programs do not properly write the drive formatting and certain systems/recoveries/apps could not properly read them on the android. the best most consistent (android friendly) formats that i have gotten to date were in ubuntu (or any other) linux using "gparted". It seemed to always be the best and usually better than the format done by the phone recovery. Hope this helps. Sorry to drone on and on.
Partitioned originally with gparted. Have since resized to be 2048, and set its label to 'sd-ext'. Now instead of getting an error saying sd-ext might not be supported on my device, it just gives me a generic 'error mounting sd-ext'
I've had ext partition mounting problems before, I'm not sure if the cause is something to do with vold or what, but
after unmounting a sd card to exchange it with another one, it changes the device partitions in /dev/block like
/dev/block/mmcblk1p2
for the sd-ext partition instead of the normal
/dev/block/mmcblk0p2
you can see if this has happened by
Code:
ls /dev/block
in adb shell.
to mount it manually, if the numbering is off,
Code:
mount /dev/block/mmcblk1p2 /sd-ext
I've only had this happen with android running, but it might work in recovery too
Switched over to using data2ext. Mounts the 2nd partition as the /data partition instead of /sd-ext. Can manually mount 2nd as /sd-ext from within rom, but it doesn't carry over to recovery.
A possible solution... Create a symbolic link pointing /sd-ext to the 2nd partition? But then again, since /data now points to 2nd partition, is recovery picking up on that unknowingly and backing up the 2nd's contents when it thinks its backing up the normal /data?
I suppose I should investigate.
Edit: Yep it does backup the 2nd partition, thankfully. Just tried to install a theme made in UOT Kitchen, it borked some stuff, and the restore worked.
Hi, i have installed a custom rom with CWM, the installation script converted system, data and cache partition to EXT4, now i want to return to stock with CWM backup but when i try the procedure e receive an error after restoring system, i think it's because EXT4 partition aren't supported by stock, how can i convert EXT4 to EXT3?
Thanks.
gdemis said:
Hi, i have installed a custom rom with CWM, the installation script converted system, data and cache partition to EXT4, now i want to return to stock with CWM backup but when i try the procedure e receive an error after restoring system, i think it's because EXT4 partition aren't supported by stock, how can i convert EXT4 to EXT3?
Thanks.
Click to expand...
Click to collapse
Open the zip of the backup you're trying to restore with a file manager. Each partition should be in there and have either an EXT3 or EXT4 filename. The recovery will automatically format the partitions based on how the backup was saved. So if /System is saved with an EXT3 extension, the recovery will format it for you. If you are getting an error then it might be a bad backup.
Also, try using fastboot to wipe everything instead of CWM. I though romracer told me fastboot always formats to EXT3, but I couldn't find the specific post/message. Won't hurt to try
I take error while restoring \system with cwm, this is the log details:
solibPhotoEditor.solibmtpstack.solibGLESv1_CM.solibmot_btpan_jni.solibnvmm_service.soliba2dp.solibWifiAPHardware.solibvpnclient_jni.sotar: write error: No space left on device
solibreverbwrapper.solibbundlewrapper.solibvisualizer.soError while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Firmware_Tim_2.3.4", "boot", "system", "data", "cache", "sd-ext")
I've been playing around with which filesystems I can format the android systems partitions and then install a custom ROM on.
I tried formatting them to F2FS and then installing a CM and Squids kernel found it wouldn't boot, then wiped them back and formatted
them to ext4 (which I think is the default android filesystem) and installed CM and Squid's kernel
and now on boot its asking me to enter a password to boot my android system.
partitions were the filesystems were changed are /system /data /cache.
I really don't want to be admitting this right now that I bjorked my system while tinker gnoming,
and don't know enough to put it back.
But yeah formatting ext4 /data /cache /system and then flashing everything back should have done it right?
Damn think I may have run into a bug in the Recovery where no matter what happens it still thinks /data is f2fs even when its been formatted back to ext4
Never mind unbricked it, I think this is the end of late night beer fueled tinkering for me, but I've restored the system.
Should TWRP have been able to format /data to another filesystem besides ext4 or f2fs and which filesystem was the
default on /data from the beginning?
The recovery system seemed to assume that /data was F2FS and even after trying to format it with something different
the repair tool ran was always the F2FS one and always dropped some error messages even after a format to Ext4.
This whole project started when I got the 'good idea' into my head to see if I could format all the partitions that mattered with
F2FS and flash CM 12.1 R53 with Squid's R8 with the partitions formatted F2FS.
Eh I'm done shooting myself in the foot for awhile (or the ass).
Ended with /system (ext4), /data (f2fs), /cache (ext4) and then flashed everything and the system is running great.
The whole experience was worth getting more familiar with TWRP and learning that it is built noob 'tough'.
And can perform awesome awesome surgery for you, when your done shooting your self in the ass.
By the way bro... I think the data partition on this phone comes in f2fs by default
Sent from my MotoE2(4G-LTE) using Tapatalk
I have the same issue!
Fishy.. why in the hell would you do that unless you *found* a phone
and were then trying like a noob to reformat it ?
Hi all.
I'm trying to make a last backup of the stock Android of my Swift 2x before flashing LineageOS. But TWRP (version 3.3.0-0) Seems unable to use the /data partition. I got various messages like:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid Argument)
I tried to format the partition: Wipe -> advanced wipe -> repair or change filesystem -> change filesystem -> ext4 but it didn't change anything.
What's wrong? What can I do?
Thanks a lot for any hint.
bumping this thread as I also ran into this issue.
When using TWRP, the data and system partitions can't be mounted. they also show up as being 0mb in size.
Because of this, no backups can be made and a full system wipe also yields errors.
What I did was change the filesystem to ext2 and then change it back again to ext4.
Doing this at least allowed me to flash crdroid, but making backups still doesn't work.
Whenever i go into TWRP again, it's the same thing again: unable to mount and partitions show up as 0 mb in size.
Anyone know what's causing this?
Wileyfox encrypts there data when you factory reset your device or after youve rooted your device .To get around this you need to do a factory reset using stock recovery once thats done then turn off the device. Then using minimum adb and fastboot type (fastboot boot twrp.img) that will boot your already installed twrp now erase data internal storage etc you'll notice you can finally delete stock os youll see internal storage is showing mbs available again etc worked for me perfectly.