Develop Bugs

[Q]E:format_volume: make_extf4fs failed on /dev/block/stl13

Hi guys,
Newbie to the forum and android just need a bit of help as im pretty stuck at the moment and i dont know whats gone wrong.
I wanted to install Jelly Bread v5.0 or something other that the restricted phone carrier os on my phone when i got it (i wont mention just incase) so heres what i did.
rooted the phone using an update.zip from on this forum somewhere.
installed: signed_cwm-5.0.2.7-flashablezip-ext4only.zip
then installed: Jelly Bread v5.0
was ok for a while and working but then i wanted to play with other ROMS (in this case i now wanted to try cm-10.1.4-GT-S5660-gio++.zip)
I enter recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, wipe batt stats
Then install cm-10.1.4-GT-S5660-gio++.zip
Then it hung for 35mins at loading blue circle screen.
I then took battery out and enter recovery, and attempt to wipe data/fatory reset and it says:
--Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/stl13
Formatting /Cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/ .android secure...
Data wipe complete
Also i cant wipe dalvik cache it just does nothing blinks 1 second then back to menu.
From here (silly me i forgot to backup) ive tried to flash a few stock roms but still getting boot loops and the same above errors.
Is there any way i can format and write /data and /sd-ext?
Anyone know what i can do to fix this please?
Thanks for any help in advance.

update
Hi guys,
Just an update.. have tried several stock ROMS via ODIN always flashing CWM and flashing custom ROMS but nothing with flash and reformat the /dev/stl13 block. im always getting this error and i believe its causing my boot loop issues.
I found this thread via google:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
is there anybody on here that could guide me through using ADB shell to rebuild/reformat the /dev/stl13 block?
I dont feel confident enough to do it. (Have already installed shell on my laptop though)
This is driving me crazy trying to fix. My first android ROM flash gone wrong
(i got it working fine with Jellybread but wanted to try something else)
Any help appreciated.
Cheers
Richie

Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?

AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456

Darkshado said:
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
Click to expand...
Click to collapse
Hey dude,
Thanks for the reply.
I have tried flashing back to stock (latest from samfirmware) and it still wont let me mount data.
Although its giving me my orignial load screen (my carrier) but still boot loops.
Ive tried look for another stock ROM i can use but alot of the links are down/broke or withdrawn etc.
I note with stock recovery i just can't mount data but after i install CWM 5.0.2.7 ext4 only it cannot format ext to block stl13.
Could this possibly mean that my internal memory has failed or it just needs to be repartitioned?
Will continue to look for another stock rom that can hopefully fix the problem.

You don't care about the errors failing to mount in the stock recovery. It's expected since it isn't set to work with an ext4 partition.
Just run the format operations from the stock recovery.
Most "stock" ROMs released here were made to run on ext4 since performance was that much better and most CWMs built also run ext4, unless explicitly stated to run RFS.
I can't think of any tools to repartition the Gio, otherwise we would have been all over it back in the day to solve the /system space shortage.

