Develop Bugs

[Q] How do you completely recover your device?

Ok, so I downloaded some files, and they ended up a bit corrupt, and not knowing this, I wiped data/cache + system and tried to flash them. Now, I have nothing but 3 corrupt ROMs (CM10.1 12-22-2012, WickedJB 5, and DarthStalker 6). I had some backups, some time ago, but thinking that I'd be able to backup as soon as I get to recovery, I didn't. So now, I have no backup and 3 corrupt files, but a functional Download and Recovery (TWRP 2.3.3.1). I tried to use the adb sideload function, but it doesn't work ("device not found"). And trying to flash cm10.1 gives me error status 7, and the other two don't give me errors but after flashing, they just stay stuck at the boot screen.
I tried Odin, but it becomes stuck at "aboot.mbn." It doesn't even give a pass/fail. It just says "aboot.mbn" and after 10 minutes, I raged and pulled the plug (and then it says failed).
So, now I have no idea what to do.
How to fix it?
Thanks

Hope this helps a little
I'd make sure that ur Downloaded Flash ROM's are not Bad files or incorrect... There is usually a MD5 file or long number with most downloads,
get a MD5 checker program and check the number of the file(s) you downloaded and see if they line up with OP's Site
At this point you know u have GREAT files (ROM's) to work with.
-Not sure what recovery you have, when you boot into recovery, what do u see...
-It is possible that you inject SuperSU or Superuser into your stock ROM and have ROOT access, but also still have STOCK RECOVERY!
-You will need any kind of RECOVERY other then stock, I suggest TWRP 2.3.3.1 (version 2.3.3.0 didn't show you your sdcard, don't use that version) v2.3.1.0 was fine to use in past.
How to add NON Stock Recovery (ROM has to be rooted)...
__________________________________________________________________________________________
***to add ROOT... Use ODIN to inject stock ROM with Root66's (Dark Chld) method... (at this point, you'll have rooted ROM with stock recovery)
1. Use "Terminal Emulator" app found on market (newest is v 1.0.50)
2. Download + Copy (TWRP v2.3.3.1) recovery .img file to sdcard (rename it to recovery.img)
*** you have to extract out xxx.img file out of .zip (.zip won't work...".img" file will work only)
3. Run Terminal Emulator 1.0.50 and type this code...
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
4. Done!
*** if all went well !, now Recovery is Changed ..reboot into recovery mode and check...
more info found here
At this point you will know you have rooted ROM and NON Stock recovery.
-With any non Stock recovery, you can flash any ROM. Read their Instructions and follow them to the letter.
-Be sure to wipe Cache's, System, (and most of the time DATA) and other stuff as instructions for that particular ROM says
-Eventually once you have any great (NON CURRUPT) ROM, make a backup, so you can always have a SAFE ROM to flash...
TWRP BACKUP's get saved to External SD Card in TWRP folder (but you have to Set them there when your creating NEW BACKUP)
*** Don't ever save files to INTERNAL SDCARD, incase you wipe internal DATA in future.
IMPORTANT : understand what you are doing as u do it...
TWRP Wipe Menu (options)
___________________________________________________________________________
Cache = always ok to WIPE (it will take longer to load after wiping on 1st boot only)
Dalvik Cache = always ok to WIPE (it will take longer to load after wiping on 1st boot only)
Factory Reset = wipes Cache(s), (Data - All settings + User Apps), (NOT data\media - Internal SDCARD), (NOT External Micro SDCARD)
System = just ROM Files (System Apps, System Files, NO settings at all)
Internal Storage = (data\media - Internal SDCARD), (NOT External Micro SDCARD))
Format Data = All settings + User Apps + (data\media - Internal SDCARD), (NOT External Micro SDCARD)

[Q] gt18160- adb pull sdcard file permission problem!

