[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro - Xiaomi Redmi Pro ROMs, Kernels, Recoveries, & Othe

{
"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?

Related

[Rom][5.0.2]UNOFFICIAL FlymeOS 4.5.3.1

{
"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"
}
_________________​Hi XDA Developer
Here another port of flymeos from member:MROM
I saw it on Another website and want to share it with you
The new port has many improvements ....
IAM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS FROM YOUR PHONE
Thanks for topsecret78 for get rom source and change details
Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Click to expand...
Click to collapse
Changelog
CHECK DOWNLOAD PAGE FOR CHANGELOG
here some pics
Another screenshots here
Click to expand...
Click to collapse
So we Reach the download part
Note : looks like flyme 5 is officially maintained by (machao) member on (gfan) forum and latest builds will be found HERE
flyme 4.5.4.3 beta Google Drive
Downloaded it?! Let's install it and taste flyme
First ensure your bootloader is unlocked
1. Put Zip file on your sdcard
2. Restart your phone into your favourite recovery
3. Backup your data
4. Wipe (System,Data,cache,dalvik cache) not important to wipe internal memory
5. Install Zip from sdcard
6.restart system
First start will take 5 up to 10 min so don't think it's bootloop
TESTED ON C6903
After start let it 2 min and restart to install Su
You can download it from official website or you can use kingroot or kingo to root
Please sent permission to download file rom.
You can download now
Hit thanks if you like it
abdo.war said:
You can download now
Hit thanks if you like it
Click to expand...
Click to collapse
Where are kernel sources? You can't post a rom without posting kernel sources. Also, could you post a link to rom sources too. Thanks.
I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me
abdo.war said:
I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me
Click to expand...
Click to collapse
Doesn't matter who the builder is: posting roms without kernel sources is not allowed. For your sake you should post kernel sources or the mods will close this thread.
Report thread to mods to close it
I am sorry but I am still new here
abdo.war said:
Report thread to mods to close it
I am sorry but I am still new here
Click to expand...
Click to collapse
I am not going to report you, but rules are rules. They are part of GPL license...
Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Translate from google
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..
markakash said:
hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..
Click to expand...
Click to collapse
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
fastboot flash boot boot.IMG
Then reboot
fastboot reboot
Click to expand...
Click to collapse
Then try to install it
I installed rom from flashfire but it's dangerous
link to download in fisrt post
https://drive.google.com/file/d/0B3yReeEdHxbWSkFrYmhXbjJRaE0/view
or
http://pan.baidu.com/s/1pJXPr8R
I tested and work xperia Z1 C6903
---------- Post added at 16:30 ---------- Previous post was at 16:21 ----------
Info from source
"According to the competition regulations to place the file and naming 2: According to the rules without built-root themselves into the brush to 3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart"
and
"Please read the complete message painted machine
ROM tested before release because of personal consequences Brush problems caused not bear
Built-in networking to promote the software, please support the author can then run reservations can also uninstall (as some promotion app requires placing it under the system needs to RE Manager Entering system / app Delete)
Prohibit secondary modified to personally thank all publication reproduced, please indicate support oil"
Since this is based on CM12 meaning android 5.0.2
Does this have any slow charging issues?
Rom update to Flyme 4.5.4.4R
Change details ========================== ======================
Update fixes
[Contact]
All models support SIM card contacts
【camera】
Repair photographs sound problems can not be closed
Added (some models) Set the option to save photos to SD card
【music】
Repair song not normally know the songs matching problem
【other】
Living repair service hotel category loading problems
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Link to download
http://pan.baidu.com/s/1jGYfpdG
1: According to the competition regulations to place the file and naming
2: According to the rules without built-root themselves into the brush to
3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart
What about C6902??
abdo.war said:
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
Then try to install it
I installed rom from flashfire but it's dangerous
Click to expand...
Click to collapse
whare boot.IMG??
msamsameemo said:
whare boot.IMG??
Click to expand...
Click to collapse
In the Zip file
Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875
topsecret78 said:
Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875
Click to expand...
Click to collapse
What's the password?
Abu Badr said:
What's the password?
Click to expand...
Click to collapse
you don't need this link i already uploaded it to google drive go to
download at first post under screenshots
i have uploaded too iuni os if you want i can post it
Click to expand...
Click to collapse

[Tool] Rayglobe Italian Knife Ver 1.7 * TWRP - Root - Debrand ** UPDATE 2-14-16 **

{
"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"
}
Credits: @duraaraa (great guy from Xda), @inside!out, @VirusPlus, HRT Chinese team, Maximo76
1. Download this file
Ver. 1.6 ---------------------------> DOWNLOAD
2. Extract in a directory on your PC Rayglobe_Knife.exe
3. Launch this exe
XDA:DevDB Information
[Tool] Rayglobe Mate 8 Italian Knife, Tool/Utility for the Huawei Mate 8
Contributors
acer73, Inside!out, Virusplus, HRT Chinese Team, Maximo76
Source Code: http://forum.hdblog.it/index.php?/topic/49051-italian-knife-tool-by-hdblogit-huawei-mate-8/
Version Information
Status: Alpha
Created 2016-01-17
Last Updated 2016-02-06
Reserved
HELP
************************************************** ***********************************************
--------- User Manual HUAWEI MATE 8 Italian knife by Raimondo Martire (aka acer73) V1. 2 ----------
*
*
================================================== ========================================
**************The following points can be activated only with ADB and FASTBOOT active
**
*****0: FIRST START
*****1: BOOTLOADER
*****2: Recovery
*****3: Root
*****4: gapps
*****5: debrand
6: UNBRICK
7: EXTRA
8: Download EMUI
9: Thread Huawei Mate 8 on HDBlog.it
**
*****Q: Donate and Thanks? HELP (hdblog.it) X: CLOSE
================================================== ========================================
*
Before you start remember stop/freeze the antivirus because it may interfere with the download
*
================================================== ========================================
*
MENU 0: First Start
*
In this menu, 'there are two preliminary operations are the driver installation
for the proper functioning of the options adb and software download Hisuite.
Remember not to jump the menu '"First start"
because you will need to verify that you have properly enabled the option "USB debugging" in the menu 'developer
*
================================================== ========================================
*
MENU 1: Bootloader
*
In this menu 'you can use a fast tool for a fee ($4) to unlock the bootloader.
Huawei also provides for an option to unlock via email.
More information in this forum
*
NB. Unlocking the bootloader is necessary if you want to use all options of this tool
*
================================================== ========================================
*
MENU 2: Recovery
*
* 2-1 * The recovery TWRP need to install zip unsigned and root.
* 2-2 * The stock is recovery available with Huawei rom
*
================================================== ========================================
*
MENU 3: Root
*
The root, from the English "root", is a process derived from Linux and applied on
Android to get superuser rights and thus have unrestricted access to the system and to
right to modify it at will by real developers.
It is not nothing but to overcome a barrier and open the huge iron gates behind
which hides the world of modding and custom ROMs.
IMPORTANT: For the root must install the TWRP recovery and have the boot decrypt
*
================================================== ========================================
*
MENU 4: gapps
*
You can install Gapps for Huawei chinese rom. Please consider to decrypt boot before
*
================================================== ========================================
*
MENU 5: debrand
*
It really a pleasure to present this function for switch beetween chinese AL10 model to European L29 Model
*
================================================== ========================================
*
MENU 6: UNBRICK
*
It 'a menu' emergency and experimental enabled only when the smartphone is in brick state
*
================================================== ========================================
*
MENU 7: Extra
*
In this menu, 'there are more frequent reboots: recovery, bootloader and the possibility for the user
to flash their own recovery or a boot image. The files must be placed in the directory
USER
*
================================================== ========================================
*
MENU 8: Download EMUI
*
This menu 'will be active for download roms stock EMUI of the Chinese model.
*
================================================== ========================================
*
MENU 9: Thread Huawei Mate 8 on HDBlog.it
*
Italian forum when I've published first my work
*
================================================== ========================================
*
MENU D: Donate
*
This tool and 'released for purely private. Any commercial use without permission
the author will be prosecuted according to law.
If you want to keep this tool active currency the possibility to donate to the purchase of space
Web and to give me comfort with a glass of good Italian wine
*
================================================== ========================================
*
Menu?: Help
*
To choose the menu 'for help and' exclusively in Italian
*
================================================== ========================================
*
MENU X: Close
*
Closes this tool
Changelog
1.5
Smaller exe
Rayglobe Twrp recovery Multilanguage
1.3
New Twrp multilanguage
Remake Extra section with 2 new stuff
thank you for your help
I have a problem against the software does not recognize my mate 8 I have this red message <waiting for device>, and when I run a command prompt my device is recognized without problems
You are the hero we need, we just didn't know it! Massive thanks for your work mate.
lorenzw said:
thank you for your help
I have a problem against the software does not recognize my mate 8 I have this red message <waiting for device>, and when I run a command prompt my device is recognized without problems
Click to expand...
Click to collapse
You have driver problem. Have you used driver that I punt in first start command?
Extensive help please
Just looking for some more detailed help, ill post the issues I have with understanding.
Sorry if some things I ask are basic or stupid, I have never had an android phone and haven't had the opportunity to check your tool out with a phone yet.
acer73 said:
*
MENU 0: First Start
*
In this menu, 'there are two preliminary operations are the driver installation
for the proper functioning of the options adb and software download Hisuite.
Remember not to jump the menu '"First start"
because you will need to verify that you have properly enabled the option "USB debugging" in the menu 'developer
*
Click to expand...
Click to collapse
So I just need to run this command (after enabling USB debugging) and that will download everything I need to run the commands?
acer73 said:
*
MENU 1: Bootloader
*
In this menu 'you can use a fast tool for a fee ($4) to unlock the bootloader.
Huawei also provides for an option to unlock via email.
More information in this forum
*
NB. Unlocking the bootloader is necessary if you want to use all options of this tool
*
Click to expand...
Click to collapse
So whats this first menu do?
Link me to these two places?
acer73 said:
*
MENU 2: Recovery
*
* 2-1 * The recovery TWRP need to install zip unsigned and root.
* 2-2 * The stock is recovery available with Huawei rom
*
Click to expand...
Click to collapse
What do these mean?
TWRP will be installed on it if I select one?
Then what does the stock one do? Remove TWRP?
acer73 said:
*
MENU 3: Root
*
The root, from the English "root", is a process derived from Linux and applied on
Android to get superuser rights and thus have unrestricted access to the system and to
right to modify it at will by real developers.
It is not nothing but to overcome a barrier and open the huge iron gates behind
which hides the world of modding and custom ROMs.
IMPORTANT: For the root must install the TWRP recovery and have the boot decrypt
*
Click to expand...
Click to collapse
How do I get boot decrypt?
acer73 said:
*
MENU 4: gapps
*
You can install Gapps for Huawei chinese rom. Please consider to decrypt boot before
*
Click to expand...
Click to collapse
Once again, what is decrypt boot?
What happens if I dont have decrypt boot and I do this?
Also what GAPPS are included?
acer73 said:
*
MENU 5: debrand
*
It really a pleasure to present this function for switch beetween chinese AL10 model to European L29 Model
*
Click to expand...
Click to collapse
Basically this will flash the european rom on the phone?
Does it work the other way as well, european to chinese?
acer73 said:
*
MENU 6: UNBRICK
*
It 'a menu' emergency and experimental enabled only when the smartphone is in brick state
*
Click to expand...
Click to collapse
So if I brick my phone this will be able to fix it most of the time?
What kind of things does it do?
acer73 said:
*
MENU 7: Extra
*
In this menu, 'there are more frequent reboots: recovery, bootloader and the possibility for the user
to flash their own recovery or a boot image. The files must be placed in the directory
USER
*
Click to expand...
Click to collapse
So this menu gives the user the option to boot into different modes?
acer73 said:
*
MENU 8: Download EMUI
*
This menu 'will be active for download roms stock EMUI of the Chinese model.
*
Click to expand...
Click to collapse
What does this do? Flash the chinese rom?
Does that mean the chinese to international rom wouldnt work backwards, you need to use this one to do it?
So I just need to run this command (after enabling USB debugging) and that will download everything I need to run the commands?
So whats this first menu do?
Link me to these two places?
Install correct adb driver. remember to activate usb debug in developer menu
What do these mean?
TWRP will be installed on it if I select one?
Then what does the stock one do? Remove TWRP?
Twrp in a custom recovery to flash unsigned zip
How do I get boot decrypt?
In menu 3
Once again, what is decrypt boot?
What happens if I dont have decrypt boot and I do this?
Also what GAPPS are included?
Micro GApps package for chinese rom
Basically this will flash the european rom on the phone?
Does it work the other way as well, european to chinese?
Yes european rom work on chinese model
So if I brick my phone this will be able to fix it most of the time?
What kind of things does it do?
So this menu gives the user the option to boot into different modes?
You can boot in recovery or fastboot mode. Some command can be made in recovery mode other one in bootloader mode
What does this do? Flash the chinese rom?
Does that mean the chinese to international rom wouldnt work backwards, you need to use this one to do it?
Yes you can flash from chinese to european and return to chinese
Hello,
I made this tool for Honor6 and inside!out port it for Honor7 later. We both now merged our tools into one HONOR MultiTool and we still keep it "open" in .bat so anyone can use/port it for other models. I don't get why you "close" it with .exe format.
I see that you add me and inside!out as contributors but i don't want make changes into your OP, so please give me and inside!out the right credits of your port on our work into OP and your Tool.
This is the original HONOR6 MultiTool Thread and this is the port for HONOR7 MultiTool Thread.
Thank you!
Hi I know several people have already asked this, but when I run first run I just get waiting for device. In device manager there's no missing drivers. I can't see where you have the adb driver located. Is it possible to post a link to the correct driver? I was able to install hiSuit, but not able to get the device detected. Does anyone have any other ideas?
hisuite actually has the USB drivers included...
davoidd said:
Hi I know several people have already asked this, but when I run first run I just get waiting for device. In device manager there's no missing drivers. I can't see where you have the adb driver located. Is it possible to post a link to the correct driver? I was able to install hiSuit, but not able to get the device detected. Does anyone have any other ideas?
Click to expand...
Click to collapse
I am in the same situation as Davoidd and I still have not found the solution.
I'm on Windows 10 and Hisuite and adb drivers are installed
all orders that I make are not allowed via fastboot with Rayglobe Italian Knife
but I can flash the TWRP via fastboot without using Rayglobe Italian Knife
Can I use your tools for Factory Reset Protection (FRP) rest?
VirusPlus said:
Hello,
I made this tool for Honor6 and inside!out port it for Honor7 later. We both now merged our tools into one HONOR MultiTool and we still keep it "open" in .bat so anyone can use/port it for other models. I don't get why you "close" it with .exe format.
I see that you add me and inside!out as contributors but i don't want make changes into your OP, so please give me and inside!out the right credits of your port on our work into OP and your Tool.
This is the original HONOR6 MultiTool Thread and this is the port for HONOR7 MultiTool Thread.
Thank you!
Click to expand...
Click to collapse
Sorry mate. I created this thread as you can see with right credits in the first time and put your name also in contributors. I put your name in contributors in this way xda system send you an email and you can verify work just because you have choose to not receive Pm so no possibility to contact you. I don't think only to give credit in OP and tool . I'll upload new version with credit in OP according your right desire and I've modified first image for better visibility. :good:
copysat said:
Can I use your tools for Factory Reset Protection (FRP) rest?
Click to expand...
Click to collapse
No, I don't test for it. Use this option only in an emergence fase
jbmc83 said:
hisuite actually has the USB drivers included...
Click to expand...
Click to collapse
Yes right
lorenzw said:
I am in the same situation as Davoidd and I still have not found the solution.
I'm on Windows 10 and Hisuite and adb drivers are installed
all orders that I make are not allowed via fastboot with Rayglobe Italian Knife
but I can flash the TWRP via fastboot without using Rayglobe Italian Knife
Click to expand...
Click to collapse
Yes you can flash in fastboot with this command
fastboot flash recovery twrp.img
I'll see in tool why some user don't flash. Only a test if you wright
adb devices
you see a number?
acer73 said:
Yes you can flash in fastboot with this command
fastboot flash recovery twrp.img
I'll see in tool why some user don't flash. Only a test if you wright
adb devices
you see a number?
Click to expand...
Click to collapse
yes i see a number , with adb in fastboot i can flash twtrp.img with the firmware NXT-AL10_C00B129SP02 I also have with your made tool a backup of oeminfo but with the firmware NXT-AL10C00B137 I can't flash twrp.img ! (failed command not allowed)
At present I am under the firmware NXT-AL10_C00B129SP02 with TWRP and SuperSu
lorenzw said:
yes i see a number , with adb in fastboot i can flash twtrp.img with the firmware NXT-AL10_C00B129SP02 I also have with your made tool a backup of oeminfo but with the firmware NXT-AL10C00B137 I can't flash twrp.img ! (failed command not allowed)
At present I am under the firmware NXT-AL10_C00B129SP02 with TWRP and SuperSu
Click to expand...
Click to collapse
I'll change tool to ver 1.0.0.1 try with this . I'm sure that now you can flash without problem
https://www.androidfilehost.com/?fid=24369303960690339
happy to report that ur tool saved me a lot of work @acer73 im now on L29 firmware with decrypted boot, twrp and supersu installed, everything running smoothly. so far no issues with notifications, but still watching out for this...
Sent from my Huawei Mate 8 using Tapatalk

[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

[ROM+GUIDE][SM-G955x][AQH3] CeX - Flashable Repackaged Stock [29/08/17]

{
"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"
}
Definition
Let me first define what I mean by Creator's Experience. This ROM is just as good as your stock ROM on KNOX 0x0. I am in no way taking credit for any of the development in this ROM, I'm just repackaging the stock Samsung ROM in Samsung's experience how they created it. But if you flashed stock ROM you may get a ton of KNOX warnings so selling the device or giving your device to someone else would make it more complicated and frustrating due to nagging popups that you have to disable by first setting up the device. I wanted to create something that you can restore your device to when you get bored of a custom ROM, or you just want to use the latest stock firmware again.
This ROM will never contain any tweaks or system addons, it is barebones stock with no KNOX and stubs so people can use it as a rescue/reference firmware.
Purpose
Being the owner of the Korean Samsung Galaxy S8+ 128GB/6GB (SM-G955N), there are only so many stock firmwares available from Updato or Sammobile. All listed firmwares contain all the CSCs located in the /system partition, and the CSC file toggles between them. This means that regardless of what CSC you flash on the device, you will activate all the applications that were disabled by the CSC (KT mobile apps should be disabled on the SKT CSC, and vice versa). So flashing a Canadian CSC will still have every single South Korean carrier bloat on your device, which sucks.
This is a strange situation with 955N users, where ALL THE BLOAT is stored in /system/priv-app, while the csc is just one small file that controls which applications are active/inactive on the device.
Process
So, what does this mean? I wanted the stock international 955F ROM on my device, really badly. But Odin refused to flash it due to a secure write/invalid magic string error. I have tried everything from modifying the PIT tables in the ROMs to flashing custom ROMs. As much as custom ROMs are great, I wanted something I could fall back to when sh*t hits the fan, as well as something that fit the stock lifestyle...since I would really have loved to keep KNOX 0x0 if the Korean firmware was not as bloated as I thought it would be.
So for those who were searching for the stock ROM that was created with stock in mind, I have repackaged the 955F stock using the kitchen by @SuperR., with removed KNOX + KNOX apps (Secure Folder, KNOX Settings 1 & 2, Samsung Pay, Samsung Pass, etc.), removed stub apps (Microsoft apps folder) and removed CSC (I will elaborate more below).
As it takes me from 3-6 minutes to download stock firmware, I will be keeping this up to date for people who will need a rescue zip.
Reproduction
The reason why I'm keeping this as clean as possible is because it functions the same way as the Odin package. The AP will be the ROM zip, while you have to flash your own custom kernel, and flash the CSC package by @Tkkg1994. Finally, to top everything off, Magisk will be flashed.
A flowchart of this process (clean flash) is listed below:
Flash CeX stock (this ROM)
Flash the CSC using the CSC utility tool by @Tkkg1994: https://forum.xda-developers.com/galaxy-s8+/development/utility-flashable-csc-selection-v1-0-0-t3605264
Flash the kernel, I highly recommend @jesec's Jesse Kernel: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-exynos-t3603521
Flash Magisk v12+: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
A flowchart of this process (dirty flash) is listed below [dirty flash is supported on CeX, as long as you follow these steps]:
Use TWRP and wipe /system
Flash CeX stock (this ROM)
Flash the CSC using the CSC utility tool by @Tkkg1994: https://forum.xda-developers.com/galaxy-s8+/development/utility-flashable-csc-selection-v1-0-0-t3605264
Flash the kernel, I highly recommend @jesec's Jesse Kernel: https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-jesse-s-kernel-galaxy-s8-exynos-t3603521
Flash Magisk v12+: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Anomalies
At the current stage, this is just the stock Samsung firmware. So any bugs found in the official bugs list of the current firmware revision would be present in this ROM. See the second bracketed codename in the title of this thread.
Do you use Netflix or Amazon Prime Video?
With their Widevine DRM Module, it bypasses anything Magisk Hide has to offer.
Using TWRP, remove /system/lib/liboemcrypto.so, then reboot to system.
If you ever want to restore stock, this is the AQEB binary: https://www.androidfilehost.com/?fid=961840155545569722
Screenshots
There really doesn't need to be any screenshots, unless you have never turned on your phone on stock ROM before...but here, I'll show you Settings.
SafetyNet?
This is a simple phenomenon solved by having both a custom kernel with KNOX 0x0 simulation, like Jesse's kernel, and Magisk v12 installed with Magisk Hide enabled. It is confirmed that CeX respects SafetyNet.
Programmatically Displayed Debloated Applications/Services/Libraries
Code:
system/app/Facebook_stub*
system/app/MSSkype_stub*
system/app/SecureFolderSetupPage*
system/priv-app/OneDrive_Samsung_v2*
system/priv-app/SecureFolder*
system/priv-app/SamsungPass_1.1*
system/priv-app/Excel_SamsungStub*
system/priv-app/PowerPoint_SamsungStub*
system/priv-app/Word_SamsungStub*
system/container*
system/app/BBCAgent*
system/app/Bridge*
system/app/ContainerAgent*
system/app/ContainerEventsRelayManager*
system/app/kioskdefault*
system/app/KLMSAgent*
system/app/Knox*
system/app/KNOX*
system/app/MyKNOX*
system/app/RCPComponents*
system/app/SecurityLogAgent*
system/app/SwitchKnoxI*
system/app/UniversalMDMClient*
system/container*
system/etc/secure_storage/com.sec.knox*
system/preloadedkiosk*
system/preloadedmdm*
system/preloadedsso*
system/priv-app/KLMSAgent*
Download Links
AndroidFileHost Folder (Autopushed builds): https://www.androidfilehost.com/?w=files&flid=185563
AQH3 builds (August):
FullRebaseOptions from last build:
https://www.androidfilehost.com/?fid=745425885120758691
Normal build:
https://www.androidfilehost.com/?fid=817550096634795846
AQF7 build (June): https://www.androidfilehost.com/?fid=673368273298964156
AQEB build (May): https://www.androidfilehost.com/?fid=817550096634773510
Credits & Thanks
@SuperR. for his kitchen
@jesec for him helping out when I was frustrated something isn't working, and pretty much his experience with his 955N
@fahadali2315 for refreshing my memory of messing with a Samsung device
Anyone I missed, just hit me up in private!
XDA:DevDB Information
CeX, ROM for the Samsung Galaxy S8+
Contributors
nicholaschum, fahadali2315
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Current Stable Version: AQH3
Stable Release Date: 2017-05-31
Created 2017-06-01
Last Updated 2017-08-29
Building with SuperR Kitchen for your own stock region ROM
If you're interested in creating your own flashable ZIP based on a ROM, I will be listing the full instructions on how to get your own stock ROM up and running.
I will be building the latest XXU builds as soon as they drop.
Please do not PM me, instead, post in the thread for people to learn.
Prerequisites:
- Your device MUST be of the Exynos variant, with an available TWRP on the device. If you have a Qualcomm device, close this window now!
- You must have a Linux environment. I know @SuperR.'s kitchen works on Windows using Cygwin, but as an AOSP developer, I work with Linux to build stuff!
- Sudo account
- Collect and utilize as much wits as you can!
- I will be doing all of this from the command line using SSH, no GUI for this!
1) Download the latest SuperR kitchen here: https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
by doing this (press enter after each line in this code block):
Code:
curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash
sudo apt-get install git-lfs
git lfs install
git config --global credential.helper cache
cd ~/
git clone https://bitbucket.org/superr/superrs-kitchen.git
cd superrs-kitchen
./superr
The first time running the kitchen, you may need to install dependencies. It should automatically install all dependencies for you, but if it keeps asking you to install the same dependencies, you should install them using
Code:
sudo apt-get packageName
.
After all dependencies are installed, press 1 to create a new project, and name it whatever you want. In this example I will name it STOCK.
Press Q once the project is created (quits SuperR kitchen)
2) Download your Samsung stock firmware. There are two main sites nowadays to get Samsung stock firmwares from, including Updato and Sammobile.
Updato: http://updato.com/firmware-archive-select-model?q=SM-G955F&rpp=15&order=date&dir=desc&exact=1
Sammobile: https://www.sammobile.com/firmwares/galaxy-s8/SM-G955F/
You will need to get the firmware on your Linux box, or from Updato, right click Download (the orange button) and click Copy Link.
If you are planning to download from the SSH box, do:
Code:
cd ~/superr-kitchen/superr_STOCK && wget link_of_updato
3) Your firmware file is now ready to be loaded up into the kitchen. So do:
Code:
./superr
Then click 4 to extract for a new ROM, then click "y"
4) When it asks you whether you want to include cache.img, it doesn't really matter if you do or don't. Click "y" and include it in the ROM.
5) It will then ask you to type a name for your output ZIP
6) If it asks you where to locate the partition info from, pick the entry that is recommended, which takes the partition from system.img and recovery.img (Detect by-name from boot/recovery images (recommended))
So simply click 1.
7) Finally, we must set the perm type/archive type of your images. Click 1 for set_metadata (KitKat+)
NOTE: I have tried using Sparse dat for Korean 955N image - which working at a cost of all Google apps crashing/not responding, but doing so on the 955F ZIP will completely break and cause it to get stuck in TWRP trying to flash. set_metadata is the most stable.
8) You can now fiddle with the ROM! It is highly recommended to replace the stock kernel with @jesec's kernel, but make sure you extract his other folders from his ZIP into your working directory (~/superr-kitchen/superr_STOCK/system/*) or you won't boot! You can either opt for this, or just flash the kernel ZIP to retain support from Jesse (this is what I picked for CeX).
Key configurations (the options I picked for CeX):
->7) Boot/Recovery Tools
- Unpack boot.img
- Type 5 and disable forceencrypt
- Type 1 and pack boot.img
->8) ROM Tools Menu
- Asserts Menu (if you're trying to do 955N ROM)
- Add/Remove Device (dream2lte) <- change from dream2lteks or any other model, since TWRP only recognizes dream2lte.
->6) Debloat Menu
- Custom Debloat
- ~/superr-kitchen/tools/root/bloat_custom must be edited to contain these entries (nano ~/superr-kitchen/tools/root/bloat_custom to edit the file):
Code:
system/app/Facebook_stub*
system/app/MSSkype_stub*
system/app/SecureFolderSetupPage*
system/priv-app/OneDrive_Samsung_v2*
system/priv-app/SecureFolder*
system/priv-app/SamsungPass_1.1*
system/priv-app/Excel_SamsungStub*
system/priv-app/PowerPoint_SamsungStub*
system/priv-app/Word_SamsungStub*
system/container*
- Remove Samsung Knox
9) You can make external edits by placing files in ~/superr-kitchen/superr_STOCK/system, or do whatever you want with the APKs
10) Let's start building!
If you left the window, all you have to do is do:
Code:
./superr
8
7
1
This will get you to the ROM zip building screen.
If the kitchen asks if you would like to convert the updater-script to an updater-binary, do it. Now give it some time to build. Usually my computer takes 2-3 minutes.
11) Finally, you can decide whether you want to sign the ZIP or not. Personally, I do not sign my ZIPs.
If you decide to skip signing, you're done! Just type "n" on your keyboard and click "q" to quit the kitchen. Your new ZIP is located in ~/superr-kitchen/superr_STOCK/STOCK_BASED_ROM.zip
You can either move this to your h5ai server, like I do at http://download.projektsubstratum.com/, or you could use transfer.sh here:
Code:
curl --upload-file ./STOCK_BASED_ROM.zip https://transfer.sh/STOCK_BASED_ROM.zip
You could also move it to AndroidFileHost using FTP, if you have a developer account.
This may take a while for the upload to complete, but once it is done, you are ready to flash the four ZIPs:
The ROM
A custom kernel
The CSC utility flasher
Magisk (for SafetyNet)
12) Congratulations, you're done!
Pulling your own CSC files
So you tried to extract the CSC file (cache.img) from the CP tar for Odin but no luck flashing...but you really wanted an up to date version..
Prerequisites:
- Your device MUST be of the Exynos variant, with an available TWRP on the device. If you have a Qualcomm device, close this window now!
- You must have a Linux environment for simg2img
- Sudo account
- Collect and utilize as much wits as you can!
- I will be doing all of this from the command line using SSH, no GUI for this!
1) Download simg2img to your Linux box and build the project
Code:
cd ~/
git clone https://github.com/anestisb/android-simg2img
cd android-simg2img
make
2) After simg2img has been compiled, we will have to use it.
Place your cache.img.ext4, yanked out of the CP.tar.md5 file (renamed to CP.tar) in the same directory of the git cloned repo
If you need a command to extract the .tar file, run:
Code:
tar xf CP.tar
3) Convert the image
Code:
./simg2img cache.img.ext4 cache.raw.img
4) Mount the image
Code:
sudo mkdir /media/csc
sudo mount -t ext4 -o loop cache.raw.img /media/csc
cd /media/csc
5) Copy the prepared flashable CSC zip out of the image
Code:
cp sec_csc.zip ~/
6) Flash the ZIP
7) Boot into the system. If you flashed a multi-CSC, you may need to configure it to be specific to your country.
This will require root, so get yourself into adb shell, then (credits to @jesec):
Code:
adb shell
su
am start com.sec.android.Preconfig/.Preconfig
A window will pop up giving you all the options selectable in your MultiCSC. Clicking and installing any of them will wipe your device, so watch out!
one last reserve post
locking my thread till the upload is finished....
@OP
Great idea bro, thanks a lot.
Nice work! @nicholaschum
Very Good! Thanks!
Sorry, my english is to bad...
Thats mean, if i Flash this Rom and later, when i go back to stock, my knox will be 0x0?
No, KNOX still tripped but with fake 0x0
Good work !! @nicholaschum
Th3PorTuGa said:
No, KNOX still tripped but with fake 0x0
Click to expand...
Click to collapse
Thanks
@nicholaschum
Can I ask possibly a dumb question
Is flashing CSC required?
I mean what happens if you don't flash CSC.
I am currently in AU on Vodafone CSC. I would change it to XSA but if I decided not to or forgot to do it. Would the CSC activate based on what is currently set as my CSC there or is this required so the rom can then load the apps based on location?
Perfect Build Perfect ROM. Installed as per instructions and works like a charm. Thanks for the work.
davjak said:
@nicholaschum
Can I ask possibly a dumb question
Is flashing CSC required?
I mean what happens if you don't flash CSC.
I am currently in AU on Vodafone CSC. I would change it to XSA but if I decided not to or forgot to do it. Would the CSC activate based on what is currently set as my CSC there or is this required so the rom can then load the apps based on location?
Click to expand...
Click to collapse
The CSC is required or else Samsung stock ROMs will not know how to configure your phone. This also I closed LTE-A capabilities, wifi calling and VoLTE functionality. Since this ROM does not contain any CSC you could flash the DBT CSC from the flashing utility which is the default CSC on most ROMs that is Germany debranded.
@nicholaschum - thanks for sharing this ROM. i'm using as a daily driver for my "work device" in combination with the ATT CSC flashed via TK's CSC package. if/when Substratum is available for TW based S8 ROMs, can i assume your ROM will support it? thanks for taking time to read/respond to my question.
Just installed. Silky smooth! Great work op
cortez.i said:
@nicholaschum - thanks for sharing this ROM. i'm using as a daily driver for my "work device" in combination with the ATT CSC flashed via TK's CSC package. if/when Substratum is available for TW based S8 ROMs, can i assume your ROM will support it? thanks for taking time to read/respond to my question.
Click to expand...
Click to collapse
Yes. That is the whole point behind it , keeping it stockish with subs support when it arrives.
I want install it, but i dont what do..
I want sale my phone later and get Note 7.
Is complicate if we cant use Samsung pay when we back to stock.
@nicholaschum Thanks heaps for this, took the leap and followed the instructions. Very simple task! now running XSA CSC with AQEB

