Develop Bugs

[tool] Multirom v3 , DualBoot Patcher Updated to version 3

{
"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"
}
Multirom v3 , DualBoot Patcher
tutorial also changed please read again
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* dead phones , car explosion , your phone explosion
* 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 tool
* 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.
*/
Introduction :
I'm proud to present you the first dual boot project for the Qualcomm-based Samsung Galaxy S3 Neo and Samsung Galaxy Grand 2 and Galaxy S5 mini ! This will allow any ROMs and as many as you want to be installed at the same time. It works by patching the secondary's ROM installation scripts and boot image to load the ROM files from an alternate location (/system/dual, /cache/dual, and /data/dual). Because of the way this is implemented, no changes to the primary ROM are necessary
About :
Hello guys, as some of you guys know and some of you dont I was working on dual boot and dual boot v1 beta, which was released in our great Telegram group, but not in XDA, because of some reasons and rude MAXSIMUS96 that doesn't have any respect to a great development. But anyway I dont care
Lets Start
Well here's v3 + dbtools removed
patched files are flashable with recovery now
added full s3 neo support :angel:
added full grand 2 support :angel:
added full s5 mini support :angel:
more
Now you can have unlimited ROMs!
Tested with 4 CMROMs + 2 stock ROMs
Here's the topic of the base tool used: Dual Boot Patcher
Here
Make sure you leave a like on the great post of base tool I used here
What is Dual Boot or Multiboot?
DualBooting or multi Booting means having 2 or more ROMs at same time on the phone and choose between what you want to boot on next reboot
Why i need this? Is it even useful???
Yes it is! You can fix offline charging on some ROMs like CM12.1, you can have stock battery life, motion beauty, CM12.1's and CM11's performence at the same time without flashing any of them. Just one click from changing to the ROM you like
Whoa that sounds awesomeeee! is it difficult to install??
In v1 yes, but now on v1.5 i added dbtools (DualBootTools) that make most of things automated and even easier for noobs
now v2 things got even easier full s3 neo support
Any ScreenShots !?
see post #3 attachments
I want to see how it is ! is it possible , any videos ?? !?
see post #3 post
First Things first ! Go and make Backup of your files
Requirements :
an S3 NEO
root access of course
busybox if you are on stock ROM
recovery (twrp 3.0.0 is the best)
brain (the most important)
time and being relaxed
downloaded files
installation tree:
download and preparing files
setting kernel
patching the ROM
flashing
switching ROM
updating ramdisk
extras...
done enjoying
Explaining the tools
First: dbtools (removed due v2)
DualBootPatcher:
the great app mentiond above that made dualbooting possible
installation :
Now we know all about the tools,so it's time to use our brain
Step 1
download and install DualbootPatcher app
if you are in motion rom do this
if you are on motion rom install Motion fix zip at downloads section . it will change device codename back to s3ve3g
Step 2
Open the app
Slide the menu and go to ROMs
It will request for root access
Allow the root access
and a message will ask about to set the kernel
Select "set now" and after it said kernel set now
Step 3
reboot your device
Now after device is turned on
Go to the app and navigate "Patch Zip File" from the menu
and tap that + button select zip of ROM you want to patch
A window will come up and if you see in "your device selected by default" you done everything right.
then:
If you are CMuser ( means you have a cm12.1 , cm11 or ... on your primary rom)
and want to install another cyanogeonmod rom (cm11 , cm12.1 ...)
Select the partition configuration as "Secondary"
If you are trying to install another ROM that has a huge system
Select partiton configuration as "data slot" and select an ID for the ROM
better to be a number
(It will be installed on data partition this means it will use the device internal storage space )
and select continue and set where to place patched file .
you can add more files to patch there .
and after you are ready to patch the files tap that tick button in action bar
to start patching
Step 4
After you patched the zip ROM go ahead and navigate to ROMs from the menu
select button down corner and select patched zip you patched
and then select keep location (or if you want you can change the location ) and add more patched zips or tap the up corner tick to start install
note : if any thing wrong happend PM me on telegram and send me multiboot.log in internal storage.
Step 5
after ROM is installed
it should be selected the installed rom .
tap and switch to primary rom
now use three dot on side of primary and select update ram disk
and then select reboot now
now after device rebooted go back to the app navigate to roms
now use three dot on side of new ROM you installed and select update ram disk
after it said done
select the rom you installed . ( tap on the icon of it or name )
( if you saw a message about checksum select continue )
reboot the device and see the magic !!!!
your new ROM is booting !!!!
Cool, let's stop enjoying and continue
Step 6
now after your new ROM booted
take your time to setup the device
and go and install dualboot patcher app again
now open the app
Go to ROMs and allow root access and
now use three dot menu in side of primary ROM and select update ramdisk
now use three dot in side of new ROM and select update ramdisk
and reboot
Step 7
now ENJOY your dual booted phone
for now on you just need to select the ROM and boot into it
it doesnt need updating ramdisk any more.
now go to the browser and navigate to this topic and leave a thanks
it helps to keep up the work
How to flash a kernel gapps, camera fix, etc.?
Just patch the file to same partition configuration and flash with app
or patch it with recovery tools and flash
How to flash a kernel gapps, camera fix, etc. on primary rom ?
Just patch the file to primary configuration and flash with app
or patch it with recovery tools and flash
How to boot into other rom if you have boot loop with the current rom ?
boot into recovery twrp 3 and select images , navigate to /sdcard/multiboot/ and you see your ROMS listed in folder , like primary , dual , etc .... open the folder of ROM you desire to boot and flash boot.img to boot partition and reboot the phone
How to Wipe the roms ?
go to rom options in dualboot app select wipe rom and tick all of them and done .
or use the dualbootpatcher utility
How to use dualbootpatcher utility ?
flash in the recovery and BOOOOM !
Thanks & credits
It's all done now, thanks for reading carefully
Please at least leave a THANKS to the topic, it make me feel better and work harder on v2 for our device.
I can't receive any donation due to my country. It will be really nice if you send me donations with google gift cards
credits : DualBootPatcher Developer : @chenxiaolong
@LGaljo for his great help about fixing grammar mistakes and thanks to @Swp1996 for testing on grand 2 and thanks to @sasukesama for testing and helping with s5 mini and thanks to @ziad311 for testing v2 & thanks too @German Developer for video tutorial
hitting thanks button isn't that hard guys
Version Information
note SEANDROID ENFORCING is not a bug it's needed so please don't try to edit the work without permission or try to fix SEANDROID ENFORCING!!!!
What is working and what is not working on the ROMs?
Everything works great
Only bug is about CM11 :
Files created by CM11 ROM can't be opended with the other ROM :B
That's only problem .
Status : stable
version : 3
dbtools version : removed in v2

