{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have added support for the Lenovo Vibe P1
Link
I am not the creator, just the supporter
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
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
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
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.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App 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.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
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.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
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".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
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:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Latest DualBootPatcher APK
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@devansh21 for being a fantastic tester
XDA:DevDB Information
DualBootPatcher for P1a42, Tool/Utility for the Lenovo Vibe P1
Contributors
MSF Jarvis, FireLord, devansh21
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/18180f432ba1ebb69c3029c80f2678c9c4ecdb9e
Version Information
Status: Snapshot
Created 2016-10-08
Last Updated 2016-10-08
Bug reports without logs from flashing the GetLogs ZIP will be ignored and the post deleted.
Please make sure you read the entire first post properly, everything important is given here!
Reserved
hey, i'm using a stock mm 288 for primary rom.
but, when i flash anyting to data slot for secondary rom, i cant get root to work.
i've already try flash patched BETA-SuperSU-v2.72-20160510112018 but didn't work.
can you help me?
sorry for my bad english
@MSF Jarvis
hi thnx for great job.it's run perfect.
Error installation
We got found error when try installation dual boot
arfans said:
We got found error when try installation dual boot
Click to expand...
Click to collapse
Which ROM were you trying to install?
danthecoolboy said:
Which ROM were you trying to install?
Click to expand...
Click to collapse
Originally stock rom P1a42_S288_160721_ROW_RAW and i'm trying install custom rom DotOS
Thanks a ton for the update @MSF Jarvis
MSF Jarvis said:
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have added support for the Lenovo Vibe P1
Link
I am not the creator, just the supporter
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
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
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
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.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App 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.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
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.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
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".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
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:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Latest DualBootPatcher APK
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@devansh21 for being a fantastic tester
XDA:DevDB Information
DualBootPatcher for P1a42, Tool/Utility for the Lenovo Vibe P1
Contributors
MSF Jarvis, FireLord, devansh21
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/18180f432ba1ebb69c3029c80f2678c9c4ecdb9e
Version Information
Status: Snapshot
Created 2016-10-08
Last Updated 2016-10-08
Click to expand...
Click to collapse
Followed the guide in my Lenovo Vibe p1a42 rooted running custom AOSP Extended 5.6 . I tried installing Custom Carbon 5.1 Rom. The installation/flashing process is completed successfully, But after choosing the second Rom and rebooting the device, the boot open TWRP Recovery. And further boots also open recovery. I had to reinstall the AOSP Extended Rom using TWRP to boot into Android. Can you please suggest what would have gone wrong on my end which resulted the reboot to boot into recovery rather then the second ROM.
This is derived from the latest N910F UK BTU stock Marshmallow v6.0.1 firmware.
Some info:
PDA/AP (ROM firmware) version: N910FXXU1DRI2
CSC code: N910FBTU1DRJ1 (BTU)
Modem/CP/baseband version: N910FXXS1DQA1
There is no multi-CSC support, it is too much work to add. If you need a different CSC besides BTU, then you should consider @_alexndr's DevBase, @Andycar's ROM, etc. They are based on older firmware, but should work fine. Having this ROM's BTU CSC may mean that carrier-specific features like VOLTE/wifi calling/etc may or may not work. I think the BTU CSC should work fine for most.
Why am I doing this? Well, for one, noone has posted (to my knowledge) a deodexed version of this firmware. And 2nd, as a baseline modding resource for other users, I only ask that I'm given credit for providing the files.
Old zips:
I've taken the N910FXXU1DRI2 stock firmware from SamMobile, deodexed it with SuperR's Kitchen, and created a TWRP-flashable firmware/ROM zip. It is only deodexed, no other changes have been made, nothing has been removed. All stock bloat/Knox is present. It isnt rooted, but you may root it with Magisk/SuperSU/Phh's Superuser. The kernel is pure stock, but you may flash a custom kernel afterwards if you wish. This ROM should pass SafetyNet even without Magisk/SuperSU, as long as you dont flash something like Xposed. Private Mode will not work with this zip out of the box, you will need to flash the modded Private Mode zip to get it to work. You should only use this zip if you just want a deodexed ROM with no additional changes. Flash from TWRP. This zip only includes the stock boot.img and a deodexed system.img.
There is now a 2nd version of this, it is based on the original N910FDeodex.zip, but converted from raw img format to set_metadata format. This version will only flash the used portion of the system partition into /system, resulting in less write hits. If you want a deodexed only version of this ROM with no further changes, then use the set_metadata version. These 2 zips are otherwise identical.
https://androidfilehost.com/?fid=8889791610682928982
https://androidfilehost.com/?fid=8889791610682917301
New revised zip (deodexed, debloated, Knox removed, GApps removed, some minor changes):
This is almost the same as the above zip. Everyone should use this new zip, unless they only want a zip that is deodexed only with no further changes. Private Mode will work out of the box. You will also be able to pass SafetyNet with or without Magisk/SuperSU.
https://androidfilehost.com/?fid=8889791610682924674
See the following post for what's removed:
https://forum.xda-developers.com/showpost.php?p=83379549&postcount=38
And this one too. It includes an optional debloat script that removes even more:
https://forum.xda-developers.com/showpost.php?p=83385447&postcount=44
Link to script:
https://androidfilehost.com/?fid=8889791610682925297
Install order for revised zip:
1. Wipe system/data/cache and flash ROM zip
2. Flash my revised debloat script if you want it
3. Flash latest OpenGApps ARM 6.0 nano zip (dont use anything higher, system apps like Messages/Tags/dialer will be removed if you do!)
4. Flash Google Contacts Sync Adapter zip from Extras section (to avoid "Android is optimizing" on every boot)
5. Check /system/app/WebViewGoogle, /system/priv-app/GooglePackageInstaller, and /system/priv-app/Tags, make sure they're not deleted. If they are, flash the appropriate zips from Extras section
6. Flash any other extras you want
7. Flash custom kernel (optional)
8. Flash root (optional)
9. Reboot into ROM
For MicroG users:
1. Wipe partitions, flash ROM zip.
2. Flash my revised debloat script if you want it.
3. Flash MicroG installer zip. Signature spoofing patch is already built into ROM.
4. Flash play store, backup transport, calendar sync adapter, Google dialer, maps/media effects/widevine libraries, deodexed google contacts sync adapter, google keyboard and swype libraries. These are optional.
5.Flash any other extras you want
6. Flash custom kernel (optional)
7. Flash root (optional)
8. Reboot into ROM
Note: In my tests, ROM didnt pass SafetyNet with MicroG installed. but it did pass when I flashed OpenGApps. This means the fail is due to something in MicroG. Ask in the MicroG XDA thread for help.
Another note: I only used the official APKs from MicroG website, permissions XML file from MicroG Installer Revived, and Play Store APK from APKMirror. You can update MicroG if/when they release new APKs.
Make sure to follow these steps in the order I've listed them!
You only need to use my stock boot image and kernel library modules zip if:
1. Before you flash a custom kernel
2. Before flashing root (skip my zip if you are already using custom kernel)
You can also get rid of a custom kernel/root by flashing this zip. But it is advised that you use Magisk uninstaller zip first. Or to delete SuperSU, you can use the unSU zip by @osm0sis. Then flash my zip.
If you get an error in TWRP when flashing either of these zips, this probably means your MicroSD card is using the GPT partition table, instead of MBR. My advice is to use SD Card Formatter tool to format your SD, then copy the ROM zip onto it and try to flash the zip again. If this doesnt work, post the exact error here.
If you used the "nand erase all" option in Odin, it is advised to format data/cache in TWRP *BEFORE* flashing the ROM zip. Look at the Mount button in TWRP and see if they are checked. If they are, then all is good. If not, use the wipe/format data functions until they are checked. I advise using nand erase all because it cleans data/cache of incompatible data. Especially recommended if you are coming from different firmware/custom ROM.
Please only do clean flashes! Dirty flashes not supported! Do not report bugs if you have dirty flashed! Do not report bugs if you are using other mods like Xposed (or root), etc! Clean flash with no changes, then post here if the bug is still present.
Additional firmware-related files:
My N910FXXU1DRI2 mini firmware package. This includes all files from the stock firmware package with the exception of the boot, system, and cache partitions. This is intended to be flashed before flashing my ROM zip. Boot/system arent needed because they are included in the ROM zip. Cache also isnt needed because its' contents (the UK BTU CSC code) is already processed into the system.img. This package also includes the latest official TWRP recovery, instead of the stock recovery. I would advise that you flash this file before flashing the ROM zip, but it may only be necessary if the ROM fails to boot (which means your installed firmware is an incorrect/incompatible version).
https://androidfilehost.com/?fid=8889791610682917321
You need Odin (version 3.12.7 recommended), Samsung USB drivers, and a Windows PC. In Odin, select the "nand erase all" and select the tar file in the AP slot. Also uncheck the autoreboot box. Leave everything else as-is. Once it is flashed, wait a minute or 2 before unplugging phone from PC.
Once you've done this, pull battery from phone, put it back in, then use VolUp+Home+Power to boot into TWRP. From there you can flash the ROM zip.
Pure stock firmware N910FXXU1DRI2. This is identical to what you would get from SamMobile, I have not modded the firmware in any way. I have only recompressed the tar file so that the total overall download size is smaller. Unpack the 7z file with 7-Zip/WinRAR/some other software, then flash the tar file from Odin. Flashing instructions are the same as above. You only need this if you want a truly clean start with nothing whatsoever changed. This file can be used alone without the others, or it can be flashed before the stock ROM zip. This file does not include TWRP. If you intend on flashing the stock ROM zip, I would suggest using my mini firmware package instead.
Note: I've deleted this file, you can find it in my N910FXXU1DRI2 mega firmware collection thread.
N910FXXU1DRI2 pit file. This file is to be flashed with Odin, if you need to repartition the device. Only use it with a full, official firmware package, like the one from above. I extracted it from my device with TWRP, it is not changed in any way. Most people generally wont need this. Only use this on an N910F, it may brick other devices!!! You've been warned!
https://androidfilehost.com/?fid=8889791610682917326
Link to extra files folder:
https://androidfilehost.com/?w=files&flid=316633
You can use these files to restore removed functionality if you need it. Most of these should be flashed from TWRP. More info below:
1. AccuWeather: Restores AccuWeather widget
2. Android default hosts file: Restores the stock hosts file
3. ANT system apps: Restores ANT apps. These are mainly fitness-related
4. Autorotation library: Flash this if your autorotate isnt working
5. Car Mode/Car Mode Remote: Restores Car Mode
6. Chrome customizations: Restores a system app which sets defaults for Chrome. Generally unneeded
7. DiagMonAgent: Related to Knox, it likes to phone home
8. Dropbox stub: Restores Dropbox stub for SCloud in Settings
9. Easy mode contacts widget: self-explanatory
10. Google FaceDetect library: Part of GApps. Restores FaceDetect library. Google cancelled support for this due to security reasons. You probably dont need it
11. Google Package Installer: Needed by Android! Flash this if OpenGApps zip removes /system/priv-app/GooglePackageInstaller
12. Google WebView: Needed by Android! Flash this if OpenGApps zip removes /system/app/WebViewGoogle
13. Help widget: Restores help/manual widget
14. MicroG installer: This will install GmsCore, GsfProxy, DroidGuard, and a permissions XML file. OpenGApps users dont need this
15. Stock firmware media files: Placed in internal storage by stock recovery. probably not needed. Extract zip and copy to /sdcard/ or /storage/emulated/0
16. Official play store: Installs PS for MicroG users. OpenGApps users dont need this
17. Original Private Mode APK: Restores original Private Mode APK. PM will not work if you flash this. probably not needed
18. Patched Private Mode APK: Installs patched Private Mode APK. PM should work fine now
19. S-Voice: Restores Samsung S-Voice app (who uses this crap?)
20. Collection of updated apps from the Note 4. Extract zip and install the APKs you want.
21. Samsung Apps widget: widget for Galaxy Apps store
22. Samsung Email/Exchange: Restores Samsung email/Exchange apps
23. Samsung_Galaxy_Store_-_Samsung_Cloud_-_Samsung_Account: Restores system apps for Samsung Account, Samsung Cloud, and Galaxy Apps store
24. Samsung game optimizer: restores game optimizer
25. Samsung Gear/Watch: Restores Gear/Watch system apps
26. Samsung Health Service: Restores Health Service, which SHealth depends on
27. Samsung internet browser: Restores stock browser
28. Samsung Kies: Restores Kies stub, which is needed for interfacing with the Kies PC software
29. Samsung QuickConnect/SFinder: restores files needed to make these work. They will also reappear in the pulldown statusbar again
30. Scrapbook: restores Scrapbook app
31. SmartManager v3: restores Smart Manager
32. Stock task manager and widget: restores task manager and Active Applications widget
33. Stock boot image and kernel library modules: restores stock boot.img and the kernel library modules it depends on.
34. Calculator: restores stock calculator
35. Stock clock apps: restores all stock clock apps
36. Stock fonts: restore stock fonts system apps
37. Stock music: restores Samsung Music app
38. stock_others.xml: This is is default others.xml with no added icons in the statusbar quick pulldown menu. Rename to others.xml (all lowercase), copy file to /system/csc/, set permissions to 0644. It is preferred that you do this from TWRP. root file manager will work too, but the owner and UID values must be 0 (root). You must factory reset before the icons will go back to default settings
39. SPlanner Calendar app and widget: Restores stock calendar and widget
40. Stock Tags (NFC) system app: Flash this if the OpenGApps zip removes /system/priv-app/Tags
41. Voice recorder: Restores stock voice recorder app
42. Stock wallpapers: Restores NoiseField and PhaseBeam wallpapers
43. System daydreams apps: Restores stock daydreams apps
44. Tap and pay widget: restores widget that lets you choose payment method
45. Google backup transport: needed by MicroG users, if they want contacts/calendar sync to work. OpenGApps users dont need this
46. Google calendar sync adapter: For MicroG users. Must also flash Google Backup Transport zip. OpenGApps users dont need this
47. Google Dialer: Installs GDialer and other files it needs to work. This is for MicroG users. OpenGApps users can just install GDialer from Play Store instead
48. Google Maps/media effects/widevine libraries: For MicroG users. Some apps wont work without these. OpenGApps users dont need this.
49. Original deodexed Google Contacts Sync Adapter: For MicroG users and OpenGApps users. MicroG users must also flash Google Backup Transport zip. This APK prevents the "Android is optimizing" message on every boot.
50. Google keyboard and Swype libraries: For MicroG users. Installs GBoard, and Swype libraries that other keyboards can use. OpenGApps users dont need this, they can just install GBoard from Play Store.
51. RBoard Theme Manager: This is an app that lets you install optional themes for Gboard. Gboard has a few default themes you can pick, this app lets you install dozens more. Along with sound effects. This app needs root. You dont need to install the RBoard magisk module separately
52. Patched build.prop for RBoard Themes Manager: This zip includes an edited build.prop so that RBoard can work. And empty /system/etc/gboard_theme folder. Rboard installs themes into this folder. Flash this before installing RBoard APK
Other mods I've done:
1. Remove Smart Manager v3. Now you will see "Power Saving" instead of "Battery" in settings
2. Adblocking hosts file integrated
3. Modded Private Mode APK by @TEKHD (now it turns on). However, PM may still break with certain custom kernels, or if you install other mods/changes I havent mentioned
4. Added 27 toggles in the statusbar (pull down to see them). Restore my default others.xml if you dont want them
5. Changed ro.securestorage.support from true to false in build.prop. Apparently Private Mode and SHealth work better when this value is false
Other notes:
Custom kernels: I would recommend FlashPoint kernel, v3 or v4 is fine. I dont recommend Ram Kernel. It is stable, but it has a bug where mobile data will stop working after awhile. It just cuts out, only a reboot will fix it...really annoying. This especially tends to happen when doing big downloads. Other kernels may work too, but i havent tried them. if you install a custom kernel, i'm not responsible if things break, like Private Mode/SafetyNet!
SafetyNet: My revised ROM zip will pass SafetyNet without root. This means you can use Pokemon Go, Netflix, banking apps, etc. There are SN checker apps out there, install one and run the test, should pass. It should also pass even with Magisk installed (it does for me). I didnt test with SuperSU, but if you install it in systemless mode, it might pass SN...no gaurantees. However, if you install Xposed, SN will definitely break. Other mods may or may not break it. I'm not responsible!
2 new additions (modded FlashPoint kernels):
With @kevintm78's permission, I am posting modded zips of FlashPoint v3.1 and FlashPoint v4 beta. They are based on the following zips:
https://androidfilehost.com/?fid=745849072291697438
https://androidfilehost.com/?fid=890129502657582253
See the FlashPoint XDA thread for details on these kernels.
I did this for the following reasons:
1. The original zips have init.d related scripts in the boot.img that remount system partition to read/write on every boot. This is fine...but it prevents most Magisk modules from working (they cant bind mount into the system partition because of the remount).
The original zips also appear to flash BusyBox into the system partition. In addition to this, there is init.d stuff in the boot images. These 2 things can potentially cause SafetyNet to fail.
I have made the following changes:
1. Removed BusyBox installer zips (install it manually if needed, or use Magisk's systemless BusyBox module)
2. Removed Magisk installer zips (because they are very old)
3. Removed init.d functionality from the boot images (this involved deleting 2 scripts, and deleting a line from init.rc)
4. Removed some unnecessary ui_print and set_progress lines from the updater-script files
If you need init.d support in the kernel, then use @osm0sis's Kernel init.d Support Injector zip
http://forum.xda-developers.com/attachment.php?attachmentid=3761907&d=1464187934
Flashing order:
1. Flash either of my custom Flashpoint zips
2. Flash Kernel init.d Support Injector zip
3. Flash root
You can also use Magisk for script execution support on boot instead. SuperSU also has su.d scripts support which works like init.d. I still prefer init.d in the kernel (I'm old school), but others may not.
Kernel Adiutor app is the recommended way of configuring these kernels. Both of the modded zips have the extended battery patches built in, so if you have an extended battery (like me), then the kernels will support it fully. If you just have a stock battery, no worries. i've tried both batteries with these kernels, found no difference in battery life or % displaying correctly.
I cant gaurantee that SafetyNet will pass with my modded zips, I had Xposed installed when I tested them. But i think it should. If you're using Magisk on top of these modded kernels, try turning on Magisk Hide, then run a SN test.
Besides the changes I've listed, nothing else is changed, everything should work pretty much the same as the original FP zips. Report kernel issues in the FP XDA thread if you run into problems, but mention that you're using my zips.
At @kevintm78's request, here are links to the source code for these kernels:
https://github.com/kevintm78/Flashpoint-F_3
https://github.com/kevintm78/Flashpoint-v4
Awesome work!!! @AnonVendetta Nice to see development for the Note 4 in 2020. Much appreciated and I thank you.
this is really great news!
thanks a lot for your efforts, I do love my N4, it can't be simply replaced because of removable battery and s-pen...
I would like to make shure not to run into trouble and kindly ask for a short confirmation if I understand all the info in your first post correctly:
my phone info current status:
android 5.1.1 - N910FXXS1COK1 - TWRP 3.4 - rooted
my target is a rooted Android 6 stock ROM
action:
1. I directly flash your deodexed TWRP-flashable ROM with TWRP.
2. I check if the phone boots correctly.
The result is: I now have a unrooted StockFW still with my TWRP in place.
2. I flash Stock N910FXXU1DRI2 boot.img with Odin in order to be able to successfully flash Magisk via TWRP. (isn't it possible to flash the boot.img also with TWRP?)
3. I now flash latest Magisk.
thanks and best wishes,
Su
@suse_: it's been a long time since I ran KitKat/Lollipop on the Note 4. For your situation, I believe the following steps will work. Since you are coming from much older firmware, flashing the ROM zip alone will almost certainly not boot, because of your older bootloader:
1. Flash my mini firmware package. This will upgrade the bootloader, modem, etc to what is compatible with the ROM. My mini firmware will overwrite your TWRP with latest TWRP, no need to flash TWRP separately.
2. Flash my ROM zip from TWRP. Be sure to wipe data/cache. While it boots, wait up to 20 mins. Because the ROM is deodexed, the 1st boot will take much longer. This is the nature of deodexed ROMs. If it hasnt booted in 20 mins, or bootloops/autoreboots...
Then you should try flashing the full, official firmware package in Odin. You can flash my ROM zip after this, but you dont need to, however you will end up with an odexed ROM if you dont.
Odin will not directly flash boot.img files, but TWRP can. No need to flash this separately unless you havent yet installed root/custom kernel but plan to.
thanks a lot @AnonVendetta for your helpful reply, will try my luck tomorrow and report back:good:
best
Su
I may later release a lightly debloated and deodexed version later. And, if anyone wants it, a debloated odexed version as well. But for right now, my laptop is out of commission, so no more work can be done for about a month. There really isnt much to do anyway, besides change the system image storage format to one that is compressed. As it is, it is just a byte for byte identical copy of the deodexed system partition, no compression applied.
n910f samsung note4
yep cant replace due spen ir removable battery superb fone and very nice size
Ive loaded sooooo many custom roms, but cant find one where everything works and is fast, camera bluetooth etc, presntly on acip
if anyone knows a custom rom where everything works on sm910f appreciate a link.
Its a fone not a toy! I need it to work with the bluetooth in the car or i get fied, I need the camera to come on immediately and not freeze of i lose the pic, I need it to start reasonably quickly and not freeze!!!!!!!!
Thankyou for this marshmallow 6 rom, may I confirm
load zip file to sd card fat32 flash with twrp
end up with stock android6 still with twrp in case a good custom rom comes out.
Advantage of custom roms... note 4 commands similar to a modern fone, i forget stuff like swype up for appstore/left button app store or was it right etc runs apps like bose which no longer run on android6 possibility of volte for poor signal in home
Actually there are a couple of better features in android 6 not carried over, swype down once and see text as well as pic for data wifi etc on shade, and big bright typefaces......
gwm121 said:
yep cant replace due spen ir removable battery superb fone and very nice size
Ive loaded sooooo many custom roms, but cant find one where everything works and is fast, camera bluetooth etc, presntly on acip
if anyone knows a custom rom where everything works on sm910f appreciate a link.
Its a fone not a toy! I need it to work with the bluetooth in the car or i get fied, I need the camera to come on immediately and not freeze of i lose the pic, I need it to start reasonably quickly and not freeze!!!!!!!!
Thankyou for this marshmallow 6 rom, may I confirm
load zip file to sd card fat32 flash with twrp
end up with stock android6 still with twrp in case a good custom rom comes out.
Advantage of custom roms... note 4 commands similar to a modern fone, i forget stuff like swype up for appstore/left button app store or was it right etc runs apps like bose which no longer run on android6 possibility of volte for poor signal in home
Actually there are a couple of better features in android 6 not carried over, swype down once and see text as well as pic for data wifi etc on shade, and big bright typefaces......
Click to expand...
Click to collapse
The GRX TouchWiz Home mod V8 runs excellent with stock roms.
@gwm121: This isnt technically a custom ROM, it's just a deodexed stock ROM. As noted above, nothing has been removed, so everything should work, in terms of functionality it is identical to the odexed stock ROM. What mods you decide to install (root, Xposed, busybox, viper, custom kernel, etc), is up to you, this is just a baseline.
Yes, just flash the zip from TWRP. If it doesnt boot, then read my posts above, you will find the answer.
hi @AnonVendetta, I followed your recommendations and successfully updated my phone, looking foreward now to check battery drain over night...
unfortunately I could not (yet) install xposed, my first attempt ended in a not starting device and I had to restore backup, need to further investigate what to do.
anyway thanks a lot once more for all your efforts!
best
Su
@suse_: The battery life on this should be pretty much the same as the stock odexed ROM. I have ran many odexed/deodexed ROMs over the years, and never noticed any significant difference between them.
If you want Xposed, this is the right version to use:
https://androidfilehost.com/?fid=529152257862685344
Do not use @rovo89's regular Xposed for Marshmallow, it will bootloop/hang on Samsung stock ROMs.
You also need the Xposed Installer app by dvdandroid.
This is what I'm running now, no issues. The deodexed ROM I've provided does *NOT* have Xposed installed.
Here is a safe debloat script. It doesnt remove that much, and everything it deletes can be installed from Play Store/Galaxy Apps if you want them back. The only apps I've added are the ones that I feel are 100% safe to delete and wont affect system stability. Maybe will add more in the future as I test.
EDIT: DEBLOAT SCRIPT REMOVED
AnonVendetta said:
@suse_: The battery life on this should be pretty much the same as the stock odexed ROM. I have ran many odexed/deodexed ROMs over the years, and never noticed any significant difference between them.
If you want Xposed, this is the right version to use:
https://androidfilehost.com/?fid=529152257862685344
Do not use @rovo89's regular Xposed for Marshmallow, it will bootloop/hang on Samsung stock ROMs.
You also need the Xposed Installer app by dvdandroid.
This is what I'm running now, no issues. The deodexed ROM I've provided does *NOT* have Xposed installed.
Click to expand...
Click to collapse
running fine now, thanks a lot!
AnonVendetta said:
Here is a safe debloat script. It doesnt remove that much, and everything it deletes can be installed from Play Store/Galaxy Apps if you want them back. The only apps I've added are the ones that I feel are 100% safe to delete and wont affect system stability. Maybe will add more in the future as I test.
Click to expand...
Click to collapse
stupid question: how to apply this? I installed it via TWRP, it did nothing, I searched appdrawer without success... is it for the commandline?
thanks
@suse_: Yes, it's a script. I forgot to mention that it needs to be flashed from TWRP. I kind of just assumed that people would know how to use it.
Can i use this on but exynos
@Tx Panda: No, you definitely shouldn't flash this on Exynos N910C. Different model/CPU chipset = not compatible. You will at the very least not be able to boot the ROM, and your device may softbrick until you repair flash with Odin.
I borrowed a friend's old desktop, monitor, and keyboard for a few weeks, while my laptop is away for repairs. It's not nearly as powerful as what I have, but it enables me to do work that can only be done on a PC.
Last night I tried to convert the raw system.img to a compressed Brotli format, but the zip didn't flash. So tonight I'm going to try to convert it to compressed ext4. If it works, I'll upload it. I may debloat it as well, along with a list of what is removed.
I really don't see a point in releasing a debloated odexed ROM, since a debloated and deodexed zip accomplishes pretty much the same thing, and is much easier and less aggravating to mod system files. I actually do prefer odexed ROMS, because they seem to run slightly faster overall than deodexed. But the speed difference is minimal, and if you have a good device like the Note 4, the differences are negligable.
A few other things I'd like to note:
1. Do not use Titanium Backup to debloat. It has a tendency to delete a bit more than necessary. I have seen users complain in the past about auto-rotate not working after using TiBu. This is because it deletes, in addition to the APK, odex files as well, as well as library files (name's ending in *.so, you can find them in /system/lib/ and /system/vendor/lib/). Sometimes these library files are used by other Android processes. Use TiBu as a reference to find the location of an app that you want gone, then delete it manually with a root file manager or TWRP. This leaves library files intact. TiBu is great, I use it for backup/restore, but never for debloating.
2. If you want to confirm that the bootloader, ROM version, CSC version, and baseband/CP/modem version are the same as the values I posted, you can use the free version of Phone Info by vndnguyen (search Play Store). However, these values may not match if you didn't at least flash my mini firmware package or the full official package before the deodexed zip. This way you will know your firmware is up to date. And if you switch to a different ROM, then you probably don't need to update it. As an alternative to stock, I find Resurrection Remix Nougat to be very fast and stable. If you wanted to run this or one of the new custom ROMS, you could just flash my mini firmware, then skip this deodexed ROM.
So, I'm currently building a new ROM zip. It is deodexed, same as original zip, but also debloated/de-knoxed. I removed a fair bit more than what my safe debloat script zip deletes. Nothing has been added. This leaves the system partition with about 38% free space (2.2GB used). I've tried to limit the removals to what I feel won't affect system usability/stability. So, here's what's removed:
/system/app/Books (Google Books)
/system/app/Chrome
/system/app/Drive (Google Drive)
/system/app/Dropbox_zero (Dropbox app)
/system/app/Flipboard (news app)
/system/app/FlipboardBriefing (news app)
/system/app/Gmail2
/system/app/Hangouts
/system/app/Maps (Google Maps)
/system/app/Photos (Google Photos)
/system/app/Music2 (Google Play Music)
/system/app/Newsstand (Google Play Newsstand)
/system/app/PlayGames (Google Play Games)
/system/app/PlusOne (Google+)
task manager and associated widget (who uses a task manager these days?)
/system/app/Videos (Google Play Movies/TV)
/system/app/YouTube
lots of apps related to facebook/instagram/whatsapp/evernote
Samsung print service plugin
PEN.UP
Peel Smart Remote (constantly bombards the **** out of your phone with ads like every minute, and when you unlock screen, it had to ****ing go...never seen a more annoying app)
S Note
Galaxy Apps widget (Galaxy apps store not removed, only its' useless widget)
stock email/exhange app (there are way better email apps out there)
Hancom office
stock calculator
S Health (left S Health service intact, you can reinstall S Health if you want, it will work)
stock voice recorder (way better stuff out there)
bubbles/phase beam stock wallpapers
knox:
/system/app/BBCAgent
/system/app/Knox
/system/app/MDMApp
/system/app/RCPComponents
/system/app/SamsungDLPService
/system/app/SecurityLogAgent
/system/app/SecurityProviderSEC
/system/app/SysScope
/system/app/UniversalMDMClient
/system/container
/system/etc/secure_storage/com.sec.knox
/system/preloadedmdm
/system/priv-app/KLMSAgent
/system/priv-app/SPDClient
Knox has got to be the most annoying POS security system Samsung has ever made, it likes to block root stuff. I've always just ripped it out by the balls, never had a loss in functionality because of this.
Most of what i've removed can be reinstalled from Play Store/Galaxy Apps, except Knox. The rest is generally useless junk that I feel most people won't miss. The whole point is to decrease the installed footprint of the system partition, while saving battery/CPU/RAM.
I'll spend the rest of tomorrow testing, then upload. This will very likely be the last released zip, I don't intend on turning this into a full-on custom ROM. In fact, I mainly created this topic to help out @prkfsz with a deodexed ROM that he could easily install MicroG onto. So far he hasn't reported whether it works. But then I realized I'd be doing the community a small service, so I created this topic. With that said, I'm not inclined to do much more free work, I'm a very busy guy most of the time. But I'll still stick around to answer questions.
@AnonVendetta - thank you for all the work. Sorry for not answering before, as i said, i was away and just recently got back. Will not have time to try your ROM untill next week.
I did manage to deodex stock ROM before with that APKtool you suggested, and it was a breeze with your instructions. Even here your instructions are very clear. You should be writing manuals..
Glad to see that there still is an interest for this great device. Personally i am going to run it as long as it works. And then i have a backup or five..
Am gratefull also for this ROM you are working on. That is almost exactly what i was looking for to begin with. I just sortof don't really get why you would remove S Note from the stock rom - that is basically one of the greatest advantages of this phone. I know there are other writing apps out there, i guess Squid is ok but in my opinion no apps come close to original SNote.
Looking forward to trying out your creations!
@prkfsz: I removed S Note and PEN.UP because I very rarely use the pen. Both of these are installable from Play Store/Galaxy Apps, so you're not really losing them. I have always considered them to be bloat. Another reason is that the versions Samsung includes in the ROM are old and not up to date.
You could have deodexed the entire ROM with APKTool, but it would have taken forever compared to the Kitchen. On my powerhouse PC, deodexing takes about 15 mins.
Disclaimer:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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.
I'm sorry if my English is bad as it's not my native language.
* This ROM isn't mine. I just modified a bit to fit to daily use.
What is SlimLP?
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
SlimLP is the project name for SlimRoms based on Android 5.0 and offers the following original features:
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter (Coming Soon)
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
ROM Information:
ROM Name: SlimLP
Android version: Android 5.1.1
Compatibility: All Galaxy Core 2 model (SM-G355H/SM-G355M/SM-G355HN)
Update (August 5th 2022): Might not work on M/HN model.
Features:
* Based on the original custom ROM made by @Ih24n.
* Removed some unwanted apps.
* Built-in root are installed and working stably.
Bugs:
- Hardware buttons are not working. You need to enable navigation bar in Settings.
Update (August 5th 2022): Install Button Mapper to fix.
- Tell me if you have issues when using this ROM.
Requirements:
- A Galaxy Core 2 device.
- Custom recovery (You should use TWRP).
How to install?
1. Reboot your device to recovery mode.
2. Wipe: Dalvik-cache, Cache, Data, System.
3. Choose Install in TWRP Menu.
4. Choose your ROM destination (Internal Storage or Micro SD Card).
5. Choose the .zip file.
6. Swipe to install the ROM.
7. IMPORTANT! After the ROM is installed successfully, don't choose Reboot System.
Flash these files: Fix GPS, Fix Off Charging and Fix Battery.
8. Restart to System.
More information about this ROM:
http://www.sandroidteam.com/2016/12/custom-rom-slim-lp-015-samsung-galaxy.html
Download ROM and Fixes:
https://bom.to/fp71U5
Kernel source: Here
It doesn't work for me on a Galaxy Core 2 SM-G355HM, the rom installs successfully, but when I reset the phone, it ends up stuck in a bootloop with the boot animation. Is there any fix?
Arturo2006 said:
It doesn't work for me on a Galaxy Core 2 SM-G355HM, the rom installs successfully, but when I reset the phone, it ends up stuck in a bootloop with the boot animation. Is there any fix?
Click to expand...
Click to collapse
The author of the original custom ROM (@Ih24n) only has a SM-G355H model, so the ROM might not compatible with M/HN. You should try other custom ROMs. Sorry.
You can visit Sandroid Team Project website for custom ROMS or you can try my other modified rom from that project for lighter experience, since I debloat and customize for battery and performance.
Sandroid Team Project link: https://ih24n69.github.io/downloads/kanas/
Hello, can you port the cm12.1 made for core prime to core 2 keeping the stock kernel? Because i have used the one ih24n made and his one had bugs and wasn't stable for daily use and his sandroid kernel slows down games drastically for whatever reason and these issues exists in all the roms i got from him.
Or just a detailed guide for porting a core prime rom to core 2 keeping the stock kernel will just do a lot for me.
I want ROM which supports CH341 driver(kernel edit), can we do something about it?
"Hello everyone,
I’m having trouble installing the SlimLP ROM (Edited Version) on my Samsung Galaxy Core 2 SM-G355M. The installation process gets stuck on the boot screen and I can’t seem to get past it. I would really appreciate any help or advice on how to fix this issue, as this is my only phone and I don’t have the means to buy a new one at the moment.
Thank you in advance for your help!"
You can copy and paste this message into a new thread or reply to an existing thread about the SlimLP ROM on the XDA Developers forum. Make sure to provide as much detail as possible about the issue you’re experiencing to help others understand and assist you better.
Is there anything else you would like to know?