Develop Bugs

[TOOL][CWM] Aroma Wiper and formatter 2.0 - Faster and easier wipes and downgrades

:::: Description ::::
This is a tool inspired on hsrars-d`s Defy Ultimate Wipe™ zips, which i use a lot. The only problem is that there are 6 diferent zips to flash...
So i decided to improve this by making 1 zip with aroma installer and all the 6 wipers included, also with a formatter to downgrade to Gingerbread.
:::: Features ::::
-Select your file system (ext3 or ext4)
-Select desired wipe profile:
Cache/Dalvik
Data and Cache/Dalvik
Everything (System, data and cache) <---- DO NOT REBOOT AFTER USING THIS OR YOU'LL NEED TO FLASH SBF
-Fast and easy interface. Faster than using recovery menus.
-NEW (2.0) Format to Ext3 without using bootmenu to easy downgrade from Jelly Bean to Gingerbread
:::: How to use it ::::
Download the zip and save it on your SD card
Flash it via CWM
:::: Download ::::
Mediafire
Google Drive
Uncledan (thanks for mirroring)
:::: FAQ ::::
How do i downgrade from Jelly Bean to Gingerbread? i like the speedz
Click to expand...
Click to collapse
Copy the Gingerbread rom that you like and Aroma wiper zips to your SD card, then reboot into recovery and flash Aroma wiper. Select "Ext3 - format & wipe" and exit. Now without robooting, flash the rom. Its not necessary to do any wipe, aroma wiper already did it. Thats all
If i select only wipe the partitions are formated?
Click to expand...
Click to collapse
No, they will be only wiped, no formating. e.g you are on Jelly Bean (which is ext4) and you do an ext4 wipe, then you will still be on ext4.
Thanks to hsrars-d for the idea and amarullz for aroma installer :highfive:
Also thanks to Uncledan for mirroring
Happy Flashing!

after wiping ext4 do i need to convert ex4 to ext 3 for CM7 or miui
from CM10

Anands3 said:
after wiping ext4 do i need to convert ex4 to ext 3 for CM7 or miui
from CM10
Click to expand...
Click to collapse
Exactly. Thats the correct way.:good:

Re: [TOOL][CWM] Aroma Wiper for Defy/Defy+ - Faster and easier wipes
Just to be clear, if I want to switch FROM a jb rom TO a jb rom, I have to use the ext4 wipes, is that right?
Sent from my LT30p using xda app-developers app

Roshan_P said:
Just to be clear, if I want to switch FROM a jb rom TO a jb rom, I have to use the ext4 wipes, is that right?
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
Exactly. :good:

mato_d007 said:
:::: Description::::
This is a tool inspired on hsrars-d`s Defy Ultimate Wipe™ zips, which i use a lot. The only problem is that there are 6 diferent zips to flash...
So i decided to improve this by making 1 zip with aroma installer and all the 6 wipers included.
::::Features::::
-Select your file system (ext3 or ext4)
-Select desired wipe profile:
Cache/Dalvik
Data and Cache/Dalvik
Everything (System, data and cache) <---- DO NOT REBOOT AFTER USING THIS OR YOU'LL NEED TO FLASH SBF
-Fast and easy interface. Faster than using recovery menus.
::::How to use it::::
Download the zip and save it on your SD card
Flash it via CWM
Important: this tool will not change your data and cache format. If you are on Ext4 and you do a wipe, you will still be on Ext4, same goes for Ext3
:::: Download::::
Google Drive (Cick on file->Download)
Mediafire
Thanks to hsrars-d for the idea and amarullz for aroma installer :highfive:
Happy Flashing!
Click to expand...
Click to collapse
Hello,
is it possible to convert the zip package to sbf? My defy's power button does't function, and i need to wipe. Please help me...

miim113 said:
Hello,
is it possible to convert the zip package to sbf? My defy's power button does't function, and i need to wipe. Please help me...
Click to expand...
Click to collapse
I have no idea tbh, this is an aroma installer zip, not a regular flashable zip so im not sure. Also i never did that kind of conversion but i will do some research.

