Develop Bugs

ROM Factory v1.7.1[May/12/2012]

{
"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"
}
And thank you all for your Ad clicking and donations. You guys are awesome!
Android Market Link [free]
ROM Factory​
What is ROM Factory?
Its a tool that will allow the user to create a picture perfect .img from your boot and system partition. It will then create an update.zip from it.
What is a "Fruit Cake"?
A fruit cake is the finish product, a self contain rom, already ready for installation, already inside an update.zip.
So really what does it do?
It allows a bootloader unlocked user to create a full copy of their boot and system partition. All of it, including mods and changes done to either one of those partitions.
Can this be use for easier rom development?
Yes! Beyond just its normal capabilities! After installing the resources you can modify the script and add things to it in *sdcard* /fcm/workdir! Once you are done adding and changing things in there, press "Create ROM".
Supported Devices:
olympus (atrix), sunfire (photon), triumph, WX435, fb0 (triumph), p999 (lg g2x), p990 (lg o2x), p970 (lg optimus black), ace (htc desired hd), pyramid (htc sensation), galaxys2, GT-I9100, GT-I9100M, GT-I9100T, SGH-I777, SGH-I727, hercules, crespo (nexus s), crespo4g (nexus s 4g), toro (cdma galaxy nexus), maguro (gsm galaxy nexus)
Experimental Support:
umts_jordan(defy), wingray, stingray (xoom)​
Your phone must be rooted!
Step One: Press the Install Resources button on screen.
Patience this step could take up to 5 minutes.
Step Two: Press the Create Fruit Cake button on the screen.
Patience this step could take up to 5 minutes.​
You use this application at your own risk, I am in no way responsible for any damage this application causes.​

Oficial Support for Galaxy S2
Back Up mode = Further information is needed to enable back up mode for this device

Am I right to understand that this is an alternative to taking Nandroid backup?.

hacksome said:
Am I right to understand that this is an alternative to taking Nandroid backup?.
Click to expand...
Click to collapse
no 10 xchar

So it will create an update.zip which is CWM flashable? How about generating a .tar.md5 for Odin?
Anyways, great work! Looking forward to this!

hacksome said:
Am I right to understand that this is an alternative to taking Nandroid backup?.
Click to expand...
Click to collapse
Sounds like it, looks cool non the less.
Sent from my GT-I9100 using XDA App

Kingybear said:
Sounds like it, looks cool non the less.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Afaik a nandroid backup is everything including data folder. This one i think is a little less than that. As op said it copies the rom so devs can pass them to their beta testers etc. A nandoid backup is including ur personal settings like bookmarks or last viewed webpages and contacts etc. And a nandroid backup is recovery dependant. Afaik a nandroid from a cwm v4 base wont be suitable for a phone with a cwm v5 phone.
Sent from my GT-I9100 using Tapatalk

FCM RC3 v1.4.4
FCM RC3 v1.4.4(Current Release)
Release Notes
Added Reset Option Menu.
Re-write the engine that configures the phone install!
fixed a bug on photon 4g.
fixed the force close of doom bug.
fixed sgs2att issues
fixed sgs2att install script
fixes to various bugs
Added support for latest ics
GUI Touch Ups
Added Experimental Support:
triumph, WX435, fb0, p999, p990, p970, ace, pyramid, galaxys2, GT-I9100, GT-I9100M, GT-I9100T, SGH-I777, SGH-I727, hercules, crespo, crespo4g, toro, maguro

#FCM RC4 v1.5(Current Release)
-GUI Enhancements
Multiple Screen Size support
Tablet Support
A new themed layout
NO MORE ADS
-Script Engine Enhancements
Options, ie: Dev name, rom name, save rom preferences.
-Performance
Complete Re-write of the install and create methods (faster performance)
The reset button is bye bye! The app will now erase the workdir as it creates the rom!

Hello Guys
Is anyone experiencing issues, someone msg me about some installation issues, but did not really offer any info. If you are an user and you are suffering from install issues, let me know!

guys for latest info always check http://fcm.x10.mx/joomla/

