yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moistcity:
This may be off-topic.

I found a fully deodexed rom of the april update(AQC5) in a russian website. Should I go for it?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
I'm not sure what is preventing you saving the log?

If you can boot to twrp, do the procedures you need to do, IE, wipe, backup, restore then immediately save the log to the sd card.

Post that log (file only) here and I'll take a look.

As far as I'm aware everything but installing SuperSU is working as it was fully tested by others in another thread.

https://xdaforums.com/samsung-a-series/development/recovery-twrp-3-1-0-1-samsung-galaxy-a7-t3588590
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

No, if it boots to the logo screen right after the failed wiping, and gets stuck on that screen, you can't retrieve the logs.

If it's working for other users, good for them, but then maybe there are key differences between AQC5 and mine (APLI), as I had originally suspected, and you said it wouldn't make a difference. They are most likely hardware differences, even though the CPU is the same, but something else might be different, but at this point, it's just a guess of mine.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
So you're saying as soon as you wipe the device with TWRP it auto-reboots?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Yes, it did that. I'm gonna try again at a later date, but I'm not looking forward to it, as either way it goes, I'll spend 6+ hours reinstalling all apps and restoring accounts.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Just to clarify something:

I'm assuming you have FORMATTED the DATA partition to make DATA mountable and then applied the boot patch?

Before wiping anything, are you able to backup your device including DATA?

.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

I'll try backing up first next time, so I don't have an answer for that yet.

As a former PC/Windows advanced user, I assume FORMAT is WIPING, so, if not the same in the Linux/Android world, how exactly do I "format" first, to only then wipe?

But, again, just as a footnote, the official TWRP for the j7elte just worked. I didn't have to do anything (like "formatting first, then they can be wiped" requirements, or SU not being flashable with it). All I had to do with that image was install it, it would do the rest by itself. I guess that's why official is a big deal, being just a tag or not. I didn't even need a "no-encrypt..." zip back in those days with the J7, just the TWRP file.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
You really don't get it do you and TBH I'm getting tired of your flippant remarks? :rolleyes:

The reason why the J700F(2015) didn't need any of the 'Formatting first stuff' is because it wasn't shipped with forced encryption. Devices shipped with Marshmallow and Nougat are shipped with forced encryption enabled. TWRP does not support Samsungs encryption and therefore to remove it and mount DATA it needs to be removed by FORMATTING using the FORMAT DATA button in TWRP. This is now common on ALL recent Samsung devices. For example the S7 https://xdaforums.com/s7-edge/help/twrp-mount-data-unable-to-crypto-footer-t3360331

I suggest if you're not prepared to follow the steps required then just leave well alone as I've tried to help you, but you're obviously not happy. :(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Well, the J7 didn't ship with Marshmallow, but it was updated to it. That was the confusing part, or one of them.

I'll try it again soon.

PS: I don't see a "FORMAT" button on the TWRP screenshots of this thread. So it's under "wipe" anyway.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Hey ashyx. So, I am finally rooted, and I am with Magisk, since SuperSU doesn't flash. Thanks, ashyx.

A new issue has surfaced due to my inexperience with Magisk (with SuperSU, this is a bliss). Anyway, I installed PHH Superuser and enabled multi-user, then I modified my buildprop accordingly (to enable multi-users), then I created the 2nd user and linked my 2nd Google account to it, installed PHH and Magisk Manager on it too. But I'm not getting SU access rights on "user #2". What am I missing?

Thanks for everything.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
A little confused as to why you've installed PHH as well as Magisk su? Magisk su should be all that's needed, it works pretty much like Supersu does.

If you really want to install Supersu then you can probably install the SuperSU ZIP with Flashfire
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

No, just the PHH manager, and it's because a few other users do it too, so I thought the fix for my multi-user issue depended on it so it wouldn't hurt to try, but it didn't fix the problem at all. Anyway, is there a fix for SU access with multi-users? Magisk doesn't seem to have an option in its settings.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
It wouldn't advise using another manager for Magisk su. It may conflict, just the same as it wouldn't be advisable to use another manager for supersu.

Tbh there shouldn't be an issue with multiusers as Magisksu such should work regardless of profiles.

The only thing I can think of is installing the Magisk manager while using the other user profile as the stored su management entries may only apply to that particular user.

This means each user has to give root permission per app they use.

Does it state root is granted for any apps in Magisk manager while using the other profile?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Well, the only things Magisk Manager says while logged on the 2nd profile are:

1- 12.0 installed (green lighted)

2- "Rooted, but no root permission, not allowed?"

