yashsingh1/xdaforums huggingface dataset:
[LeEco Le Max 2 Questions & Answers] ThE_MarD:
[MENTION=8769107]7h30[/MENTION], I think it's your adb driver is incorrect. I'd recommend using the official Google drivers from here and follow the guide within this link on how to install it.

https://developer.android.com/studio/run/win-usb
[LeEco Le Max 2 Questions & Answers] 7h30:
I did it but it says that it's already installed
[LeEco Le Max 2 Questions & Answers] ThE_MarD:
https://developer.android.com/studio/run/oem-usb.html#InstallingDriver
[LeEco Le Max 2 Questions & Answers] 7h30:
that's what I did and it gave me back http://prntscr.com/qad48h
[LeEco Le Max 2 Questions & Answers] ThE_MarD:
Hmm there should be an option to manually select the driver to install, I forget the menu option sorry but it might be something like "let me choose the driver"
[LeEco Le Max 2 Questions & Answers] 7h30:
Yes, that's what I did and what I sent you was the result
[LeEco Le Max 2 Questions & Answers] 7h30:
[MENTION=6235294]ThE_MarD[/MENTION] Any ideas?
[LeEco Le Max 2 Questions & Answers] bilausdaniel:
Enable mount system read only in twrp.also delete all previous drivers for x2 installed in PC.go to device manager.uninstall drivers from there.OK?

---------- Post added at 06:46 AM ---------- Previous post was at 06:44 AM ----------

Use 3.1.1.0 twrp for eui 19 stock
[LeEco Le Max 2 Questions & Answers] 7h30:
I've just left for Christmas so I'll be checking this out when I return. Thank you!!!
[Meizu Pro 7 Questions & Answers] we.he1016:
Anyone have G rom for the pro7 S?
[Android Q&A, Help & Troubleshooting] lentmain:
I have a newer 10.1" Chinese tablet, a Jlinksz ZH960 tablet, that I am having a problem trying to see whither or not it has a bootloader or not... I can't use fastboot to load the newest TWRP..., I did use MTK to create a scatter txt file... I guess I'm still too ignorant of the process to open up this thing... Not sure what to do next..?

Any helpers out there for MT65XX processor..?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] xXxDmCxXx:
how to root and install TWRP or CWM in January 2018 security patch?? :crying:

version : A520FXXU4BRA8
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Not a chance.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] xXxDmCxXx:
can I do rooting without twrp?:(
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Unfortunately you can't root or modify at all.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Andriano24:
Is there any change that we would modify our phones again with February security patch? I mean it is possible that the bootloader may become level 2 again or so?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] catdoggy:
Hi, i have A520FXXBQIJ with twrp and root... so i just download the new firmware, i.e.from sammobile, flash with flashfire and bootloader is save/not locked??
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Should be fine if you update with Flashfire.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] catdoggy:
Thanks, sounds good. I will test it on weekend :)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] moozer:
Can you run through steps needed to do this via Flashfire?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Charles Miller:
My A5 2017 is still on November patch, but not rooted. It never auto updated because I already tripped knox when I unsuccessfully tried to root with Chainfire. Could I just use Odin to update to everything to January (excluding the BL, which would come from Marshmallow) and then try to install TWRP and the 'No Verity/Encrypt' patch? Does it matter what version of TWRP or root manager I use?

And from then on, I'll need to update only through "flashfire" if I want to be able to root again? Logic tells me I could just keep using Odin with the MM bootloader as I described above to repeat the process.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Just make sure you only use the sboot.bin from the Marshmallow firmware when flashing with Odin.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Charles Miller:
I'm not sure I follow. Aren't all the files I flash MD5 Files? My assumption was that I download the stock firmwares of MM and January Nougat from a site like Sammoble, finding the right files with my phone specs (CSC, build number, baseband). Then I start up Odin and put all the MD5 files from the downloaded folders into their appropriate sections (AP in AP, BL in BL, ect), using the bootloader MD5 file from Marshmellow, but everything else from the January Nougat folder. Then flash it.