1.6 - The update that took a month. Will be release today. This will be amazing. I'm just waiting on testers.
Advance Mode
Apps Mode
Back Up Mode
New look
Open Source components
New site, new forums, new devices.
The update will be made available late tonight or early tomorrow. Depends on how tire I am after i get off work.
We are alive and kicking. Since release, Fruit Cake Maker has been downloaded 1,956 times. We are 556 active developers. A total of 12 bugs have been crushed. We currently work on 20+ devices and devices variants.
Nightlys and experimental.
Starting Feb 1st or 2nd. My build bot will begin auto compiling nightlys for those who want to experiment with the latest changes. Nightlys will be compile each night and made available no later than midnight.
An experimental build will begin to be compile mid Feb. the build will be compile every friday at 6pm. The experimental build will feture a different preference screen, and will require the user to specify all the variables. ie: boot location, system location, storage, mode. so on. This build aims at enthusiast who wish to use the tool on a non supported device.
FCM now has requirements. Busybox must be installed to use the back up mode.
Thank guys for your support.

I think it's great personally, used it on DHD also with ease.
I'm surprised this project doesn't receive more attention.
It certainly deserves it.
Many thanks

Wow. If I get it well, it create a flashable zip image of your current installation, with apps etc?
Wow. That will be a lot easier to share beta ROMs in the future.
Many many thanks.
Envoyé depuis mon GT-I9100 avec Tapatalk

I'm currently waiting on Google.
I submitted the new version into the market, but somehow i ended up with an older version being available for download. hopefully this issue will be solved soon. I'm sorry for the inconvenience.

1.6 finally!
Some of the testers are reporting errors with the new modes, but changing storage location seem to be working quit good. I will be writing a tutorial on how to properly use all the new modes. Regardless, this new version requires Busybox for app mode, and back up mode. It must be installed on /system/xbin << same location used by cm7 and cm9. I will be releasing a new version tomorrow or Thursday, to fix some of the new mode woes.
Again, sorry for the inconvenience.

Very good work!

Awesome! keep the good work, I will try it tonight from home.

Sounds Great
Hello,
The ROM Factory sounds like a great Idea, im not a developer but i can see why its great for devs,
Question is, will it be useful for just a user like I am?
if i am to use it to back up, how does it differ from Titanium and CWM NAND backup?
Thanks

Go read post #7

--OLD DELETE ME! [ROM] OnePlus One / CyanogenMod 11S

OnePlus One CyanogenMod 11S for the Oppo Find 7a
People with much better skills and more time on their hands than me have been doing great work on this after I initially posted it. I am updating the OP with their comment. Please give all credit to them.
CM11s for Find 7(a) V3: DOWNLOAD
SDCard Support Package V3: DOWNLOAD
Changelog:
*) Removed NFC Support (it was broken anyway, and consumed a lot of battery)
*) Greatly increased Battery Runtime (see above why)
*) VOOC Charging Support
*) SDCard Lagfix (for those using the SDCard Support Image, if you like benchmarks see appendum)
Appendum:
SDCard Benchmark before Lagfix (128GB Sandisk SD Card):
27.82MB/s Read / 12.48MB/s Write
SDCard Benchmark after Lagfix (128GB Sandisk SD Card):
39.42MB/s Read / 12.55MB/s Write
INSTRUCTIONS FOR INTERNAL MEMORY USERS (10GB Storage)
1. Install TWRP Recovery
2. Install cm11s-oppo-find7a.zip
3. In TWRP Recovery do... Wipe -> Advanced Wipe -> Tick System, Cache and Internal SD -> Slide to Wipe
4. Reboot System
INSTRUCTIONS FOR EXTERNAL MEMORY USERS (as much storage as your SD-card can offer, for me thats 128GB)
1. Format your SD-Card as EXT4 and plug it into your Find 7(a)
2. Install TWRP Recovery
3. Install cm11s-oppo-find7a.zip followed directly by sdcard-data.zip
4. In TWRP Recovery do... Wipe -> Advanced Wipe -> Tick System and Cache -> Slide to Wipe
5. Reboot System
Final Notes
This bundle includes the first two OTAs from the first page of this topic, a bunch of sensor configuration changes to fix the sluggish behavior of the GUI and the slow (un)locking of the screen as well as the proper Find 7(a) radio binaries to give you proper reception.
The Back Camera is still upside-down with this package and just like many other people in this topic I'm still researching why that is the case / how to fix it. Truth be told though I think someone else will have it figured out way before me!
Also - this ROM is meant to work with a "unified storage" at its core.
The basic installation will use the internal /sdcard partition as its unified storage (rather than the leak on page 1 which uses /data) giving you 10GB of unified storage for both your apps and data.
If you need more storage, you can flash the optional sdcard-data package which will use your external SD-card as the unified storage for apps, settings and data.
To do that though your SD-card has to be EXT4 formatted, I suggest using Ubuntu plus the gparted Tool to get the job done, a live-boot-disc is enough to do that.
As for me, I highly suggest going the SD-card unified storage route, its damn nice having 128gb of unified storage to work with.
Also, should you ever need to back your data up all you have to do is pull the SD-card and copy it somewhere using Linux (all your data - and I do mean ALL - is stored on that SD-card after all thanks to the unified storage).
PS. Unlike what some other people have told here, using this build with the changed sensor configuration seems to run okay on FastCharging from what I can tell. Non the less please handle all of this thread's contents as early early alpha content and expect to run into bugs.
Should you find any, please report them and / or share constructive criticism on how to fix them.

