Develop Bugs

[L7][Recovery] TWRP Recovery v2.6.3.0

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Code:
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
Phone look:
{
"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"
}
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
P700
Instalation:
Flash via CWM.
BUGS:
none so far
Contributors
Dees_Troy, bigbiff

Thanks a lot!! That's a wonderful surprise!!!
Good job OP!! I try it now! :fingers-crossed:
Edit: I keep it! TWRP is really nice!

Can i use this on p705 Sir..??

It should be compatible with p705.
Sent from my LG-P700 using xda app-developers app

Any chance for a port to L5? Thanks alt for all your effort

@tudorsirb in Recovery when you tried to install something from Phone memory, Recovery shows folder "0" on Phone memory as a main foleder of Internal (a.k.a. Phone) memory.. Can you change that destination on "sdcard0" because like this, you can not pick anything from sdcard0 to install, if that is not in "0" folder on sdcard0 memory.. Sorry on bad English, i hope you understand..

miki89 said:
@tudorsirb in Recovery when you tried to install something from Phone memory, Recovery shows folder "0" on Phone memory as a main foleder of Internal (a.k.a. Phone) memory.. Can you change that destination on "sdcard0" because like this, you can not pick anything from sdcard0 to install, if that is not in "0" folder on sdcard0 memory.. Sorry on bad English, i hope you understand..
Click to expand...
Click to collapse
0 is the default destination on 4.3. If you are on older ROMs create that folder.
L5 is out of the question because I don't have that phone to test and a bad recovery bricks your phone pretty bad.
Sent from my LG-P700 using xda app-developers app

Great Recovery, Thanks! One question tho, all the ROMs come with CWM so is there a way i can keep TWRP through flashing ROM's / Kernels?

Made a backup through twrp for Vanir and now when I try to restore it, it fails ..

anwarkhan25 said:
Made a backup through twrp for Vanir and now when I try to restore it, it fails ..
Click to expand...
Click to collapse
I just restored a backup to test this. Can you be more specific on your problem?

tudorsirb said:
I just restored a backup to test this. Can you be more specific on your problem?
Click to expand...
Click to collapse
Basically i made a full wipe (system, data, cache & dalvik cache) and then tried restoring my backup i made just a hour or so ago. It starts, but restoring data starts and stays for a while but then after ~5 mins at the top it says Finished and under it says Failed. just to be on the safe side, i didnt reboot into system. I just flashed back to vanir. It's my first time playing with backups so it might be my fault somewhere. thankss!

I really new to whole LG development. I have LG Optimus L7 II. Would this work on that device?
Thanks!

apratomo said:
I really new to whole LG development. I have LG Optimus L7 II. Would this work on that device?
Thanks!
Click to expand...
Click to collapse
This is not compatible with P710 (L7 II). Here is a CWM for P710. This is not my work. I am only directing you to a link for P710. I am not resposable for any damage to your phone. I did not test this,

tudorsirb said:
This is not compatible with P710 (L7 II). Here is a CWM for P710. This is not my work. I am only directing you to a link for P710. I am not resposable for any damage to your phone. I did not test this,
Click to expand...
Click to collapse
:good:

can this work for LG E405, pls

akins47 said:
can this work for LG E405, pls
Click to expand...
Click to collapse
If title say L7 ONLY then its only for L7 !

Any update op to be compatible with the latest kitkat?
sent from my p705g - v20f jellybean extreme w/ stock kernel

vaikz said:
Any update op to be compatible with the latest kitkat?
sent from my p705g - v20f jellybean extreme w/ stock kernel
Click to expand...
Click to collapse
It is

If device is off... How to come into TWRP? Same as CWM?

TheAvngrZ said:
If device is off... How to come into TWRP? Same as CWM?
Click to expand...
Click to collapse
Yup
Sent from my LG-p705 using Tapatalk

[ROM][I8150][5.1.1][LMY47X] AOSP Alpha-1 [2015/05/12]