I went through this process to fix my A5 after my first failed root attempt left it unable to enter recovery mode, except I just needed only the November nougat MD5 files. I don't recall using or even downloading any "bin" files.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
If you do it that way then you will be flashing more than just the bootloader as there are several images in the BL tar file, sboot.bin is one of these.

It will likely work, but there maybe wifi and telephony issues.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Charles Miller:
I see. So you're saying that instead of just loading the whole BL file from Marshmallow into Odin, I need to do something else. Are you advising that I find a way to take this sboot.bin file out of the Marshmallow BL MD5 file and put it into the BL section of Odin as it is? Or am I supposed to replace the sboot.bin file of the January Nougat bootloader MD5 with the sboot.bin file of the Marshmellow bootloader to create a sort of customised BL MD5, then flash that?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
I suggest pulling the sboot.bin out of the marshmallow md5 and unpacking the BL md5 from the Nougat firmware and swapping the sboot.bin then repacking everything back into a BL tar.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Charles Miller:
Very well. I'll look into learning how to do that. Hopefully it's not too complicated. Apparently, it's either this process, or learning how to update with Flashfire if I wish to get updates and still be able to root. I can't help but feel like I'm playing with fire, though. Odds are, there will eventually to be an update that won't work with the MM bootloader at all. I can't imagine this will still work by the time Oreo is released.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
Hi ashyx... can you teach me how to do unpack and repack also what app. Can I use for all of those?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
It's OK I'll repack it and post it later for you.

---------- Post added at 04:17 PM ---------- Previous post was at 04:11 PM ----------

I think you're probably right, but as long people don't update the bootloader then downgrade is always possible.

Happy willy nilly flashers need to be aware that they don't need to jump on every update available, especially unknown security updates which inevitably can turn out to be nothing more than ways to lock a device down even more.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
Thanks bro...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Here you go, this is a mix of the Marshmallow A520FXXU2AQF7 sboot and the rest from the Nougat A520FXXU2BQK1 BL file.

https://androidfilehost.com/?fid=962187416754456246

.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] gcrutchr:
Hi,

Thanks for the tip!

Still have same problem of bootlooping at bootlogo screen

I changed TWRP to 3.1.1.0...same issue...I have just reinstalled stock system, recovery, boot and now it boots properly

Also, RMM lock is reset to Prenormal...damn!!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] McFy:
Hey everyone, found this, if it can help some users :)

I didn't updated to thoses locked bootloader so I can't/wont confirm it is working

https://xdaforums.com/android/general/guides-android-8-0-oreo-mods-thread-t3772017/page6

This is to avoid to wait 168 hours, would be glad to see if it have been patched or if it is still working
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] dani010:
i try that and not working in my a5 2017 on CRD5
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] haidermiz:
I'm very beginner in this and i wanted to root my phone A520f running android 7.0 i tried to root using supersu and twrp and root was successful but there was some problem like brightness was set to high and cannot adjust and camera wasn't working to i return to stock now i wanted to root properly is there any step-by-step guide to root?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Sesshomar:
Is there a way to root after the upgrade to Android 8.0 ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] flyingpants:
This thread is ridiculous. Can someone please post a CLEAR, start-to-finish guide, with STEP-BY-STEP instructions, that works for SM-A520F as of May 30th 2018, and then put it in a new thread? (both Exynos and Qualcomm versions)

Thanks.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] corsicanu:
Not sure what's more ridiculous, this thread or your post. If you would read last 2-3 pages (5 min thing), you would probably know already what you need to do. But as always people skip reading, they need a personal assistant for all the question they have, everything must be updated to current date, daily updates, hourly maybe.

As for A520F "qualcomm version", when you find one please do tell me, i want to buy that phone.

Check this thread if you have more questions.

