Is there any rom supporting f2fs? Since there are 4 or 5 kernel supporting it but seems like no rom can use it. Maybe something to enable it myself?
Oxofrmbl said:
Is there any rom supporting f2fs? Since there are 4 or 5 kernel supporting it but seems like no rom can use it. Maybe something to enable it myself?
Click to expand...
Click to collapse
Made a zip with F2FS enabled fstab for whyred. In theory if you format the data and cache to F2FS, flash any ROM, F2FS enabled kernel and this zip, should work(or not)
https://drive.google.com/open?id=1FQtgYtFbXjA-pp0NAlJNdWYAc45PCn0X
edit: Im lazy to backup the internal storage and test it.
ktommy91 said:
Made a zip with F2FS enabled fstab for whyred. In theory if you format the data and cache to F2FS, flash any ROM, F2FS enabled kernel and this zip, should work(or not)
https://drive.google.com/open?id=1FQtgYtFbXjA-pp0NAlJNdWYAc45PCn0X
edit: Im lazy to backup the internal storage and test it.
Click to expand...
Click to collapse
THX i will try and report
ktommy91 said:
Made a zip with F2FS enabled fstab for whyred. In theory if you format the data and cache to F2FS, flash any ROM, F2FS enabled kernel and this zip, should work(or not)
https://drive.google.com/open?id=1FQtgYtFbXjA-pp0NAlJNdWYAc45PCn0X
edit: Im lazy to backup the internal storage and test it.
Click to expand...
Click to collapse
ok, i tried some things, i formatted cache and data to f2fs, flashed your zip and i bootlooped
then i tried to edit fstab from rom (PE PIE) with adding the 2 lines mentioning f2fs from your fstab to the rom fstab
both with restoring data (with rm -f instead of formatting) and with clean partition
and none of that was working (bootlooping), with still edited fstab i changed filesystems back to ext4 and restored data and it was working....
kernel is latest InsigniuX which is mentioned to be f2fs compatible in changelog
Oxofrmbl said:
Is there any rom supporting f2fs? Since there are 4 or 5 kernel supporting it but seems like no rom can use it. Maybe something to enable it myself?
Click to expand...
Click to collapse
I was looking at CRYPTFS related to latest PE rom, and I would strongly reconsider changing filesystem like that.
For example, I read about encrypting using cryptfs on a f2fs requires different file system requirements (such as some sufficient space for the encryption related data) or different things.
Encryption on a PE rom hardly worked since 3-4 weeks ago, and with specific requirements which have proven to be not standard for many.
I'd say that type of decision of changing fs, should be done by the rom person and also working with recovery teams as their formatting might impact all that.
Sure, it's an example and maybe that's the only potential issue...
Well you seems qualified enough to fiddle, most user will be annoying after doing something similar because they will pollute threads by claiming something not working in the rom, while in fact it's because they fiddled.
PS: to "enable" f2fs", you could format the partition in recovery... for example mkfs.f2fs (there are several options I think...).
htchd2sucks said:
I was looking at CRYPTFS related to latest PE rom, and I would strongly reconsider changing filesystem like that.
For example, I read about encrypting using cryptfs on a f2fs requires different file system requirements (such as some sufficient space for the encryption related data) or different things.
Encryption on a PE rom hardly worked since 3-4 weeks ago, and with specific requirements which have proven to be not standard for many.
I'd say that type of decision of changing fs, should be done by the rom person and also working with recovery teams as their formatting might impact all that.
Sure, it's an example and maybe that's the only potential issue...
Well you seems qualified enough to fiddle, most user will be annoying after doing something similar because they will pollute threads by claiming something not working in the rom, while in fact it's because they fiddled.
PS: to "enable" f2fs", you could format the partition in recovery... for example mkfs.f2fs (there are several options I think...).
Click to expand...
Click to collapse
I tried formatting with twrp, but I was either bootlooping or it said something about "couldn't encrypt filesystem"
thx for giving me some more information. I don't really understand everything, but I think I should be patiently waiting for a Dev to implement it itself, if someone wants to to this.
Oxofrmbl said:
I tried formatting with twrp, but I was either bootlooping or it said something about "couldn't encrypt filesystem"
thx for giving me some more information. I don't really understand everything, but I think I should be patiently waiting for a Dev to implement it itself, if someone wants to to this.
Click to expand...
Click to collapse
FORMAT in twrp (talking about /data) means removing the encryption entirely. Some roms which needs the /data to be encrypted (such as LOS) would then boot loop, unable to install or continue.
"couldn't encrypt filesystem" (again, if it's about /data) would be a different story.
If you want to encrypt, then it's usually done 2 ways, flashing MIUI rom or flashing PE and encrypting from the settings. I don't see why "Just like that" in TWRP it would try to encrypt a filesystem.
What would be required to have a file system not in EXT4 but in "f2fs" would be to format that filesystem and then use a tool to change it's type, it's like formatting it in a specific FS type.
What you probably meant, in TWRP was to "CHANGE FS" and not format:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bottom line, simply changing FS from EXT4 to F2FS will/could have consequences in the ROM. Since you don't understand, yes, the best is you propose that feature to a developer explainign why you think it's good and wait and see!
Related
Hello all,sorry to open such a thread in Dev section,it's only temporary and to be deleted as soon as it's stated useless by your reports or by moderators but i think there's a general issue with /datadata partition on CM10.1 based roms and i'd like to see things identified as soon as possible.
Question is simple:
If you're then on a CM10.1 based rom,approximately post 05/12,could you check you're /datadata partition and report if it is empty/unused?
"Chances" for that to happen: Having done a factory reset after 05/12 and not come no wipe from other rom than CM10.1 sources based ones (so not coming from Pawitp's aosp preview as /datadata works fine with it,only cm10.1 sources based roms).
Thanks for help.
Since that I am Helly Bean (base CM 10.1), I have never made of factory reset, however, my "datadata" folder is empty. I don't know when and how, this has begun!
Otherwise, all works correctly, it's good, fast and smooth... Go to understand why!
Try to use "df" command in terminal emulator, and check used space of /datadata.
KSLevel11 said:
Try to use "df" command in terminal emulator, and check used space of /datadata.
Click to expand...
Click to collapse
Yeah,that's what i want CM10.1 based roms users to do and report
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This one of Wingg to compare! datadata is OK for him...
/datadata is a protected folder. You can't view its content with a simple file browser. You must use a root file explorer.
Viewed using Root Explorer. My /datadata seems to be fine. Tictico might have a point.
ROM: BeastROM 12/07 build
tictico said:
/datadata is a protected folder. You can't view its content with a simple file browser. You must use a root file explorer.
Click to expand...
Click to collapse
Lame , you can see that Franzyroy has run the 'su' command already which allows complete root access to that app.
Also , I tried Hellybean 2012/12/08 today and my datadata is 8.5MB used , but it is empty inside.
If 4.2 doesnt use datadata , then maybe Fishears build without datadata and 1.8GB /data is actually beneficial, as we get extra space for apps without losing speed.
tictico said:
/datadata is a protected folder. You can't view its content with a simple file browser. You must use a root file explorer.
Click to expand...
Click to collapse
I know... I uses Solid Explorer or Estrongs Files Explorer with root activated, and also show the hidden files.
---------- Post added at 05:20 PM ---------- Previous post was at 05:14 PM ----------
ts1506 said:
Lame , you can see that Franzyroy has run the 'su' command already which allows complete root access to that app.
Click to expand...
Click to collapse
Good seen! But to confirm with su command.
!n0x said:
Viewed using Root Explorer. My /datadata seems to be fine. Tictico might have a point.
ROM: BeastROM 12/07 build
Click to expand...
Click to collapse
I was wondering what point but i got it now,no i'm used to that stuffs and not just reporting my own issue,it's just that i see many concording reports here and there and see peoples complaining about lags,reflashing,wiping data again thinking it's a specific rom issue and not knowing why their device COULD be laggy (not every phone acts the same with /datadata></data/data symlink broken).
Reports must come with little background please,the main point is "wiped data at least one time since approximately 05/12?"
By the way there's is two Beast rom 12/07 builds,yours is 4.2.1?
ts1506 said:
If 4.2 doesnt use datadata , then maybe Fishears build without datadata and 1.8GB /data is actually beneficial, as we get extra space for apps without losing speed.
Click to expand...
Click to collapse
Indeed as Fishears build doesn't use any /datadata partition it is not concerned but i don't think it will be 4.2 on sgs cm10.1 way.
It seems to have seen a Rom without datadata folder, I was wondering why, but I haven't reported it. I won't know to say which it was!
No lags
Bejda said:
I was wondering what point but i got it now,no i'm used to that stuffs and not just reporting my own issue,it's just that i see many concording reports here and there and see peoples complaining about lags,reflashing,wiping data again thinking it's a specific rom issue and not knowing why their device COULD be laggy (not every phone acts the same with /datadata></data/data symlink broken).
Reports must come with little background please,the main point is "wiped data at least one time since approximately 05/12?"
Click to expand...
Click to collapse
I always flash with full wipes of /data , /datadata , /cache , /system , and I dont face any lags with Hellybean 05/12 or 08/12 . Also , I tried GNex 4.2 ROM by Elite F7 build, no lags .
Without wiping from CM10 , there are some lags , but they are easily solved by only cache , dalvik cache wipe.
All is well on my end. I use CM10 daily , but will test Hellybean 08/12 from tomorrow in order to find lag issue, if any. Will report findings.
ts1506 said:
I always flash with full wipes of /data , /datadata , /cache , /system , and I dont face any lags with Hellybean 05/12 or 08/12 . Also , I tried GNex 4.2 ROM by Elite F7 build, no lags .
Without wiping from CM10 , there are some lags , but they are easily solved by only cache , dalvik cache wipe.
All is well on my end. I use CM10 daily , but will test Hellybean 08/12 from tomorrow in order to find lag issue, if any. Will report findings.
Click to expand...
Click to collapse
You may not face any lags with unused /datadata partition,check Fishears thread to know that first:
fishears said:
So, Is this ROM right for me?
If you have the fast iNand then, yes, because you'll get more data storage space with no loss of speed If you have the MoviNand then maybe yes, maybe no. My advice is "Try both".
To see which Nand you have look at the following file in a text viewer:
/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/name
If the content starts with "S" then you have iNand. If it starts with "M" then you have MoviNand.
Click to expand...
Click to collapse
And even if as me you're on MoviNand you still may not face any visible lags on your device,mine does as many others,a choice has been made on cm10 to keep using /datadata as it was the better solution for the majority of users.
Keep using /datadata + lvm for best performance/storage balance for majority.
Bejda said:
You may not face any lags with unused /datadata partition,check Fishears thread to know that first:
And even if as me you're on MoviNand you still may not face any visible lags on your device,mine does as many others,a choice has been made on cm10 to keep using /datadata as it was the better solution for the majority of users.
Keep using /datadata + lvm for best performance/storage balance for majority.
Click to expand...
Click to collapse
My Galaxy S has iNand, maybe thats why my phone does not lag, but one of my friends have Galaxy S with moviNand , with Elite F7 4.2.1 , his phone also doesnt face any lag( this is installed with full wipe ).
ts1506 said:
My Galaxy S has iNand, maybe thats why my phone does not lag, but one of my friends have Galaxy S with moviNand , with Elite F7 4.2.1 , his phone also doesnt face any lag( this is installed with full wipe ).
Click to expand...
Click to collapse
That's why,at least the main reason.
Fishears build could be a good choice for you if you need more /data space (among others things like following a cool dev and enjoy rom's specific features and all...)
The bug,if exists,is only concerning CM10.1 recents builds.Elite's rom is aosp build.
so datadata should be anything else but 0.0?
Szighy said:
so datadata should be anything else but 0.0?
Click to expand...
Click to collapse
It should be filled with some app's data (cache,libs,...) It should have the exact same content as what you have in /data/data,it's a symlink.
Bejda said:
It should be filled with some app's data (cache,libs,...) It should have the exact same content as what you have in /data/data,it's a symlink.
Click to expand...
Click to collapse
for me says only 2.3M in terminal emulator...i guess that's not good then
Szighy said:
for me says only 2.3M in terminal emulator...i guess that's not good then
Click to expand...
Click to collapse
No good in theory If you're not feeling lags on the rom you are then don't worry.
Wich rom btw?Helly user too?
For now i tested 3 rom with same behavior,Helly 05 and 08/12,Mackay 08/12 and matt73300's 05/12 unofficial build.
Disclaimer
I accept no responsibility if you damage your phone, lose your data or fail to attend an important meeting because of a broken phone agenda.
If you follow this tutorial DO backup. To an external sdcard or preferably a PC.
Also, continue reading if you are ok on FULL WIPING your device. You've been warned!
I take no credit at all for the ROMs and recoveries offered in this thread. They are only examples and I have no plans on maintaining them other than for personal use. Instructions to patch or rebuilds more up to date nightly builds are offered.
Special thanks to:
* CyanogenMod team
* Entropy512 and the Omni team
* Dees_Troy for TWRP
The problem
Probably you are feeling like me. This is a great device, but the storage layout is frustrating. Only 3GB for /data an 9GB for /sdcard !!!
Meaning:
- Just a few apps before the storage is full
- Google Music will not be able to download more than a few albums
The reason
Oppo decided to not have unified partition layout (/data and /sdcard do not share the same space as any other modern phone does). This is something my three years old Galaxy Nexus has!!!!
Solutions
There are a few, but without Oppo's support (meaning: repartitioning) all of them will be non standard and will limit ROM interoperability.
On this thread I will focus on three of the less dangerous solutions:
Option 1 : Use "sdcard0" (9GB) as /data, "userdata" (3GB) as "sdcard1" and the external sdcard as "sdcard0"
Option 2 : WIP : Create a volume group (LVM) using "userdata" and "sdcard0" physical devices (totalling 13GB). Use this as /data and the external sdcard1 as sdcard0. This is based on an idea by Entropy512 and I take no credit at all
Option 3 : WIP : Same as 2 plus unified partition layout (/sdcard0 on top of data). Leave sdcard1 as sdcard1 if you have it.
What you will need
Options 1 and 2 require an external sdcard. Option 3 does not (although you can still use it)
You should have installed fastboot and adb in order to flash a new recovery and do backups.
You need to use my special TWRP builds only.
Option 1
This is the easiest (but less than ideal) solution. You will have 9GB in /data and use your external sdcard as /sdcard0 (as if it was internal). the remaining 3GB will be considered as an external /sdcard1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The trick is simple, just replace the partition table (fstab.qcom) with this one. Put it on device/oppo/find7/rootdir/etc/fstab.qcom and brunch find7. Additionally rebuild TWRP with a similarly modded twrp.fstab. Alternatively you might want to rebuild the boot.img ramdisk, build for another ROM (OMNI is a great option too) OR use the downloads below:
* CM11 with the new parition layout (source built on 20140626)
* TWRP with similar partition layout (although external_sd is still external_sd and internal_sd is sdcard0).
Instructions:
1) Use your existing standard TWRP to do a nandroid backup to your external sdcard
2) Reboot into your bootloader (adb reboot bootloader or hold on your vol up and power button)
3) Flash this special TWRP image (fastboot flash recovery twrp-find7a-swapped-data-sdcard.img)
4) Reboot into recovery (power off, hold vol down and power button)
5) Click on Wipe, Advanced Wipe. Check Dalvik Cache, System, Data, Cache, Internal_sd, Android Secure (pretty much everything EXCEPT external_sd)
6) Flash the provided CM11. BE SURE YOU ARE USING THE CUSTOM TWRP IMAGE.
7) Reboot
8) Profit
Options 2 and 3
These are still WIP.
Extras
After flashing the ROM you would like to flash some extras:
* PA_GApps : DO not use anything other than MICRO MODULAR PA package, as the others will overwrite camera files will Google camera and it is broken.
* OnePlus One CyanogenMod 11s Camera : Works nicely
Rolling back
Just flash the original TWRP.
Go to Wipe menu, full wipe every partition (except external sd)
Flash whatever ROM you want.
Done
Reserved 2
FixMyOppo
alienmind sir,
amazing outstanding...so a quick question CM11 is now ready for the FIND 7 QHD X9077& X9076..didn't see that anywhere
i have a thread on oppo forums http://www.oppoforums.com/threads/free-our-memory-movement.17302/
trying to convince oppo to deal with this very issue of the 3gb app issue i have informed the members after being informed by a member,(rpcherrera),about this link,so just need confirmation this will work before flooding your thread with willing participants...
I can't grant the ROMs provided will work with the QHD model as I don't have one to test it. In principle this little hack or a very similar one should work though if you patch any QHD image with the provided fstab or something very similar. Although I accept test devices if you are willing to donate ;-]
Enviado desde mi Find7 mediante Tapatalk
fixmyoppo
thank you for your reply,if i had a spare £450 lying about i would gladly donate one to you,if you would like me to put the feelers out on the thread for the members to donate to you for this purpose i will do so...no problem
it's a shame there is no working development for the QHD yet...i know @coldbird is working on some and i can't wait till he has a working rom,(miui), or fix for this issue
so i can update my thread and let the users know this is for find 7a only...thank you
and please let me know if you want me to help you get donations from my thread,when i hear back from you about it,i will start the ball rolling
:laugh:
Don't worry about the donation thing, I was just kidding. Although the images provided are not directly flashable, as soon as you have CM11 support for the QHD, the hack above should work - given that you rebuild with the provided fstab.
Enviado desde mi Find7 mediante Tapatalk
fixmyoppo
yeah things are looking slow for the find 7 QHD,i will probably have my 1+1 by the time this device gets a stable custom rom,plus i am also looking at the VIVO XPLAY 3S another great device...unfortunately i doubt there will be any custom roms made for that device i doubt the source code will be released for it....also the nubia X6 http://liaow.com/nubia-x6-128g-white.php is another nice device that may never see a dev get their hands on the source code to customise...a shame really but thems the breaks i suppose,
once again thank you for all your hard work up till now and in the future
:good::good::good:
mrsynister1971 said:
yeah things are looking slow for the find 7 QHD,i will probably have my 1+1 by the time this device gets a stable custom rom,plus i am also looking at the VIVO XPLAY 3S another great device...unfortunately i doubt there will be any custom roms made for that device i doubt the source code will be released for it....also the nubia X6 http://liaow.com/nubia-x6-128g-white.php is another nice device that may never see a dev get their hands on the source code to customise...a shame really but thems the breaks i suppose,
once again thank you for all your hard work up till now and in the future
:good::good::good:
Click to expand...
Click to collapse
most devs are just getting dev units.... Ethan Chan already working on kernel for Fin7Qhd on cm so... just be patient ....
Is this persistent after an upgrade?
Want to confirm this isn't broken after installing a newer nightly
So does it work on x7096 qhd?? anyone can confirm please?
thx in advance
Hi everybody.
I compiled Twrp for our device with new partition layout. I hope you like it Also I am not responsible for anything just flash it at your own risk. I have tested and it is working
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
How it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to change filesystem (for Lollipop) follow these steps.
After flashing TWRP reboot inside TWRP recovery again, because now you must be sure to use the new one
Wipe Data as ext4 or f2fs partition (Wipe -> Advanced Wipe -> Select Data -> Repair or Change File System -> Change File System -> EXT4 or F2FS -> Swipe)
Wipe Dalvik Cache, Cache, System and Android Secure (inside Wipe -> Advanced Wipe)
If you haven't copied the installation files yet, be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files inside internal sd or external sd
Install the rom package
Install the gapps package
Reboot the system
Great work bro, Congratulations
Everything is working with it?, I cant test it now.
That's great because my home button broke. Now I can update to Lollipop, yay.
Madridii said:
Great work bro, Congratulations
Everything is working with it?, I cant test it now.
Click to expand...
Click to collapse
I tried flashing rom, backup, restore and f2fs. Working here.
Sent from my GT-I8150 using XDA Premium 4 mobile app
Big Thanks @lafactorial . Thanks for the great support . I wait TWRP supports convert partitions f2fs: long time. Very amazing.
Great work! but the two files you upload are the same? And can i use it on kitkat?
micnicmic said:
Great work! but the two files you upload are the same? And can i use it on kitkat?
Click to expand...
Click to collapse
I will check if there are two files when I go home. Yes you can use it on kitkat.
Sent from my GT-I8150 using XDA Premium 4 mobile app
I tested it with pristine way to flash new fresh build of cm-12.1 (f2fs /data), but do you think there is any need to have option to wipe internal storage in menu? maybe it should be removed.
Thanks bro for your work
Hey guys, in case of want to install cm12 should use twrp or the cwm by arco, (not for me)
Both are suitable. If anyone wants to change filesystem of data to f2fs twrp is required.
Sent from my GT-I8150 using XDA Premium 4 mobile app
lafactorial said:
Both are suitable. If anyone wants to change filesystem of data to f2fs twrp is required.
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok thanks for the answer
@lafactorial
+1 :good::good::good:
I can't install kitkat with it
kirito said:
I can't install kitkat with it
Click to expand...
Click to collapse
Can you explain your steps??? I can flash kitkat here.
lafactorial said:
Can you explain your steps??? I can flash kitkat here.
Click to expand...
Click to collapse
I flash thw twrp then reboot to recovery, change data file system (I try both, one by one on every step), clear system, data, dalvik (i don't found android secure on advance wipe, so I skip it) flash rom (failed) then try to install gapps (failed too). The things that only work that just install another recovery haha, so I'm back to install cwm (but I love twrp so much)
kirito said:
I flash thw twrp then reboot to recovery, change data file system (I try both, one by one on every step), clear system, data, dalvik (i don't found android secure on advance wipe, so I skip it) flash rom (failed) then try to install gapps (failed too). The things that only work that just install another recovery haha, so I'm back to install cwm (but I love twrp so much)
Click to expand...
Click to collapse
There is no f2fs support on kitkat. I think that is the problem.
would it be fine if i do the same w/ cache and system partition? thnx much!
dec0der said:
would it be fine if i do the same w/ cache and system partition? thnx much!
Click to expand...
Click to collapse
Only data supports.
Sent from my GT-I8150 using XDA Premium 4 mobile app
Works very well! Changed data to f2fs too and installed Resurrection Remix without any problems.
Reverting to old cwm meanwhile to restore my pa-rom backup was no prop too.
Good job!
Got a little problem after reverting old cwm and restoring my backup..
At first everything looked allright, all apps available and working. On a second view i discovered that i cannot access my internal sdcard anymore. It is shown in the file manager but i dont have permission to write or read.
Guess i have to format it again. But i am not sure what is the correct file system to choose in the recovery?
Any idea else?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TeamWin's TWRP Touch Recovery for LG Optimus G (geehrc).
https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Screenshots:
Flashing Instructions:
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise use adb.
Remember to do backup of your current recovery before installing.
Changes:
compiled on omnirom-7.1 source
latest twrp updates included
updated device trees
prebuilt kernel
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
permissive selinux
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
enabled usb-otg support
enabled modem backup
Download Links:
TWRP-3.0.0-0: geehrc
Device Source:
https://github.com/Split-Screen/android_device_lge_geehrc
https://github.com/TeamHorizon/android_kernel_lge_gee
XDA:DevDB Information
Unofficial TWRP-3.0.3-3 for LG Optimus G variants by dadi11, Tool/Utility for the LG Optimus G
Contributors
dadi11
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-02-06
Last Updated 2017-01-27
Reserved
Changelog:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Great work! Im new to this how do i install it?
enapah said:
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Click to expand...
Click to collapse
I have the same errors
can someone create a flashable zip?
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Guys sorry for errors. I have no OG anymore but still wanted to release something for you guys! I will try to fix it and release update in some minutes
please download and try this one: https://mirrors.c0urier.net/android/Dadi11/TWRP/TWRP-3.0.0-0_GEEHRC.img
enapah said:
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Click to expand...
Click to collapse
He can easily flash TWRP or CWM by using FreeGee App.
I have done this 10minutes ago.
---------- Post added at 08:31 PM ---------- Previous post was at 08:16 PM ----------
Now recovery is working very well!
AROMA Installers are working too
pawelelos said:
Now recovery is working very well!
AROMA Installers are working too
Click to expand...
Click to collapse
Thanks for confirmation
good job
Thanks dadi11. Very generous, especially considering LGOG is not your primary device anymore.
@dadi11 Thank you very much for your time, specially given this is no longer a device at your hand.
I do have one "small" request to make, for those of us who run the official CM builds, it would mean the world to us if we had an image with e975 as device name (instead of geehrc). Any chance you could make one extra build?
Code:
ro.build.product=e975
ro.product.model=LG-E975
ro.product.device=e975
Stable, not bugs:
http://xyyx.ga/nitrogen-os/geehrc/twrp-geehrc-3.0.0.zip
File manager doesn't work properly, cannot list contents in some folders (ex: system)
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
gledis96 said:
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
Click to expand...
Click to collapse
Install as any other zip, then chose reboot recovery from ur recovery which u use.
tiennhu89 said:
Install as any other zip, then chose reboot recovery from ur recovery which u use.
Click to expand...
Click to collapse
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
gledis96 said:
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
Click to expand...
Click to collapse
Ok.u r wellcome.☺
tiennhu89 said:
Ok.u r wellcome.
Click to expand...
Click to collapse
another thing do you know how to install xposed cause i tried flashing it but my phone gets stuck in boot i have this rom
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-aosp-5-1-1r8-optimus-g-t3160195
I want to know any compatible custom recovery for Xperia 10 III. I tried installing TWRP but that ended up bricking my phone.
I don't know if it helps but it is an XQ-BT52.
TrulyPain said:
I want to know any compatible custom recovery for Xperia 10 III. I tried installing TWRP but that ended up bricking my phone.
I don't know if it helps but it is an XQ-BT52.
Click to expand...
Click to collapse
no any custom recovery available for your devices
ada12 said:
no any custom recovery available for your devices
Click to expand...
Click to collapse
Okay, would you expect any custom recovery being released soon or is my best hope to create an myself?
TrulyPain said:
Okay, would you expect any custom recovery being released soon or is my best hope to create an myself?
Click to expand...
Click to collapse
Best solution is compile yourself ...
3day ago I have used twrp trees generator from stock recovery.img
Here sources https://github.com/Aarqw12/twrp_lena
But I no compile succefully for now I'm really no experimented for twrp stuff...
or I will try compile stock recovery witch signature verificstion disabled for allow all zip flash
TrulyPain said:
Okay, would you expect any custom recovery being released soon or is my best hope to create an myself?
Click to expand...
Click to collapse
good news I booted just now twrp compiled
I need fix some issue before open thread
bug no fixed : internal storage decryption ( mtp too so )
work : booting , touchscreen , fastbootd, external storage / usb otg , backup , access to partition system,vendor ...
I hope in 1-2 day its stable
ada12 said:
bug no fixed : internal storage decryption ( mtp too so )
work : booting , touchscreen , fastbootd, external storage / usb otg , backup , access to partition system,vendor ...
I hope in 1-2 day its stable
Click to expand...
Click to collapse
It is sufficient for custom roms
I have a small request. Can you send me system and vendor partitions? Or at least tell me how to get it.
In LG, I could use qfil for this. In Sony I can't do that anymore
In adb I don't see vendor and system
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kyrimeas said:
It is sufficient for custom roms
I have a small request. Can you send me system and vendor partitions? Or at least tell me how to get it.
In LG, I could use qfil for this. In Sony I can't do that anymore
In adb I don't see vendor and system
View attachment 5469595
Click to expand...
Click to collapse
Its fstab I extracted from /vendor/etc , its give you response how is mounted
For encryption, you can just decrypt it after installing twrp. Then you'll be able to see your sdcard no problem.
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
ada12 said:
bug no fixed : internal storage decryption ( mtp too so )
work : booting , touchscreen , fastbootd, external storage / usb otg , backup , access to partition system,vendor ...
I hope in 1-2 day its stable
Click to expand...
Click to collapse
Got any updates on how it's going?
TrulyPain said:
Got any updates on how it's going?
Click to expand...
Click to collapse
No, when I add qcom encryption & blobs recovery no boot...
Without encryption stuff its boot but I get 0mb internal storage
Has there been any progress on the matter yet?
It would be really great if we have the ability to flash unsigned zip files.
@ada12 can you provide me your TWRP build?
I would love to test it.
Even without working decryption it would be a huge added value
@psychofaktory what are you trying to accomplish with the recovery? There's a Magisk module (Backup, by Draco) which gives you a command line tool that dumps partition images, and you can flash them with fastboot. I've dumped the boot partition and compared the checksum with the one I flashed (the one patched by Magisk) and they're identical.
There's also a stock recovery that's very limited but allows you to do factory reset.
It would give the ability to flash unsigned zip files.
This guy has a twrp tree for 10 III. Maybe it can be built and used. Optionally, we can modify the tree from 10 II.
https://github.com/pintaf/android_device_sony_lena_twrp
psychofaktory said:
Has there been any progress on the matter yet?
It would be really great if we have the ability to flash unsigned zip files.
@ada12 can you provide me your TWRP build?
I would love to test it.
Even without working decryption it would be a huge added value
Click to expand...
Click to collapse
I have no shared in public any build because its unusable for user , twrp boot but impossible to mount internal storage , we simply cant flash gapps zip and more ... I need help from pro twrp dev for encryption but seem nobody care for this devices.
they are no sources twrp usable for lena
Would it work to disable the encryption temporarily so that the internal memory of TWRP does not have to be decrypted at all?
It would be really awesome if more developers would show interest in the device.
It's a really great device with a lot of potential.
Can anyone provide TWRP for Xperia 10 III?
ada12 said:
I have no shared in public any build because its unusable for user , twrp boot but impossible to mount internal storage , we simply cant flash gapps zip and more ... I need help from pro twrp dev for encryption but seem nobody care for this devices.
they are no sources twrp usable for lena
Click to expand...
Click to collapse
What kernel are you using?
Maybe some dev from another Xperia could help you.
@modpunk @Sjll
Kyrimeas said:
What kernel are you using?
Maybe some dev from another Xperia could help you.
@modpunk @Sjll
Click to expand...
Click to collapse
I found the solution, flash litegapps systemless as magisk module https://sourceforge.net/projects/li...MAGISK]LiteGapps++_v2.3_official.zip/download