Related
Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
I have another question, sorry but I don't want to make another thread.
SuperSU has an option "Survival Mode" that says that we must disable it before Nandroid Backup, what happends if I forgot to disable it ?
Thanks for your help, sorry if it was already asked (search results didn't help me).
For the installation paths, i dont really think it matters whether you put it in either of the above.
About survival mode, again i say it does not really matter whether you disable it or not. Your nandroid backup will go smooth.
Some developer can explain it to you in detail if any of the above really matters.
Sent from my LG-E730 using Tapatalk 2
Ok, thanks.
If anyone has more infos your welcome.
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
qwerty12 said:
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
Click to expand...
Click to collapse
Neither in htc wildfire nor in lg optimus sol disabling the survival is important. I have flashed and restored a hundred times but nothing happened..
Sent from my LG-E730 using Tapatalk 2
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
CNK80Q3MX said:
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
Click to expand...
Click to collapse
I am having the same question.. I have viewed each of the 4 directories using a root file explorer and noticed /bin /xbin and su/bin su/xbin all contain ifferent files so im not sure if doing that helped me o confused me more. Lol but im not sure it matters ,well im sure it makes differences but I cant find a difference other than some symlinks may be rewritten and handled by busybox instead of androids tool box.... Once again that means nothing to me without knowing what exactly androids tool.box is... I know a couple tool boxes but unfortunantly this is not one, ... So if anyone has a link to explain this or an educated opinion that would be great! Thanks..
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Shagerty said:
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Click to expand...
Click to collapse
UPDATING: I'm wondering that being MM, Busybox installer chooses su/bin path automatically (some suggest "su/xbin", which is not present in stock MM, hence installer su/bin choice) in order to make Busybox "systemless". SuperSu actually does the same. Though I'm pretty sure about this, I'm also looking for confirmation. Since this thread and its early answers even date back to 2012 when there was no MM and "systemless" stuff wasn't that popular (I assume) they point to install Busybox in "system/xbin" or "system/bin"...
babylonbwoy said:
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
Click to expand...
Click to collapse
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Mainak007 said:
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Click to expand...
Click to collapse
I think it's a little bit too late, thread is from 2012.
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
babylonbwoy said:
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
Click to expand...
Click to collapse
Why??.......do you frightened of bricking device??????
You can get all smartphone firmware Here
:highfive::fingers-crossed:
babylonbwoy said:
I think it's a little bit too late, thread is from 2012.
Click to expand...
Click to collapse
And I gave the answer for other who will visit the forum next time:angel:
Mainak007 said:
And I gave the answer for other who will visit the forum next time:angel:
Click to expand...
Click to collapse
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Doesn't matter..... Install anywhere and symlink to others
Mainak007 said:
Doesn't matter..... Install anywhere and symlink to others
Click to expand...
Click to collapse
Just install it to any folder in $PATH and execute it as any other command.
Code:
echo $PATH
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Banking / payment apps are looking in 3 mentioned paths to detect whether Android got rooted or not: hence best is to install BB to custom path.
BusyBox Pro says that it can is unsuccessful at installing in the /system/xbin folder on my Moto G Stylus 5G, I don't suppose anyone could explain to me why this keeps happening could they? Also, I don't have the option to install to /system/sbin either. The only options I have are /system/xbin, /system/bin, and custom. But when I install and reboot i have to reinstall BusyBox Pro again. I noticed in the settings tab that you can have busybox, on every boot, reinstall to /sbin....how is this possible if you install to /bin? also, how can I get it to install to /xbin? there is also another option that says busybox will, on every boot, be removed from /sbin as long as busybox has been installed to /bin or /xbin, but the feature I'm speaking of assists kernels that re-install busy box to /sbin on every boot.....OMG!!! Which option do I choose? Or should I not choose any, and just reinstall each time i boot up, which will be very tedious.....Please HELP!!!..... Also, should I choose Smart Install? Or just use install without the Smart Install option ticked? Sorry I see there are similar posts here, but I don't really understand where I would install if i chose to install to a custom path, which is why I'm asking such questions if it seems repetitive I apologize. Thanks in advance!
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Vaibhav Chauhan said:
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
Click to expand...
Click to collapse
can i use another rom's updater script in my rom which has same base??
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
es0tericcha0s said:
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
Click to expand...
Click to collapse
i tried to replace updater script but not working
i also have tried to compare set perms but i am unable to find fault in it
@es0tericcha0s
please tell me what to do??
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
es0tericcha0s said:
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
Click to expand...
Click to collapse
actually i am using android kitchen to make the rom
and when i use the cosmic rom's updater script in it the status 1 error was solved
but it stuck on boot animation
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Vaibhav Chauhan said:
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Click to expand...
Click to collapse
Not all phones have adb access while in a bootloop. But to do so you would need adb set up on your computer, change directories to the adb folder (or if it's enabled globally, then where ever), and type:
adb logcat
You'll want to save it somewhere like:
http://pastebin.com/
and upload the link.
I am not skilled at reading logcats, so not sure if I can be of any more help after that.
If you don't have adb set up already, then just use this one: http://forum.xda-developers.com/showthread.php?t=2317790
I appologize if this is the wrong forum, please move the thread if it is.
I have a quick question for whoever can help. I have been working on a new ROM and have everything perfect now including Aroma installer. The only issue that I am having now though is that once installed, It doesnt seem to have working root. It installed supersu apk and it looks like all the files are in the correct places however when I start supersu it gives the "Supersu binary is not installed and cannot install it, this is a problem". Nothing else obviously has root either.
I would appreciate if someone can point me in the right direction as to what may be causing this. Thanks in advance!
tp2215 said:
I appologize if this is the wrong forum, please move the thread if it is.
I have a quick question for whoever can help. I have been working on a new ROM and have everything perfect now including Aroma installer. The only issue that I am having now though is that once installed, It doesnt seem to have working root. It installed supersu apk and it looks like all the files are in the correct places however when I start supersu it gives the "Supersu binary is not installed and cannot install it, this is a problem". Nothing else obviously has root either.
I would appreciate if someone can point me in the right direction as to what may be causing this. Thanks in advance!
Click to expand...
Click to collapse
I know this supersu below ships with the system binary, You may need to extract, or download su and install it to /system/xbin before installing supersu
httpscolon//f-droiddotorg/repository/browse/?fdcategory=Security&fdid=com.koushikdutta.superuser
pull su alone here httpcolon//downloads.androidsudotcom/superuser/su-bin-3.1.1-arm-signed.zip
you have to fix the url, i have too low a post count to post links
dougunder said:
I know this supersu below ships with the system binary, You may need to extract, or download su and install it to /system/xbin before installing supersu
httpscolon//f-droiddotorg/repository/browse/?fdcategory=Security&fdid=com.koushikdutta.superuser
pull su alone here httpcolon//downloads.androidsudotcom/superuser/su-bin-3.1.1-arm-signed.zip
you have to fix the url, i have too low a post count to post links
Click to expand...
Click to collapse
Thanks but I just double checked and the su binary is in system/xbin. I have also tried re-coppying a fresh su there in the outcome is still the same.
Pretty sure it makes a difference on what phone you are building for, because sometimes there can be something in the kernel preventing it too. And what kind of rom are you making? CM? Stock based (Touchwiz, etc)? Other?
tp2215 said:
Thanks but I just double checked and the su binary is in system/xbin. I have also tried re-coppying a fresh su there in the outcome is still the same.
Click to expand...
Click to collapse
What do you get if you type su in the terminal?
Also found this post that may be of use
http://forum.xda-developers.com/showthread.php?t=2479233
dougunder said:
What do you get if you type su in the terminal?
Also found this post that may be of use
http://forum.xda-developers.com/showthread.php?t=2479233
Click to expand...
Click to collapse
Thanks but nevermind. I figured it out, just forgot to update this thread.
tp2215 said:
Thanks but nevermind. I figured it out, just forgot to update this thread.
Click to expand...
Click to collapse
Good to hear.
What was the fix, for other that find this thread?
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.