Downloads and changelog
Downloads
Fixed Grand2 not Detecting
DualBootPatcher-V3 s3 neo and grand 2 & s5 mini
Orginal DualBootPatcher app You can download the utility here
S3 Neo MotionFIx fixed thanks to @Antix2835 for reporting an issue
S3 Neo Duos MotionFIx
Grand 2 motion fix
updated to v3 tutorial changed also make sure u read tutorial AGAIN
if you used v.1.5 u need a clean install for using v2
Code:
v3
added s3ve3gdd ( fixed )
added s5 mini lte version
new design ( im sorry for v2.7 bad design )
fixed cm13 completely
added db-wiki
--------------------------------
v2.7
added in app tut
added fixes for cm13 possibility fix ( my device doesn’t have cm13 so i cant test it )
--------------------------------
v2.6
added new design
--------------------------------
v2.5
optimized Samsung devices
--------------------------------
v2.4
fixes
added multi patch ( more then 2 )
--------------------------------
v2.3
security updates
--------------------------------
v2.2
added support s5 mini
--------------------------------
v2.1
added grand 2 device support
added grand 2 motion fix
--------------------------------
v2
files are flashable with recovery now
dbtools removed
easier to install
update to last sources
new design
fixed partitions
added full s3 neo support
--------------------------------
v1.5
Now you can have unlimited ROMs!
bug fix with system partiton
added data slot support (fixed)

