Related
Note that this rom has a dedicated Q&A thread: http://forum.xda-developers.com/showthread.php?p=59185266
Stock firmware for the Samsung N910W8, based on official Samsung builds. Works with all supported Canadian carriers. Rom is rooted, zipaligned, deodexed, and includes both busybox and Init.d support. There are two versions to choose from: Regular and Debloated. Enjoy!
N910W8 "Regular" Version
Base:
v3.21 - COK3 (Lollipop 5.1.1, Bell Mobility Canada)
v3.2 - COK3 (Lollipop 5.1.1, Bell Mobility Canada)
v3.1 - COI4 (Lollipop 5.1.1, Bell Mobility Canada)
v3.0 - COI4 (Lollipop 5.1.1, Bell Mobility Canada)
v2.5 - BOE2 (Lollipop 5.0.1, Bell Mobility Canada)
v2.4 - BOF2 (Lollipop 5.0.1, Puerto Rico)
v2.3 - BOE1 (Lollipop 5.0.1, Telus)
v2.1 - BOC4 (Lollipop 5.0.1, Bell Mobility Canada)
v1.1 - AOA1 (Kitkat 4.4.4, Bell Mobility Canada)
v1.0 - AOA1 (Kitkat 4.4.4, Bell Mobility Canada)
Modem:
Modem removed (your modem will not be changed by flashing this rom).
Changes from stock:
Added init.d support
Added BusyBox
Rooted
Deodexed
Zipaligned
Disabled securestorage support for improved compatibility with Xposed (Regular v1.0/v1.1 only)
Restored external SD card write permissions (Regular v1.0/v1.1 only)
N910W8 "Debloated" Version
Base:
v3.21 - COK3 (Lollipop 5.1.1, Bell Mobility Canada)
v3.2 - COK3 (Lollipop 5.1.1, Bell Mobility Canada)
v3.1 - COI4 (Lollipop 5.1.1, Bell Mobility Canada)
v3.0 - COI4 (Lollipop 5.1.1, Bell Mobility Canada)
v2.5 - BOE2 (Lollipop 5.0.1, Bell Mobility Canada)
v2.4 - BOF2 (Lollipop 5.0.1, Puerto Rico)
v2.3 - BOE1 (Lollipop 5.0.1, Telus)
v2.2 - BOC4 (Lollipop 5.0.1, Bell Mobility Canada)
v1.1 - AOA1 (Kitkat 4.4.4, Bell Mobility Canada)
v1.0 - AOA1 (Kitkat 4.4.4, Bell Mobility Canada)
Modem:
Modem removed (your modem will not be changed by flashing this rom).
Changes from stock:
Added init.d support
Added BusyBox
Rooted
Deodexed
Zipaligned
Removed Knox Apps/Folders
Debloated
List of removed/cleaned apps and folders in "Debloated" version:
Spoiler
AutomationTest_FB
BlueToothTest
Blurb
Books
Bridge
ChocoEUKor
Chrome
com.sec.knox.store
container
CoolEUKor
Drive
Dropbox
DualClockDigital
EasySettings
Facebook
Flipboard
Hangouts
HwModuleTest
InteractiveTutorial
KLMSAgent
KnoxAttestationAgent
KnoxSetupWizardClient
Magazines
MobileTrackerEngineTwo
NoiseField
PhaseBeam
PlusOne
preloadedsso
PreloadInstaller
RCPComponents
RoseEUKor
SamsungSans
sCloudBackupApp
sCloudDataRelay
sCloudDataSync
sCloudSyncCalendar
sCloudSyncContacts
SecFactoryPhoneTest
SecSafetyAssurance
SNS
SPDClient
SPPPushClient_Prod
talkback
UniversalMDMClient
Videos
WlanTest
YouTube
WHAT'S NEW
Spoiler
Regular/Debloated v3.21:
Added CSC folder back into the rom (LTE icon is back).
Removed multiple apks that weren't being properly debloated in a few of the previous rom versions -- see list of removed apps in OP.
Regular/Debloated v3.2:
Updated to latest official N910W8 base from sammobile.com
Updated SuperSu to v2.62.
Different build method -- used "sparse_dat" instead of "set_metadata" to avoid bootloops.
A few apks that I normally remove from the Debloated version were left untouched this time (Dropbox, Flipboard, ChocoEUKor, CoolEUKor). Just remove them manually if needed
Rom now boots with Selinux Enforcing stock kernel!
Regular/Debloated v3.1:
Fixed to allow boot with modded stock kernel (used "set_perm" instead of "set_metadata". Big thank you to Raziel2k6 for all his help with the kernel boot issue!).
Rom now includes modified stock Selinux Enforcing COI4 5.1.1 kernel from OP2. Note: new kernel seems to cause issues with the camera. If your camera force closes, or if you get bootloops due to latest Samsung policy security update, then use a custom 5.1.1 kernel for now until these issues can be resolved.
Updated SuperSu to v2.50 beta.
Note that after booting up you will see a black screen for 5-10 seconds. I'm not exactly sure what the cause is, but I'll continue working on it. For now it doesn't seem to affect anything beyond that.
Removed several more apks in the debloated version that were missed in v3.0 (Bridge, ChocoEUKor, CoolEUKor, Drive, Dropbox, Flipboard, Hangouts, UniversalMDMClient, YouTube).
Regular/Debloated v3.0:
Updated to latest official Samsung 5.1.1 Lollipop COI4 base (Bell Mobility Canada).
The rom's included stock kernel will not boot because the rom is rooted (new 5.1.1 security...yay). Be sure to flash a custom 5.1.1 kernel like Emotion or AEL after installing the rom in TWRP! I'm working to find another solution regarding the stock kernel for a subsequent update, but if no success then I will at least look into including a custom 5.1.1 kernel so the rom boots without needing to flash another kernel afterwards.
SuperSu seems to allow us to use "Prompt" instead of "Grant" again. If you have any problems though, just switch to back to "Grant".
Removed as many Knox files as possible from the Debloated version, but left everything intact for the Regular version to keep it as close to possible to stock (since some might use this base for further development). Either way, you may get KNOX-related FCs after the initial boot, especially on Regular. Recommend you run Titanium Backup at this point, and search for any apps containing the word "knox". Freeze all the apps that appear and you should be good to go from there.
Regular/Debloated v2.5:
Updated to latest official 5.0.1 Lollipop BOE2 base (Bell Mobility Canada) from sammobile.
Stagefright patch.
Regular/Debloated v2.4:
Based on new BOF2 firmware released for the N910W8 (Puerto Rico). Not clear what changes are in this build compared to BOE1 firmware, but hey it's here if anyone is curious .
ROM is based for Puerto Rico, so it's not in English by default. During initial setup you can change the language to English. You'll also want to change the language to English in the keyboard settings menu, as well as in the Handwriting Recognition settings (under Settings/Language and Input).
More carrier bloatware in this firmware release (compared to what we usually get from Bell, Telus, etc.). The "Regular" version of my rom is always kept as close to stock as possible, so Regular v2.4 includes the "Claro" boot animation, shutdown animation, .ogg sound files, wallpapers, and related apks. All of these have been removed in Debloated v2.4 though (well, all except for one pesky apk I couldn't find...just disable/freeze claro.apk after rom installation and first boot).
Regular/Debloated v2.3:
Updated to latest official 5.0.1 Lollipop BOE1 base (Telus) from sammobile.
Debloated v2.2:
Used a new debloat process and also fixed FC when using the front-facing camera.
Regular/Debloated v2.1:
Updated to latest official 5.0.1 Lollipop BOC4 base (Bell Mobility Canada) from sammobile.
Securestorage and read/write permissions are unchanged from stock in these latest builds. This provides a clean base for everyone. See post #2 for instructions on tweaking these settings if you prefer.
Regular/Debloated version 1.1:
Restored external SD card write permissions
Disabled securestorage support (improved compatibility with Xposed)
Regular/Debloated version 1.0:
Initial build, based on official KitKat 4.4.4 AOA1 firmware (Bell Mobility Canada) from sammobile.
ROM INSTALLATION
I tested all versions of the rom on my own device and everything works well, but you know the drill: This will trip Knox and void warranty. Flash at your own risk and always make a backup in recovery before flashing
Make a Backup!
Make sure you are on the correct base firmware (e.g. COI4, AOA1, BOC4, etc). If not then download it through sammobile.com and flash it through Odin.
Make sure you have twrp installed. If not, download it on xda and install it through odin.
Download the rom (links at the end of this post).
Reboot to recovery mode.
Wipe data, cache, dalvik, and system
Install the rom.
Note: As of Regular/Debloated v3.2, you do not need to install a custom kernel to boot! For Regular v3.0 and v3.1 though, you will need to flash a Selinux permissive custom kernel (e.g. Emotion, AEL, Beastmode) at this point in the process or you will get stuck in a boot loop.
Reboot (if prompted, do NOT allow TWRP to install supersu. It says it's not installed but it is).
Phone may bootloop once but then will boot fine after that (normal effect of using supersu 2.62). Enjoy!
Post-installation notes:
Known bugs (as of latest builds): Action memo not working on Regular/Debloated builds. Will fix as soon as I can figure it out or as soon as someone lets me know the cause!
For 5.0.1 roms only: Open the SuperSu app to see if you're prompted to update binaries. If so, update them using the "Normal" method and not the "CWM/TWRP" method. If you are on 5.0.1, make sure to also change the SuperSu app's "Default Prompt" from "Prompt" to "Grant".
For 5.1.1 only: If you get any Knox-related FCs after initial boot-up, particularly if you're on Regular v3.0 or v3.1. Just freeze any remaining Knox apks through TitaniumBackup. If you encounter any other FCs (such as Google Maps or Samsung Link Platform), just make sure to update the problematic app from the Play Store/Samsung's Galaxy Apps Store or disable the app altogether.
ROM DOWNLOADS
Regular version:
Regular v3.21: https://www.androidfilehost.com/?fid=24269982087016361
Regular v3.2: https://www.androidfilehost.com/?fid=24269982087015673
Regular v3.1: https://www.androidfilehost.com/?fid=24052804347834682
Regular v3.0: https://www.androidfilehost.com/?fid=24052804347830440
Regular v2.5: https://www.androidfilehost.com/?fid=24052804347792646
Regular v2.4: https://www.androidfilehost.com/?fid=24052804347775503
Regular v2.3: https://www.androidfilehost.com/?fid=23991606952612924
Regular v2.1: https://www.androidfilehost.com/?fid=95916177934554867
Regular v1.1: https://www.androidfilehost.com/?fid=95916177934527385
Regular v1.0: https://www.androidfilehost.com/?fid=95916177934522750
Debloated version:
Debloated v3.21: https://www.androidfilehost.com/?fid=24269982087016387
Debloated v3.2: https://www.androidfilehost.com/?fid=24269982087015672
Debloated v3.1: https://www.androidfilehost.com/?fid=24052804347834704
Debloated v3.0: https://www.androidfilehost.com/?fid=24052804347830461
Debloated v2.5: https://www.androidfilehost.com/?fid=24052804347792645
Debloated v2.4: https://www.androidfilehost.com/?fid=24052804347775572
Debloated v2.3: https://www.androidfilehost.com/?fid=23991606952612923
Debloated v2.2: https://www.androidfilehost.com/?fid=23991606952595292
Debloated v1.1: https://www.androidfilehost.com/?fid=95916177934527450
Debloated v1.0: https://www.androidfilehost.com/?fid=95916177934526323
Modified N910W8 COI4 5.1.1 Stock Kernel (beta)
If anyone is interested I have a beta kernel available for download/testing/feedback!
I modified the 5.1.1 stock COI4 kernel to allow it to boot COI4-based 5.1.1 roms rooted with supersu beta v2.50-v2.52. Kernel is otherwise pure stock, and boots in Selinux Enforcing mode (yes, rooted). Big thank you to Chainfire for figuring this one out and sharing with XDA.
As always, I never share anything without testing it first...but it's still beta so make a backup please and flash at your own risk
KNOWN BUGS:
Camera force closes on custom 5.1.1 roms, but works fine on rooted stock 5.1.1. If using a custom 5.1.1 rom, please use a custom 5.1.1 kernel.
UPDATE #1: Latest Samsung security policy update seems to have killed root and cause bootloops when using the modded Selinux enforcing kernel on 5.1.1 roms. For now you will need a selinux permissive custom kernel unless chainfire can identify another solution.
UPDATE #2: Chainfire has released SuperSu beta v2.62 which now modifies the stock kernel directly on your device (without having to manually modify it first). This means that for the newer COK3 firmware a separate modified kernel is no longer necessary to run root on stock. Will leave this kernel here anyways, in case someone wants to use it to run a system-based root on stock COI4. Otherwise I suggest using the newer SuperSu methods like systemless 2.62 and beyond as Chainfire released new updates for us.
KERNEL INSTALLATION:
Boot to TWRP recovery
Flash a COI4-based rom (skip this step if you already have a compatible rom installed)
Flash SuperSu beta 2.50 (skip this step if your rom already has supersu 2.50-2.52 installed)
Flash modified COI4 kernel (see download link below)
Reboot
KERNEL DOWNLOAD:
SelEnforce COI4 v0.1: https://www.androidfilehost.com/?fid=24052804347832210
Just a few tips and tricks. I'll add more when there's time...
You know the drill: Any modifications or flashes to your device are done at your own risk. Keep a recent backup for extra safety
Restoring debloated apps (for Debloated rom only):
HWModuleTest: Restores the ability to enter the Samsung diagnostic menu system code (*#0*#) through the dialer. To install, begin by downloading the apk to your phone. Then use Root Explorer to create a new folder named "HwModuleTest" (without the quotes) in your phone's /system/priv-app/ folder. Change the new folder's permissions to rwxr-xr-x and then copy the apk you downloaded to this new folder you just created. Change permissions on the file to rw-r--r-- and reboot! The code should now work properly and allow you to access the diagnostic menu. Thank you to Larkstarr for identifying the apk's functionality and testing the apk!
TaskManager: Restores the TaskManager functionality. To install, begin by downloading the apk to your phone. Then use Root Explorer to create a new folder named "TaskManager" (without the quotes) in your phone's /system/app/ folder. Change the new folder's permissions to rwxr-xr-x and then copy the apk you downloaded to this new folder you just created. Change permissions on the file to rw-r--r-- and reboot! The code should now work properly and allow you to access the diagnostic menu. Thank you to Cryingmoose for leading me in the right direction to figure this out out!
Changing your boot animation:
Search online or in XDA and download a new boot animation to your phone (Google is your friend). There should be two files, both in the .qmg format. Make sure they are named bootsamsung.qmg and bootsamsungloop.qmg (If not, rename them now).
Use Root Explorer to navigate to /system/media/ on your phone.
Rename bootsamsung.qmg to bootsamsung.qmg.bak (if prompted to remount as read-write, press "Yes").
Rename bootsamsungloop.qmg to bootsamsungloop.qmg.bak (if prompted to remount as read-write, press "Yes").
Use Root Explorer to move (or copy) your new boot animation to the /system/media/ folder
Use Root Explorer to change the permissions on the new system/media/bootsamsung.qmg file to 644 (rw-r--r--)
Use Root Explorer to change the permissions on the new system/media/bootsamsungloop.qmg file to 644 (rw-r--r--)
Reboot!
Changing your shutdown animation:
Search online or in XDA and download a new shutdown animation to your phone (Google is your friend). Your animation should be in the .qmg format. Make sure it is named shutdown.qmg (If not, rename it now).
Use Root Explorer to navigate to /system/media/ on your phone.
Rename shutdown.qmg to shutdown.qmg.bak (if prompted to remount as read-write, press "Yes").
Use Root Explorer to move (or copy) your new shutdown animation to the /system/media/ folder
Use Root Explorer to change the permissions on the new system/media/shutdown.qmg file to 644 (rw-r--r--)
Reboot!
Having trouble running init.d scripts at boot?
See the following post for info and link to the solution: http://forum.xda-developers.com/showthread.php?p=58804378
How to enable write permissions for external SD card:
See the following for instructions: http://forum.xda-developers.com/showthread.php?t=2687734
How to enable/disable secure storage support:
Use Root Explorer to navigate to the /system/ folder on your phone.
Edit build.prop
Find the line that references ro.securestorage.support
Edit this line accordingly. "True" to enable, "false" to disable (without the quotes of course!)
Save the file and reboot.
If you have trouble connecting to wifi after making this change, simply forget your saved wifi connection and add it again.
Removing the S-Finder and Quick Connect toggles:
See this post for instructions: http://forum.xda-developers.com/showthread.php?p=62949226
Themes:
Not a fan of the stock TouchWiz look? Check out the following thread for themes that have been confirmed to work on this rom without issues. More will be added as they are tested/confirmed.
Nacos themes thread: http://forum.xda-developers.com/showthread.php?p=59019781
Awesome!
Thanks for this my friend..im sure everyone will appreciate the effort.
Lets show this man some thanks!
sent from Canada via my Note 4, 3, 2 or S3
Thanks for the deodexed A1. Not sure why but when I flash I lose modem no wifi or signal. It says no sim I am on Rogers I know it says bmc but with the csc removed it shouldn't make a difference. I tried flashing the modem through odin, no go had to flash whole rom through odin . Also get a direct pen error as well not sure what app deals with that
32dave said:
Thanks for the deodexed A1. Not sure why but when I flash I lose modem no wifi or signal. It says no sim I am on Rogers I know it says bmc but with the csc removed it shouldn't make a difference. I tried flashing the modem through odin, no go had to flash whole rom through odin . Also get a direct pen error as well not sure what app deals with that
Click to expand...
Click to collapse
So you flashed the entire A1 firmware package via ofin then this and still no baseband or wifi?
sent from Canada via my Note 4, 3, 2 or S3
force70 said:
So you flashed the entire A1 firmware package via odin then this and still no baseband or wifi?
sent from Canada via my Note 4, 3, 2 or S3
Click to expand...
Click to collapse
I was on another custom rom , wiped flashed lost wifi and signal. So I flashed the modem with odin same had to flash entire A1 rom with odin and it came back
32dave said:
I was on another custom rom , wiped flashed lost wifi and signal. So I flashed the modem with odin same had to flash entire A1 rom with odin and it came back
Click to expand...
Click to collapse
Just checking..if you flashed the firmware and still had those issues then id be confused.
Once your on A1 shouldnt be any problems
sent from Canada via my Note 4, 3, 2 or S3
32dave said:
I was on another custom rom , wiped flashed lost wifi and signal. So I flashed the modem with odin same had to flash entire A1 rom with odin and it came back
Click to expand...
Click to collapse
Had you ever upgraded to AOA1 through Odin before? If not then your experience makes sense. You need to odin flash the new base at least once before flashing new AOA1 roms through recovery. Now that you have, you should be ok moving forward.
sefrcoko said:
Had you ever upgraded to AOA1 through Odin before? If not then your experience makes sense. You need to odin flash the new base at least once before flashing new AOA1 roms through recovery. Now that you have, you should be ok moving forward.
Click to expand...
Click to collapse
No I was on A1 already through odin when it came out
32dave said:
No I was on A1 already through odin when it came out
Click to expand...
Click to collapse
Ok thanks for the feedback. Hmm, is it possible the APNs were reset to Bell instead of Rogers by flashing this? Not sure if that would cause your issue but just a thought... If so you would need to enter your own APN info after flashing this. If not, well I could always build a version based off the Rogers firmware and add it to the first post if you're willing to try it out. For the s-pen issue I'll need to flash the debloated version tonight and see if I get the same error. Might be one of the removed apps because the regular version works fine for me, although from looking at the list of removed apps I dont immediately see anything that would cause a problem.
OK so the the full version has no issues just the debloated version if that helps narrow it down
32dave said:
OK so the the full version has no issues just the debloated version if that helps narrow it down
Click to expand...
Click to collapse
Yes that does help, thanks! Seems like I may have removed something I shouldn't have . Added a few things back and testing now on my device. If it works I'll re-upload a new debloated version and update OP...
sefrcoko said:
Yes that does help, thanks! Seems like removing the CSC here was a bad idea . I didn't realize that all Canadian CSCs are already included in that folder, so no need to remove I guess. Added a few things back and testing now on my device. If all works well I'll re-upload a new debloated version shortly and update OP...
Click to expand...
Click to collapse
I had the same issue when i flashed the de-bloated version of your rom, probably the csc you removed because when i flash the firmware you pm'd me it works just fine
Ok, looks like it's all sorted out now. After a lot of digging and testing it seems like it was simply a bad build with the Debloated version and nothing to do with any of the theories I mentioned lol. I had the same issues as everyone else with the previous debloated version, but this new one works fine for me now (finally!).
I have re-uploaded the fixed Debloated version and updated the link/md5 in OP. Let me know if you run into any issues with the new build. If you happen to get an S_Planner Force Close error, just click ok and reboot. I only got it once but it seems to disappear for good after that first time.
Also, I'm assuming that since the Regular version seems to be working on Rogers then it should also work for other supported Canadian carriers like Telus, Fido, etc... Anyone else not with Bell who can confirm?
Working for me. Thanks
The debloated version didn't work for me. It downloads fine but I get an "unexpected end of archive" error when I try to open it up on my PC. Also it doesn't want to copy to the phone over USB. It seems to be an archiving issue. I'll try to download it again, maybe over a different mirror link. I'll post updates...
sefrcoko said:
Ok, looks like it's all sorted out now. After a lot of digging and testing it seems like it was simply a bad build with the Debloated version and nothing to do with any of the theories I mentioned lol. I had the same issues as everyone else with the previous debloated version, but this new one works fine for me now (finally!).
I have re-uploaded the fixed Debloated version and updated the link/md5 in OP. Let me know if you run into any issues with the new build. If you happen to get an S_Planner Force Close error, just click ok and reboot. I only got it once but it seems to disappear for good after that first time.
Also, I'm assuming that since the Regular version seems to be working on Rogers then it should also work for other supported Canadian carriers like Telus, Fido, etc... Anyone else not with Bell who can confirm?
Click to expand...
Click to collapse
I am using it on my t-mobile note 4, and no issue with the new debloated build
nacos said:
The debloated version didn't work for me. It downloads fine but I get an "unexpected end of archive" error when I try to open it up on my PC. Also it doesn't want to copy to the phone over USB. It seems to be an archiving issue. I'll try to download it again, maybe over a different mirror link. I'll post updates...
Click to expand...
Click to collapse
Yes sounds like a bad download to me. Try checking md5 and/or downloading again. I'm able to open the zip here, so sounds like the transfer to your PC got corrupted along the way. Let us know... Thx!
sefrcoko said:
Yes sounds like a bad download to me. Try checking md5 and/or downloading again. I'm able to open the zip here, so sounds like the transfer to your PC got corrupted along the way. Let us know... Thx!
Click to expand...
Click to collapse
Yes, it may have been a bad download. I downloaded it again and it worked just fine. A few observations though!
1. If this is a Bell base why is it that the LTE symbol in the status bar was replaced by a 4G symbol? I've been with Bell for as long as I know and I've never seen the 4G symbol in
the status bar for LTE networks?
2. I would suggest including the modified platform.xml in the ROM - for full access to the external SD (adding media_rw)
3. While on stock (rooted) I was never able to mount media_rw at boot by automatically running a script for a shell command (made a new userinit.sh file and placed it under data/local/). Normally, the file userinit.sh should be automatically executed at boot but it never did work. The userinit.sh would be:
Code:
#!/system/bin/sh
busybox mount -o remount,rw /
chmod 770 /mnt/media_rw
I always assumed it was due to not having init.d support, however I just tried it on this ROM and it still doesn't execute it. I've also tried using the same script with ROM Toolbox'
scripter and set the script to run at boot but it doesn't do anything at all. Any idea, suggestions?
PLEASE READ NEW FLASHING INSTRUCTIONS​
Disclaimer:
I am not responsible for any bricks. By flashing this you understand that no one involved with the making of this Rom is responsible for a brick. However, if two nations go to war, that's okay, because they will destroy themselves and their people will worship me, THE BUTTAHLORD OF BUTTERNOOBIA!!!
I mean uhh... No, very bad thing, no countries should not go to war *cough* destroy yourselves *cough*
PLEASE READ ENTIRE THREAD BEFORE FLASHING, D/Ls and Changelog in 2nd Post​
Okay past the joking, this is a stock, rooted KitKat ROM for the ZTE ZMAX. The deodexed version would not boot, so this is odexed. However, this version is free of any King Related apps and I've also removed the little bit of crapware in the device.
FEATURES:
Removal of All King Related Apps
Pre-Rooted
Clear of Bloatware
Added Xposed
Added SuperSU
Removed crappy ZTE/Metro/TMO apps
Overall Clean experience
HOW TO FLASH (NEW INSTRUCTIONS):
1. Place ZIP on SD Card
2. Reboot Into TWRP
3. NANDROID (DO NOT SKIP THIS FOR YOUR SAKE)
4. Don't factory reset the normal way, go to wipe > advanced wipe and click "dalvik cache", "data", "cache" and "system". If you don't, you run the risk of getting an updater-script error (not from the zip, it's a bug in some TWRP builds).
5. New Step: Reboot recovery (in the recovery menu). It will ask if you want to install su, press do not install.
5. Flash the ROM
6. Reboot and rep Butternoob!
BUGS:
Free and clear, you tell me!
ADDITIONAL INFORMATION:
Butternoob has been confirmed to work on all variants of the ZTE ZMAX by at least two people on each variant. THIS IS NOT SUPERBUTTER! For those that don't know, Superbutter will be a heavily modified custom rom. Butternoob was designed to be a stock, clean experience with solid performance. I may add tweaks, but you won't find a lot beyond the stock experience.
CREDITS:
-XDA User Mazer.One for the Bootanimation. I made some edits to his and don't take credit for the original work.
-JCase for helping us get root
-Hroark13 for helping me fix the wifi issue in the updater-script
-ZTE Because I have to... They are banished from ButterNoobia though...
-Masterchief87 for the 4.4.4 base and boot.img
ENJOY, REPORT BUGS, FEEL FREE TO USE AS A BASE AND GIVE PROPER CREDITS!
People have asked what my PayPal email is for donations, it is [email protected] . Never required but always appreciated, I'll give 100% regardless
Changelog:
V2:
-Updated to Android 4.4.4 base
-Band 12 Ready
-Replaced Google Launcher with Apex
--Advice on Apex: Go into menu > apex settings > drawer settings > drawer animation > circle to enable Lollipop-style animation for the drawer opening!
-Fixed SuperUser (All binaries updated)
-Fixed Gapps Force Closes
- New Wallpaper, taste of the SuperButter
-All bugs are squashed
V1:
-Initial Release
-Android 4.4.2
-Removed T-Mobile Apps
-Removed ZTE Apps (i.e. music, file manager, etc.)
DOWNLOAD:
BUTTERNOOB Stock 4.4.4 v2.0
md5: E44F1F84B47D3C4401DA522D0A7494F5
BUTTERNOOB Stock 4.4.2 v1.0
md5: 092cee0504d07fa4decde02d2206a2b7
Mine again
Cricket Zte Z987
Will this work on Cricket ZTE Z987 model
How to enable VOLTE on this rom?
work
will this work on ZMAXX Z958 ?
kas hif said:
will this work on zmaxx z958 ?
Click to expand...
Click to collapse
no. Don't try it. Unless you want to buy another phone.
Having an odd issue with LTE. When I call with LTE enabled, it tries to force the call through VOLTE, rather than handing off to a 4g (or whatever) local band. The call, of course, fails with no audio in or out; is this a known issue, is there a workaround, do I need to re-flash, or is this something weird that nobody's heard about before?
Does this work on Grand X Max + Z987?
Sent from my Z987 using Xparent Blue Tapatalk 2
Zmax Z970 RamDisk Boot.img packing problem
Hi,
Im attempting to repack the ram-disk image for my boot img on my ZTE Zmax z970 running the BN 2.0-oxed ROM. I was trying to use gzip with mkbootimg and it is not working, im assuming due to the fact that my newly repacked ram-disk cpio compressed file was not the same size as the original making the phone fail to boot when the boot.img was sent back to the boot block. My pc is running Ubuntu 14.04-32 bit. I know that the unpack-bootimg and mkbootimg scripts are working correctly because when i repack an unchanged boot.img-ramdisk.cpio.gz file (unpack the img and recreate the boot.img file) and re-upload it to the boot block, the phone boots correctly so I know that my procedures outside of the ram-disk cpio file are correct. My question is, How can I find out how much padding i need on the ram-disk file, where the padding should go, and how to apply the padding to get the file the correct size so that it will work as intended? Any help you can give me would be greatly appreciated.
P.S. I only unpackaged the boot image to change one entry in the ramdisk to the default.prop file. If there is a way to open the compressed cpio file with an archive manager and could update the file once i make my change. that would work as well. I can open the gz file with the archive manager but can not open the cpio folder contained inside.
Thanks,
Much appreciation.....f20062e
I followed your directions. Surprisingly it was super easy! Thanks!!!!!
Does this work on 6.0.1 Zmax Pro Tmobile?
link
Need link to root the z981 and link for twrp to install the recovery image. Thanks all for the hard work this excellent community pours out on a daily basis!
Hi there! I just got this flashed, and I need to know if it's safe to do an OTA update over your ROM.
Thanks a ton!
ZTE 982
Hi there good morning I have a big question, I have the ZTE z982 from MetroPCS I went ahead and rooted and installed TWRP on it. Now I was having some issues trying to flash a custom rom Slimrom to be exact (https://forum.xda-developers.com/zte-zmax/development/slimrom-5-0-2-t3161888) but I kept getting errors about legacy property? So something along those lines. Well I then read somewhere that it could be because of TWRP being outdated. I took it upon myself to look and find an .IMG witch I then flashed and now am stuck with a sorta bootloop flashes on but the screen goes black. Any suggestions? I would really appreciate it.
how did you get past fastboot. my z982 cant find device there?
soLo1Blue said:
Hi there good morning I have a big question, I have the ZTE z982 from MetroPCS I went ahead and rooted and installed TWRP on it. Now I was having some issues trying to flash a custom rom Slimrom to be exact (https://forum.xda-developers.com/zte-zmax/development/slimrom-5-0-2-t3161888) but I kept getting errors about legacy property? So something along those lines. Well I then read somewhere that it could be because of TWRP being outdated. I took it upon myself to look and find an .IMG witch I then flashed and now am stuck with a sorta bootloop flashes on but the screen goes black. Any suggestions? I would really appreciate it.
Click to expand...
Click to collapse
No matter what I do I cannot get this vile little phone to root. It is located in adb but fastboot just isnt there or doesnt' want to find it. I have tried every dang driver you can think of and still nothing in fastboot. I must know its driving me crazy. I have got to where i absolutely hate this phone!
works on z981 ??
Original thread and download can be found here:
http://forum.xda-developers.com/showthread.php?t=2318514
The zip file contains folders and files that will be injected to the framework-res.apk. So please make a backup before flashing the zip file. I have not tested it on Lollipop but works on my phone with original Kitkat firmware ANK3. I flashed it using CWM. This would probably work on most Samsung latest devices but not totally sure. You can test it on your device after doing a BACKUP.
HIT the THANKS button if you like my post. Have a good flashing everyone.
Samsung Galaxy Tab A 7.0 LTE/WIFI 2016 TINKER EDITION ROM (DEOXED/ROOT/XPOSED)
============================================
Update 01/04/2017
-----------------------
Tinker Edition V5.1 is now out.
* Re-added Samsung stock camera and gallery
* revert back to stock vold to fix issues people are having with micro sdcards
Now available for the SM-T285, SM-T280 to follow
Update 10/29/2016
------------------------
TWRP for the SM-T285 here
Early Build of TWRP for the T285 (see post by @ashyx will update this if an official version is released. The T280 version should be available not far behind I believe
Update 09/21/2016
-----------------------
V5 now out (root, deodexed, xposed) for the SM-T280/T285, still working on the SM-T280
Update 09/20/2016
------------------------
Turns out this device is not as locked as we all thought it too be. See thread below for my ordeal and more details:
http://forum.xda-developers.com/galaxy-tab-a/help/resources-samsung-galaxy-tab-7-0-2016-t3431022
Modifications:
===========
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Busybox
* Hijacked Vold (using CM 12.1 sources) to run shell scripts stored in /data/scripts/vold.init
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
* Dolby Atmos mod (09/11/2016) (thanks to @Nando14sunny)
* Deodexed/Xposed (09/13/2016) (thanks to @wanam and @rovo89)
* soft linked /etc/hosts to /data/scripts/hosts and can be edited using adb shell (09/13/2016) (thanks to @venomrat)
* V5: root chainfire's SuperSu 2.78 (09/21/2016) (thanks to @Chainfire)
* stock boot animation
Special thanks also to @ashyx for initially taking a look at this device , I haven't given up on rooting this device yet.
Special thanks to @klemen241 for helping me try out the SM-T280 build
Haven't done extensive testing on Xposed modules, but the pokemon go iv mod/hacked worked and that was good enough for me (Before pokemon Go was patched). If you use this ROM feedback is highly appreciated
NOTES: To be safe, perform a cache wipe using recovery. I didn't need to do this personally but I haven't tested all use cases
NOTES: Since this rom is deodexed, the first boot will take quite a while, so please be patient .
NOTES: if you are coming from V2 and are using the mount_ext4 apps2sd scripts please update it for additional support for the V3 ROM HERE:
https://github.com/jedld/smt285_data_scripts
NOTES: (09/13/2016) Unfortunately, the V3 build fails the Google SafetyNet check, will be a problem if you play Pokemon Go
Other Notes: Removed support for zygote.init scripts in V3 as I am now using the app_process32_xposed binary, will work to get this back soon. I haven't had a need for zygote scripts though. The vold.init scripts shoud still work as before if you are using the apps2sd script
Installation Instructions:
Odin or Heimdall Required. I you are coming from the Stock Rom please wipe/factory reset to be sure. If you are upgrading from V1 or V2 you are not required to wipe unless there are problems. If you are upgrading to V3 cache wipe is recommended using recovery.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Choose the appropriate download for the model (wifi only T280/ lte T285) that you have:
WIFI ONLY Download (SM-T280)
==========================
Link (V5 Deodexed, Rooted and Xposed):
https://mega.nz/#!0Jdg0a4D!XWLES1BwCPrkBlUzqNhRfRi_91LOdawYHydQ_scV2dI
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
LTE Version Downloads (SM-T285)
===========================
Link (V5.1 Deodexed, Rooted and Xposed):
https://mega.nz/#!ZFFTFKYZ!NAeajNUjIgYI7zOslpWoJ2AeJ-NCKG0Ut8Buz_6eCgU
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
Link (Original V2 odexed version):
Download from Mega (V2 09/11/2016)
If you have suggestions, send me a PM.
Other Notes (So people don't have to ask):
* I've tried to run superuser daemonsu, but unfortunately the sepolicy scopes for vold and zygote are too narrow in this device for supersu to use despite being root. In theory a version of daemonsu can be made specifically to run on this device with a somewhat castrated functionality though I don't have access to the source code to figure it out. Navigating the sepolicy landmine is hard.
WIFI ISSUES
=========
There are reports of wifi problems with the latest build due to wrong permissions with dhcp hooks, if so you can do the following (big thanks to @_mone):
Using adb shell:
Code:
su
mount -o rw,remount,rw /system
chmod 755 /system/etc/dhcpcd/dhcpcd-run-hooks
mount -o ro,remount,ro /system
/system is readonly by default, which is why you need the remount commands. Reboot your device after just to make sure.
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
venomrat said:
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
Click to expand...
Click to collapse
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
jedld said:
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
Click to expand...
Click to collapse
Thanks for your hard work. It's a pity this device is not as popular as their other models or more people would have already signed the petition.
I regret not doing more research before buying this tablet.
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Nando14sunny said:
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Click to expand...
Click to collapse
we could try, could you point me to a rom that has the specified libraries for Dolby?
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Nando14sunny said:
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Click to expand...
Click to collapse
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
jedld said:
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
Click to expand...
Click to collapse
Wow thank you! I'll test it right now
Edit:
It works like a charm! You really improved my devie with it!
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
venomrat said:
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
Click to expand...
Click to collapse
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
jedld said:
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
Click to expand...
Click to collapse
No hurry. I can wait. What you are doing now is more important. :good:
venomrat said:
No hurry. I can wait. What you are doing now is more important. :good:
Click to expand...
Click to collapse
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
corzradio said:
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
Click to expand...
Click to collapse
May need to modify build.prop, you may do this yourself here:
http://forum.xda-developers.com/galaxy-tab-a/how-to/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
Also there may be an Xposed framework modules that do that. Not sure though since I'm ok with the stock DPI
jedld said:
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
Click to expand...
Click to collapse
Thanks. Will need to find time to re-flash this weekend.
Regarding xposed have you actually tested any other modules that need root?
I already built a rom with xposed but it was all but useless because pretty much all the modules I use need root.
most of those I tried don't need root so far (youtube adaway, pokemon go iv). Haven't tried those that need root but I suppose those wouldn't work.
I use app settings and it works for dpi change, and you are welcome. I am glad to test stuff, its fun haha. If anyone has questions about t280 you can ask me
how can i boost the volume? since its not rooted i cant find the mixer.xml
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.