Re: [TOOL][CWM] Aroma Wiper for Defy/Defy+ - Faster and easier wipes
miim113 said:
Hello,
is it possible to convert the zip package to sbf? My defy's power button does't function, and i need to wipe. Please help me...
Click to expand...
Click to collapse
If your volume up down buttons and the capacitive buttons are working fine, you should not have any problem choosing any option in the "custom" recovery. Use the extreme left capacitive button i.e. the one to the left of the home button, to select the option (which is usually done using the power button, but I prefer using capacitive buttons).
If you can get into the bootmenu, choose custom recovery and you should be able to wipe or flash with no problems.
Sent from my LT30p using xda app-developers app

AW: [TOOL][CWM] Aroma Wiper for Defy/Defy+ - Faster and easier wipes
If the stock wiper format 'data to ext3...' in bootmenu of quarx jb is working corret we can use this , if we want to go to cm7
If you think if there is somthing wrong with your system partition because of stange bugs like no gsm or no wifi you could wipe the system with this tools
And i think sometimes there is no other way just flash stock sbf from moto to get things work.
MB525 red lense

New version
New version replaces the old one. Now you can also format to ext3 without entering to bootmenu :laugh:
Instructions and FAQ added, please read the first post.
I need some feedback, tell me if everything is working for you guys.

When I did a full wipe (using the first version) it showed that the installation was aborted, I saved the logs and realized that the sd card wasn't mounted. I'd suggest you add a disclaimer in the OP to mount the sdcard before using this tool.
Otherwise, it works perfectly alright! It's quite convenient to have aroma installer for wiping! Thank you for you work, mato.:thumbup:
Will definitely try the new wiper when you upload a new build of xperia D(take your time )
EDIT: OK So I decided to reflash Xperia D 3.5 to try some other features(nothing major just the keyboard, camera).
First thing I noticed about the 2.0 wiper is that it still shows 1.0 in the aroma installer at some places but that isn't an important issue.
THE issue was this: I did a full wipe and saved the logs, flashed the ROM and the first thing I checked when it booted was the logs. It showed that the mounting was unsuccessful.
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Aroma Wiper & formatter for Defy
ROM Version : 1.0
ROM Author : mato_d007
Device : Motorola Defy/Defy+
Start at : Sun Mar 31 19:04:46 2013
*****************************************************
* Aroma Wiper & formatter for Motorola Defy/Defy+ *
*****************************************************
Ext4 wipe selected
Mounting
mount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
************************************************
Wiping Data and Cache
************************************************
Finished
script result was [Finished]
Installer Sucessfull (Status 0)
End at : Sun Mar 31 19:04:46 2013
Click to expand...
Click to collapse
So I again rebooted into the recovery, mounted sd card, flashed Aroma wiper 2.0, wiped the system and then flashed Xperia 3.5. When I reached "installation type" I wasn't able to select any option. :|
Ofcourse since I had wiped the system, I had to flash the sbf and start from scratch. This time I wiped from the ROM zip itself.. and have no issues.
I hope this helps!
Sent from my MB526 using xda app-developers app

Can anybody please confirm that the scripts do not cause any problems? I just want to be sure before using this again.. :/
Sent from my MB526 using xda app-developers app

Dont worry about the mount warnings, the script does not need sdcard mounted since it only wipes /system, /data and /cache. Thanks for the feedback, i will fix the wrong version number asap.

miim113 said:
Hello,
is it possible to convert the zip package to sbf? My defy's power button does't function, and i need to wipe. Please help me...
Click to expand...
Click to collapse
if ur power button is not working then u can simply use ur menu button instead of power button that is the first the button toward ur left side (the one with small 4 boxes).
cheersss :victory:

one doubt
i m on cm10 with custim kernel 2.6.32.60...now i want to install cm7.2... steps here mentioned is "reboot into recovery and flash Aroma wiper. Select "Ext3 - format & wipe" and exit. Now without robooting, flash the rom"
now my question is do i need to flash froyo kernel after flashing CM7.2 rom????
and btw i have defy mb525 red lense