rayfin said:
You can install the OnePlus One ROM from the OnePlus One on the Find 7a.
What works:
Front Camera / Video
Microphone
WiFi
Data
Bluetooth
Sound
GPS
Calling
What doesn't work:
Rear Camera / Video are upside down
Voice Wake
NFC
Storage is only reporting 3GB
--------------------
I modified the updater script to not check for the OnePlus One (bacon) when flashing. You can download it here:
Full ROM: http://www.androidfilehost.com/?fid=23487008491963275
OTA: http://www.androidfilehost.com/?fid=23487008491963298
Click to expand...
Click to collapse
Awesome! Thanks. Now someone needs to tinker with it and get everything tweaked to work properly on the 7a.

Nice.. Now give me credit
Sent from my One using Tapatalk

rayfin said:
You can install the OnePlus One ROM from the OnePlus One on the Find 7a.
What works:
Front Camera / Video
Microphone
WiFi
Data
Bluetooth
Sound
GPS
Calling
What doesn't work:
Rear Camera / Video are upside down
Voice Wake
NFC
Storage is only reporting 3GB
--------------------
I modified the updater script to not check for the OnePlus One (bacon) when flashing. You can download it here:
Full ROM: http://www.androidfilehost.com/?fid=23487008491963275
OTA: http://www.androidfilehost.com/?fid=23487008491963298
Click to expand...
Click to collapse
I've got the ColorOS rom downloaded, so I'll give this a shot tomorrow after work and report back.
Doesn't look like there could be too much more to fix (other than optimizations of course) in order to get this ported completely...

rear camera can likely be fixed by using find7a's sensor conf

http://www23.zippyshare.com/v/76743245/file.html
^ second system update

ayysir said:
http://www23.zippyshare.com/v/76743245/file.html
^ second system update
Click to expand...
Click to collapse
Hi Ayysir, do you have any idea of what has been changed with this update?

MicMeo said:
Hi Ayysir, do you have any idea of what has been changed with this update?
Click to expand...
Click to collapse
The OnePlus One is currently running a pre-production build of CM11S. This is another OTA to get bugs squashed before launch.

ayysir said:
http://www23.zippyshare.com/v/76743245/file.html
^ second system update
Click to expand...
Click to collapse
I'll take a look at this when I get home in a few see of I can get it working.
Sent from my One using Tapatalk

graffixnyc said:
I'll take a look at this when I get home in a few see of I can get it working.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
2nd update is 109 mb
{
"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"
}

ayysir said:
2nd update is 109 mb
Click to expand...
Click to collapse
@ayysir: It would be very appreciated if you could upload the 2nd update to another host as I'm downloading from Zippyshare with around 2KBps.
Cheers.

Please post screenshots or updates so we know how it's going and what everything looks like. Kudos to person/persons responsible for porting this to the 7a.

Looks fun ! Same device with another name... then another ROm... Portage can be easy enough...