Harakhti said:
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Click to expand...
Click to collapse
Do you suggest to flash stock via Odin?
And then correct me if im wrong but to get to CM10,1 i go in this order after a stock flash:
1. Install CWM 6.0.3.2
2. run ext formatter
3. install ROM (in this case CM10.1??
Cheers for any help in advance.
Im quite new to Android.. but not new to flashing etc (BIOS, PSP's other devices etc) but this is my first android phone and i didnt like the Phone Carrier custom ROM and network lock. So attempted to try something else. Got Jellybread running fine but decided to have a look around. And now im phone less (well not really using my old nokia n97) but it is sooo painful! lol

I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app

Darkshado said:
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Click to expand...
Click to collapse
Sorry man i had not read your reply before my previous post.
As stated in my previous post, I have flashed 2 stock ROM's from samfirmware via Odin and it passes.
On one of the ROMS (an NZ ROM) it gives me the error: E:format_Volume: rfs format failed on /dev/stl13
On the other ROM (The Aus ROM) it gives me the error: Unable to mount /data
On both im getting boot loop.

If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.

Darkshado said:
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Click to expand...
Click to collapse
It formats the /cache partitions just not the /data as it cant mount it.
Warranty service? I will have to pay? as i have bought the phone 2nd hand and i dont think its under warranty.
I did see the other post and have downloaded "Samsung GT-S5660M Galaxy Gio - RFS format data and cache partition images to dd back into place"
But i cannot find the post again with the directions. Also when pushing these images from the SD card am i meant to be in stock recovery or RFS CWM?
Cheers Darkshado for all the help so far.

I had the explanation right below that download link here and a more detailed one here.

hmm doesn't look good eh?

Darkshado said:
I had the explanation right below that download link here and a more detailed one here.
Click to expand...
Click to collapse
Could it possibly be a physical hardware failure?

Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado

you can install a rom after downloading and flashing ext4 formatter.zip

Darkshado said:
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
Click to expand...
Click to collapse
Have been extremely busy with other projects and work lately and haven't had net the past week (so painful!)
but otherwise latest results are attached. Can you make anything of it? Does this look normal?
Cheers again.
Richie

Looks normal at first glance, though I don't have a Gio to compare with.
You could try and dig into how these phones are partitioned exactly and go from there, but you'll probably be on your own since most people who were interested in early MSM7227 devices have moved on.
Unless the underlying memory is defective, it's possible your only option left at this point is to try a JTAG repair.
However, depending on how much you'd be charged for such an operation locally, and taking into consideration the value of your typical used Gio (I've seen them go for 50$CAD in local classifieds)... You're probably better off cutting your losses and getting another phone.
Good luck,
Darkshado
Sent from my SGH-T889V using xda app-developers app

[Q] TWRP Restored Successfully On /Data(f2fs) But Device Won't Boot.

Hi guys,
I am getting interested in these ROM flashing things recently, so I backed up /System /Data /Boot by TWRP after I installed all apps I want.
Just today, I tried to restore from one of my backups but couldn't get it work. CM12 just stuck on the boot animation screen forever.
The backup & restore processes were all perfect without any error, the MD5 also matched.
Here are some basic facts I made:
1. I wiped /System /Data /Cache /D-Cache before restoring.
2. I wiped /Cache /D-Cache after restoring.
3. Reflasing kernel -> NO change
4. Reflashing /System /GApps -> NO change
5. Fix Permission ->NO change
6. Wipe /Data = CAN boot
7. Restoring from another backup -> NO change
So clearly there is something wrong with /Data.
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
[Spec]
Nexus 7 2013 WIFI(flo)
TWRP 2.8.6
Kernel Glitch for Flo/Deb - r320
(No overlock, No additional drivers)
CM12 Nightly 20150405
gapps itvends.com/gapps/gapps-lp-20141212-signed.zip
/Data /Cache=f2fs
/System = ext4

akipapa said:
Hi guys,
I am getting interested in these ROM flashing things recently, so I backed up /System /Data /Boot by TWRP after I installed all apps I want.
Just today, I tried to restore from one of my backups but couldn't get it work. CM12 just stuck on the boot animation screen forever.
The backup & restore processes were all perfect without any error, the MD5 also matched.
Here are some basic facts I made:
1. I wiped /System /Data /Cache /D-Cache before restoring.
2. I wiped /Cache /D-Cache after restoring.
3. Reflasing kernel -> NO change
4. Reflashing /System /GApps -> NO change
5. Fix Permission ->NO change
6 Wipe /Data = CAN boot
So clearly there is something wrong with /Data.
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
[Spec]
Nexus 7 2013 WIFI(flo)
TWRP 2.8.6
Kernel Glitch for Flo/Deb - r320
(No overlock, No additional drivers)
CM12 Nightly 20150405
gapps itvends.com/gapps/gapps-lp-20141212-signed.zip
/Data /Cache=f2fs
/System = ext4
Click to expand...
Click to collapse
Without restoring data, it boots up properly?

Thanks for your reply.
I didn't try that, but I tried to wipe /data(not format) after restoring, and it booted fine.

akipapa said:
Thanks for your reply.
I didn't try that, but I tried to wipe /data(not format) after restoring, and it booted fine.
Click to expand...
Click to collapse
Your wlcm... And u can always press that thanks button if I helped...

akipapa said:
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
Click to expand...
Click to collapse
I see that you changed your file system to f2fs.
Did you flash a modified TWRP to support the new file system after changing it?
Sent from my Canvas Turbo using Tapatalk ^~^

User17745 said:
I see that you changed your file system to f2fs.
Did you flash a modified TWRP to support the new file system after changing it?
Sent from my Canvas Turbo using Tapatalk ^~^
Click to expand...
Click to collapse
I thought twrp2.8.6 supports f2fs because I could format f2fs and browse f2fs /data with its file manager.
Does it need further modifications?

akipapa said:
I thought twrp2.8.6 supports f2fs because I could format f2fs and browse f2fs /data with its file manager.
Does it need further modifications?
Click to expand...
Click to collapse
I looked up on the internet and it seems that it does support f2fs.
What about the kernel, does your kernel support it?
I guess if you were using the same kernel earlier with f2fs then kernel should also not be the problem here.
Maybe it's just a faulty backup.
I don't know much about f2fs myself.
Maybe you should contact someone who does.
Sent from my Canvas Turbo using Tapatalk ^~^

User17745 said:
I looked up on the internet and it seems that it does support f2fs.
What about the kernel, does your kernel support it?
I guess if you were using the same kernel earlier with f2fs then kernel should also not be the problem here.
Maybe it's just a faulty backup.
I don't know much about f2fs myself.
Maybe you should contact someone who does.
Sent from my Canvas Turbo using Tapatalk ^~^
Click to expand...
Click to collapse
I'm sure this is not about kernel, because I tried restore /boot and reflash the kernel.
Besides the kernel that I use works fine with f2fs.
I also tried to restore another backup with no luck, maybe they both were faulty...

akipapa said:
I'm sure this is not about kernel, because I tried restore /boot and reflash the kernel.
Besides the kernel that I use works fine with f2fs.
I also tried to restore another backup with no luck, maybe they both were faulty...
Click to expand...
Click to collapse
You mean 2 backups with faulty data partition?
That's highly unlikely to happen.
When you took those backups, did TWRP showed any error?
Sent from my Canvas Turbo using Tapatalk ^~^

akipapa said:
Hi guys,
I am getting interested in these ROM flashing things recently, so I backed up /System /Data /Boot by TWRP after I installed all apps I want.
Just today, I tried to restore from one of my backups but couldn't get it work. CM12 just stuck on the boot animation screen forever.
The backup & restore processes were all perfect without any error, the MD5 also matched.
Here are some basic facts I made:
1. I wiped /System /Data /Cache /D-Cache before restoring.
2. I wiped /Cache /D-Cache after restoring.
3. Reflasing kernel -> NO change
4. Reflashing /System /GApps -> NO change
5. Fix Permission ->NO change
6. Wipe /Data = CAN boot
7. Restoring from another backup -> NO change
So clearly there is something wrong with /Data.
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
[Spec]
Nexus 7 2013 WIFI(flo)
TWRP 2.8.6
Kernel Glitch for Flo/Deb - r320
(No overlock, No additional drivers)
CM12 Nightly 20150405
gapps itvends.com/gapps/gapps-lp-20141212-signed.zip
/Data /Cache=f2fs
/System = ext4
Click to expand...
Click to collapse
I read that the last CM nightlies got some sort of new compression implemented and that's why there's problems with restoring data. You'll have to wait for the TWRP creator to repair it

matcho13579 said:
I read that the last CM nightlies got some sort of new compression implemented and that's why there's problems with restoring data. You'll have to wait for the TWRP creator to repair it
Click to expand...
Click to collapse
That explains everything, thanks for the information.

akipapa said:
That explains everything, thanks for the information.
Click to expand...
Click to collapse
I'm glad I helped

same issue here
falcon, cm12.1 20/04 , twrp

[Tutorial] how to format data & cache from ext4 to f2fs (cm12.1)

Maybe there is someone who do not know how to format the data and cache partition to f2fs (cm12.1 only), so I create this thread. Hope this tutorial can help.
The first step, copy the file mkfs.f2fs from /sbin to /external-sd (recommended). You can use file manager like root Explorer for example.
The second step, reboot the device into recovery mode(twrp recovery), copy back the files mkfs.f2fs from /external-sd into the /sbin
Step three, in the recovery mode, select wipe> advanced wipe> checklist cache> fs option > change fs> and click f2fs and Swipe for change. (if you don't see f2fs buttons, you must have a custom theme for twrp, or reload your themes to make f2fs button is visible. @vbvn thank's for your tips bro).
Repeat the same steps for the data partition.
And yeah,,, now you have data and cache partition in the f2fs formats...
Don't forget to backup Internal sd to safe your data (like a photos or mp3 for example).
For more detailed step, you can ask Google for it.
Greetings.
Sorry for my bad English

Screenshot

Thanks, that worked. I got the option for F2FS immediately after copying the file, though I have to copy it every time I have to format the partition else it says binary not found.

Good tip op. Also one can do a nandroid on data. Once cache and data has been converted you can restore data and reboot.
Sent from my HM 1SW using Tapatalk

What r the benefits of f2fs file system?
Sent from my HM 1SW using Tapatalk

kuldeepraj said:
What r the benefits of f2fs file system?
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
Short version, it makes your phone fast.

does the stock MIUI or developer MIUI ROM support this type of formatting?

!Aman! said:
does the stock MIUI or developer MIUI ROM support this type of formatting?
Click to expand...
Click to collapse
Don't think so.

No it doesn't. And MUI will not read ext4 for you ext card either.
Sent from my HM 1S using Tapatalk

Can I use this method to format only system partition , will it be effective
Because I use dual boot and secondary ROM is miui v5
Thanks
Sent from my HM 1SW using xda Forum

as9333 said:
Can I use this method to format only system partition , will it be effective
Because I use dual boot and secondary ROM is miui v5
Thanks
Sent from my HM 1SW using xda Forum
Click to expand...
Click to collapse
1. Yes, you can use this method to format /system.
2. As /system is read only, and F2FS doesn't really improve read speed, it won't be effective.
3. I haven't tested this, but I have seen no reports or have no reasons to believe miui supports F2FS.
There goes your answers. For next time, please read the thread, and use this little thing called Google. I've heard it's kinda awesome.

Will it work ?????
If i format system to f2fs, will the rom work ??

TheMightyDeep said:
If i format system to f2fs, will the rom work ??
Click to expand...
Click to collapse
Any armani-dev based ROM should work just fine. Which is, almost every source based custom room out there.

the rom is working but it's waaay to slow, please how to revert back?

Berinjo said:
the rom is working but it's waaay to slow, please how to revert back?
Click to expand...
Click to collapse
Just the way you formatted to F2FS. Except this time, select EXT4.

Thnx for the guide @ippatt
Tip:-
no need to install additional theme. after copying file to sbin, just use "reload theme" option and F2FS option becomes visible...
OP may be updated with this tip.. thanks.

vbvn said:
Thnx for the guide @ippatt
Tip:-
no need to install additional theme. after copying file to sbin, just use "reload theme" option and F2FS option becomes visible...
OP may be updated with this tip.. thanks.
Click to expand...
Click to collapse
Thank's @vbvn,will be updated soon... :thumbup:

So I just have to do this for /cache and /data, and that will wipe data and cache, right ? Or will that wipe external / internal SD card as well?
I can just backup my data using titanium and do this procedure and just restore the data ?
Sent from my HM 1SW using Tapatalk

i think ijust had an bootloop after formating to f2fs, how to fix it??
Edit: just fixed, i had to pull out my baterry twice & now boot perfectly & FAST....)
Edit Again: seem to be if i flash exposed framework from twrp it ended up bootlop at reboot system, gues exposed hasn't fully support of f2fs or maybe there is something wrong with my phone, mcurrently my phone work fastly after flash CM12.1 R18+GAPPS+SuperSU 2.46