The settings in the manager on either profiles don't have a "toggle multi-user on/off". So, either I am missing something, or this feature should be requested for future updates of Magisk.

Thanks for replying.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
2- "Rooted, but no root permission, not allowed?"

I don't understand where it says that, got a screen shot?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Here you go.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
What does it say in the log?

Seems like someone else posted the same issue on the bug tracker.

https://github.com/topjohnwu/MagiskManager/issues/138
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Thanks. I don't know how to see the log, the manager on the second profile doesn't have a "log" option.

I don't know if the manager has a log on the main/primary profile, but since the main one has root permission, it might be there. But the logs will not be about the second profile.

Thanks for the link, I think I will wait for a fix or request the multi-user feature option though. I'd rather stay with Magisk now, so I hope this can be fixed.

And thanks, [MENTION=4899305]ashyx[/MENTION]. I finally got rid of all the Microsoft bloatware too.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
I think I found something. The manager on the 2nd profile is being denied, but I can't manually "grant" access to it on the primary profile, so we'll need a multi-user option just like the one in SuperSU.

Here are the logs from the primary profile:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Crackers,the app is denying itself root permission. Wtf?

So it seems magisk does not yet support Multi user mode. WIP.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Indeed. I will request the multi-user feature from the developer on the official thread soon.

Thanks [MENTION=4899305]ashyx[/MENTION]. For everything.

Update: Good news, I reached out and [MENTION=6429309]DodoGTA[/MENTION] said multi-user support is a plan for the future. Now, we just wait. In the meantime, flashfire/supersu are options, if we need it before then.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SAINI99:
Any progress
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yepnegiishere:
Will this Twrp working on Nougat ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] korwynkim:
Do we even know when we are getting Nougat yet?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] yepnegiishere:
I have it
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
We'll get it in September. Probably 7.0, by what Samsung updated us with, not 7.1 or 7.1.2, unfortunately.

The A 2016 ones are getting it too (and I think the 2015 ones too, but I don't remember if this is going to be the case), so, hopefully this means our new 2017 models are powerful enough to get the Oreo update sometime next year.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moistcity:
Can this work on the newest firmware update?

Edit: Tried flashing on A720FXXU1AQD5 firmware and it works.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] SAINI99:
Iam on XXU1AQE1 latest this will work anyone confirm root is working and nandroid backup
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Ngochoan:
Root unsuccessful

Pls help

I already installed twrp successfully, then fl su, it's successful too,. But when I reboot and check root by root checker, it showed that my phone was not rooted yet.

I try again, formated data, then flash magisk instead, by same result.

Anyone can help me. I did everything I can.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moistcity:
Been two months since release but, cf-autoroot for A720FXXU1AQC5 is available. TWRP will be overwritten so be sure to flash TWRP again.

https://download.chainfire.eu/1101/CF-Root/CF-Auto-Root/CF-Auto-Root-a7y17lte-a7y17ltexx-sma720f.zip

Edit: Reflashing TWRP encrypted my storage again and formatting data removes supersu. What do I do? Can I remove cf-auto-root's recovery.img?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Richard_10:
Same issue here
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] luk3dm:
Good afternoon!!

My Twrp is giving the following error when will I flash some zip: "ERROR MOUNT DATA" And the mount option or data is not marking. How to proceed?

Thank you very much!!!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] kumbangdesa:
Hi sir..

I tried with build number A720FXXS1AQF5 but no luck.

After format data, It can mount but when flashing magisk v13.3 the screen is blank before the flashing process complete. Tried many time still got the same result. It fail to root.

Can you update the twrp again sir?. Thanks.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Magisk v13 has issues. I suggest you try v12.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] kumbangdesa:
Thanks sir. I will try again later and report back.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moistcity:
After flashing v12, install flashfire and flash v13.2 or SuperSu 2.82
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
SamMobile already has Android Nougat for our device, for now only for Russia, Ukraine, Chile and a few others.

If anyone can test TWRP and no-verity-no-encrypt.zip with the stock Nougat update, please do, and report back any issues that might happen (with the bootloader being updated and all) to [MENTION=4899305]ashyx[/MENTION] here.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] kumbangdesa:
Hi sir. Can you making update to TWRP 3.1.1?. Nougat had already rolling for our model. Thanks sir.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] moistcity:
[MENTION=7757700]stephymv[/MENTION]

TWRP works without problems in Nougat,though no-verity-no-encrypt.zip do tend to delay unlocking the phone for about 3-5 seconds after entering the password.

The internal storage can still be accessed in TWRP even without using no-verity-no-encrypt.zip so it looks unnecessary to flash the zip. Confirmed by doing a backup and restoring after a day.

