Related
Hello
I made backup of my efs with the latest EFS professional 2.0.70. Do i need to backup something else, or does this EFS partion include everything i need? efs.img size is 20Mb. And yes i have galaxy s3 i9305. I have also backed up my rom using CMW.
Thanks
Basics
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Hi,
I'm using a CM11 LBL ROM with Williams kernel. The rom uses the wipedata hack to enter recovery and then extract files on /temp and /
I wonder if I can use the fota partition to put the files already extracted in it to win some time at reboot. I will then modify the scripts to use this partition.
I tried some commands to see what's the size of mmcblk0p11 without success.
So: someone knows this partition size ? (I need about 20MB) Can I format it in ext4 without messing something ?
Thanks.
sambastrakan said:
Hi,
I'm using a CM11 LBL ROM with Williams kernel. The rom uses the wipedata hack to enter recovery and then extract files on /temp and /
I wonder if I can use the fota partition to put the files already extracted in it to win some time at reboot. I will then modify the scripts to use this partition.
I tried some commands to see what's the size of mmcblk0p11 without success.
So: someone knows this partition size ? (I need about 20MB) Can I format it in ext4 without messing something ?
Thanks.
Click to expand...
Click to collapse
I don't think that this gets you much speed. It takes not a single second to move 20mib.
The Rashr recoveries are saved in the fota partition. So it should be possible to use fota for your own stuff.
Have a look how big a rashr recovery is. That's the amount of space you have at least.
Or look how big the fota partition in a stock ftf is.
But I don't think it's worth the time.
Gesendet von meinem
Sony Xperia SP - Cyanogenmod 12.1
Kaffeetrinker said:
I don't think that this gets you much speed. It takes not a single second to move 20mib.
The Rashr recoveries are saved in the fota partition. So it should be possible to use fota for your own stuff.
Have a look how big a rashr recovery is. That's the amount of space you have at least.
Or look how big the fota partition in a stock ftf is.
But I don't think it's worth the time.
Gesendet von meinem
Sony Xperia SP - Cyanogenmod 12.1
Click to expand...
Click to collapse
Thank you for your answer.
recovery img are about 10MB and it seems the partition is about 16MB.
The way recoveries are implemented on my rom it seems to take about 3secs to extract the files and launch the script.
Well, it's more for fun than to win time.
The more important is to know if I can format it without any bad surprise ... In theory there is no reason but ...
I am pretty sure you can format it.
Rashr does it too...
Maybe you should do reasearch how Rashr works.
And google for stuff like "Fota messed up bootloop bricked". That way you can see what the worst thing is that can happen.
And look for partition table problems just in case...
Gesendet von meinem
Sony Xperia SP - Cyanogenmod 12.1
TWRP 3.0.1-0 with "All-F2FS" support
I have modified the standard TWRP recovery to work with F2FS partitions.
This is different from the previous recoveries that i published.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel.
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Download:
Zeus-Kernel.zip (CM12.1) - Here
Zeus-Kernel-MM.zip ( MM ) - Here
recovery-sprout-F2FS-All.img - Here
TWRP 3.0.1-0 Latest - Here
Changelogs:
-29/10/15: Initial Release
-02/04/15 : TWRP 3.0.1-0 Release
To switch your /system, /cache and /data partitions to F2FS follow instructions:
You need:
-Two files you can download above.
-A Android One (Sprout4) device obviously.
-Patience and Time.
Steps:
Flash this recovery with Fastboot (Maybe Flashify, Your wish)
Reboot in new recovery
Backup your /system , /data
(a) Go to Wipe, then Advanced Wipe, Select /System.
(b) Click on "Repair or Change File System"
(c) Click on "Change File System" option
(d) Select F2FS then Swipe to Change.
Repeat steps (a) to (d) with /data and /cache as you did with /system.
Now come back to main screen and go to "Settings"
Select "Use rm -rf instead of formatting."
Go to Restore menu and restore your previously backed up data.
Now Flash the Kernel zip provided above.
Reboot.
Done.
It's easier than it seems.
To restore partitions to stock:
Backup /system and /data
Change File System to EXT4.
Go to Restore menu and restore /system and /data again.
XDA:DevDB Information
[RECOVERY][All-F2FS] TWRP 3.0.1-0 with All-F2FS support, Tool/Utility for the OEM Cross Device Development
Contributors
Swapnil Solanki
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.0.1-0
Stable Release Date: 2016-04-02
Created 2015-10-30
Last Updated 2016-04-02
Reserved
Reserved
Yay......
It's here..
Thanks sir...
Thanks I got it resolved..
In the Meantime I'll keep mashing Thanks button...
Could you make a flashable zip for the recovery? Thanks!
vjtigas said:
Could you make a flashable zip for the recovery? Thanks!
Click to expand...
Click to collapse
Sure I'll make it soon.
Keep mashing thanks button
Regards.
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Minions_Army said:
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Click to expand...
Click to collapse
This doesn't change it. It just gives support for it.
No. (Misunderstood your question.)
He said it's for sprout4, but I think it don't wipe that.
vjtigas said:
This doesn't change it. It just gives support for it.
I don't think so.
He said it's or sprout4, but I think don't it wipes that.
Click to expand...
Click to collapse
wait for Op explain this
:cheers
hi i am using my sd card as adapted internal storage on android m. will this recovery detect any zip placed on this card? if no how to push the zip to my phone
vjtigas said:
Could you make a flashable zip for the recovery? Thanks!
Click to expand...
Click to collapse
Well I made a flashable zip
https://www.androidfilehost.com/?fid=24052804347850387
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
austinpinto said:
hi i am using my sd card as adapted internal storage on android m. will this recovery detect any zip placed on this card? if no how to push the zip to my phone
Click to expand...
Click to collapse
No recovery is made to detect card formatted as Internal Storage as it encrypts it. To flash zip, you can put it in /data/media folder or OEM folder or simply use adb sideload from PC
Minions_Army said:
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Click to expand...
Click to collapse
Yeah, it'll allow you to change the filesystems to F2FS.
It should still be F2FS after flashing KK ROMs. But LP and MM ROMs include an EXT4 image in their zips, so flashing MM or LP ROMs will convert the system partition to EXT4. Data and cache will stay as EXT4.
Formatting data always wipe /data/media. Wiping data with sprout8 recovery keeps /data/media, but as OP says that this is for sprout 4, it'll either not work with sprout8 (not sure) or wipe /data/media if you wipe /data.
hp5942 said:
Well I made a flashable zip
https://www.androidfilehost.com/?fid=24052804347850387
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
No recovery is made to detect card formatted as Internal Storage as it encrypts it. To flash zip, you can put it in /data/media folder or OEM folder or simply use adb sideload from PC
Click to expand...
Click to collapse
i have the drivers for the phone but when i do adb sideload on pc when phone is in this recovery nothing hapends.
are there any other drivers that i must install?
i installed the google usb driver from google
austinpinto said:
i have the drivers for the phone but when i do adb sideload on pc when phone is in this recovery nothing hapends.
are there any other drivers that i must install?
i installed the google usb driver from google
Click to expand...
Click to collapse
Try reinstalling driver while device is in recovery. I had to install it twice on Win10
Hope that helps
I'm not sure where I'm going wrong. After I converted to f2fs, TWRP straight up refused to mount /system, /data and /cache.
I had to convert it back to ext4 before TWRP would mount them. Can anybody help me out?
I'm using cm13 beta2 having 3.10.92 Zeus kernel n 2.8.7.0 twrp recovery so do I need to change kernel after chnging system file to f2fs ...?
harsh. said:
I'm using cm13 beta2 having 3.10.92 Zeus kernel n 2.8.7.0 twrp recovery so do I need to change kernel after chnging system file to f2fs ...?
Click to expand...
Click to collapse
I think Zeus is the only kernel for sprout that supports f2fs. Your safest bet would be to install the latest Zeus(4.5) kernel.
If I flash the flashable zip uploaded by @hp5942, then, will the /system, /cache & /data to f2fs?
krittin98 said:
If I flash the flashable zip uploaded by @hp5942, then, will the /system, /cache & /data to f2fs?
Click to expand...
Click to collapse
No you'll have to do that yourself manually. Recovery is flashed to support mounting of F2FS. Follow instructions given at the beginning of thread and don't forget to flash Zeus kernel given at beginning of thread (mm of lollipop specific depending on your rom). Happy Flashing
I'm unable to take backup as not enough space can I flash system ROM n gapps from SD card after F2FS?
Sent from my Micromax AQ4501 using Tapatalk
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
(°_o) said:
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
Click to expand...
Click to collapse
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
MYEUHD said:
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
Click to expand...
Click to collapse
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
MYEUHD said:
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
Click to expand...
Click to collapse
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
xc-racer99 said:
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
Click to expand...
Click to collapse
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
(°_o) said:
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
Click to expand...
Click to collapse
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
xc-racer99 said:
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
Click to expand...
Click to collapse
The mtd doesnt interface the whole NAND storage.. so i'm gonna have to rebuild the kernel exposing the original efs partition..
Let's see how it goes.
@xc-racer99
I dumped the 10mb parition but it wasnt mountable by any means..
Then I hex viewed it and it showed.. FSR_STL in beginning..
Which lead me to, https://github.com/Benjamin-Dobell/Samsung-Read-Only-FSR/blob/master/Inc/FSR_STL.h
So unless I check out the STL implementation or use one that is I guess I have to go back to stock :\
I cannot get any valid data from the dump.
I've attached the dump of it, if youre intrested.
Hello xda community and OP3(T) users!
In April I created an image of my f2fs /data partition according to this hint:
https://stackoverflow.com/questions/26967862/how-to-make-an-image-of-android-partition-to-your-pc
This was successful and a *.img file sized 53+ GB now resides safely and quietly on an external hard drive.
Now I want to mount as well explore it with my Linux laptop. ))
How do I do this? Which tools and commands are needed?
P.S.: in the past this partition was also encrypted and decrypted via a simple 3x3 pattern by TWRP as well as before a ROM boots....