babyree said:
Please post screenshots or updates so we know how it's going and what everything looks like. Kudos to person/persons responsible for porting this to the 7a.
Click to expand...
Click to collapse
use google.com and youtube.com... plenty to find there

There is no need to download all updates. You guys can flash original 1+1 recovery and then you get all 1+1 updates OTA.
Gesendet von meinem One mit Tapatalk

When you do so, are there any bugs left? Because if not they wouldn´t get fixed because of the original ota which is for the oneplus, or not?

EnormoDerClown said:
When you do so, are there any bugs left? Because if not they wouldn´t get fixed because of the original ota which is for the oneplus, or not?
Click to expand...
Click to collapse
ofc there is bugs... sensors is derped and storage is mapped for internal sd only

That´s what i thought, but than an official ota is useless, because you will never be able to use the phone fpr 100%, or not?

ayysir said:
ofc there is bugs... sensors is derped and storage is mapped for internal sd only
Click to expand...
Click to collapse
I think AOSPA is round the corner because you can use alot stuff from 1+1.

m3dd0g said:
I think AOSPA is round the corner because you can use alot stuff from 1+1.
Click to expand...
Click to collapse
actually wrong, most of the blobs are the same and cm using some old configs

please help :(

hello all
i don't know where i can post this so plz anyone help me i have a problem with auto rotate how i can fix it

Max Code said:
hello all
i don't know where i can post this so plz anyone help me i have a problem with auto rotate how i can fix it
Click to expand...
Click to collapse
Hello.
Let's take them one by one.
1. you should post things like this here.
2. you need to specify which ROM are you using and whether or not you installed any mods or tweaks on it.
If you're using a custom ROM, such as a CyanogenMod ROM or another one based on it, make sure that the installation procedure below was followed (ALL the steps). This is in case you have a custom ROM like the ones mentioned above. For stock ROMs, you will need to use ODIN on your PC and follow steps 1 , 2, 3, 5. On step 4, you will need to flash the stock ROM via ODIN. For both cases, you will need CWM Recovery (which will be replaced by the stock recovery when the flashing of the stock ROM is completed successfully).
Steps to follow when flashing a custom ROM. Make sure the ROM and the Gapps are on your external memory.
Enter CWM and:
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
install the ROM (from the external sd)
install the corresponding Gapps (from the external sd)
reboot your phone

arsradu said:
Hello.
Let's take them one by one.
1. you should post things like this here.
2. you need to specify which ROM are you using and whether or not you installed any mods or tweaks on it.
If you're using a custom ROM, such as a CyanogenMod ROM or another one based on it, make sure that the installation procedure below was followed (ALL the steps). This is in case you have a custom ROM like the ones mentioned above. For stock ROMs, you will need to use ODIN on your PC and follow steps 1 , 2, 3, 5. On step 4, you will need to flash the stock ROM via ODIN. For both cases, you will need CWM Recovery (which will be replaced by the stock recovery when the flashing of the stock ROM is completed successfully).
Steps to follow when flashing a custom ROM. Make sure the ROM and the Gapps are on your external memory.
Enter CWM and:
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
install the ROM (from the external sd)
install the corresponding Gapps (from the external sd)
reboot your phone
Click to expand...
Click to collapse
thanks very much i solved the problem

Max Code said:
thanks very much i solved the problem
Click to expand...
Click to collapse
Glad to be helpful.
Sent from my GT-I9195 using Tapatalk

arsradu said:
Glad to be helpful.
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
2 more questions pls
i always see the status bar color blue but mine is white how i cant change it to be blue like that
{
"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"
}
another question
is this kernel gives me more ram
http://forum.xda-developers.com/showthread.php?t=2528600
and thanks very much for your help

Max Code said:
2 more questions pls
i always see the status bar color blue but mine is white how i cant change it to be blue like that
another question
is this kernel gives me more ram
http://forum.xda-developers.com/showthread.php?t=2528600
and thanks very much for your help
Click to expand...
Click to collapse
1st question: since you're probably running CM11 (KitKat), use a theme from the Play Store. There are a few default JellyBean themes that should change those colors back to blue. I personally love the new white in KitKat but, of course, it's a matter of taste really. If you're on JellyBean, you just have to apply the default system theme (assuming you didn't do a dirty installation, after flashing a KitKat ROM for example). That white is only available as a CM11 theme, or by default, in CM11 ROM.
2nd question: That kernel is:
for CM10.1 or CM10.2. So if you're running CM11, no, you cannot use it
not up to date. So it might not play nice with CM10.1 or CM10.2. So, I wouldn't recommend it. Yes, it should give you more RAM, BUT it might cause you more troubles since it's not updated.
The problem with this device is the low amount of RAM and the fact that the apps are becoming more and more hungry for RAM. If you allocate more RAM for the user, you take from the one for the system, and eventually you might encounter system freezes. If you give more to the system, the user will have less to load apps. It's a compromise, especially when you're working with this low amount of RAM.

