Database Users

G530-W

I would like to ask for any help possible because it is getting just too frustrating
I have been trying to make Xposed to work for over a good 2 weeks now with no luck.
I have researched extensively on ARM and sdk22 to see if it is possible to make this version of the Grand Prime Work with progress being halted right the point of install. Most attempts by work around posted here by developers ended up with this version of grand prime to go into boot loop/system wipe somehow or simple error in process.
1- Rooted the G530-W (using G530-H as it was the only one compatible through trial and error)
2 - Installed Custom Recovery TWRP
3 - I have no clue if the rom has been DEOXED for any method install a DEOXED version has so far been incompatible
Any help tips or proper steps will be greatly appreciated
The phone is a
OS -5.1.1
Grand Prime (G530-W)
CPU - Quad-core 1.2 GHz Cortex-A53
Cortex A53 - 32/64 bit processor running SDK 22
Micro arch. - ARMv8-A
UPDATE:
Alright finally managed to do this after weeks of attempts.
Here are the steps for users who might be in my situation.
Step 1:
Back Up your Phone (Yes, I know you are too much of pro to do that and will not screw something up but guess what you will)
Use samsungs kies-3 or smart switch to do that. Probebly the best ones if you are using a pc. You can use titanium back up or any other app from the app store to make the process much easier.
Step 2:
Root your G530W
Most root methods work for grand prime variations close to it. (Suggest using any G530H root method)
Search for root G530H or any varition of grand prime released in 2014-2015
Step3:
Find your stock rom file.
this wiil be important if you somehow wipe everything off your phone. Search for your carrier example Bell, Vergin, Verison etc plus the correct version of the rom.
-You do not NEED it but its good to have
Link for Grand Prime G530W...
http://www.sammobile.com/firmwares/database/SM-G530W/
Step 4:
Install TWRP, go to TWRP main website and flash latest verson of TWRP. This should not trip anything unless your root method was unsucceful the TWRP should work.
If this does not work for Grand Prime try older versions of TWRP, personaly I had issues later on with TWRP boot looping me. So to save the hassle I downloaded a version specified for 5.0.2 but able to run fulll on 5.1.1
I am new so I do not know if we are allowed to have download links here from external sources but if need for the specific TWRP i used il provide it.
Step 5:
Search for Samsung 5.1.1 xposed installer.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
And download v79.1 ARM (ARM only for G530W) SDK 22
You can also download uninstaller for any future tweaking.
IMPORTANT TO INSTALL THE LATEST ALPHA APK of xposed framework, its v4 i believe
You can install this by flashing your zip file in TWRP
FLASH:
Go into recovery - this will pop up custom recover
Go to install
Find where the zip file is
Click on it and install, it will ask for reboot
Step 6:
After flash wait for reboot
Do not panic if long SAMSUNG logo even after 5 min (Unless its 30 or 1 hour then we have a problem)
Step7:
Profit

Where did you find a custom recovery for sm-g530w? When I downloaded twrp this model is not listed. The only one I saw on the list was galaxy grand prime ve which it would not allow me to download.

Jvirg said:
Where did you find a custom recovery for sm-g530w? When I downloaded twrp this model is not listed. The only one I saw on the list was galaxy grand prime ve which it would not allow me to download.
Click to expand...
Click to collapse
Try flashing this with Odin, it works fine.
http://forum.xda-developers.com/gra...om-recovery-twrp-2-8-7-0for-lollipop-t3190351
EDIT: Even though it seems like the G530W doesn't have many users interested in this sort of customization, I would like to confirm that this method to install Xposed is working fine so far on my SM-G530W with TWRP 2.8.7.0 and the TrapKernel by ShinySide. Installed a few modules and activated and rebooted, no problems at all so far. Also, thanks for the info, I was really hoping to find that someone had successfully installed the xposed framework on this phone.