this post will be the ROM suggestions and combinations and screenshots
here is a video by @German Developer https://www.youtube.com/watch?v=ePRdE1OzRWE
my own best :
stock or motion as primary cm12.1 as other
app data sharing is on beta DONT USE IT TILL V2.1 . ( it make apps use same data )
any tw rom should be as primary to work ! this means if u want use any motion or motion based it should be in primary
THIS MEANS YOU CAN NOT INSTALL MOTION OR ANY STOCK AS DATA OR ANY OTHER SLOT !
You can install stock , and install motion on data BUT ! You will face RIL Problem .
with this intruction :
first install motion normally on the data slot,
note : you need 2 gbs space .
then install a custom kernel for motion rom :highfive:

Man, it's great, but I have some questions... If I install a new ROM, I'll not have to reinstall my apps, right?
EDIT: Sorry for my bad english

MarcusBS said:
Man, it's great, but I have some questions... If I install a new ROM, I'll not have to reinstall my apps, right?
EDIT: Sorry for my bad english
Click to expand...
Click to collapse
if you install a new rom like u normal yes . if you install a rom as dual or data slot you have a clean rom you can install any apps you want

Okay, and... About my storage, this will fill my storage?
Sorry for my bad english again

MarcusBS said:
Okay, and... About my storage, this will fill my storage?
Sorry for my bad english again
Click to expand...
Click to collapse
you can install telegram and talk to me there with this link : http://telegram.me/imthemr
yeah it will but if you install on dual ( if it have enough space ) it will not

Excellent

salah eltony said:
Excellent
Click to expand...
Click to collapse
it's a pleasure use thanks button !

I'mTheMr said:
you can install telegram and talk to me there with this link : http://telegram.me/imthemr
yeah it will but if you install on dual ( if it have enough space ) it will not
Click to expand...
Click to collapse
Thank you so much, man...

Great Job mate !!
I'm waiting for v2

Thank!!! Please, make video instruction

iYaro said:
Thank!!! Please, make video instruction
Click to expand...
Click to collapse
Please wait I think @German_Developer is making a little video about this

I will make a video, don't worry, but first when the v2 comes out

twrp 3.0
Sorry bit i don't find the twrp recovery versione 3.0, can you past a link please? Thanks
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Can install the blisspop ROM?

Great work mr!

emabertax said:
Sorry bit i don't find the twrp recovery versione 3.0, can you past a link please? Thanks
---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------
Can install the blisspop ROM?
Click to expand...
Click to collapse
wait for v2 it will be released today

thanks !
sev3n1985 said:
Great work mr!
Click to expand...
Click to collapse
Thanks !

So, in V2, can I boot any S3 Neo Rom as secondary rom? (for example FIUI?)

Antix2835 said:
So, in V2, can I boot any S3 Neo Rom as secondary rom? (for example FIUI?)
Click to expand...
Click to collapse
its not about possibility (everything is possibe) its about space u got . u cant install as dual partition on motion rom and stock however you can install it on data slot as many as you want

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro

{
"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"
}
I am proud to present first Dualboot project For Redmi Pro. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Redmi Pro to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
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. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-omega-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
All Downloads Here​Cheers ! we are officially supported ​
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some ​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Redmi Pro Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro, Tool/Utility for the Xiaomi Redmi Pro
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-08-19
Last Updated 2017-10-03

Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP

Changelogs
-19/08/2017
Initial Release, waiting for adding officially

Much thanks

yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try

yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
Here are the screenshots

yshalsager said:
-19/08/2017
Initial Release, waiting for adding officially
Click to expand...
Click to collapse
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back

daffa ZRN said:
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
Click to expand...
Click to collapse
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines

daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
You can choose zip using any explorer app like ES File

yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Sorry but can you show me how(I'm a noob)

Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?
Error log:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/kate/kate:6.0.1/MMB29M/V8.2.4.0.MHRMIDL:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 13581, tid: 14315, name: pool-1-thread-1 >>> com.github.chenxiaolong.dualbootpatcher.snapshot <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
Abort message: 'invalid address or address of corrupt block 0x7fa60f0090 passed to dlfree'
x0 0000000000000000 x1 0000007faf7ba7d0 x2 0000000000000001 x3 00000000007fabf9
x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010
x8 7f7f7f7fffff7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 0101010101010101
x12 0000007faf7ba7c8 x13 58934240ef78b85e x14 58934240ef78b85e x15 0030f907887041ba
x16 0000007faf7b4a58 x17 0000000000000000 x18 0000007faca2a000 x19 0000007fa60f0090
x20 0000007faf7bb000 x21 0000007fa60f00a0 x22 0000007faf7bba70 x23 00000055995187e8
x24 0000000000000002 x25 0000005599529258 x26 0000000000000000 x27 0000000032e3dbe0
x28 00000055995a5860 x29 0000007f93a7f060 x30 0000007faf753580
sp 0000007f93a7f060 pc 0000007faf753588 pstate 0000000060000000
backtrace:
#00 pc 0000000000047588 /system/lib64/libc.so (dlfree+408)
#01 pc 00000000000195a8 /system/lib64/libc.so (free+20)
#02 pc 0000000000029054 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#03 pc 0000000000029224 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#04 pc 0000000000011b40 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so (_ZN2mb8format_vERSsPKcSt9__va_list+132)
#05 pc 000000000000abd0 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader11set_error_vESt10error_codePKcSt9__va_list+84)
#06 pc 0000000000009588 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader9set_errorESt10error_codePKcz+108)
#07 pc 000000000000d300 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#08 pc 000000000000c96c /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#09 pc 0000000000009ed8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader4openEPNS_4FileE+308)
#10 pc 0000000000009a88 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader13open_filenameERKSs+216)
#11 pc 0000000000011ec8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmiscstuff-jni.so (Java_com_github_chenxiaolong_dualbootpatcher_nativelib_libmiscstuff_LibMiscStuff_getBootImageRomId+300)
#12 pc 0000000000603934 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/oat/arm64/base.odex (offset 0x35c000)

I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:

yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help

zhaodelin2002 said:
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
Click to expand...
Click to collapse
You know how to fix my issue?

daffa ZRN said:
You know how to fix my issue?
Click to expand...
Click to collapse
sorry,my way isn't same as yours......

Ivan Torres said:
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?)
Click to expand...
Click to collapse
The problem is from app. Not from your device. For me r199 works perfectly. You can use version in this thread also

daffa ZRN said:
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
Click to expand...
Click to collapse
Remove from starting of file to the end of line 3
The file should be started with "package" line

zhaodelin2002 said:
sorry,my way isn't same as yours......
Click to expand...
Click to collapse
What's your way, maybe I can try

daffa ZRN said:
What's your way, maybe I can try
Click to expand...
Click to collapse
modify build.prop

yshalsager said:
Remove from starting of file to the end of line 3
The file should be started with "package" line
Click to expand...
Click to collapse
Still not working do you have a ROM already modified?

[RECOVERY][UNOFFICIAL] TWRP for Xiaomi Mi A2 Lite (daisy) by TWRPBuilder

TWRP Recovery 3.2.3-0 For Xiaomi Mi A2 (daisy) by TWRPBuilder
​
Code:
#include
/*
* 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.
*/
Welcome, all Mi A2 users, This is Lastest TWRP Recovery For your device By TWRPBuilder Team
CHANGELOG for 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
Downloads​Xiaomi Mi A2 Recovery img
​
Sources:
Code:
[CENTER][URL="https://github.com/TwrpBuilder/android_device_xiaomi_daisy"][COLOR="bule"]Device tree[/COLOR][/URL]
[URL="https://github.com/TeamWin/Team-Win-Recovery-Project"][COLOR="bule"]TeamWin Github
[/COLOR][/URL][/CENTER]
How to install:
You must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot boot recovery.img
Then flash img from the recovery
Notes:
You have to format data and disable force encryption in order to access data partition:
- Format data
- Flash Magisk DFE or DisableForceEncryption zip, attached below.
Don't Forget to Hit Thanks :good:
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP for Xiaomi Mi A2 Lite (daisy) by TWRPBuilder, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
TwrpBuilder, yshalsager
Source Code: https://github.com/TwrpBuilder/android_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2018-08-09
Created 2018-08-09
Last Updated 2018-08-18