@ippatt
Nice tuts. F2FS menu comes out after I copied the mkfs using the TWRP Recovery's File Manager. The only problem is, why did I get the log "E:Unable to mount /cache" after formatting the /cache into F2FS? This happens with the /data too. "E:Unable to mount /data". What went wrong? :S

Problems after Updates and Wipes

Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!

You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.

Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.

Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.

cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far

Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.

Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.

jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:

Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).

cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!

Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.

cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!

Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks

[FLASHABLE_SCRIPT][UPDATED_ERRORS FIXED] Increase system space to 1.2/2GB [15/7/2017]

-By following this you can can increase /system space from default 800MB to 1.2GB/2GB
-You can flash gapps on CM ROMs without insufficient space issue.
-You can flash regular MIUI ROMs too,without any issue.
Statutory warning
*Repartition can kill your phone forever if anything goes wrong,so proceed with caution (and make sure you have at least 30% battery)
*This process would format your internal sdcard,backup its contents
*I'm not responsible If your phone dies during this procedure under any circumstances beyond control
Prerequisites:
1)Redmi 1s partition script_system space 1.2GB.zip/2GB.zip
2)Parted
3)Twrp v3.0.2-1.zip
4)Download and copy all these files to external sdcard
Procedure:
1)Flash Twrp recovery(incase if aren't already using it).
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manager for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Redmi 1s partition script_system space 1.2GB.zip/2GB.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)Install your ROM(don't flash gapps now).
9)Back again to Twrp start screen select "Wipe"-->Advanced wipe-->select/mark "System"-->press "Repair or change file system(notice that size hasn't increased to 1.2GB/2GB)-->Resize file system.
10)Back(though size of partition appears unchanged, its actually increased to 1.2GB)-->Back>select/mark"System"-->Repair or change file system-->Notice size of partition increased.
10)Back to Twrp start screen and flash gapps,that's it.
Reset to default partition:
1)I am also giving link for flashabe script file "Reset to default partition.zip" for restoring default partition sizes.
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manage for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Reset to default partition.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)that's it you are back to default partition.
PS:
1.Need for "Resizing System partition"(step 9) comes only with CM14.1(haven't tried other CM versions or other custom roms) no need to do that if you are flasing MIUI ROMs(i,e you can skip step 9 if you are flashing MIUI ROMs)
2.If you still need more System space or want to further modify partition table(only if you know what you are doing),you can edit "update-binary" file inside the zip as per your needs.
Credits:
1)forumber2_ Samsung Galaxy S III.
2)slst_for his valuable input.
3)owaisnaim & fefifofum Twrp for redmi 1s.
Downloads:
1)parted:https://drive.google.com/folderview?id=0B6_hhjS3nx4IU05yLVc2Mk9uOEk
2)Repartition script Redmi 1s_1.2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRkJFZzAtMjZEa2s
3)Repartition script Redmi 1s_2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRXlDZUU1cEJ3Smc
4)Reset to default partition:https://drive.google.com/folderview?id=0B6_hhjS3nx4IeGtXb0liazdLWVk
5)TWRP 3.0.2-1.zip:https://drive.google.com/folderview?id=0B6_hhjS3nx4IdzFHXzdfNXVCYm8