NachoBusiness said:
Try flashing this with Odin, it works fine.
http://forum.xda-developers.com/gra...om-recovery-twrp-2-8-7-0for-lollipop-t3190351
EDIT: Even though it seems like the G530W doesn't have many users interested in this sort of customization, I would like to confirm that so far this method to install Xposed is working fine so far on my SM-G530W with TWRP 2.8.7.0 and the TrapKernel by ShinySide. Installed a few modules and activated and rebootedrebooted, no problems at all so far. Also, thanks for the info, I was really hoping to find that someone had successfully installed the xposed framework on this phone.
Click to expand...
Click to collapse
Thank you so much with this, i tested and it should be working, this is a failsail type step process but strictly SM-G530W
Nacho Thanks for the proper trwp XD
Anyways
Step One:
Backup
Nandroid/SD/Partitions/System/Rom
U can search how to do these, not really complicated but
Step Two:
Find your Rom, in this thread there is a link to it above
Step Three: (NOTE THIS IS NOT NEEDED, ONLY IF THINGS ARE MESSED UP)
Perform full restore
Get all the service updates after reboot
Step Four: (CAN BE STEP ONE IF U DID NOT DO THE FULL RESTORE, BUT IT IS VERY HANDY)
Flash root your phone with odin
Now not all can work, but most do with the varients to SW-G530W (so basically 530h is the best bet)
Nacho's root may have worked for him but not for me so its an experiment
I personally used ------- TrapKernel_G530T_AOF8_Root.tar -----
I sadly have no links, so if u can find THIS SPECIFIC one it will probebly work, as it is a variation of TrapKernal
Step Five: (OPTIONAL)
Install necessary apps/files that need to be varified by google or their counter services
For example if u want snapprefs (HANDY SNAP HACK TOOL) u must install the proper version of snapchat that works with it and authentcate yourself with the app by loging in.
After the installation of Xposed it is no longer possible because a FEW companies tend to place a check if xposed is installed
If u do not do this step then to get these apps working u will have to restart this entire process, so full restore, and back to step 1
Step 6:
Install TWRP
NachoBusiness said:
Try flashing this with Odin, it works fine.
http://forum.xda-developers.com/gra...om-recovery-twrp-2-8-7-0for-lollipop-t3190351
EDIT: Even though it seems like the G530W doesn't have many users interested in this sort of customization, I would like to confirm that so far this method to install Xposed is working fine so far on my SM-G530W with TWRP 2.8.7.0 and the TrapKernel by ShinySide. Installed a few modules and activated and rebootedrebooted, no problems at all so far. Also, thanks for the info, I was really hoping to find that someone had successfully installed the xposed framework on this phone.
Click to expand...
Click to collapse
YUP Thanks to nacho for the link the recovery will function and can do all the task u need without tether and all that, and s#it ton of glitches and crashes
Step Seven:
Flash Xposed 79.1 (link in original post above) through flashy
This will manually install it through your phone
You can try doing it through twrp directly but this sometimes caused a entire twrp to crash for me so do what works, try flashy first, if not then do it manually
Step 8:
Install the xposed app
Step9:
This should be it, u can now get SU, and App2Sd whatever floats your boat to completely blow up your phone
Any more links will be great and if im wrong or something confusing il be happy to reply

The kernel I'm using comes with root, if I remember correctly. All that's required is to install supersu from the play store.
I really would like to see a more stable release of twrp for this phone though. The current one available is by far better than nothing, but I can't use it to make a full backup and it, for lack of a better explanation, does some weird **** sometimes.

I want xposed framework on my a3 sm-a300h

I've been working on getting xposed framework to work for two months now. All I want is to install xposed framework on my sm-a300h. Can it really be that hard that it should take up all my waking time during two months to install it?????
My system has been deodexed by someone else, so don't ask me how he managed to make that work.
Tried to install TWRP by following instructions here!: http://forum.xda-developers.com/sam...overy-twrp-2-8-7-0-samsung-galaxy-a3-t3173382
Managed to get TWRP to work!
I had already installed XposedInstaller_3.0-alpha4.apk
With TWRP I tried to install this (Xposed framework):
xposed-v84-sdk21-arm.zip from http://dl-xda.xposed.info/framework/sdk21/arm/xposed-v84-sdk21-arm.zip
When I restarted I suppose I got a so called boot loop, I just see the Samsung logo over and over.
So my two questions are,
1. Why didn't it work to install Xposed Framework?
2. How do I get out of the boot loop and get the phone to work again? haven't made any backups.
Has anyone installed xposed framework on this model or should I sell the piece of s*t phone and try with some other phone???? I'm wasting my life trying to get this to work....
My head's just spinning trying to find information in different threads in here, I'm think I'm on the limit to having a nervous breakdown. As far as I can see there's no thread on how to install xposed framework on sm-a300h? Please, help. If I need to buy a new phone, just tell me what phone to buy, and how much it is and ill buy that phone instead...

