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 ??
Related
[PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
So from there, download Dual Boot Switcher app and DualBootUtility zip.
And loki-doki from here.
The unzip whatever ROM you're wanting to dual boot. Go to META-INF/com/google/android/updater-script and edit the updater-script manually. The instructions for that are in the post up top I linked to.
Patch the boot.img with the automatic patcher tool, patch-ramdisk.sh. It will create boot_dualboot.img. I just renamed that to boot.img.
Then I put the new boot.img back into the ROM folder.
Create a file named dualboot.sh, and put this in there dualboot.sh.
Put this file in the base of the ROM folder, the same place where the boot.img is.
Zip this all up. the gapps zip I just patched automatically with the patcher app, also in the downloads from the first link.
Instructions for dual booting
Before doing anything, download the Dual Boot Switcher app and the DualBootUtilities.zip from the download section below.
Follow these steps.
chenxiaolong said:
Before doing anything, download the Dual Boot Switcher app and the DualBootUtilities.zip from the download section below.
Note: Only the secondary ROM and other zips that should be installed for the secondary ROM need to be patched. Nothing needs to be done for the primary ROM.
Boot into your primary ROM and install the Dual Boot Switcher app
Open the app and set the current kernel as the primary kernel (screenshot)
If the primary ROM is TouchWiz, you will need to remove some bloatware. Otherwise, two ROMs won't be able to fit on the /system partition. You can also convert some system apps to user apps with this tool: https://play.google.com/store/apps/details?id=de.j4velin.systemappmover&hl=en
Patch the ROM (see the "How to use the patcher" section)
Reboot into recovery
Flash the patched zip files.
Reboot
Install the Dual Boot Switcher app again in the secondary ROM. If you have a locked bootloader, set the kernel for the secondary ROM (just in case).
Enjoy!
Click to expand...
Click to collapse
Then just flash your ROM.zip, gapps.zip, and loki-doki.zip. Don't wipe anything. Just reboot. It should boot into your second ROM. Install the ROM switcher app again, set the current kernel as the secondary kernel.
If you want to boot back into your primary ROM, just pick it in the ROM switcher app.
Note: When manually patching, you can go off the examples, and it makes it easier, BUT be careful because not all updater-scripts are the same. I copied off of aokp.dualboot.patch and it kept ruining my ROM. I could boot into AOKP all day long, but if I tried to boot into HyperDrive, it'd just stick at the Samsung splash screen. I looked over my patched updater-script and there was another line with:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
that I missed. So, just be sure to make a nandroid backup.
I'm including a copy of the AOKP updater-script that I edited. It's for the official 10-18 nightly. I tried to make a patch info file to send to the guy who came up this awesome app/mod, but for some reason I'm just inept in this area. I suck at how-to's as well, but I don't see anyone else trying to explain this for our phone
Since you said you had to do some steps, care to share them for users in general? Might save your inbox from getting slammed.
Well I had to remove/add a few lines to the updater script, which I kept messing up because I seem to get deslycix when reading code at 2 am.
Then the boot.img needs to be patched, but there's a tool for that in the OP of the thread I linked. It will create a file called boot_dualboot.img. I renamed that to just boot.img, and removed the original from the zip.
Then I put dualboot.sh at the base of the ROM zip.
Patched gapps automatically with the patcher tool.
Flashed patched ROM, patched gapps, and loki-doki. Just Google loki-doki, it's the first result.
Patching the boot.img removes loki. Flashing loki-doki will loki the kernel again.
Edit: I'll do up a better How to later. I'm at school right now though.
Sent from your mom's smartphone
Updated OP. If you have any problems, just post and I'll help where I can. I'm no expert, I'm just good at following instructions.
Hey, thanks for doing this thread. How do you remove dual booting when you want your phone back to normal again? haha
Restore a nandroid. Or do a clean flash from recovery and you'll be on one ROM.
Sent from your mom's smartphone
If anyone can do a precise and accurate video tutorial for this, that would be awesome! I'm more of a visual learner.
That is way beyond my level of knowledge lol.
Sent from your mom's smartphone
thats pretty ill. i personally do not see a reason to do it, but i like that its possible, LOL
As you may know, there's a well-known Android 5.0 Lollipop issue - Memory leak.
Lots of community built ROMs out there has already applied the "supposed" fix.
Why not our LG G Watch?
For such devices which has a very long uptime, memory leaks are critical.
This "fix" should benefit to a "stabler" LG G Watch
Just throw the attached "services.jar" on /system/framework and reboot.
It'll rebuild all of the ART caches, so the initial boot after applying may take up to 15 minutes.
<Tested on Android 5.0.2 Lollipop build>
V2 - Support for Android 5.0.2 Lollipop build
Memory leak patches taken from
https://github.com/temasek/android_frameworks_base/commits/cm-12.0/services/core/java/com/android/server/display
Thanks to @temasek !!
Hello arter97. Thanks for your support. Could you please be so kind to tell us how to do it?
For your information, I am currently on Gohma 2.3 and to tell you the truth, with the wear mini launcher running on the background, the g watch sometimes feels unresponsive.
Thanks again for your patience
Does this require root
Hey is there anyway that you might be able to make a flashable zip so we can install it with twrp? Please
ewalk4866 said:
Hey is there anyway that you might be able to make a flashable zip so we can install it with twrp? Please
Click to expand...
Click to collapse
Let me see what I can do. I tried adb pushing the file into /system/framework/ myself, but kept running into read only issues.
Apoplectic1 said:
Let me see what I can do. I tried adb pushing the file into /system/framework/ myself, but kept running into read only issues.
Click to expand...
Click to collapse
Make it with TWRP also Recovery
sallto said:
Make it with TWRP also Recovery
Click to expand...
Click to collapse
And here we go.
https://drive.google.com/file/d/0B7r1gfrm1vXoYVJzVEdkYjNEUTg/view?usp=sharing
Great thank you
Can someone please post instructions for getting the zip file on to the watch so that it can flashed by TWRP. Or how to move the services.jar to the proper location on the watch with correct permissions. I have already searched the threads, however all I can find are how to sideload apps not move files.
*Update* Finally found what I needed, so here it is.
adb push services.zip /sdcard/services.zip
Moguledyouth said:
Can someone please post instructions for getting the zip file on to the watch so that it can flashed by TWRP. Or how to move the services.jar to the proper location on the watch with correct permissions. I have already searched the threads, however all I can find are how to sideload apps not move files.
*Update* Finally found what I needed, so here it is.
adb push services.zip /sdcard/services.zip
Click to expand...
Click to collapse
That's the one, though I usually do adb push services.zip /sdcard/Download/services.zip, but it makes no difference whether it's in the sdcard, or a subdirectory.
Great job guys, my watch is finally usable again, thanks a lot @arter97 for making this and @Apoplectic1 for making it a zip so it is easier to apply the mod.
Do we still need this file if we're on 5.0.2?
arter97 said:
As you may know, there's a well-known Android 5.0 Lollipop issue - Memory leak.
Lots of community built ROMs out there has already applied the "supposed" fix.
Why not our LG G Watch?
For such devices which has a very long uptime, memory leaks are critical.
This "fix" should benefit to a "stabler" LG G Watch
Just throw the attached "services.jar" on /system/framework and reboot.
It'll rebuild all of the ART caches, so the initial boot after applying may take up to 15 minutes.
<Tested on Android 5.0.1 Lollipop LWX48P build>
Memory leak patches taken from
https://github.com/temasek/android_frameworks_base/commits/cm-12.0/services/core/java/com/android/server/display
Thanks to @temasek !!
Click to expand...
Click to collapse
@arter97 is this fix also available for Nexus 5? I've used this - isn't it enough?
Thanks
Thank you! I'm waiting for an updated Ghoma release as I didn't see any sense in returning to stock to do the ota update, while it works its very smooth for me, in the mean time we'll see if this solves my crash about every-other day issue.
FYI if you're having trouble pushing the file directly to /system/framework I'd recommend placing it somewhere that doesn't require root privs to write to, such as /sdcard/Download and then doing an adb shell, su, remount system, and copying it from there into /system/framework. Make sure you back up your current services.jar in case something goes wonky.
--edit-- ERROR: caused watch to fall into a completely unresponsive state, though the time was still updating. Had to connect to usb and force a reboot with adb to break it out of whatever happened. Don't have time to diagnose further right now, reverted to stock services.jar for the moment. I'm not saying this is a general issue with this mod yet, just that it didn't work on my watch.
New V2 for 5.0.2 is now up.
Im getting "read only file system" or something like that. Also cant get it to work with su commands. I'd appreciate if someone will make flashable zip for 5.0.2 update (im currently on stock recovery, but it can be changed easily with g watch tools)
Actually i made flashable zip myself (not sure if correct, but it worked). But considering fact that first "services.jar" which was uploaded for older version should replace file by same name in system/framework, shouldnt newest version be called "services" also? Now i ended up having in my framework folder "services_v2.jar" AND "services.jar". Should i rename this one with "v2"? Or is it intended to leave both of them?
Lasiu said:
Actually i made flashable zip myself (not sure if correct, but it worked). But considering fact that first "services.jar" which was uploaded for older version should replace file by same name in system/framework, shouldnt newest version be called "services" also? Now i ended up having in my framework folder "services_v2.jar" AND "services.jar". Should i rename this one with "v2"? Or is it intended to leave both of them?
Click to expand...
Click to collapse
It's only services.jar. Rename the new one.
Thanks @arter97! Looking forward to a more stable 5.0.2!
buru898 said:
It's only services.jar. Rename the new one.
Click to expand...
Click to collapse
Thats what i did, working great, thanks! Do any of you by any chance know how to stop ota notification from appearing? (i tried going back to 5.0.1 after installing 5.0.2 but this notification appeared again )
I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
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.