Disable Force Encryption
Flash one of these files

Screenshots
Attached below

i install it and not boot on twrp, please fix it bro

Will i lost anything after formatting data?

krzygaj said:
Will i lost anything after formatting data?
Click to expand...
Click to collapse
Yes, you will lose all your data (music, video, documents, app, etc.).

BubuXP said:
Yes, you will lose all your data (music, video, documents, app, etc.).
Click to expand...
Click to collapse
Bubu, Seguendo la guida si riesce ad installare la recovery modificata correttamente?
Ho letto che, visto la nuova politica Google delle partizioni A e B, non funziona più fare semplicemente flash recovery blablabla.img

michaelsan1337 said:
Bubu, Seguendo la guida si riesce ad installare la recovery modificata correttamente?
Ho letto che, visto la nuova politica Google delle partizioni A e B, non funziona più fare semplicemente flash recovery blablabla.img
Click to expand...
Click to collapse
Non ho provato ancora questa TWRP, però so che è come dici, cioè non c'è più la partizione di recovery nei nuovi telefoni A/B quindi la custom recovery può essere avviata solo da PC tramite fastboot, non sarà più possibile lasciarla installata sul telefono pronta all'uso.
I didn't test this TWRP on my Mi A2 Lite, but you cannot install a custom recovery anymore on new phones with A/B partitioning scheme, because there isn't a recovery partition anymore. The only way to use a custom recovery is via fastboot with a PC.
EDIT: looking at the TWRP threads for Mi A1 (very similar device), it's possible to install TWRP by adding it to the boot partition (more or less how Magisk is installed).

BubuXP said:
Non ho provato ancora questa TWRP, però so che è come dici, cioè non c'è più la partizione di recovery nei nuovi telefoni A/B quindi la custom recovery può essere avviata solo da PC tramite fastboot, non sar
Click to expand...
Click to collapse

Doesn't boot.

doesn't boot into recovery.img
when i enter:
fastboot boot recovery.img (tried it with TWRP-3.2.3-TwrpBuilder-daisy-20180809.img)
just the normal android starts and not the twrp recovery
cmd history:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot TWRP-3.2.3-TwrpBui
lder-daisy-20180809.img
downloading 'boot.img'...
OKAY [ 0.930s]
booting...
OKAY [ 0.595s]
finished. total time: 1.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>

fizze17 said:
when i enter:
fastboot boot recovery.img (tried it with TWRP-3.2.3-TwrpBuilder-daisy-20180809.img)
just the normal android starts and not the twrp recovery
(…)
Click to expand...
Click to collapse
Can confirm this. Doesn't work.
I don't want to disparage any hard working dev's efforts, but does anyone actually check these things?
We get a "stable" version and install instructions. But if it's impossible to boot through fastboot, it's impossible to test. So how can it be stable?
And if there's no recovery partition, it's impossible to install. So why do we get install instructions?
Is there any evidence that someone was able to disable forced encryption? I couldn't through a modified boot.img.

Curunir said:
Can confirm this. Doesn't work.
I don't want to disparage any hard working dev's efforts, but does anyone actually check these things?
We get a "stable" version and install instructions. But if it's impossible to boot through fastboot, it's impossible to test. So how can it be stable?
And if there's no recovery partition, it's impossible to install. So why do we get install instructions?
Is there any evidence that someone was able to disable forced encryption? I couldn't through a modified boot.img.
Click to expand...
Click to collapse
I was wrong in the previous posts, actually it seems that TWRP could be installed in the boot partition, by modifying it (just like Magisk does).
I checked the info in the Mi A1 forum, as the device is very similar to ours.
But if the TWRP doesn't boot via fastboot, it means it doesn't work. Probably OP compiled the code automatically, without testing it against the device.
EDIT 1: in fact, as they say on their presentation post:
We do not guarantee all images will work as expected. It might even not boot.
Click to expand...
Click to collapse
EDIT 2: finally I tested this, and the result is the same as the other users: it's not booting.
But instead it succeeded to remove Magisk somehow. It's because the phone has booted with the TWRP boot image, not with the Magisk boot.img saved in the phone. In fact, rebooting the phone brings back Magisk.