https://xdaforums.com/showthread.php?p=75514974

Just my 2 cents.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Anything else you'd like sir, washing, ironing, grocery shopping doing maybe?

Sorry for the sarcasm, but nature gave you a mind and 10 digits. Google gave us everything else.

Use them.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] flyingpants:
Yeah thanks, I read plenty of these pages. If there was a clear and concise guide written (5 min thing), I would probably already know what I need to do. But as always, there's 19 pages of some random, disjointed info and contradictory instructions, and people having problems with them.

Thanks for the link, that should be edited into the OP, and not hidden on page 19. The rest of your post was unnecessary.

You can't be serious? We are on the forum where people read guides and ask for help, and you're telling me to use Google instead? All it takes is 1 person who's successfully done it to write a proper guide, it's not that hard. I would do it myself if I already rooted my device..
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] pjrs2812:
Should I install the oem patch? I have a UAE 950F which I using on T-mobile in the US. I was able to enable the developer option and turn on the oem unlock the first time I turned the phone on without a sim installed or signing in to my Samsung account. I have installed TWRP and botting the phone I was still able to trun on the oem unlock with out wait. In download mode there is not RMM status.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] puddingoz:
Sounds like you don't need to but it won't hurt if you do anyway.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ryRy:
Sir rmm state in download mode was not there so it means it is normal.can i flash twrp without doing a clean flashed and wait for 7 days?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] lincolnsxda:
Rmm prenormal. Efs won't mount. Device won't boot

Download mode says frp lock off oem lock off rmm State pre normal. It says binary official system custom. When I try to flash anything besides stock Samsung Odin files I get cannot flash error. Device won't boot hangs and Recovery reboots hangs in recovery reviews Etc. Stock recovery also gives failed to mount EFS partition invalid argument and failed to mount misc partition and DM Verity fail. So I can't do anything through recovery there is no using ADB I cannot boot the system no matter what bootloader or version of firmware I flash I am unable to do anything

Help please
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] JeepinxJosh:
I finally laughed today... thanks man. Yet I do see his side... I just spent almost an hour reading the 4 pages of this post... (I think I have 50 post per page set) and I am unclear on what bootloader you guys are testing this on.... your saying RD1 or ARECor whatever but leaving out the bootloader number like on G950usqs3cre2 which is what I am on the 3 tells me I am proper *Bleeped* cuz I am on v3 or further I think. I was hoping this thread would change that theory.. and It still may but I see why he is unclear on what to do cuz I am unclear or what I can do and who can do what... I am on a s8 obviously v 3 bl... in dl mode I have no RMM

this is wht is listed

carrier tmb

RPmb fuse blown

rpbm provisioned

current bin sam official

sys stat official

frp lock on.. (BOUT TO FIX THAT)

Warranty void 0x0

qual sec boot enabled

rp swrev b31,1,1,1,1, k2 s3

sec dwnld enabled

did 205e59780724

now I am not gonna wait for an answer... cuz I can wait 7 days of jail to twrp and root... so I am gonna install factory bin. and remove frp and then reinstalll 3cre2 firmware and factory reset and then try and install twrp (the twrp is a hope and dream right now) then flash your zip to disable rmm and delete that app... I hope your zip does all that for me cuz I am not sure how to do all the build prop and permission stuff.... I know dos and windows in and out and can do almost anything yet linux and android are foreign to me... so sorry if this is way to much info.... I will post results so that everyone can see cuz from what I have read no one with a g950 v3 bl has tried this... *hold my beer... and watch this!*

oh yeah and yes I have the prince comsey and the 13.3.1b (the one that will flash anything to anything... ) and I do know how to and when to use those.... that much I do know...

p.s. can anyone here throw me a twrp link for the g950u or a compatible one?? also should I flash your noverity 6.0 ?? ashyx?