Flashing both SuperSU and Magisk 13.3 in TWRP now works for some reason.

Overall very satisfied with the Nougat update.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] kumbangdesa:
Thanks sir.. it work.. I had tried with SuperSU and Magisk 13.5.. both running well on Nougat.. :good::good::good:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Oves786:
nice work bro
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] fabelbish:
I managed to flash twrp from odin however in twrp I keep getting error can't mount sdcard or external sdcard.CWM also gives me same error. How do I fix this?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
If I had a pound every time someone asked this...

It's CLEARLY posted in the OP. :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] fabelbish:
oh my bad. should be this one right:

"To disable forced encryption and mount internal storage (/DATA): "

might have overlook this step. hmmm this will wipe my internal data..will try tonight .thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Hungcpvina:
Hi bro. My device A720F has flashed to Android 7.0 nougat. I tried to rooted it by CF Auto-root file. But it has failed sound system after root. Could u fix it. tks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Oves786:
nice work mate
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] denkyo999:
please help

[IMG="bootloader"]https://scontent.fmnl4-5.fna.fbcdn.net/v/t34.0-12/21469554_10155115632044613_1038825579_n.jpg?oh=4282d617edccc7dffac422fc11fa4f5b&oe=59B63C79[/IMG]

[IMG="android dead"]https://scontent.fmnl4-5.fna.fbcdn.net/v/t34.0-12/21469874_10155115631039613_1857057017_n.jpg?oh=f69c06af62d5e6bdb240e9da9bd2fef8&oe=59B65653[/IMG]

i can't open the download recovery mode.. it will bypass to bootloader and i could not overwrite it.. please help
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
[MENTION=4899305]ashyx[/MENTION]

Something curious happened yesterday. So, the Nougat update for my region was never seeing the light of day, so after waiting on it and never getting it, I downloaded one from a different region, a full ROM image from SamMobile. TWRP and no-verity-no-encrypt.zip were still working too.

What happened is the following: yesterday, I downgraded to Marshmallow, because the Nougat update for my region is available now, only just through OTA at the moment, not SamMobile yet. After the update process was done, I made a factory reset, and after that was out of the way, I proceeded to install TWRP with Odin, and...it doesn't work anymore. I tried it again, just to be sure, and even though the flashing process went "green" in Odin, when accessing the Recovery mode, I get the stock one, and my device's software's status is "official", and I can check for OTAs normally.

I know Magisk has a new method to patch the boot image, but there are no in-depth details on this method on its thread (Samsung specific), so I won't risk it.

I guess I lost root forever on this device. I wonder if the multi-part full ROM from SamMobile installs extra files or not, in comparison with the smaller OTA update, and maybe some missing files are the cause for failing to flash the custom recovery? Although, that doesn't make sense to me, but it's the only difference I can think of between the foreign ROM and my region's one, one was a full ROM while the other was an OTA update. I don't know why TWRP worked with the ROM from the foreign region I used, and it doesn't work with my region's ROM. Anyway, I thought you should know about this.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Seems you're missing the important step of immediately booting to recovery after flashing with odin.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
I wouldn't be updating you if I hadn't done everything I could have done and that I know how to do. Besides, seems you missed the part where I had it working with the Nougat ROM for Chile. So it not working on the one for my region is just that, it is a puzzle on why it doesn't work.

Plus, neither Marshmallow nor Chile's Nougat required immediately rebooting to TWRP. The only difference is regional (between the Chile and Brazil ROMs). Other than that, it's Nougat, as in, it's the same update. Why TWRP ceased to work? You tell us. And the auto-reboot is too fast too. With the J7, Odin would auto-reboot the device to TWRP, but the A7 gets rebooted to the system. Sometimes I am fast enough to press the keys for it to go into TWRP, sometimes I'm not. It's ok, as it was never necessary with any previous ROMs, as I stated.

If it had the official tag, it would have been updated by now. It's ok if you don't care, just stop being condescending when you're talking to people who are not totally unaware of how things are done.

Anyway, you're updated, it's up to you now.

I don't know if this makes any difference, but the stock recovery says it can't access the /misc partition. Which is a failed error message that the Chile's stock recovery never showed, I think.

All I can still do on my end is try the currently available TWRP when SamMobile publishes the full version of the ROM for my region.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] denkyo999:
does your sd card work properly on a7? i got this issue when restart/reboot, all the files on the sd card were erased.. and i can't think anyway to solve this..

