After installing TWRP and changing file system of /data to EXT2 & EXT4, I can't boot the system (Boot loop?). I can still open up TWRP though. Not sure what to do to fix it.
Device: Nextbook Ares 11a (NXA116QC164)
Edit: New thread here. <<<
Try format . Wipe dalvik cache / cache / data
resty1 said:
After installing TWRP and changing file system of /data to EXT2 & EXT4, I can't boot the system (Boot loop?). I can still open up TWRP though. Not sure what to do to fix it.
Device: Nextbook Ares 11a (NXA116QC164)
Click to expand...
Click to collapse
What method do you use for flashing twrp recovery?
Not all devices use ext4. Are you sure this one does?
Related
It first started when I flashed an ICS rom. Thereafter I have been unable to get working any other roms. I read somewhere that I need to format /system /boot /cache /data partitions. /boot makes sense because any other rom that I flash hangs on the HTC splash screen. But here is my problem, I cannot find an option in TWRP 2.0 for formatting /boot. I have flashed CWM 4.0.1.4 and same thing, no option for format /boot. How can I format /boot?
the superwipe ZIPs that are floating around the forum should be able to do it, alternatively, I think it can also be done from fastboot, somebody who knows more than me should be able to confirm it.
The fastboot command to erase boot is:
Code:
fastboot erase boot
But i dont know why you should have to do all that. Should be sufficient to clear data and flash a new rom, they all include boot.img files.
Eighteen90 said:
It first started when I flashed an ICS rom. Thereafter I have been unable to get working any other roms. I read somewhere that I need to format /system /boot /cache /data partitions. /boot makes sense because any other rom that I flash hangs on the HTC splash screen. But here is my problem, I cannot find an option in TWRP 2.0 for formatting /boot. I have flashed CWM 4.0.1.4 and same thing, no option for format /boot. How can I format /boot?
Click to expand...
Click to collapse
Flash CWM 5.0.2.0 via ROM Manager and you can wipe your boot partition from there. Just please do be careful, formatting boot is NEVER usually a good idea unless the partition has become corrupt. Have you tried wiping dalvik cache along with system, data, cache, and battery stats? I'd give that a try beforehand. Good luck, mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
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")
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 !
Hi, after have done all the procedures for unencrypt phone and root, I've found to be in this situation:
- data partition: F2FS
- cache partition: EXT4
I don't know if data partition was EXT4 or F2FS on stock, but probably it has been converted to F2FS by TWRP when I formatted it to unencrypt the phone (after kernel patch applied...).
My questions are:
1) is this your situation?
2) Is it safe on stock kernel/ROM to convert to F2FS the cache partition too?
3) In case what is the safest mode to do it without data losses?
@erfanoabdi?
enetec said:
Hi, after have done all the procedures for unencrypt phone and root, I've found to be in this situation:
- data partition: F2FS
- cache partition: EXT4
I don't know if data partition was EXT4 or F2FS on stock, but probably it has been converted to F2FS by TWRP when I formatted it to unencrypt the phone (after kernel patch applied...).
My questions are:
1) is this your situation?
2) Is it safe on stock kernel/ROM to convert to F2FS the cache partition too?
3) In case what is the safest mode to do it without data losses?
Click to expand...
Click to collapse
Hi again
Actually disabling force encryption won't change file systems
Disabling Force encryption is changing "forceencrypt" to "encryptable" in qcom.fstab file at boot partition
So Motorola Official devices have same file system as you said you have in your phone:
- data partition: F2FS
- cache partition: EXT4
And about wiping data partition after disabling,
We have to wipe it because this partition is encrypted by default and we just changed "forceencrypt" to "encryptable" so if we want to read and write access on TWRP or ... For root, Xposed and any related zip flashing we have to wipe data to make it unencrypted to do all of them
Why you want to change Cache partition file system ??
If you change it Cache partition won't detect any more, don't play with file system this may brick your device
All (already) clear what I've removed...
erfanoabdi said:
So Motorola Official devices have same file system as you said you have in your phone:
- data partition: F2FS
- cache partition: EXT4
...
Why you want to change Cache partition file system ??
If you change it Cache partition won't detect any more, don't play with file system this may brick your device
Click to expand...
Click to collapse
Because F2FS is reported to be faster. Are you sure that a ROM capable of using it on /data can't use it on /cache?
enetec said:
All (already) clear what I've removed...
Because F2FS is reported to be faster. Are you sure that a ROM capable of using it on /data can't use it on /cache?
Click to expand...
Click to collapse
Oh ok it's faster but not too much
If you want to use it on Cache partition
I think you have to compile and build new rom
Or maybe with editing qcom.fstab it's gonna be alright
I've never did it before sorry I don't know very much
erfanoabdi said:
Oh ok it's faster but not too much
If you want to use it on Cache partition
I think you have to compile and build new rom
Or maybe with editing qcom.fstab it's gonna be alright
I've never did it before sorry I don't know very much
Click to expand...
Click to collapse
Than anyway! :fingers-crossed:
Im using Moto E 1st generation, Bootloader unlocked with TWRP custom recovery. I was using custom rom Marshmallow by Temasek and I thought to change the rom. Recently, I upgraded TWRP to 3.0.2-0.
I have wiped system, dalvik, internal storage, cache and data everything went smoothly.
when i tried to install Rom zip i encounter and error that causing boot loop.
HTML:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name system at /system: invalid argument
unmount of /system failed : no such volume
Patching system image unconditionally ...
flashing Supersu..
scripting succeed result was []
update partition details
...done
when i reboot, my phone goes in boot loop.
i tried with repair or change file system but still the error is same
my file system and format
/system ext4
/Data ext4
/cache ext4
Please Help to recover my mobile thank you...
flash the stock firmware, some times it fix this issues.
flash the stock firmware without flashing the recovery partition, and flash again twrp to avoid any issue, then flash temasek