BubuXP said:
EDIT 2: finally I tested this, and the result is the same as the other users: it's not booting.
But instead it succeeded to remove Magisk somehow. It's because the phone has booted with the TWRP boot image, not with the Magisk boot.img saved in the phone. In fact, rebooting the phone brings back Magisk.
Click to expand...
Click to collapse
I can confirm this. Sme behavior for me. Somehow,it also removed the password to boot Android. My phone still show as encrypted but is not asking the password anymore to boot, which is weird.

BubuXP said:
I was wrong in the previous posts, actually it seems that TWRP could be installed in the boot partition, by modifying it (just like Magisk does).
I checked the info in the Mi A1 forum, as the device is very similar to ours.
But if the TWRP doesn't boot via fastboot, it means it doesn't work. Probably OP compiled the code automatically, without testing it against the device.
EDIT 1: in fact, as they say on their presentation post:
EDIT 2: finally I tested this, and the result is the same as the other users: it's not booting.
But instead it succeeded to remove Magisk somehow. It's because the phone has booted with the TWRP boot image, not with the Magisk boot.img saved in the phone. In fact, rebooting the phone brings back Magisk.
Click to expand...
Click to collapse
As I don't have the device, all testing is the Requester responsibility.
I didn't publish it before testing, he tested and reporting It's working
Anyway, I'll look into it within a few days.

yshalsager said:
As I don't have the device, all testing is the Requester responsibility.
I didn't publish it before testing, he tested and reporting It's working
Anyway, I'll look into it within a few days.
Click to expand...
Click to collapse
Thanks for clarifying. I hope it's possible to fix it!

Are there any news about a twrp that works?

alonsosjumper said:
Are there any news about a twrp that works?
Click to expand...
Click to collapse
Curunir said:
Thanks for clarifying. I hope it's possible to fix it!
Click to expand...
Click to collapse
Here's a working version!
Everything is fixed except data decryption
https://github.com/TwrpBuilder/android_device_xiaomi_daisy/releases
Thanks @Mashudi97 for testing

whats the meaning of custom recovery on this phone while there are no custom rom? just curious

machine1104 said:
whats the meaning of custom recovery on this phone while there are no custom rom? just curious
Click to expand...
Click to collapse
You can root with magisk, flash Project treble GSIs and backup your device

crDroid (10) GSI ported to HUAWEI P10 Lite (Tested On WAS-LX1A)

Hi guys, i ported the crDroid gsi from here.
I removed the unnecessary files from the rom, and included gapps.
And AIO fixes thanks to @DarkJoker360.
Install steps are easy.
1. Download the ROM from HERE.
2. Extract it.
3. Download Pretoriano80's TWRP from "HERE" and flash it using "fastboot flash recovery_ramdisk <path to TWRP.img>".
4. After that reboot to TWRP while holding the VOL+ and POWER button.
5. In TWRP wipe internal storage and flash "THIS" to decrypt the phone.
6. Reboot to TWRP again.
7. Reboot to bootloader while in TWRP.
8. Flash DarkJoker360's TWRP.
9. Wipe everything except Vendor.
10. Transfer the system.img from the rom to your device's internal storage.
11. Tap on Install, then tap on install image, look for the system.img and flash it as System Image and reboot.
I haven't had any bugs for now, if u find something tell me.

It doesn't work.
{
"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"
}

alexut210008 said:
It doesn't work.View attachment 5323563
Click to expand...
Click to collapse
Which TWRP recovery did you use?

At first - twrp_p10_lite_0.6_test
Then - TWRP_3.4.0-0-warsaw_DarkJoker360_20200611

alexut210008 said:
At first - twrp_p10_lite_0.6_test
Then - TWRP_3.4.0-0-warsaw_DarkJoker360_20200611
Click to expand...
Click to collapse
And none of them work? For me they both work, which version of emui are you on? I used the latest update for my phone.

is switching recoverys an important step? weird
wow this actually worked, android 11 aosp for prague booting now on my p10 lite

I did everything according to the instructions. Swears at the size of system.img

is there android 11 based crdroid gsi images you can port?