EDIT: Wow ok so this is why I read and you non reader quick posting no eye using finger less instant gratification guys get hard bricked and boot looped.... I won't be flashing twrp... as there isn't one for my device.... and.... my device to my knowledge doesn't have the rmm lock unless its a new thing in the updates past v2 bl.... anyways sticking to just frp removal.... (holy cow I almost really hd a bad day right there....)

---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------

Take it with a grain of salt man and laugh... these guys know so much that most of what we sit and try to fathom they take as kindergarten everyone should know stuff and probably forgot stuff we will never learn....

---------- Post added at 06:09 PM ---------- Previous post was at 06:05 PM ----------

have you tried to use the 13.3.1b odin.... (it is different from the prince comsey one... even more capable of flashing anything.... in fact it will i think... so be carefull.... i can link it to you if you pm me and need it still
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] surmany:
:good::good::good::good::good::good::good::good::good::good::good:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] vriend80:
Hi,

I'm using N950FD (Note 8 Exynos) with Official Stock firmware. I'm rooted using Magisk, and using RMM Fix Patch. And all are working good.

The only problem is, random crash occurs oftenly.

I have a question. There is a OTA update for my N950FD. I paused the download process to avoid the update process accidentally.

Is it safe to OTA update and i want to keep my device stay rooted with Magisk?

And What happened to RMM State after an OTA Update happen? Beacuse AFAIK, if RMM state become prenormal (and oem unlock menu is disappeared i think), i cannot safely go to TWRP or reboot my N950FD.

Anyone have done this before?

Thank you, Any Help would be appreciated...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] corsicanu:
Don't try to install any OTA, process will fail anyways because you probably have twrp, but even if you flash back stock recovery will still fail because your kernel is already magisk patched and md5 check from ota will see different checksum for boot.

Stay as you are, you don't need anything more.

Regards.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] vriend80:
[/COLOR]

Thank you for save me from the Trouble [MENTION=4658360]corsicanu[/MENTION]
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] LysolPionex:
I notice that the v2 of the rmm bypass zip only has the binary file in it. Do we need to put that into the old version to replace the old version's binary, or can we just run v2 without the script and manifest etc.?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] LysolPionex:
[MENTION=5150393]_alexndr[/MENTION] [MENTION=6911575]BlackMesa123[/MENTION] I assume I'd need to put the binary from v2 into the original rmm bypass zip? Cause v2 only has the binary, no script or manifest or anything...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] BlackMesa123:
No lol, just flash the zip as it is...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Loupps:
Hello,

Could you please tell me if the RMM-State_Bypass_Mesa_v2 which is containing binary is running with a the CRGH ROM?

I've previously used no-verify-opt-encrypt, RMM-State_Bypass_Mesa (with updater-script), magicsk but after a notification asking me to reboot the system to finalize some actions I got the stucked message "Only offcial ROM are allowed...".

This is on Galaxy S8 SM-950FD.

Thanks for your prompt reply.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] spawnlives:
This should work and won't hurt to try

I would follow this guide

https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535

It should be noted that in twrp you have to allow modifications.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Seagold:
Do I Flash RMM state via Odin or TWRP?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] spawnlives:
Via TWRP
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] BavoV:
Does this methode still works with the october update? (buildnumber A520FXXU7CRI1)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
I have an A3 2017 that is still on stock Android 6.0.1. Would this work to avoid all the latest lockout problems:

- Replace sboot.bin inside the Oreo BL.tar with the sboot.bin from 6.0.1 firmware

- Flash that modified BL.tar in ODIN together with the rest of the components from latest Oreo firmware

Then continue as normal, flash TWRP, then root?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Probably. It worked on nougat.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
Thinking about it...the "anti-feature" that disables the OEM Unlock menu entry must be in the OS part of the firmware. So if I only exchange the BL for an older one, the menu entry to OEM unlock may still be missing, or not? OEM Unlock as such is a 5.1 feature, so a 6.0.1 BL must support it.