arsradu said:
1st question: since you're probably running CM11 (KitKat), use a theme from the Play Store. There are a few default JellyBean themes that should change those colors back to blue. I personally love the new white in KitKat but, of course, it's a matter of taste really. If you're on JellyBean, you just have to apply the default system theme (assuming you didn't do a dirty installation, after flashing a KitKat ROM for example). That white is only available as a CM11 theme, or by default, in CM11 ROM.
2nd question: That kernel is:
for CM10.1 or CM10.2. So if you're running CM11, no, you cannot use it
not up to date. So it might not play nice with CM10.1 or CM10.2. So, I wouldn't recommend it. Yes, it should give you more RAM, BUT it might cause you more troubles since it's not updated.
The problem with this device is the low amount of RAM and the fact that the apps are becoming more and more hungry for RAM. If you allocate more RAM for the user, you take from the one for the system, and eventually you might encounter system freezes. If you give more to the system, the user will have less to load apps. It's a compromise, especially when you're working with this low amount of RAM.
Click to expand...
Click to collapse
you're great thanks very much

Nice info, thanks

[GUIDE] Dualboot Custom ROMs on L5 and L7

{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support L3II, L5, L7 and L7II (Officially)
I am not the creator, just the supporter
XDA NEWS!!!
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch or the old CWM )
2. A KitKat ROM (Real KitKat ROM, not build.prop edited, a fake KK ROM)
3. The Dualboot Patcher - http://goo.gl/0bcbbN (Download the APK in Downloads Section)(For L3II, L5, L7 and L7II)
4. A KitKat ROM (To install )
Installation
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire)
2. Install the DualbootPatcher
3. In the Patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. After this you need to go in menu (the tree dots) of Primary ROM and search for Update Ramdisk. Press it.
5. In the patcher, go to the Patch ZIP file section, open your ROM zip file
6. After this select in what partition you want to install:
Primary ROM Upgrade - To update ROM without affect the Secundary ROM (and others) when you have one installed.
Secundary - To install in /system.
MultiROM (1-3) - To install in /cache, you have 3 slots in this.
Data Slot - To install in /data (ID is IDentification of ROM)
Extsd slot - To install in your sdcard
7. You not need to change the Device
8. Do the same for GAPPS (optional)
9. Press in confirmation button and wait.
You have two options here:
9. Go to ROMs section and press in button of a device with arrow inside, select the patched zip files (ROM and GAPPS), and by last press in confirmation button, just wait..
10. After finish, close the app (see Know Issues), open and go again to ROMs section and you will see the default ROM to boot (the last installed). Reboot your phone.
11. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
or
9. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
10. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Never use this in JellyBean 4.1 or "You are gonna have a bad time"
- Contact me
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@virulentt for him original thread for tutorial (and encouragement)
@Jonas Cardoso for testing in L5
@WinterR for testing in L7
@ECr34T1v3 for testing in L3II
ScreeShots
​

Thanks for the mention

@WinterR test the unofficial snapshot, please

What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1

ch3mn3y said:
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
Click to expand...
Click to collapse
For kernels you need to flash two times, first flash with patched zip (in app) and second flash you need to set the ROM and flash again (via recovery).
The first will update modules (/system) and second is to update the boot.img
Note: Ever you change kernel you need to go to app and set the kernel to save you new boot.img

Now DualBootPatcher supports the L7 and L7II!!!