AOSP-Samsung-msm7x30
{
"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"
}
​
Code:
android-5.1.1_r2
Code:
- WIP
Code:
/*
* 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.
*/
Install
Use CWM6.
Warning: Only use this recovery to flash CM-12.0. Otherwise, you risk bricking your phone, or you might experience boot and stability issues!
Wipe data and cache.
Format /system (only first time coning from older recovery)
Format /data and /data/media (only first time coning from older recovery)
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM12.0 since /system is formatted, wiping your previous add-ons.
Reboot phone.
First boot might take 30-40 minutes, so be patient.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades
Upgrades from previous versions of CM12.0 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM12.0 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
AOSP-Ancora_Alpha-1
Credits
arco
christopher83
CyanogenMod Team
AriesVE DevConnection Team
OptiPop Team
LegacyXperiaAOSP Team
Everyone that donated me
XDA:DevDB Information
AOSP-Samsung-msm7x30, ROM for the Samsung Galaxy W I8150
Contributors
K_TECH, arco68
Source Code: https://github.com/aosp-samsung-msm7x30
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Alpha
Created 2015-05-13
Last Updated 2015-05-13

Aosp changelogs
UNOFFICIAL CHANGELOGS​
Code:
[B][SIZE="4"]2015/05/12[/SIZE][/B]
-Initial release for ancora
-Using K^kernel source as stock kernel (416 of ram) by Christopher83
ANNOYANCES​
Code:
[B][SIZE="4"]2015/05/12[/SIZE][/B]
Knowing bug of AOSP Alpha-1 for samsung msm7x30 devices
- Torch toggle
- No root access
- Button backlight
- Graphic glitch in video recording
- Sometimes graphic glitch in AOSP plat logo
- Power off charging

Enjoy it guys, Hope you like it

gaps
K_TECH said:
Enjoy it guys, Hope you like it
Click to expand...
Click to collapse
gaps nya mana ya mas... / mohon link nya dong...

nice work. pure aosp?
K_TECH said:
ANNOYANCES​
Code:
[B][SIZE="4"]2015/05/12[/SIZE][/B]
Knowing bug of AOSP Alpha-1 for samsung msm7x30 devices
- No root access
Click to expand...
Click to collapse
cant activate root via development options?

I wish there is aosp based on ICS

AOSP LP 5.1.1 ROM, great job @K_TECH, thank you. I'm gonna try it.
Edit:
Has just installed. very light ROM, love it.
one question, I'm okey with no root access or no pre-built file manager installed
but, even with no root access, is it possible to reach my external sdcard using file manager from play store?
Edit 2:
Got it, still can reach external sdcard, my bad

embethcakep said:
gaps nya mana ya mas... / mohon link nya dong...
Click to expand...
Click to collapse
here mas bro, make sure you choose Gapps for 5.1
and next time it will be good if we are using English instead our mother language in international forums.

discotine.... :fingers-crossed:

If you want root access in AOSP, you must flash supersu.zip

Good Work's ;
Adden "File Manager" "EFS Manager vs...."
GAAps Added Link 5.1
PleaseOnly Play Store Added new version

Screenshot
the feature wasn't complete. it cant do screencapture, apps too slow to appear when it touched.
button shortcut not installed too
but the ROM was good

deleoren said:
Good Work's ;
Adden "File Manager" "EFS Manager vs...."
GAAps Added Link 5.1
PleaseOnly Play Store Added new version
Click to expand...
Click to collapse
Installing the GaAps the phone became very slow.....and can't be used....

How to root this rom?

andra81 said:
How to root this rom?
Click to expand...
Click to collapse
Flash supersu

ddstr69 said:
the feature wasn't complete. it cant do screencapture, apps too slow to appear when it touched.
button shortcut not installed too
but the ROM was good
Click to expand...
Click to collapse
Just press and hold power + volume down button for seconds, it works on my phone

iwjosi said:
Flash supersu
Click to expand...
Click to collapse
link me

[EXPERIMENTAL][CAF][MRA58K] Homemade Android 6.0 Marshmallow build