I guess I have to flash a stock rom in order to get my phone working again?
I downloaded a stock rom from sammobile for my device, A300HXXU1BPA1_A300HUUBBPA1_BVO.zip but the only way I can flash a rom now is through odin, but odin doesn't take .zip files. So how can I restore my phone and flash the zip?
I tried the Wipe function in TWRP, but it doesn't work... Still boot loops.

I guess the mistake I did was flashing the wrong version of xposed framework for my device?
Which version should I use the next time i try?
Does this work for my device? http://forum.xda-developers.com/showpost.php?p=64900847&postcount=3681

helphelphelphelp said:
I guess the mistake I did was flashing the wrong version of xposed framework for my device?
Which version should I use the next time i try?
Does this work for my device? http://forum.xda-developers.com/showpost.php?p=64900847&postcount=3681
Click to expand...
Click to collapse
Instead of second guessing then getting frustrated and annoyed when it doesn't work. Why not just spend literally 2 mins and make a proper backup first then if there are any issues just restore it?
Whats the point in having a custom recovery and not using it's main feature?
You've only got yourself to blame for your errors and resultant frustration and anyone else reading this should also take note.
Anyway pet talk over.
You should be good with the link you posted.

ashyx said:
Instead of second guessing then getting frustrated and annoyed when it doesn't work. Why not just spend literally 2 mins and make a proper backup first then if there are any issues just restore it?
Whats the point in having a custom recovery and not using it's main feature?
You've only got yourself to blame for your errors and resultant frustration and anyone else reading this should also take note.
Anyway pet talk over.
You should be good with the link you posted.
Click to expand...
Click to collapse
Did everything again from the beginning, flashed a ROM from sammobile, flashed TWRP.
Installed XposedInstaller_3.0-alpha4.apk
Then I tried to install this version of xposed framework: http://www.arter97.com/browse/tmp/hsk/xposed/ using TWRP.
Then I got an error while installing xposed framework. The error message says i need to free up more /system space. arter97 recommends in his thread that you "debloat your current ROM installation via root access.", but how do I do that?
And when I tried to start the phone after trying to install xposed framework it went into a boot loop.
So then I tried to restore the backup in TWRP. Restore Failed.
Get this error: Cannot restore system -- mounted read only.
What now?

helphelphelphelp said:
Did everything again from the beginning, flashed a ROM from sammobile, flashed TWRP.
Installed XposedInstaller_3.0-alpha4.apk
Then I tried to install this version of xposed framework: http://www.arter97.com/browse/tmp/hsk/xposed/ using TWRP.
Then I got an error while installing xposed framework. The error message says i need to free up more /system space. arter97 recommends in his thread that you "debloat your current ROM installation via root access.", but how do I do that?
And when I tried to start the phone after trying to install xposed framework it went into a boot loop.
So then I tried to restore the backup in TWRP. Restore Failed.
Get this error: Cannot restore system -- mounted read only.
What now?
Click to expand...
Click to collapse
To restore your backup remove the check in 'SYSTEM partition read only' under MOUNT.
Make sure your rom is deodexed.
Install this via twrp: http://forum.xda-developers.com/attachment.php?attachmentid=3510616&d=1445173483
Install Xposed installer.
Done

if you bothered reading the xposed thread, you would've noticed that Samsung TouchWiz firmwares are not supported from the official xposed from rovo.
use this one from arter97/dkcldark. Keep in mind, this is for sdk21 (5.0), in case we ever get 5.1 (sdk22) or 6.0 (sk23), we wont need this one anymore.

with the dkcldark version you don't even need to debloat anymore;
I also made a tutorial some time ago; should be the same steps for this a3:
http://forum.xda-developers.com/samsung-a-series/general/tuto-xposed-odex-rom-yes-knox-0x0-t3316688/
anyway, you should read a lot first before even thinking about flashing something, and like said above, a backup is a must because even those who (think they) know what they are doing sometimes **** up