Hello lovely android people,
I am a newbie, so im guessing this probably isnt the right place to post this type of question. Please feel free to guide me to the right place.
So the question...
I rooted my galaxy ace2 (gt18160) and install Pimp My Rom app from the market. Did some changes with it and now the phone wont start up, stuck in the bootloop where the logo appears and it does not go anywhere from there.
Ive been researching for solution since yesterday, and found out that I could re-flash the firmware using o2 stock using odin.(although im not quite sure this is a correct solution)
Since there's a possibility of all the data getting deleted, I want to get some files out of the device using ADB pull.
I used adb shell to look for the files I need. At first I could see the sdcard in the root directory / but could not access it without su. After doing su command I can go inside the sdcard directory (where my files are), but it appears to be empty.
ls -l /mnt lists the sdcard with unusual d--------- permission.
Im stuck and dont know how I can grab my files from the sdcard folder.
any suggestion will help.:cyclops:
Thanks

mnt/sdcard is only a symlink to storage/sdcard0 (mount for the internal sdcard) so it does make sense that adb can't cope with that path.
Still, it is impossibibble to delete stuff from either of your sdcards via odin or recovery. Flashing via odin doesn't wipe the data partition either, so as ong as u select the right firmware for our phones, nothing can go wrong really

Thanks for your reply Carpe-Dimi.
after checking /prop.partiitons, it seems that sdcard hasnt been mounted.
The problem now is that there are 18 partitions and I dont know which is the sdcard?
I tried mounting the first mmcblk0. Give me the 'device or resource busy' error.
Excuse my arrogance but I would have liked to find out why I cant access the sdcard or why I cant mount the partitions.
...and thanks again for letting me know that flashing does not wipe the data. :good:

SOLVED!
As Dimi said, flashing does not wipe data partition. But I was able to recover my files in recovery mode as it automatically mounted the mmcblk0p8 partition.
Then installed stock firmware.... tried new jelly bean, then went back to stock as its slow and laggy.
Cheers

[Q] how to upgrade to 4.4 from 4.3 a and backup TA

What are all the steps involved from 4.3 bootloader locked to cm11?
Some threads are saying you can brick your internal partition if you don't unlock properly. I used to be a sammy owner( see signature). I'm new to the xperia world. I understand that root is required for TA backup and latest CM need 4.3 baseband. But 4.3 no root with locked bl?
Also, will flashtool flash device with locked bootloader to go from 4.3 > 4.1?

theperson333 said:
What are all the steps involved from 4.3 bootloader locked to cm11?
Some threads are saying you can brick your internal partition if you don't unlock properly. I used to be a sammy owner( see signature). I'm new to the xperia world. I understand that root is required for TA backup and latest CM need 4.3 baseband. But 4.3 no root with locked bl?
Also, will flashtool flash device with locked bootloader to go from 4.3 > 4.1?
Click to expand...
Click to collapse
Also, What is your recommended method of unlocking the bootloader and why?
Please post any answers in a separate thread and link to it, so it can be made a sticky.

I am not responsible if anything goes wrong.
Go to http://xperiafirmware.com/8-firmware/40-sony-xperia-m-c1905, and follow the steps under "Upgrade to latest 4.1.2". This works on locked bootloaders too, and it even works if it is a downgrade, not upgrade.
Stock 4.1.2 is rootable with Framaroot's Gandalf exploit (search for it on XDA), root it. Then you can back up the TA partition, either with the flashtool you have downloaded earlier, or in some manual way. Make absolutely sure it went well before proceeding! I think you have read plenty of warnings if you have asked this question.
Then proceed as usual. Go ask Sony for an unlock key, unlock your phone with fastboot. Download the 4.4 ROM you wish to use, then flash the boot.img of it by
Code:
fastboot flash boot boot.img
. Then boot the phone into recovery mode using
Code:
fastboot reboot
and when it begins to boot, bash the volume up key a few times. Then install your new ROM from recovery.
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Also, this is from experience, I have a C1905, which I prior upgraded with SEUS to 4.3. The procedure I wrote worked on it nevertheless.
Another thing that happened to me is that in the process my /data partition got corrupted. The "internal sdcard" lives at /data/media, and recoveries want to preserve this folder, so when they can't mount it and rescue files from it, they skip it, and the new ROM won't boot because it can't mount the /data partition either. So if you get a bootloop after installing the new ROM, try formatting /data AND the internal storage, there's an option in the recovery to do this.

When did your /data/ get corrupt? I read on xda that after boot loader unlock, you must boot a stock firmware to format /data/ properly, is this true? I'll post link to that topic when I have access to computer.(new user of xda app)
Sent from my C1905 using XDA Free mobile app