I do everything strictly according to the instructions.

LesterDMolester said:
Hi guys, i ported the crDroid gsi from here.
I removed the unnecessary files from the rom, and included gapps.
And AIO fixes thanks to @DarkJoker360.
Install steps are easy.
1. Download the ROM from HERE.
2. Extract it.
3. Download Pretoriano80's TWRP from here and flash it using "fastboot flash recovery_ramdisk <path to TWRP.img>".
4. After that reboot to TWRP while holding the VOL+ and POWER button.
5. In TWRP wipe internal storage and flash this to decrypt the phone.
6. Reboot to TWRP again.
7. Reboot to bootloader while in TWRP.
8. Flash DarkJoker360's TWRP.
9. Wipe everything except Vendor.
10. Transfer the system.img from the rom to your device's internal storage.
11. Tap on Install, then tap on install image, look for the system.img and flash it as System Image and reboot.
I haven't had any bugs for now, if u find something tell me.
Click to expand...
Click to collapse
Hi...
ok i will give you a method that i used to get it work on my p10 lite WAS-LX1A 4Gb Dual-Sim
First...if you come from latest stock rom was-lx1a 8.0.0b398c432 you need to downgrade to was-lx1a 8.0.0b394c432 with dload or how ever you prefer. cause with b398 you system partition is just 3,7Gb and can not get rezise. but with the b394 you can rezise it but its no need to. cause after encrypting with fstab.hi6250b and the known following steps...format wipe and so on...the system partition have a size from 4.5gb.
I use the Pretoriano80 TWRP 3.2.1.0 twrp_p10_lite_0.5_test.img
then after initial boot and setup the first config....you can see in apps there is superuser app...its integrate in the Rom.
For using magisk i did the following steps thanks to @Hami_Do
hang-in the system and open file manager in TWRP
delete the following
system/bin/adb_root
system/bin/abdb
system/etc/init/adb_root.rc
system/etc/init/adbd.rc
system/etc/init/su.rc
system/app/superuser
system/bin/su
system/xbin/su
flash the stock ramdisk.img
btw camera works with different modi
for magisk...thanks to @Hami_Do i use v23.0apk
then roboot to TWRP
there flash magisk v23.0-phh.zip

Works on a Was-Lx3 9.00.366 (C212)?
emui 8 stock With elemental kernel v5
Cada vez que instalo una rom personalizada desde Android 9.0, da la animación de arranque y allí se reinicia de vez en cuando hasta que termina en recuperación.

kanade266 said:
Works on a Was-Lx3 9.00.366 (C212)?
emui 8 stock With elemental kernel v5
Cada vez que instalo una rom personalizada desde Android 9.0, da la animación de arranque y allí se reinicia de vez en cuando hasta que termina en recuperación.
Click to expand...
Click to collapse
Why you dont try it? Make a Backup of your current System and return to Stock Rom cause you change Kernel and what ever more. After the initial boot configure the Stock Rom to activate Dev-Opt where you can activate OEM unlock and USB Debugging and so on...
solong
speedson

GizmoTheGreen said:
is there android 11 based crdroid gsi images you can port?
Click to expand...
Click to collapse
My charging port is broken, i won't be able to do any ports until i get it fixed, btw Android 11 GSI's are still not stable as Android 10 GSI's.

speedson said:
Why you dont try it? Make a Backup of your current System and return to Stock Rom cause you change Kernel and what ever more. After the initial boot configure the Stock Rom to activate Dev-Opt where you can activate OEM unlock and USB Debugging and so on...
solong
speedson
Click to expand...
Click to collapse
I already did that and it did not leave me the same problem that happened to the first comment I did everything that the post says

Damn, same problem:
"size of image is larger than target device"

The ROM works fine, although I notice it's quite slow when opening apps and animations. The fingerprint reader also doesn't works sometimes like if it wasn't there but is fixed after a restart.

hello all , thanks for this ROM.
I have a problem when I follow every step without any mistakes. my phone does not want to start . just leave twrp mode and open Huawei eRecovery ( download latest version and recovery * wide data/factory reset * reboot ...)
I don't know why my can't start normally .even the logo not shown
thanks in advance