I`m using this without any issues.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
SDK22.
SDK22 means Android Lollipop 5.1.x.
SDK23 means Android Marshmallow 6.0.x.
ARM means the devices that are running arm32 operating system.
ARM64 means the devices that are running arm64 operating system.
Try this (at your own risk).
It`s better to flash or restore backup first and then install Xposed Installer App (as normal apk installation) and then flash this from TWRP.

Messed up my Flashing somehow

I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"

SpoonOjiisan said:
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
Click to expand...
Click to collapse
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F

Rosli59564 said:
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Click to expand...
Click to collapse
Did a quick google search do these work?
download.chainfire.eu/696/supersu/
androidsage.com/2016/04/06/how-to-install-xposed-framework-on-marshmallow-update-with-xposed-v81/
and btw how exactly do i save this into my sd card, i can't get past the product logo.
also thanks a lot for replying man
edit: oh wait if you mean put the zips into an external sd card imma try that now. thx

Hi,
You have to use custom built version of xposed if you use stock or any touchwiz-based-rom(other versions cause bootloops). Just google 'xposed custom build by wanam'. Hope that helps.

Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.

SpoonOjiisan said:
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
Click to expand...
Click to collapse
I strongly believe you flashed wrong xposed zip. There is no arm7 zip by wanam. Hence find arm-sdk23. I think the last 1 is v81.
Supersu is just to give you root access. I won't causing phone to stuck at boot logo. Or do you mean splash screen showing 'samsung galaxy note 4'?
Sent from my SM-G925F

I honestly don't know if that will solve the problem, but you can try it. If it doesn't work, try flashing a rom via recovery or stock rom via odin. Since your data is already gone, I would suggest you wiping your phone completely and flashing a custom rom(I have a SM-N910C as well and I use erobot). Before doing anything, do a full backup in recovery, just in case.
Edit: If you wiped everything in recovery, including /system, that is probably the reason why your phone is stuck. Flash a rom and yo should be good.

Yeah that one exactly, splash screen showing note 4.
so based on what you guys said i should first flash a ROM so it works normally and then i can attempt for Supersu and Xposed arm-sdk23? was watching this random video you think i might have somehow wiped my touchwiz OS? was fiddling around in the Recovery trying to solve it you think i might have done that?
Since you have the same phone and you are using erobot i might go for that same ROM just to be on the safe side, i don't want to try something random.
So first try flashing custom ROM >> SuperSU >> Xposed
That's what i'm going for (i might need confirmation haha kinda scared now, i think i almost bricked my phone)

I believe your phone has to be rooted before you can install a custom rom. I can't tell if your is, but I would do the following:
Make a full backup in twrp>flash supersu again just to make sure the phone has root access>flash a custom rom.zip from your SD card>boot the custom rom, if everything works, flash xposed CUSTOM BUILD(!) and install the xposed installer.apk
I am not a pro, so wait for someone to confirm what I have written. I suggest you to use erobot as your custom rom because of the user-friendly aroma installer. Erobot is prerooted if you choose custom kernel in aroma installer, so keep in mind not to choose stock kernel.
Hope it helped

SuperSU >> Erobot >> Xposed
Ok got it, its currently 23:36 here in the Philippines guess i'm going to sleep, i'm doin that stuff tomorrow confirmation or not.
I can't really afford to throw this phone and it was a gift. So you guys have no idea how much i appreciate your help. /downslash/ Rosli thanks a bunch guys. goodnight

Hi there.. dont worry about the su not install button.. its common as i've aslo rooted my phone through chainfire an it does show me too. Click on do not install..an yeah you have flashed wrong xposed that bricked your phone.. did you backed up your phone before flashing xposed framework? If so try to restore..if not try to get in downloading mod an flash the official framework through odin.. try visiting sammobile.com there tou will get the official framework.. before flashing read ann the instruction or take a look to video tutorial on youtube about how to unbrick phone.. this might help you all the best

Question about rooting P8 Lite

Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite

TommyWhite said:
Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite
Click to expand...
Click to collapse
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?

You probably got stuck in boot animation because you flashed superSU in system mode. It should be installed in system-less mode. Magisk will install only in system-less mode and I think it's better at passing the safetynet.

amageek said:
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?
Click to expand...
Click to collapse
Thanks for replying :good:
What do you mean with "Your can error every versions..."? .. Do you mean you can root every version?
I am very new to this. Half of the time I dont know what the H im doing, and all of the time I only have a slight idea of what is going on in the Phone. For example I dont even know what a root file is, could you tell me?
How did you root with Magisk if I may ask? And whats the difference with SuperSu?
I had all kinda errors and issues along the way from B605 to B170 and B123 Android 5 back to 6 and B609. (I could make a thread of it ... maybe it helps others???)
Because today I finaly rooted my Phone.
Weirdly enough root checker basic sais it isnt but other root checkers say it is (and my device itself said after reboot that it was) ... so what to make of that?
Can I update the Phone now its rooted without unrooting it?

@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)

TommyWhite said:
@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)
Click to expand...
Click to collapse
You can't update phone which is rooted(as far as I know).
Do you have TWRP recovery installed?
If you had TWRP installed and you rooted by flashing SuperSu(this is what other guy meant with "root file"). By default SuperSu installs in system mode(meaning it does it thing into system partition). You need to install other zip file first to make it install system-less mode(meaning it does it thing into boot partition).
Magisk is also flashable zip and similiar to SuperSU. If you use apps that need to pass safetynet(like netflix) you want to root with magisk.
Don't know did that helped at all. It's hard to explain when I only know how to use it but don't know why/how it works : D
And if you don't mind doing factory reset before updating, you can also install official updates in TWRP.

Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )

1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
TommyWhite said:
Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )
Click to expand...
Click to collapse

By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...

amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
Click to expand...
Click to collapse
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?

keikari said:
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?
Click to expand...
Click to collapse
Yes but I haven't uploaded the file in my Mega Cloud... He can update it ..

keikari said:
1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
Click to expand...
Click to collapse
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )

amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...
Click to expand...
Click to collapse
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?

TommyWhite said:
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?
Click to expand...
Click to collapse
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this

amageek said:
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this
Click to expand...
Click to collapse
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!

TommyWhite said:
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!
Click to expand...
Click to collapse
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again

TommyWhite said:
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )
Click to expand...
Click to collapse
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.

amageek said:
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again
Click to expand...
Click to collapse
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.

keikari said:
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.
Click to expand...
Click to collapse
Thanks again, I copied some bits to remember. I hope you were not tired of me not understanding things. You said I should just ask so here I go again
I understand most of what you wrote but:
TWPR can make a back up/an image of the device, right? But that image doesnt include apps and app data (or data at all?)? And Titanium doesnt back up firmware I guess.
So how do I make a backup of everything (except of the hardware) then?
Also Im in a dilemma about updating TWPR, because you said it will whipe data (what data actually?) and amageek said I need new TWPR for stock updates. So I need the "backup of everything first" I guess ... what to do? I have TWPR 3.0.2 now by the way.
Also cant I just download Magisk from Google Play now that my phone is rooted ... or is that being stupid?
7: Its strange, coz I remember I had my phone rooted (with the help of some old tutorial they should remove imo) but accidentally downgraded my phone with it to lollipop (one of the many failures I encountered ). But just with local updates B052 to B132 to B170 back to some 2KB B132 to marshmallow B609 ... something like that ... it was unrooted again.
Anyway, by update script you mean a script only TWPR can read?
And therefor TWPR does not check the version allready installed?
Is that correct?
But after this you say: "If you are doing this remember to reboot recovery when installation is done (it will go to stock recovery) and to factory reset.
Then you can flash TWRP and do rooting stuff."
I dont get that, coz that means you have to start all over again ... or do I miss something?
Im sorry, im doing the best I can.

TommyWhite said:
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.
Click to expand...
Click to collapse
Do you have have stock recovery or TWRP recovery? If you have TWRP recovery then fish stock recovery and then try updating again...

[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!

From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !

Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number

I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch

Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!

Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-

It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse

Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.

finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed

Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well