No need to reflash kernel if that was the one you had before flashing cm10
Sent from my MB526 using xda premium

thekguy said:
No need to reflash kernel if that was the one you had before flashing cm10
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
thanks dude... works great...

Help!! Network
Olá. Realizei todos os procedimentos, ficou rápido, moderno e bem elegante a ROM. Porém meu celular não funciona rede (chamadas, mensagens, internet 3G/2G) Aliás. Nenhuma outra ROM além da original (2.3.5 BR) funciona a rede. Por favor me ajudem, não quero ficar com a ROM original.
[Original em Portugês, Traduzido para Inglês - GooGLe Translate]

great tool, thanks mato_d007!!

Amazing tool, so useful!! :good:
Thank you :highfive:

[armani]CWM PhilZ Touch for RedMI 1S

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI.
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut.
Install instructions:
1.With fastboot:
Extract philz_touch_*.*.*_armani.img from philz_touch_*.*.*_armani.img.tar
Run fastboot
Code:
fasboot flash recovery philz_touch_*.*.*_armani.img
2.With MiRecovery using flashable zip:
Copy philz_touch_*.*.*_armani.zip in root of internal storage
Rename it to update.zip.
Enter into recovery (volume up + power)
Install update.zip from sdcard.
Reboot.
3.With CWM or TWRP using flashable zip:
Copy philz_touch_*.*.*_armani.zip in root of external sd card
Enter into recovery (volume up + power)
Install zip from sdcard.
Reboot.
Known Issues:
Mount USB Storage don't work.
XDA:DevDB Information
[RECOVERY][ARMANI][RedMi 1S]CWM PhilZ Touch, Tool/Utility for the XIAOMI REDMI 1S
Contributors
juliusssss,Phil3759
Version Information
Status: Stable
Created 2014-08-12
Last Updated 2014-08-12

thank you juliuss, really really awesome work. and phil too. I have been using your TWRP but this is the best. great work.

Thanks... will try it out and give feedback.

Amazing work , used this to install the unofficial CM11 build on my Redmi 1S !!

I am unable to flash zip file with mi recovery. It always gives error no zip found in internal storage.please rename file as update zip and try again. I have already renamed file as update.zip after downloading it.I have zip file in internal storage and external as well. Can anyone help me out?

juliusssss said:
Main thread + features + install instructions + dev support
Click to expand...
Click to collapse
any chance of making Dual Recovery ??
like this 1 that i am using on Xperia Z1
http://forum.xda-developers.com/showthread.php?t=2261606

@juliusssss....Bro just fixed the sdcard mount problem
now sdcard is mounting in recovery mod...
Here is The Link...
Philz Touch

khan_frd2002 said:
@juliusssss....Bro just fixed the sdcard mount problem
now sdcard is mounting in recovery mod...
Here is The Link...
Philz Touch
Click to expand...
Click to collapse
Thanks @khan_frd2002, but it has the same problem, you can mount but only on read-only mode.
Thanks anyway. Greetings.

juliusssss said:
Thanks @khan_frd2002, but it has the same problem, you can mount but only on read-only mode.
Thanks anyway. Greetings.
Click to expand...
Click to collapse
really sorry bro...i just check whether it mount or not

@juliusssss....any new update bro

khan_frd2002 said:
@juliusssss....any new update bro
Click to expand...
Click to collapse
Sorry, now i'm trying to compile a custom recovery for a new device and i don't have time, when i compile this new recovery i update cmw-philz for armani :good::good:
Greetings.

juliusssss said:
Sorry, now i'm trying to compile a custom recovery for a new device and i don't have time, when i compile this new recovery i update cmw-philz for armani :good::good:
Greetings.
Click to expand...
Click to collapse
no problem bro :good:...will wait for you

just one question there is option for wipe to install new rom it will wipe as well sd-card?
sorry for my english