It is possible to have a detailed guide how to install ?
Thanks.

Hi...
ok a repeat again....if you come from Stock Rom with latest Version called WAS-LX1A 8.0.0.398 C432 your System Partition is just 3,7Gb. You need to downgrade to 1 Version before called WAS-LX1A 8.0.0.394 C432 then the System Partition is 4,5Gb. Now you can flash this custom Rom.
For downgrade use dload method and
Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip - AndroidHost.RU
Download file - Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip
androidhost.ru
download the package and in there you find software/dload and there are 4 folder and 1 update_sd.zip
create a dload folder on your desktop and extrac the update_sd.zip and the 1 folder for your Device. so my is a WAS-LX1A (LX1A=L21A) cause of this i extrac the WAS-L21A folder.
put the update_sd.zip and WAS-L21A folder from downloadet package into the createt dload folder on your desktop. Now copy/paste this dload folder from desktop to external-sd card in your Device, Power off the Device and restart it with press and hold Vol-up+Vol-down+Pwr (no usb cable plugged) now the firmware update should start and wait for progress is finished.

speedson said:
Hi...
ok a repeat again....if you come from Stock Rom with latest Version called WAS-LX1A 8.0.0.398 C432 your System Partition is just 3,7Gb. You need to downgrade to 1 Version before called WAS-LX1A 8.0.0.394 C432 then the System Partition is 4,5Gb. Now you can flash this custom Rom.
For downgrade use dload method and
Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip - AndroidHost.RU
Download file - Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.394(C432) Firmware EMUI8.0 05014JNC [androidhost.ru].zip
androidhost.ru
download the package and in there you find software/dload and there are 4 folder and 1 update_sd.zip
create a dload folder on your desktop and extrac the update_sd.zip and the 1 folder for your Device. so my is a WAS-LX1A (LX1A=L21A) cause of this i extrac the WAS-L21A folder.
put the update_sd.zip and WAS-L21A folder from downloadet package into the createt dload folder on your desktop. Now copy/paste this dload folder from desktop to external-sd card in your Device, Power off the Device and restart it with press and hold Vol-up+Vol-down+Pwr (no usb cable plugged) now the firmware update should start and wait for progress is finished.
Click to expand...
Click to collapse
Software installa failed! I have a WAS-LX1A 8.0.0.396 C432

[MAGISK] WiDEVINE L1 FiX for MIUI CUSTOM ROMS(11 is can) [MI 9T/K20]

Mod Edit: Link Removed
= Widevine L1 patch for Mi 9T / Mi 9T Pro and others devices ==
Huge thanks to:
@Benfatica (found how to easily get L1 back - v1 patch),
@sauliiin (created the TWRP zip file - v1 patch),
@robi10101298 (shared files to make v2 patch for Mi 9T) and
@r4yv3n (shared files to make v2 patch for Mi 9T Pro)
from XDA forum!
Your device must have stock Widevine L1, otherwise it will not work...
INFO: Widevine L1 is back in 20.1.21 update without patch!
-------------------------------------------
Use Official TWRP to avoid possible big issues!
1) Download one patch and put this file in root of your phone's storage.
2) Boot to TWRP Recovery.
3) Go to "Mount" menu and tick "Vendor", then "Back".
4) Go to "Install" menu and find & select your previously downloaded zip file.
5) Do NOT tick "Reboot after installation" option!
6) Flash it.
7) After flashing, click on "Wipe Dalvik&Cache" button and do the wipe.
8) Reboot and check if it works!
INFO:
- v2 = API version update (14 -> 15) for Mi 9T and Mi 9T Pro devices only!
- In case of issue, try first version too (don't forget to follow the steps above!).
- If nothing working (don't forget to mount "Vendor" partition in TWRP before flasing the remover) => TWRP_Widevine_L1_Remover.zip

@80606 Download link has to be public and mentioned on the thread, DO NOT use an external source and redirect users to other platforms like Telegram.
I have removed the link for the time being and locked the thread. Please PM me the details and link to verify before we can allow this share.
Please go through the forum rules before you copy and post any such stuff.
Thanks,
Funk Wizard
Forum Moderator