Related
HI, I am using rom 101.c.0.370 with rooted, I got 2 question,
1) I installed Rom Manager, but not able to reboot with recovery mode, does my firmware version be able to support or not?
2) I tried to installed S-note V-12 Link, as I am not able to installed the rom so I try copy all the file in folder system with permission, in lib I have overwrite the file, but I can't see any icon/shortcut for snote or other app from s-app, by app "/system/app mover", I can see those apps is in system but how am I able to launch the apps?
as far as i know there's only one way to get root and recovery on the 370 firmware at the moment there is a thread in the android development forum i cant remember the name of it but ill update this post when i find it.
Edit: This is the forum post [ROM][CWM][Recovery][Pre-Rooted]Tablet Z Stock 10.1.C.0.370 -Reboot FIX Included - http://forum.xda-developers.com/showthread.php?t=2330110
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 ??
I have been relentlessly trying to fix the drivers that couldn't install, even when I installed it. So I have finally found a fix tinkering with my system folder. I will be posting a guide + the fix so scroll down to the appropriate section! I understand that other people posted the guide but I wanted to share my own way of doing it
Pre requisite s:
Busy box
Root (non systemless because it didn't work for me on systemless)
={ GUIDE }=
1) Install Viper4Android either from other posts or from the download links below which is a flashable zip with a dark theme
2) Download SELinuxEnforcing from the download link below and install it, THERE WILL BE A WARNING FOR SOME THAY IT CAN HARM THE SYSTEM, PRESS READ MORE OR SIMILAR AND PRESS INSTALL ANYWAY. THE APP WAS JUST REMOVED FROM PLAY STORE AND THIS HAS NO HARM THAT IT CAN INFLICT!
3)Go to SELinuxEnforcing and accept root permission then press on the permissive button.
4) Download root browser from the Play Store created by JRummy.
5) Alright ready for the fun part, reboot into Recovery mode TWRP
Decrypt your device( if you have it encrypted)
6) Press install and locate to the area that this v4a zip is located ( mostly /sdcard/downloads)
6) Press and install the zip
Reboot into device
7) Go into viper4android and install the driver
8) Reboot and after if you DO not see any installed driver, move on to the FIX section!
_——_
Pre requisites[FIX] + pre installed by you :
Busybox[GUIDE]
Root[GUIDE]
SELinuxEnforcing[GUIDE]
Root Browser
={ FIX }=
Got Root? Anyway, looks like its still saying Driver not Installed even though you installed it.
1) Now there's a very easy fix. Given that you have root browser following on from the guide or sliding through to this section taking a look at the pre requisites, go into it.
2) You will now be welcomed with a lot of folders. Locate to
system then vendor then etc then you will see audio_effects.conf that is interrupting the drivers.
3) What you want to do now is to long press it, which will pop up with various options, press rename and change .conf to .bak which will disable the configuration script but keeping it backed up for if anything that goes wrong.
4) Reboot and voila! Your drivers should say neon activated and etc.
PRESS THANKS IF IT HELPED AND WORKED SO THAT OTHER PEOPLE CAN SEE ITS VALIDITY
Read here too. http://forum.xda-developers.com/showthread.php?t=2952137 I've been using Viper Atmos for a week or so now ever since the op made it work perfect with Nexus 6p.
Sent from San Antonio Tx- Nexus 6p
If you have a S7 Edge, you have to use this thread.
First of all, the credits of the second option from the tutorial below goes to @lirex, he is the one who created this tutorial in the S6 Active forum, I only edited it for the S7. This is only for the AT&T model of the S7, not for international or other models, don't try it cause you might brick your phone! This update hasn't been tested yet, so if you don't like bugs or if you r phone is important for work, don't update to an unreleased version, as there may be some bugs in it, which can cause sudden reboots or battery drains.
Second, English is not my native language. So if I made a mistake, please let me know.
Keep in mind you are updating your phone to an unreleased build. I can't say whether it's stable or not, because the update file has just been found. New update files will be released every now and then, but it is not possible to update from an unreleased build to another unreleased build. Once you're on Nougat and another update appears online, you have to flash back to PI2 and update it again.
If the update or sideload ends up failing, flashing the stock firmware with Odin will resolve this. But just be sure to follow all the instructions, AND ALWAYS BACKUP YOUR PHONE. Your phone will factory reset after the update.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
IMPORTANT: Flashing WILL WIPE EVERYTHING SO BACKUP FIRST. (I'm not responsible for anything that goes wrong, but this worked for everybody so far). You can use this regardless of your firmware version. Just make sure to sideload the proper file for your current firmware!
Prerequisites: Before you proceed prepare these necessary things as follows so you will not screw-up your phone:
• Create a back-up with Smart Switch of all your personal data, like: Contacts, Messages, Applications, Pictures and Videos, so that you will not lost it just in-case something might went wrong after the update.
• Make sure that your Galaxy S7 battery is fully charged to ensure stability and to get rid of power failure issues while updating.
• TURN OFF the Reactivation Lock - Go to Settings > PERSONAL > Lock screen and security > Find My Mobile and log in your Samsung Account. Then uncheck the Turn Reactivation lock on. This is only needed if you already turned-it-ON, from which you cannot modify the system when it's turned-ON.
• If you disabled some system bloatware manually or with a third party software, make sure everything is enabled again.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Option 1: Flash via "Apply update from SD card".
1.) Download the firmware packages from the official AT&T Update server to your PC:
To make it easier for everyone, all update files have been uploaded to Google Drive, thanks @siacono.
v2 (G930AUCU2APD1) to v3 (G930AUCS2APE1) update file
v3 (G930AUCS2APE1) to v4 (G930AUCS2APF21) update file
v4 (G930AUCS2APF2) to v5 (G930AUCU2APG1) update file
v5 (G930AUCU2APG1) to v6 (G930AUCS2APH1) update file
v6 (G930AUCS2APH1) to v7 (G930AUCS4API2) update file
v7 (G930AUCS4APK1) to unreleased (G930AUCU4BQA4) update file
Somehow I can't get the links of the v7 (G930AUCS4API2) to v8 (G930AUCS4APJ4) and the v8 (G930AUCS4APJ4) to v9 (G930AUCS4APK1) updates, so you have to update those OTA.
If you prefer downloading them from AT&T's servers, here are the original links: (NOT working anymore)
** You will see SERVER ERROR 403 or ERROR 404: NOT FOUND, that's because you have to use a download manager program like this (it's free), otherwise you won't be able to download those files. **
-> v2 (G930AUCU2APD1) to v3 (G930AUCS2APE1) update file
-> v3 (G930AUCS2APE1) to v4 (G930AUCS2APF21) update file
-> v4 (G930AUCS2APF2) to v5 (G930AUCU2APG1) update file
-> v5 (G930AUCU2APG1) to v6 (G930AUCS2APH1) update file
-> v6 (G930AUCS2APH1) to v7 (G930AUCS4API2) update file
-> v7 (G930AUCS4APK1) to unreleased (G930AUCU4BQA4) update file
Somehow I can't get the links of the v7 (G930AUCS4API2) to v8 (G930AUCS4APJ4) and the v8 (G930AUCS4APJ4) to v9 (G930AUCS4APK1) updates, so you have to update those OTA.
2.) After you download the right update, right mouse click on it, select "Rename" and add ".zip" at the end of it. Then, put it on the root of the SD card. If you have an empty one, use it, just to prevent the SD card will be formatted too.
3.) Reboot the phone into recovery. Turn it off and wait a minute for it to completely turn off. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
4.) Select "Apply update from SD card". You can scroll using the volume buttons and select using the power button.
5.) Wait patiently. The firmware files over 1 GB can take over 30-40 minutes. It's okay.
6.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done. Now repeat steps 1 to 5 until you're on the latest firmware (Android Nougat, unreleased version).
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Option 2: Flash via "Apply update from ADB".
If the first method somehow doesn't work for you, you can try it using your computer. Prepare a Windows PC, sometimes it doesn't work on a Mac.
1.) Download the firmware packages from the official AT&T Update server to your PC:
To make it easier for everyone, all update files have been uploaded to Google Drive, thanks @siacono.
v2 (G930AUCU2APD1) to v3 (G930AUCS2APE1) update file
v3 (G930AUCS2APE1) to v4 (G930AUCS2APF21) update file
v4 (G930AUCS2APF2) to v5 (G930AUCU2APG1) update file
v5 (G930AUCU2APG1) to v6 (G930AUCS2APH1) update file
v6 (G930AUCS2APH1) to v7 (G930AUCS4API2) update file
v7 (G930AUCS4APK1) to unreleased (G930AUCU4BQA4) update file
Somehow I can't get the links of the v7 (G930AUCS4API2) to v8 (G930AUCS4APJ4) and the v8 (G930AUCS4APJ4) to v9 (G930AUCS4APK1) updates, so you have to update those OTA.
If you prefer downloading them from AT&T's servers, here are the original links: (NOT working anymore)
** You will see SERVER ERROR 403 or ERROR 404: NOT FOUND, that's because you have to use a download manager program like this (it's free), otherwise you won't be able to download those files. **
-> v2 (G930AUCU2APD1) to v3 (G930AUCS2APE1) update file
-> v3 (G930AUCS2APE1) to v4 (G930AUCS2APF21) update file
-> v4 (G930AUCS2APF2) to v5 (G930AUCU2APG1) update file
-> v5 (G930AUCU2APG1) to v6 (G930AUCS2APH1) update file
-> v6 (G930AUCS2APH1) to v7 (G930AUCS4API2) update file
-> v7 (G930AUCS4APK1) to unreleased (G930AUCU4BQA4) update file
Somehow I can't get the links of the v7 (G930AUCS4API2) to v8 (G930AUCS4APJ4) and the v8 (G930AUCS4APJ4) to v9 (G930AUCS4APK1) updates, so you have to update those OTA.
2.) Reboot the phone into recovery. Turn it off and wait a minute for it to completely turn off. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
3.) Select "Apply update from ADB". You can scroll using the volume buttons and select using the power button.
4.) Make sure you have ADB and the proper drivers installed on your PC:
-> ADB & Drivers installer
5.) If you're on firmware v7 and you're going for the Nougat update the update file is called "SS-G930AUCS4APK1-to-U4BQA4-UP". Put it in the ADB folder. You can rename it to anything easy to remember like "FIRMWARE".
6.) In the ADB folder, hold SHIFT + right mouse click and choose "Open command window here". Then type the command "adb sideload FIRMWARE" (where FIRMWARE is how you named your file). If you have any problems check the Troubleshooting Tutorial at the end of the post.
7.) Wait patiently. The firmware files over 1 GB can take over 30-40 minutes. It's okay.
8.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done. Now repeat steps 1 to 5 until you're on the latest firmware (Android Nougat, unreleased version).
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you get any errors, please take a look at this forum and scroll down to the Troubleshooting Tutorial, most of the problems are being explained here.
If you still get an error message, paste it in the comments and we'll try to find a resolution .
Jimmy,
Just a quick added piece of info that will make this much easier for most everyone. There doesn't seem to be any reason to mess around with sideloading the file using ADB. I tried it on my S7 Active and screwed it up and had to start all over. Dogg94 said he had issues sideloading as well and all he did was take the file with the firmware and changed the name to have a zip extension. So I changed my file to Firmware.zip and then copied it to my SD Card and then booted into recovery and selected Update from SD Card and selected the Firmware.zip file and it worked perfectly and is currently finishing up. Much much easier process.
1st off, THANKS a ton getting this together, excellent work!!!
Couple questions
This thread is in the "regular" S7, not the Edge thread. Does this make a difference? Just trying making sure there isnt confusion out there
Step 6 - If you're on firmware v8? How do you identify that?
Blackberrynomore said:
Jimmy,
Just a quick added piece of info that will make this much easier for most everyone. There doesn't seem to be any reason to mess around with sideloading the file using ADB. I tried it on my S7 Active and screwed it up and had to start all over. Dogg94 said he had issues sideloading as well and all he did was take the file with the firmware and changed the name to have a zip extension. So I changed my file to Firmware.zip and then copied it to my SD Card and then booted into recovery and selected Update from SD Card and selected the Firmware.zip file and it worked perfectly and is currently finishing up. Much much easier process.
Click to expand...
Click to collapse
Agree my friend did it this way, i haven't yet since i am not home yet, but does work, my friend renamed to update.zip
Running On Samsung Galaxy S7 Edge G935A Wicked Venom
i wonder if theres any way to get the u nougat early!
Venom0642 said:
Agree my friend did it this way, i haven't yet since i am not home yet, but does work, my friend renamed to update.zip
Running On Samsung Galaxy S7 Edge G935A Wicked Venom
Click to expand...
Click to collapse
If it's confirmed it can be updated that way, I will rewrite the tutorial. Then the sideloading way will be for people without a SD-card.
kangi26 said:
1st off, THANKS a ton getting this together, excellent work!!!
Couple questions
This thread is in the "regular" S7, not the Edge thread. Does this make a difference? Just trying making sure there isnt confusion out there
Step 6 - If you're on firmware v8? How do you identify that?
Click to expand...
Click to collapse
If you're on FW ending in APK1
Can anyone download and host? In case they block the url?
Sent from my SM-G935U using Tapatalk
Blackberrynomore said:
Jimmy,
Just a quick added piece of info that will make this much easier for most everyone. There doesn't seem to be any reason to mess around with sideloading the file using ADB. I tried it on my S7 Active and screwed it up and had to start all over. Dogg94 said he had issues sideloading as well and all he did was take the file with the firmware and changed the name to have a zip extension. So I changed my file to Firmware.zip and then copied it to my SD Card and then booted into recovery and selected Update from SD Card and selected the Firmware.zip file and it worked perfectly and is currently finishing up. Much much easier process.
Click to expand...
Click to collapse
Please let me know if it works without issues. Also, tell me if it factory resets itself after updating from the SD-card.
Jimmyvb98 said:
If it's confirmed it can be updated that way, I will rewrite the tutorial. Then the sideloading way will be for people without a SD-card.
Click to expand...
Click to collapse
Should Pm a MOD to move Thread to AT&T S7 Edge, just a suggestion!
Venom0642 said:
Should Pm a MOD to move Thread to AT&T S7 Edge, just a suggestion!
Click to expand...
Click to collapse
I just found out I placed it in the wrong forum. So this thread will be inactive until the regular S7's update URL has been found, I'll make an annoucment in this thread once it is found, so this thread will be of use later. I'll make a new one in the S7 Edge forum right now.
Jimmyvb98 said:
If it's confirmed it can be updated that way, I will rewrite the tutorial. Then the sideloading way will be for people without a SD-card.
Click to expand...
Click to collapse
Well all I can tell you is my phone is now sporting Android 7.0 after doing the copy paste Firmware.zip process I outlined from Dogg94. So I would say it works fine. He has had his running this for several days he said without issue.
Jimmyvb98 said:
I just found out I placed it in the wrong forum. So this thread will be inactive until the regular S7's update URL has been found, I'll make an annoucment in this thread once it is found, so this thread will be of use later. I'll make a new one in the S7 Edge forum right now.
Click to expand...
Click to collapse
Ok Uploading the AT&T S7 Edge Nougat QA4 to Android File Host will post it once it's uploaded to the new thread mate Thanks!
New thread: https://forum.xda-developers.com/att-s7-edge/development/howto-update-galaxy-s7-edge-firmware-to-t3541329
Venom0642 said:
Ok Uploading the AT&T S7 Edge Nougat QA4 to Android File Host will post it once it's uploaded to the new thread mate Thanks!
Click to expand...
Click to collapse
Thank you!
Sent from my SM-G935U using Tapatalk
Does anyone know how to change the title?
Jimmyvb98 said:
Does anyone know how to change the title?
Click to expand...
Click to collapse
Hit Edit then Hit Advanced and you should be able to change title mate!
Venom0642 said:
Hit Edit then Hit Advanced and you should be able to change title mate!
Click to expand...
Click to collapse
Thank you!
Trying it out now - Thanks for finding the link!
If I use Odin to go back after updating to Nougat, will it trip Knox, making Samsung pay unusable?
Nevermind solved.
Sent from my SAMSUNG-SM-G930A using Tapatalk
I posted this a while ago in the [sm-a320fl][7.0][firmware] thread. Now in a new thread, so everybody will find it.
I'm not responsible for any damage. My phone was not branded.
This tutorial is only for SM-A320FL, also known as Galaxy A3!
Make sure you read the whole tutorial before doing anything.
Make a backup of your data. You need to make a factory reset!
Also read the additional information in the separated threads! Knox will be tripped after that, so you can't use it any more. And no more Warranty!
You can find a Android 7 version with the latest security patch with google or just use the linked one. Make sure the CSC is correct for your country/language.
1. Download the following stuff:
Android 7 A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip thx to tys0n
Latest Odin3
twrp_3.1.1-1_sm-a320f_11917 thx to ashyx
[*]Boot image patch no-verity-no-encrypt_ashyx thx to ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] thx to DVDandroid
Xposed Installer 3.1.5 thx to rovo89
Magisk thx to topjohnwu
2. Flash Android 7 via Odin. There are enough tutorials on how to do that. Basicly unzip the Android 7 zip file and assign the AP_... file to the AP slot, the BL_... file to the BL slot and so on.
2.a Unlock OEM: Settings -> Developer Options -> OEM unlocking More Information
3. Flash TWRP via Odin; Thread with additional informations
Instructions summary:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst holding POWER + HOME.
You should now see TWRP recovery.
Click to expand...
Click to collapse
4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System.
4. Format Data in TWRP. To do that click on Wipe -> Format Data in TWRP. After that all your data is lost! Reboot to System.
5. Copy the Xposed Installer APK file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP.
6. Copy the Magisk ZIP file to your SD card and install it via TWRP. Reboot to System.
7. Open the Magisk Manager and enable root access via SuperUser within the Manager.
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
8. Open Xposed Installer and install the latest Xposed framework. Follow the steps displayed.
9. Now you should have root access, Magisk and Xposed up and running.
Quotes and additional information:
[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017) by ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] by DVDandroid
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
[*][2017.9.9][Magisk][SDK 21-25] Xposed v87.3 - Universal Systemless Compatibility by topjohnwu
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo by rovo89
---------- Post added at 11:22 AM ---------- Previous post was at 11:07 AM ----------
khanvict90 said:
Any body else have lag with the patern unlock screen ?
Click to expand...
Click to collapse
I had the same problem and it drove me crazy. It appeared every time after I rooted my phone with the old "flash the SuperUser.zip via TWRP" method.
After I rooted my phone via Magisk (Tutorial above), there is no more annoying lag. :good:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
simple_s said:
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
Click to expand...
Click to collapse
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
Please read the tutorial! You need SDK 24 if you are on Android 7.
Pat750 said:
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
Click to expand...
Click to collapse
I didn't try that. Maybe it will work.
Pat750 said:
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
Click to expand...
Click to collapse
In my opinion it will do the same thing and get stuck in a boot loop. Didn't try it.
simple_s said:
Please read the tutorial! You need SDK 24 if you are on Android 7.
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
y2klol said:
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
ii_Troy said:
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
Click to expand...
Click to collapse
I had the same issue - turns out I missed the formatting step in TWRP.
Before flashing no verity, go to Wipe > Format Data Partition (I cant remember the exact wording)
simple_s said:
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Click to expand...
Click to collapse
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
y2klol said:
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
Click to expand...
Click to collapse
I only tried this tutorial on an A3. Especially the firmware and the TWRP are specialised for the A3. I think the A5 has also quite a different hardware.
Maybe someone in this thread can help you. They root A5:
A5 Root
All works great on my Galaxy A320FL, thanks !!
atlantix1 said:
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Click to expand...
Click to collapse
its because you fllashed no verify no encrypt this zip should only be flash when you root with super su ...
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Hi there.
I found something interesting by accident.
Maybe it is not necessary to install the Xposed Framework via Magisk.
Just use the Magisk Manager as a Super SU replacement and install the Xposed Framework (latest version is 89) directly via the new Xposed Installer (latest version is 3.1.5).
Official Xposed by rovo89
It seems that the phone is running a little bit smoother.
Also it seems that the boot patch is causing some problems.
Maybe the whole tutorial needs to be overlooked. But unfortunately I have now time right now.
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can write a new and better one.
simple_s said:
Sorry to hear that. Maybe you can write a new and better one.
Click to expand...
Click to collapse
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry I have to replay again. I had just a few minutes this morning.
At point 5 I clearly wrote that you have to install the apk!
At point 8 it should be clear that you have to follow the instructions from Xposed. Everybody knows that and has nothing to do with the basic tutorial.
nekos95 said:
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
Click to expand...
Click to collapse
Xposed, Root and what not is nothing for beginners. I clearly mentioned that you have to read a lot of stuff. This is not for beginners. Instead of whining and telling me how to do stuff, just write your own thread. Link everything and mention resources. Not everything in this world is baby save. You have to educate yourself!
I overlooked the whole tutorial. I think it is better now and baby save.
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
BananaOctopus said:
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
Click to expand...
Click to collapse
Thank you for your help. I updated my phone to the newest Android 7 version today. I had the same problem and solved it with your method. So I implemented this step into the tutorial.