erouz said:
just one question there is option for wipe to install new rom it will wipe as well sd-card?
sorry for my english
Click to expand...
Click to collapse
yes..it will wipe your internal sd-card

ok I know now I was use that option while waiting for reply. I was stuck on mi logo after flash because i was flash rom and speed tweak at one go
but thank you for replay

wats the key combination too boot into this ??

sherry_94 said:
wats the key combination too boot into this ??
Click to expand...
Click to collapse
Volume up + Power key
Sent from my HM 1SW using XDA Premium 4 mobile app

khan_frd2002 said:
yes..it will wipe your internal sd-card
Click to expand...
Click to collapse
U sure selecting the wipe to install new ROM will wipe the internal storage ? Asking as it does not wipe the internal on other phones just formats the system wipes del and cache.

rkkaranrk said:
U sure selecting the wipe to install new ROM will wipe the internal storage ? Asking as it does not wipe the internal on other phones just formats the system wipes del and cache.
Click to expand...
Click to collapse
Yeah. Even I thought it wipes just system and cache

nishanthhh said:
Yeah. Even I thought it wipes just system and cache
Click to expand...
Click to collapse
Thats the reason i asked him coz it does not wipe the internal memory on other phones.

[GUIDE] Convert to f2fs

All,
Since there was no clear directions on how to convert to f2fs, I decided to make a quick guide.
This *SHOULD* be device agnostic, however, I wrote it using my T-Mobile Note 3 running LeanKernel 3.12.3.
I'm not responsible if you screw up your data/device. Do this at your own risk.
1) Make sure you're on a kernel that supports f2fs. STOCK KERNELS WILL NOT WORK!
2) Boot into TWRP (at least version 2.8.1.0)
3) Make a backup to either external_sd or an OTG USB device. **THIS STEP IS REQUIRED**
4) After the backup is complete, go back to the TWRP main menu and select wipe
5) Select Advanced Wipe
6) Select the desired partition (cache OR data) and click FS OPTIONS ** DO NOT TRY TO CONVERT ANY OTHER PARTITIONS THAN CACHE AND/OR DATA UNLESS YOUR KERNEL SUPPORTS IT**
NOTE: YOU MUST DO THESE ONE AT A TIME!
7) check f2fs and then wipe
8) Ensure when finished it says current partition type f2fs
9) Repeat steps 5-7 for each partition you are convert ** DO NOT TRY TO CONVERT ANY OTHER PARTITIONS THAN CACHE AND/OR DATA UNLESS YOUR KERNEL SUPPORTS IT**
10) Go back to the TWRP Menu and select Restore
11) Select the backup you just made, and select only the partitions you are converting and restore (ignore warnings about ext4; these are normal)
12) Once restore has completed, go back to TWRP Menu and reboot into system.
13) Profit.
I know there are other kernels that support it, but my personal preference is leanKernel 3.12.3. You'll find it here: http://forum.xda-developers.com/showthread.php?t=2488233 thanks to @Imoseyon
If you need TWRP, you'll find it here: http://forum.xda-developers.com/showthread.php?t=2467001 thanks to @bigbiff
Enjoy, and again, don't blame me if you mess up your device/lose your data/etc.

What is the advantage and disadvantage of doing this procedure? Is compulsion kernel compatible?
Sent from my SM-N900T using xda premium

derride8 said:
What is the advantage and disadvantage of doing this procedure? Is compulsion kernel compatible?
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
This post sums it up pretty well.
As for compulsion, you'll want to check that kernels thread and/or the dev to find out.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T

Do apps take up twice as much space on f2fs? That's the only difference I can see so far after the conversion.

toastido, Thanks for the guide. I followed the directions, am on lean kernel 3.13 which has f2fs support. When I restored, I noticed that system was reformatted back to ext4, while I got the warning on the cache and data partitions. Did I miss a step or is there a way to prevent the reformat?