[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For HTC Desire Eye

{
"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 HTC Desire Eye. 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 HTC Desire Eye 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-eyeul-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:
In screenshots tab​
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
HTC Desire Eye Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/647
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
@androidlover5842 for helping me always
@amr soliman for testing
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For HTC Desire Eye, Tool/Utility for the HTC Desire Eye
Contributors
yshalsager, androidlover5842, Ahmed Hady, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-07-10
Last Updated 2017-10-03
Notes
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") == "cheeseburger" || getprop("ro.build.product") == "cheeseburger" || abort("E3004: This package is for device: cheeseburger; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
Changelogs
- 10/07/2017
Initial Release
What an awesome thing! Thank you!)
Need to try this on my own
Do I need to install both roms on internal storage?
Considering it's only 16GB and what if I install heavy games and tons of apps on a light rom like lineage Os or Cypher as Primary and keep minimal apps on RR Secondary. I don't think id be left with much internal storage cuz of apps.
TahirZX said:
Do I need to install both roms on internal storage?
Considering it's only 16GB and what if I install heavy games and tons of apps on a light rom like lineage Os or Cypher as Primary and keep minimal apps on RR Secondary. I don't think id be left with much internal storage cuz of apps.
Click to expand...
Click to collapse
Of course no. Please read instructions again
failed to update ramdisk ..
any suggestions for supported kernels?
Getting Error, Device is m8
Primary Is Aoscp 4 and secondary rr eyeul
deveshgupta69 said:
Getting Error, Device is m8
Primary Is Aoscp 4 and secondary rr eyeul
Click to expand...
Click to collapse
Change device in buildprop to eyeul
yshalsager said:
Change device in buildprop to eyeul
Click to expand...
Click to collapse
I don't have enough space for flashing system temp, It tried to flash on external but didn't work either.
deveshgupta69 said:
I don't have enough space for flashing system temp, It tried to flash on external but didn't work either.
Click to expand...
Click to collapse
You should make space on internal either it will not work

Categories

Resources