I got some time and would like to check it out.
I can only use 4.4.4 roms (on L7 there are no newer ones)?
How it works with sdext? Is it used as both /system and /data? Or just /system? But than where is nonprimary rom /data located?
PS. What file systems are supported by app? Or maybe it depends on kernel?

@ch3mn3y you can use all ROMs up to 4.2, because SELinux and other core things like storage/emulated/0.
The SdExt only store system.img, and only system (for now, the patch is under progress all time).
You have option to put 1 in /system (dual), 3 in /cache (multi-slot), and unlimited in /data and /sdext (External Card).
Support F2FS and Ext4, auto-detect, just need support in your ROM and all will works (not tested because no F2FS support for mine device )

If I can ask: where /data goes? I mean /data/app, /data/data, etc., not /data/media)?

So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?

ch3mn3y said:
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
Click to expand...
Click to collapse
The rom is stored in any partition in a folder called "multiboot", try other rom or old app versions.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

I used this: DualBootPatcher-8.0.0.r2115.g279e1b2-win32.zip (last build from 09.01.2016). It patched the file (older ones couldn't open the archive). Now i will try to flash it on my device and than i will probably use app from the same build (DualBootPatcherAndroid-8.0.0.r2102.gd35e5db-snapshot.apk).

Naah, i use newest app. Zips can be edited on Windows machine.
Small request: any chance to move /cache and /data to the same folder as /system? Or at least /data (as /cache is more temporary) as it can become big for one rom and we have less than 3GB of space on this partition...
Sent using XT1562 - stock 6.0 (retasia DualSim)
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
Bug?
After reboot from extsd rom back to primary, app on ptimary doesnt find sdext rom. I can only choose primary one.
Only change on sdext rom I did is installation of app...
Sent using P700 - Mahdi-Rom/SKernel

Check in external card the multiboot folder.
This app have a lot of bugs, use the zip in DualBootPatcher site, for cat the logs, and we can see if something goes wrong and report a bug.
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Its ok. After 2 reboots of primary rom, sdext one is back and after next two reboots between roms its still there. Dont know what was wrong, but right now i suppose there wont be any useful info in logs.
Downloaded the logs zip, so next time will use it.
It works really fast from class 4 sdcard. However I thought that extsd is 2 partition and created one
Sent using P700 - Mahdi-Rom/SKernel

Thread closed as per OP request.
-XDA Staff

[ROM] [UNOFFICIAL] Lineage 20 - scorpio (Mi Note 2)

By entering this zone you agree to the followings:
- Your 'expired' warranty is now void
- I'm not responsible for your girlfriend/boyfriend getting mad at you because the call didn't came through
- Also not responsible for missed alarms due to alarm not firing
- Or loosing your job due to late notifications
You're a great guy. Happy discovering and have a nice day!
Click to expand...
Click to collapse
LineageOS 20 for Mi Note 2
Beware, you are about to enter a dangerous zone!
{
"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"
}
After much tinkering and countless of brain explosions, I have determined that my lineage-20 builds for Mi Note 2 is suitable to be released for the public.
Please note that the ROM bears the "[UNOFFICIAL]" tag for a reason - you might face instability or performance issues.
You are not recommended to use this ROM for daily usage, just to be safe. I am not an experienced developer, hence my changes could be wrong or incomplete,
rendering issues to occur on the device.
Full credits to bgcncm, luk1337, haggertk, joe2k01, and all other xiaomi/msm8996 developers.
This ROM is based on official xiaomi/msm8996 sources by LineageOS, with my changes on top to get lineage-20 working.
Without their work on xiaomi/msm8996's Linux 4.4 kernel, this wouldn't be possible at all. Please consider donating to them or the LineageOS foundation.
Additional, huge credits to ChronoMonochrome and @rINanDO for their huge assistance in my early days of Android development.
Please refer to my github repositories for more information on my commits and changes made on top of official LineageOS repositories.
Things to take note:
- Not all features are fully tested as I do not have the required equipment etc, such as testing Bluetooth audio, Dual SIM network, or Netflix.
- Builds will be SELinux permissive for the time being.
- Builds are using EAS (Energy Aware Scheduling) configuration, rather than the traditional HMP configuration. No PowerHAL is included for the time being.
What's not working:
- SELinux (permissive)
- PowerHAL (excluded for EAS switch)
- Camera HAL log spam
- other untested features (ie. DRM, Bluetooth audio)
- some other non-fatal, kernel side errors and outdated configurations
- you tell me.
What's working:
- everything else.
Installation steps:
1. Update system to latest stock.
2. Unlock bootloader and perform factory reset.
3. Utilize fastboot to flash and boot recovery.img from my Download link below.
fastboot flash recovery recovery.img
fastboot boot recovery.img
You can also boot official TWRP first to make persist and EFS backups. (Highly recommended. )
4. Wipe everything, and sideload ROM zip using adb.
adb sideload lineage-20.0-20230420-UNOFFICIAL-scorpio.zip
5. Flash GAPPS if wanted. Reboot and have a sip of coffee.
Downloads:
https://drive.google.com/drive/u/0/folders/1I3r_LPRZ-2OSAVH6rMrvCDmMCJMj97RP
ROM Information
Variant: LineageOS 20 (Android 13) - UNOFFICIAL
Target: scorpio (Xiaomi Mi Note 2)
Maintainer: lee.wp14 (github.com/leewp14)
Source: https://github.com/hikuii

Latest Release: 20230424
Release Status: Not stable, not unstable, just right.
Release Notes:
- initial release
FAQs:
Spoiler: FAQs
1. What is "Not stable, not unstable, just right"?
A. Because I dare not declaring my builds stable when it is clearly based on expert works (looking timidly at LineageOS maintainers..) and they haven't release lineage-20 for gemini and natrium.
Afterall, there's still huge pile of stuffs to work on before I can slap the word 'stable' to my builds, which I can be most certain it won't happen.
2. Safetynet? Root?
A. Passing SafetyNet requires one additional measure for Android 9 and above: chmod 0640 /sys/fs/selinux/enforcing. I still haven't implement the changes in device tree. Otherwise, without Magisk installed, everything is well-handled and apps should work.
3. Some apps still detect root. Why?
A. This is because some apps are detecting system props, particularly looking for userdebug/test-keys and ro.debuggable=1 props. You could modify build.prop to workaround this, but bear in mind that in Android 13, there are multiple build.prop scattered across /system, /odm, /vendor, /system_dlkm, /system_ext...
4. ETA?
5. Ok... but when you going to update?
A. No definitive answer. I'm doing this in my free time and on a voluntarily basis. New builds will only be released after it passes my quality inspection, and that it actually includes major changes. Maybe there won't be any update at all if all is well.
Screenshots:
Spoiler: Screenshots
This is pure LineageOS, Google for pictures.

Me during development:
Give me praises if you want to keep me happy uwu <3
Cutie Pictures:
Spoiler: DO NOT OPEN

Great rom for a great smartphone!
Many thanks for your job!

Thanks.
-Just reporting. \/
edit 1: How to get rid of decrypt data? im trying to make some backups using twrp.
edit 2: besides the sad decrypt data issue, the instalation process seems to restore the default partition table. It deleted my custom 4gb+ system partition and restored to stock 2,975mb (only a problem to postmarketos/plasma users).

betume said:
edit 1: How to get rid of decrypt data? im trying to make some backups using twrp.
Click to expand...
Click to collapse
oh. Don't think that's possible. A new recompilation of TWRP is required, or if someone did it.
Now new android requires FBE encryption, not even FDE, so old TWRP will not able to decrypt it.
If backup is really important, suggest you to use dd first, or adb pull your files. I don't know how to compile TWRP, so can't build one for now.
betume said:
edit 2: besides the sad decrypt data issue, the instalation process seems to restore the default partition table. It deleted my custom 4gb+ system partition and restored to stock 2,975mb (only a problem to postmarketos/plasma users).
Click to expand...
Click to collapse
I have checked on the installaton steps of postmarket os for scorpio, and I'm stunned. If an image file could "repartition", then no doubt flashing LineageOS will also able to "repartition" it back since android zip builds use image patching too. We actually have to specify the size of partitions in device tree configurations.
I never came across this method of "repartitioning" and couldn't find further information on Google. Do share with me if you know any references about this.