theperson333 said:
When did your /data/ get corrupt? I read on xda that after boot loader unlock, you must boot a stock firmware to format /data/ properly, is this true? I'll post link to that topic when I have access to computer.(new user of xda app)
Sent from my C1905 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know. All I know is that I did these:
Reflash 4.1.2 from flashtool
Boot it, root it, push a busybox on the thing
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
Pull TA.img from the internal storage to the computer
On phone: busybox md5sum /dev/block/platform/msm_sdcc.1/by-name/TA, on computer: md5sum TA.img, ONLY PROCEED IF CHECKSUMS MATCH! (They matched the first time for me. As a precaution I put them on my Google Drive along with the checksum, they'll be safe there, you should also find a safe place for your own backup in case you want to restore it later.)
Put the phone in fastboot mode, unlock it using the official method, then flash boot.
[*]Start recovery (bashing vol+), flash full ROM from the SD card, then flash Gapps too.
[*]Boot the phone, watch it being stuck on bootanimation.
[*]Pull the battery, start recovery again, wipe /system, flash ROM
[*]Boot phone, watch another 10 minutes of the boot animation
[*]Pull battery, start recovery, wipe everything, notice that /data won't wipe because it won't mount (WTF?)
[*]Do a bit of Googling, realize that recovery is afraid to wipe /data, because the internal storage (/data/media) is inside it, and precious things can be on it (for example the Nandroid backups, the ROM you were about to flash, family photos etc.)
[*]Use "wipe /data and /data/media" in recovery, this really formats the /data partition.
Flash ROM, flash Gapps, reboot phone, be happy with it.
I marked the steps with lime colour in which I am absolutely sure my /data was corrupted, and dark green when I only suspect it.
On second thought, it may have something to do with unlocking the bootloader in the official way. As far as I know, unlocking the bootloader destroys all user data on the phone as a security measure (say your stock ROM has a password you set but an attacker could flash an alternate ROM with no password to access all of your precious data. To prevent this you can't flash an alternate firmware without unlocking the bootloader and destroying sensitive data in the process). And as fastboot is a pretty simple and dumb piece of code (all it has to do is write the internal flash), I wouldn't be surprised if it didn't bother creating a filesystem on the /data partition, but instead just zeroed it all out. Their philosopy seems to be "if you know how to unlock the bootloader, you are a developer, and developers know how to format the /data partition". So, if my train of thought here is correct, my /data was "corrupted" in the steps marked with any shade of green, only this doesn't really mean "corrupted", it means "zeroed out with no filesystem".
The recovery's "wipe /data" command means: mount /data, and delete everything except the /media folder inside, because the internal storage lives at this folder, which most people don't expect to lose when wiping /data, for idiotic historical reasons.
So all zeroes -> no filesystem -> recovery can't mount it -> recovery pees its pants in horror and doesn't touch it, because it thinks "Oh my Glob, this partition does not contain a valid filesystem, but it may have a corrupted filesystem or one that I don't recognise, and formatting it could destroy my owner's data, which could be inside this hypothetical filesystem's /media directory. Which my owner wouldn't expect and then they would think I am a bad recovery."
------
I just re-read your question. I didn't use any stock software after unlocking, my recovery formatted my /data perfectly for me.

thermate said:
I don't know. All I know is that I did these:
Reflash 4.1.2 from flashtool
Boot it, root it, push a busybox on the thing
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
Pull TA.img from the internal storage to the computer
On phone: busybox md5sum /dev/block/platform/msm_sdcc.1/by-name/TA, on computer: md5sum TA.img, ONLY PROCEED IF CHECKSUMS MATCH! (They matched the first time for me. As a precaution I put them on my Google Drive along with the checksum, they'll be safe there, you should also find a safe place for your own backup in case you want to restore it later.)
Put the phone in fastboot mode, unlock it using the official method, then flash boot.
[*]Start recovery (bashing vol+), flash full ROM from the SD card, then flash Gapps too.
[*]Boot the phone, watch it being stuck on bootanimation.
[*]Pull the battery, start recovery again, wipe /system, flash ROM
[*]Boot phone, watch another 10 minutes of the boot animation
[*]Pull battery, start recovery, wipe everything, notice that /data won't wipe because it won't mount (WTF?)
[*]Do a bit of Googling, realize that recovery is afraid to wipe /data, because the internal storage (/data/media) is inside it, and precious things can be on it (for example the Nandroid backups, the ROM you were about to flash, family photos etc.)
[*]Use "wipe /data and /data/media" in recovery, this really formats the /data partition.
Flash ROM, flash Gapps, reboot phone, be happy with it.
I marked the steps with lime colour in which I am absolutely sure my /data was corrupted, and dark green when I only suspect it.
On second thought, it may have something to do with unlocking the bootloader in the official way. As far as I know, unlocking the bootloader destroys all user data on the phone as a security measure (say your stock ROM has a password you set but an attacker could flash an alternate ROM with no password to access all of your precious data. To prevent this you can't flash an alternate firmware without unlocking the bootloader and destroying sensitive data in the process). And as fastboot is a pretty simple and dumb piece of code (all it has to do is write the internal flash), I wouldn't be surprised if it didn't bother creating a filesystem on the /data partition, but instead just zeroed it all out. Their philosopy seems to be "if you know how to unlock the bootloader, you are a developer, and developers know how to format the /data partition". So, if my train of thought here is correct, my /data was "corrupted" in the steps marked with any shade of green, only this doesn't really mean "corrupted", it means "zeroed out with no filesystem".
The recovery's "wipe /data" command means: mount /data, and delete everything except the /media folder inside, because the internal storage lives at this folder, which most people don't expect to lose when wiping /data, for idiotic historical reasons.
So all zeroes -> no filesystem -> recovery can't mount it -> recovery pees its pants in horror and doesn't touch it, because it thinks "Oh my Glob, this partition does not contain a valid filesystem, but it may have a corrupted filesystem or one that I don't recognise, and formatting it could destroy my owner's data, which could be inside this hypothetical filesystem's /media directory. Which my owner wouldn't expect and then they would think I am a bad recovery."
------
I just re-read your question. I didn't use any stock software after unlocking, my recovery formatted my /data perfectly for me.
Click to expand...
Click to collapse
Is it better to unlock bootloader with flashtool in this case? IS it possible to recreate partition with ADB?

theperson333 said:
Is it better to unlock bootloader with flashtool in this case? IS it possible to recreate partition with ADB?
Click to expand...
Click to collapse
As far as I know, flashtool is just a GUI over fastboot when it comes to unlocking the bootloader, so it does exactly the same thing you would do with fastboot. It makes no difference.
What do you mean by "recreating partition with ADB"?

Are there any adb tools or shell tools accessible from adb to recreate partitions?
Sent from my C1905 using XDA Free mobile app

[Q] Is it possible to wipe system partition before installing a ROM

This is regarding a recently bought tablet Note 8. The current usage of /system partition is at above 75%. I have been trying to wipe/delete all system data in an attempt to have a 'fresh' OS once I install new stock ROM. In CWM recovery, I have even tried to format system partition (in addition to normal data reset, cache wipe and delvek cache wipe).
I installed the new stock ROM 4.4.2 in Download mode. Afterwards I checked and my system partition was still above 75% full. I do understand that system partition is normally read only. I am trying to work out if there is there any way where I can flash the stock ROM whilst completely removing the current system files.
Please offer any guidance or advice regarding this matter. Thanks!

Possible? Yes. Necessary? No.
The installation script for a ROM will almost always format the system partition before setting it up with the new ROM files, unless the developer is doing some special testing and you would know if that is the case.
ramjet73

Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.

S2 user said:
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
Click to expand...
Click to collapse
Depending on how you flash the stock ROM, Odin will flash a .img file to the system partition and completely replace its contents or an updater-script in a stock ROM zip file will format it and then copy all the included /system files to the empty partition.
In either case you cannot control what goes into the initial configuration of the system partition, only delete things that you don't need after it is flashed, unless you flash from a stock ROM zip file and delete items from that before you flash it.
There are scripting tools that can help with ROM "slimming" but I don't know if any are available for the Note 8.0 or not.
ramjet73

[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