good work mate

Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk

vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
no you just have to go to
wipe >mark on system>click repartition
go back you can see system size 1.2gb

after doing this can i flash latest twrp ?

vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there

vinayak.ghimire said:
after doing this can i flash latest twrp ?
Click to expand...
Click to collapse
Ya you can.

and whats the size of userdata and cache partition ?

vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Based upon the scenario, the only concern is the system partition coz newer or update partition is too large. Cache partition is ok because it only use as a temp file partition. The userdata partition is large as internal storage because it shared as the same partition. That is the good thing at xiaomi phones, data partition is large as long as you have space in internal storage.
Sent from my HM 1SW using Tapatalk

vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Install diskinfo app and check

Thanks for the script. It will help us a lot in now and in future also.
I know, i am asking too much. I bet we all are from developers but I will be very glad if you can provide me link of flashable file of TWRP and philz recovery 6.55.
Thanks Loads.

Anyone have checked this tutorial working ??

I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp

Here is screenshot

apoorvpandey41 said:
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Click to expand...
Click to collapse
Thanks mate appreciated.

Thanks man works perfectly fine. Awesome tutorial.

Guys please help me:
Today morning I reparationed my Redmi 1s as the Op said. it went successful. after using for 5hours I've found an update from CM. So I updated using CM UPDATER APP. after reboot I've lost my Google play store and Google app (after updating to todays CM update using CM UPDATER APP). When I went to see the system partition size, it's size went back to the default 782mb (around 782mb, I don't remember exact size).
I checked whether it is disabled or what in apps. But I can't find there also. I tried Show system apps and reset app preferences, but nothing showed them.
I tried to get them back (play store and Google app) by resizing the partition to 1.2 gb (wipe>advanced wipe> Mark system>change or resize partition>back> checked system partition size whether 1.2gb or not>wipe cache and dalvik cache> reboot to system). But nothing worked.
So please help me in getting them back. Please exclude solution such as factory reset or flash gaggs again.
Is anybody else also facing the same issue or it's just me?:crying::crying::crying:

freeshared said:
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
Click to expand...
Click to collapse
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition

sharathe100111 said:
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
Click to expand...
Click to collapse
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.

freeshared said:
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
Click to expand...
Click to collapse
Thank you brother for your reply. Now i am on miui as i am not being able to go to CM14 anymore. But i can flash CM11. (it seems i can use only kitkat).
Here are the screenshots: for MOUNT, ADVANCED WIPE, CACHE, SYSTEM, DATA. And problem struck on patching system image unconditionally