rmarinella said:
toastido, Thanks for the guide. I followed the directions, am on lean kernel 3.13 which has f2fs support. When I restored, I noticed that system was reformatted back to ext4, while I got the warning on the cache and data partitions. Did I miss a step or is there a way to prevent the reformat?
Click to expand...
Click to collapse
Yes, go into the settings for twrp and look for the option to use rm -rf instead of formatting during wipe. Make sure that's selected.
Sent from my leanKernel 3.13 powered stock 4.4.2 (NF9) SM-N900T

toastido said:
Yes, go into the settings for twrp and look for the option to use rm -rf instead of formatting during wipe. Make sure that's selected.
Sent from my leanKernel 3.13 powered stock 4.4.2 (NF9) SM-N900T
Click to expand...
Click to collapse
That was it, Thanks!

Thanks @toastido
I imagine dp/lk will be the same

I get an error when changing the file system from ext4 to f2fs using TWRP 2.8.7.0.
It looks like this:
E:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p25 process ended with ERROR=1
E: Unable to wipe /data
E: Unknown MTP message type: 1
E: Error changing file system
I tried using TWRP 2.8.5.0 with the same result. I also tried to format data. Same result.

Gotta use 2.8.4.0 as that was the last version I was able to format data without error. Kevp75, love your rom as my daily for my note 3 but cannot use your kernel when I try this method but lean kernel 6.2/6.3 works fine.

prican25 said:
Gotta use 2.8.4.0 as that was the last version I was able to format data without error. Kevp75, love your rom as my daily for my note 3 but cannot use your kernel when I try this method but lean kernel 6.2/6.3 works fine.
Click to expand...
Click to collapse
lean works with all 3 partitions?

kevp75 said:
lean works with all 3 partitions?
Click to expand...
Click to collapse
Just Data and Cache worked, tried with system but just get loops.

prican25 said:
Just Data and Cache worked, tried with system but just get loops.
Click to expand...
Click to collapse
Right on!
System not really needed anyways as it's read-only, but the testing I've done had shown a significant boost on read
Thanks bud!

SUCCESS
Thanks for the guide. I was attempting this week following a different guide which was very similar. I have a Tmobile Note 3 and was unable to achieve this with TWRP 2.8.5 and up as those directions said to use 2.8.1.0 and up.
This time I used 2.8.1.0, the latest Lean kernel and DomPop v5. I converted Cache, Data and System. Upon Reboot it would not boot. I suspect this could be the current ROM or TWRP version I used which is just an assumption. I have not thoroughly investigated. I am going to create a new Nand, convert /System and then test the latest Dominion S6 port ROM among a few other 5.1.1 ROMs.
Note: I am not affiliated with any ROM I mentioned in this post.
Thanks again for the Guide. So far the difference is very noticeable with /Data and /Cache converted.

kevp75 said:
Right on!
System not really needed anyways as it's read-only, but the testing I've done had shown a significant boost on read
Thanks bud!
Click to expand...
Click to collapse
Have successfully get system to stick on f2fs... I have tried all but still goes back to ext4

austino pele said:
Have successfully get system to stick on f2fs... I have tried all but still goes back to ext4
Click to expand...
Click to collapse
It doesnt "mysteriously" just go back to ext4.
Something you are doing or flashing is formatting it back

kevp75 said:
It doesnt "mysteriously" just go back to ext4.
Something you are doing or flashing is formatting it back
Click to expand...
Click to collapse
Alright thanks

austino pele said:
Alright thanks
Click to expand...
Click to collapse
Check in the zip you are flashing.
You should be able to mod the updater-script
Look for the mount lines... (if it's not a CM/AOSP rom/mod)
You can change them to along these lines, and it should keep the f2fs
Code:
run_program("/sbin/mount", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
run_program("/sbin/mount", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
run_program("/sbin/mount", "/dev/block/platform/msm_sdcc.1/by-name/cache", "/cache");
Obviously you'll need to change to your device, but so long as you have Busybox installed, this will mount as filesystem independant
good luck mate

[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

[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