can you give some advice? thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
I don't think the sdcard is at the core of the issue I described. But mine works without any issues. I don't know why yours got erased, sorry to hear that. Unfortunately, I don't know the issue that plagues you, so I can't help you out with this.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
What's your problem? :eek:

I tried to point out a valid reason for your issue. If you still have stock recovery and your device still shows official then the recovery image didn't take and got replaced at boot.

This is almost always due to not forcing boot directly to recovery from odin after flashing. Unchecking AUTO REBOOT and MANUAL reboot is a MUST.

The stock recovery not being able to access the /MISC partition is because your device doesn't have one and totally unrelated to TWRP.

If you don't like my replies/suggestions then take your snarky attitude elsewhere. :rolleyes:
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] :
There's something wrong with the Brazilian Nougat update. First this TWRP not working anymore, when it still did with the version for Chile, and now the battery charging time is taking longer than usual, way longer (3-5 hours, instead of 1h45m, quick charge active still too). All previous ROMs, including the foreign Nougat I used for a month or so, kept it at 1h45m.

I might go back to Marshmallow and wait on a new update with a new security patch level.

Update: bad otimization confirmed by other users, some of them went back to the versions for Chile or Australia.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] xceejhaex:
boot image patch will work on nougat firmware??
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ggg8383:
so, i guess that this twrp works properly only on marshmallow and AUS or Chile Nougat, isn't it?

Has anybody tried it on other nougat ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ggg8383:
has anybody been able to root the a 720f/ds by installing magisk or supersu via twrp?? I've tried but everytime the phone reboots at the "patching ramdisk" stage.

Maybe I have to flash the "boot image patch" ?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ggg8383:
ok, after a few tries, I've been able to successfully root the SM-A720F/DS.

Here's what I did (some steps may be unnecessary, I don't know):

- install Nougat AUS using Odin (uncheck auto restart)

- install TWRP (link in first post) with Odin (uncheck auto restart)

- boot in TWRP. check data, system, preload in the "mount section". Format data as explained in the first post. Install Phh Supersu (link in first post). When flashing, the process should say that boot.img and Ramdisk are successfully patched

- reboot system. Configured android. At this time, the system is still NOT rooted. Enable developer mode, enable "USB debug" and "OEM unlock".

- reboot in TWRP. check data, system, preload in the "mount section". Format data as explained in the first post. Install the patched SuperSu from post #6 in this thread.

- reboot system. Now you should have root

In the last days I had tried to flash magisk 12 or 14 with no success: the Magisk Manager said installation successful but there was nothing in its supersu tab and any app needing root didn't work. The modules section of Magisk manager was blank (I was able to manually install the Viper4android module and a couple of other modules, though).

I had also tried to install ONLY the patched Supersu from post #6, and it didn't work either. Have no idea why.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] asadnow2k:
dear sir i ahve a720 with this frimware A720FXXU1AQF2 will it work? or can stuck
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Zulfi:
What is system and system image in recovery, I am bit confuesed while getting backup!

Thanks
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
System is file backup, system image is raw partition backup.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Zulfi:
Oh! So basicaly I can choose system image only then I can restored system anytime. What to do if we need whole ROM backup? Means system, user data, efs, And boot.

Thank you
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
For full back up you only need system, data, Efs, boot, modem.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] fipec:
personally, I gave up TWRP.

I now use CWM and I have no problem.

The root is done, the use is simple and free bug.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Zulfi:
Thanks dude :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] snehann:
hi there,

i need a custom recovery for samsung A700H ( samsung 2015 a series ).... i cant find it anywhere ... please help !!
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
See the relevant section. This is for 2017 models.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashkan_g00dboy:
Not work in UAE rom :(

I have error in odin

This error: this file cant flash becuse this file isnt samsung official file

Sorry for my bad speak english
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
Unfortunately your bootloader has been locked.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] GinoTonny:
And how i can unlock It again? I can't install TWRP :/ and i can't downgrade to Android 6.0.1 too :'(
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashkan_g00dboy:
Bootloader open in developer panel but dont work

In russia rom custom recovery at first time flashed and worked

But after upgrade to uae rom custom recovery dont work and give me official binary error!!

And root dont work too

Now after dangrade to russia rom too dont work custom recovery

Please help me

Frp lock too is off !
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
As said previously your bootloader has been locked by Samsung. Not a lot you can do I'm afraid, unless Samsung release another update with an unlocked bootloader.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] kirabyte:
Could i be root with locked bootloader?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] ashyx:
No.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] thexile:
How do I disable the annoying install TWRP prompt permanently?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Slash360:
Hi, I have an a question: how can I do enable OTG? I try mount but not work.