Is it known exactly how OEM unlock works? My guess is that it sets a hidden flag somewhere when you toggle the menu and the BL only checks that flag during boot.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
RMM(Remote Monitoring and Management) is a bootloader feature and requires periodic connection to the Internet.

It can be bypassed by removing the relevant flag in the build.prop and removing the RLC app.

OEM_UNLOCK is not in the OS. SYSTEM is not writable.

The flag is set in a hidden partition and encrypted.

When the bootloader sees this flag OEM_UNLOCK is set.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
Yes, exactly. But the decision whether or not to show the "OEM Unlock" menu in Developer settings is likely taken by the OS, or not?

So if I use Oreo OS and there is code that hides this entry, the BL will remain locked and I can only boot signed images.

(Not really keen on leaving the phone 7 days with a SIM, Internet connection, and logged into accounts to get the menu back.)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
The only way you can bypass is either apply the RMM bypass zip first or don't update the bootloader or just ensure OEM_UNLOCK is already on.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
Are you sure that OEM_UNLOCK survives when updating firmware in ODIN from MM to Oreo?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
It does on my devices.

It simple to check it on first boot before flashing anything.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
How? There is nothing mentioned about OEM lock in download mode, no matter which way I toggle the switch in the settings.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
On my devices it either states FRP off or OEM lock off or both.

In any case the switch will remain set at whatever position it was set at in developer settings.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
On my device it only showed FRP lock off. Thought that FRP lock and OEM lock were two different features. Anyway, I went ahead, installed TWRP and it booted just fine.

So the learning seems to be: enable OEM unlock on every new Samsung device that you want to root before installing any firmware updates and you should be fine (?)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] vulkhead:
SM-G955F over here! I have RMM STATE: Normal and still missing the OEM Unlock. I understand RMM state has to be set to normal for everything to be up and running but I can't do nothing with it. Any suggestions?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tomri:
I guess the usual procedures apply:

https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/

https://xdaforums.com/galaxy-s9/help/oem-unlock-option-missing-how-to-restore-t3764475

https://xdaforums.com/galaxy-s8/help/oem-unlock-developer-settings-t3797245/

https://xdaforums.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984

The exact criteria for unlocking appear to be a bit "fuzzy logic", but should be similar for all Samsung devices. I wouldn't even be surprised if the decision to unlock was made in the cloud based on machine learning, given how the reports differ.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] redymedan:
I confirmed this rmm bypass it did not work anymore. I have rooted my J7 Pro, when rebooting I can not enter the system. Before rebooting I checked OEM unlock option does not appear on the developers option.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] BlackMesa123:
Seems more an error you did in the procedure than else. You probably rebooted to system after flashing TWRP, and that's wrong since once you reboot to system after flashing TWRP and without flashing the RMM Bypass zip will immediately trigger RMM Prenormal lock. Please wait for the 168h uptime (or try the Date/Time hax), enable OEM Unlock, boot in Download Mode and flash TWRP img again. Remember to untick Auto-reboot in Odin and remember to not boot in system till you flash RMM Bypass zip, or lock will be triggered again.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] redymedan:
OMG!, Yes you are right! I make mistake... yes yes.. after flashed twrp, formatted data then rebooting, copy rmm bypass to internal then flash the RMM bypass. Thank you very much :) I will do it again..

Last question, How I can install the RMM bypass zip, with USB OTG or SD Card? thanks
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] BlackMesa123:
I don't see the difference of flashing it in Internal Storage or in an external memory such as SD/OTG. Simply copy the zip in the desidered location and flash it normally via TWRP.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] em.:
Im bookmarking this..

thank u so much

Quick question, after i have 7days uptime so the RMM state back to normal, i have to flash latest TWRP right? if i fail to flash twrp, will the RMM will be locked again?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] maurce249:
i have a problem just got my s8 plus with oreo on it but there is no oem in developer options how can i get to flash custom roms?