Hello everybody, I'm glad to share these days' work of bringing Marshmallow to the OnePlus One.
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
This ROM is based on CAF release LA.BF.1.1.3-00110-8x74.0, with some little modification to some components to make it build. The kernel is based on CM12.1. You can check the kernel source on my GitHub. Links will be posted later.
Nearly all basic feature should be working: 4G data, 4G->3G fallback on calls, SMS, camera/camcorder, BT, WiFi, MTP, 4K recording, HW decoding etc.
kexec hardboot is supported.
Known issues:
1. Stock camera doesn't work well. Here is a list of comparison:
Feature - Working on Stock camera - OppoCamera port - CameraNextMod?
Switching front/back cam - No - Yes - Yes
Camcorder <=1080p - No - Yes - Yes
4K Recording - No - No - Yes
Click to expand...
Click to collapse
(maybe I should get a monospace font in Firefox)
2. Battery drains... a little faster? (Just a little)
3. The ROM comes with ancient Launcher2. Launcher3 is not included. I will post this as an attachment. Launcher3 has been added since 20151018
4. Picture in apps are sometimes automatically zoomed out (and distorted) and can not be zoomed in. Is this a common problem among AOSP-based Marshmallow ROMs? I tried AOSP and CAF sources, and they both have the same issue. Need to change DPI via build.prop
5. Security related: SELinux is disabledpermissive in 20151018. HW Crypto is not working. Software-based credentials storage.
6. No gestures (DT2W etc) Workaround available in Q&A
7. Kernel panics/reboots on switching adb on & off.
8. WiFi AP still runs on 2.4G even when 5G is selected.
If you find more issues, feel free to post here. However, I may not be able to solve them since schoolwork is so heavy... And this ROM may not be updated regularly.
Video Tutorials by @udimars30:
https://www.youtube.com/watch?v=XxjnTae2nCM - How to install ROM and Gapps
https://www.youtube.com/watch?v=kWZcxVs992c - How to get root
https://www.youtube.com/watch?v=vZ7qW4j3Kso - How to enable softkeys, Now on Tap
Thanks!
Q&A:
1. Kernel Compatibility
The kernel of this ROM is based on CM12.1, but not exactly the same. You can not use kernels built for CM12.1 with this ROM. Marshmallow requires new features like updated SELinux, uid_cputime, etc, but CM12.1 source does not contain these features. You can take a look at commits and it will be clear.
Click to expand...
Click to collapse
2. Recovery Compatibility
I am using TWRP 2.8.7.0 with MultiROM support (TWRP_multirom_bacon_20150803-00.img from MultiROM thread). If you can not get the ROM installed properly, please try updating your recovery.
Click to expand...
Click to collapse
3. Rooting
Since this is a experimental build, I have turned off SELinux completely. SELinux is permissive. Just flash SuperSU 2.50 zip in the recovery and it will be fine.
Click to expand...
Click to collapse
4. F2FS Support
The kernel has F2FS driver builtin and corresponding entries in fstab file (as CM does). Vold has F2FS files as well, so you can give it a try. But I can not guarantee that it will work flawlessly.
EDIT: Some people tested and reported it not working. Make a backup before you try.
Click to expand...
Click to collapse
5. GApps
I'm using DeltaGapps with SetupWizard removed (yes it is the one that keeps force closing. you can disable that via adb as well). I think the lack of permissions(appops_whitelist.xml I guess) caused this failure. After allowing every permission required by Google apps and adding the account manually, Sync and Store works as expected. Now on Tap seems broken. Maps is working, and gets a lock in secs..
There are some other GApps package links in the first few pages. Some people say Now on Tap works with them, you can have a try.
Click to expand...
Click to collapse
6. Disabling HW Keys and Enabling Softkeys - The Easy Way
Code:
echo qemu.hw.mainkeys=0 >> /system/build.prop
reboot # enables soft keys
echo 0 > /proc/touchpanel/keypad_enable # disables hw keys, need to do this on every boot
Click to expand...
Click to collapse
7. Where Is The App Switcher?
If you are comfortable with softkeys, goto 6.
If you are not, goto 3 and take a look at http://forum.xda-developers.com/showpost.php?p=63313126&postcount=115double tap the home key.
Click to expand...
Click to collapse
8. LCD Density
Code:
wm density 440 # if you want 440
wm density reset # self-explanatory
Above will lead to corrupted pics.
Change
Code:
ro.sf.lcd_density=480
to
Code:
ro.sf.lcd_density=VALUE_YOU_WANT
(Note: I did this before installing GApps, not sure if this is related to Google Now Launcher FCs)
Click to expand...
Click to collapse
9. DT2W Workaround
Code:
echo 1 > /proc/touchpanel/double_tap_enable # do this on every boot
Then add this line to /system/usr/keylayout/Generic.kl:
Code:
key 255 POWER
DT2W has been added into settings since 20151027.
Click to expand...
Click to collapse
10. Apps Not Working
Settings -> Apps -> YOUR_APP -> Permissions -> Turn on everything
Click to expand...
Click to collapse
11. Fixing random freezes
http://forum.xda-developers.com/showpost.php?p=63378883&postcount=682
Thanks @The Dork Knight Rises
Click to expand...
Click to collapse
Now screenshot spoiler (with Google Now Launcher):
{
"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"
}
Discussion Thread:
http://forum.xda-developers.com/oneplus-one/general/discussion-homemade-android-6-0-t3227234
Download:
20151027
https://drive.google.com/file/d/0BwkmhbR5VHpAdWRxQ0ZraVgyT00/view?usp=sharing
Marshmallow's native DT2W setting (thanks CM)
USB MIDI support (What for?)
Fixed some crashes by removing SeempLog (try TiBu and network settings)
Double tap on Home key now brings up Recent View
Added a reboot option in power key menu/global actions menu
Note: if you have drain when NFC is on (or NFC setting is grayed out), please attach a logcat of booting process. I can not reproduce this on my phone... Thanks!
20151018
https://drive.google.com/file/d/0BwkmhbR5VHpAekdWT2NlVWNlNnc/view?usp=sharing
Mirror by @c43211 http://c43211.com/aosp_bacon-ota-eng.hamster-20151018.zip
Mirror by @Killer.shubham http://d-h.st/9fOO
Fixed network mode selection (2G/3G/4G switch)
Fixed network location
DT2W workaround: see Q&A
20151015
https://drive.google.com/file/d/0BwkmhbR5VHpAUVVDYkVJOFJoYVE/view?usp=sharing
Mirror by @itskapil at http://downloadmirror.co/android/tx/aosp_bacon-ota-eng.hamster.zip
Mirror by @Killer.shubham at http://d-h.st/3oBU
Mirror by @c43211 at http://c43211.com/aosp_bacon-ota-eng.hamster.zip
Thanks!
MAKE A BACKUP FIRST!
(I'm using TWRP 2.8.7.0 and it works well with this package.)
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8974 (marshmallow branch)
Device tree: https://github.com/updateing/android_device_oneplus_bacon
Blobs: https://github.com/updateing/proprietary_vendor_oneplus
local_manifest: http://www.hastebin.com/netamapate.xml
Hope you can enjoy the new feel of Marshmallow!

Wow! Need this rom to improve.

Excited flashing now!
Sent from my A0001 using Tapatalk

Finally the sweet taste of marshmallow on the OnePlus One!

Great work ! ^_^

Battery drains faster?
Guess I'll wait a little bit longer, as it's the main reason I wanna switch to M.

Kernel dilemma
If the kernel on it is based on cm 12.1 .. Can we flash any other kernels that work with CM 12.1? It should work or atleast i hope so! But yeah I'll try and get back!
Cheers! Keep up the good work!

Do we need to flash gapps & supersu?
Sent from my A0001 using Tapatalk

will it work with F2FS ? separate build would be helpful, if its not tested i will test it
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
horizon_KJ said:
If the kernel on it is based on cm 12.1 .. Can we flash any other kernels that work with CM 12.1? It should work or atleast i hope so! But yeah I'll try and get back!
Cheers! Keep up the good work!
Click to expand...
Click to collapse
i guess it would be tweaked for more compatibility to android 6.0

Great work man !!

Anyone flashed it successfully?

Nice achievement! Glad to see you made it boot.

Finally the bacon.
Was almost regretting for getting this phone

~KV said:
Anyone flashed it successfully?
Click to expand...
Click to collapse
I'm on F2FS didn't tested it

Killer.shubham said:
I'm on F2FS didn't tested it
Click to expand...
Click to collapse
If you flashed it, go to terminal to see if it's on f2fs or not?

Finally ...!!!!
Will test soon ?

This Rom's developer is little busy so we should get other developers work on it and probably get this thread featured?

Tested and WORKING ( I don't if f2fs works)

as a reminder to everyone.. .NO ETA's pls. lets respect the dev.. compiling is already a good thing, and making it boot is a great achievement..

ianstump said:
Tested and WORKING ( I don't if f2fs works)
Click to expand...
Click to collapse
will report in 10 mins
1. flashing it without any custom kernel (probably wont work)
2.flashing rom zip + ak CAF kernel. (hoping for it)
..
Results
1. TWRP says no OS installed ( System is 22mb)
2.Flashing failed

[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

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 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.
Code:
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0