Related
Hi,
i need to get this phone rooted please, no root apps works, @Chainfire maybe can help?
Any one be able to help if this can be rooted?
xxmcvapourxx said:
Any one be able to help if this can be rooted?
Click to expand...
Click to collapse
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
KNOX should remain 0x0
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
ashyx said:
Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.
Instructions
1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.
2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3
3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.
4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.
5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA
6. Wifi fix:
modify the line below in /system/build.prop:
ro.securestorage.support=true to false
Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl
Good luck I hope it works for you.
.
Click to expand...
Click to collapse
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
xxmcvapourxx said:
Hi quick question ,
i've done steps 1-3 worked fine - http://pastebin.com/raw/PbA49d0q
my next question cant i get a custom twrp to root it or custom rom cause kingaroot not working properly.
Click to expand...
Click to collapse
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
when trying to root
By Kin9Root Won Chu chu in a few ROot failure 'not yet suitable ˉ a - condolence ˉ ˉ a ˉ a "` ` One by one - one 'one one '- one - the
i get i've tried the pc version and the apk a few tries i keep getting notifications in the settings it is set to permissive
ashyx said:
Unfortunately you can't install custom recovery on this device. This device has a locked bootloader.
What issues are you reporting, did you manage to gain root?
Click to expand...
Click to collapse
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
figured it out -- it was the pin we just trying super me
xxmcvapourxx said:
i keep getting stuck on this : https://s4.postimg.org/mxi70k1vx/Image3.png
ok I tried 3 different cords, various lengths, and now no matter what I get this screen only
Click to expand...
Click to collapse
You're using the desktop version, please download and use the android English apk:
http://www.apkmirror.com/apk/kingro...-release/kingroot-5-0-5-android-apk-download/
.
Is there an update on this, did anyone achieve root?
.
ashyx said:
Is there an update on this, did anyone achieve root?
.
Click to expand...
Click to collapse
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
xxmcvapourxx said:
Hi,
Just update :
used the bootimge via odin works fine.
Installed kingaroot via app root takes a few times.
Superme (legit) brought removes kingaroot and installs super su and binaries then reboots <---- here i lose root again i have to use kingaroot sometimes it auto reboots it self.
My friend also has the same phone do you have skype or telegram so we can chat private
Click to expand...
Click to collapse
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
Yes as soon as super su me installs ask to install binaries ans ask to reboot it will lose root.
I will try the script without flashing firmware
Thank you ill let you know how i get on
ashyx said:
Does it reboot itself as soon as SuperSU me installs supersu? That's probably the reason for root not sticking.
You could try the script below, I have confirmation it still works for the same procedure.
Steps 3 to 12.
https://forum.xda-developers.com/ga...ide-how-to-root-tripping-knox-kitkat-t3129484
Obviously use updated apps and don't flash the boot partition.
You will also need to flash the system version of SuperSU not EverRoot.
When you get to step 12, don't flash the firmware.
Disable EverRoot and just flash this:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
That should give you permanent root.
Sorry, but I don't use any of those apps you posted.
Click to expand...
Click to collapse
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
xxmcvapourxx said:
My friend done a tutorial what he did on the process when losing root he followed your first guide http://pastebin.com/raw/ZSZExWt6
Click to expand...
Click to collapse
It's not related to the bootloader, the bootloader is still locked, it's simply an incomplete installation of SuperSU. Probably due to permissions.
Follow the guide posted above and you should be good. I'd also suggest using root package disabler to disable knox.
Hit search in the app and type knox. Disable all knox related files.
https://play.google.com/store/apps/details?id=com.kunkunsoft.rootpackagedisablerfree
.
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
ashyx said:
So can anybody confirm where we're up to with this. Has root been achieved? Are we good to post this as a viable root solution?
Click to expand...
Click to collapse
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
xxmcvapourxx said:
Hi,
still not rooting perm -- Followed the exact tutorial you have gave us , me and my friend and we both lost root.
stock > odin > kingroot apk > supersu me > flashfire > supersu-sytemmode.2.79 rebooted lost root.
the only way we can do this is not to ever reboot....to keep root
Click to expand...
Click to collapse
So even when flashing root with Flashfire still losing root? Did you try using the script posted above?
Also could you post a screenshot of Root validator after losing root?
I would also suggest flashing the stock firmware with FLASHFIRE.
Ensure to Uncheck the boot partition and disable EverRoot.
Add the system supersu zip to the install.
It may be remnants of Kingroot causing the issue. Flashing this way will ensure a clean system with just supersu.
Having the same problem
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
stanfox said:
I can't even do the OEM unlock and wondering if Knox is stopping me from doing it. Kingroot gets to about 77% before giving up. Also tried "one click root" and "odin" and a couple of others. Tried to uninstall Knox with many different aps but noway will it let me. I bought this J3 in HongKong and it is full of crap and adds that pop up and cover the whole screen. I have had some negative affects on the phone with all the playing around I've done to the point where when I hold down the buttons (power volume etc) the phone just goes into its first normal boot screen and stays there. Hope I haven't hijacked the thread but thought I may have the same problem as the original thread poster
Click to expand...
Click to collapse
Why can't you enable OEM unlock? Remove any pin/password from the device first.
ashyx said:
Why can't you enable OEM unlock? Remove any pin/password from the device first.
Click to expand...
Click to collapse
I was surprised at first when you directed me to this thread ashyx, the first word I saw was Kingroot and I was sure a dev such as yourself wouldn't use that.
I write against Kingroot all the time. It is information stealing malware that doesn't even give true root, packs PUPs, and sends IMEI and other info to China upon install (check the logcat).
And it's nortoriously hard to get rid of and replace with a different SU. From what I read above, true root hasnt' been achieved yet. Ive used KR a few times in the past, but never again. It used to be easier to replace KingUser w SuperSU. Not so much anymore.
Please folks, Kingroot IS NOT actual root ; please quit posting about it in a true professional developer site.
Ahyx, PM me if you wish. I'd like to work on any methods other than this. I can get the bootloader unlocked from Net 10. But not until having it hooked up w/ lthem for a year. I've already chosen to disconnect this device anyhow because I can't stand using a non-rooted phone. Too bad, it's a good machine. I got a great buy on it. $50US brand new. Same store today $99. WalMart = $120
I just bought an LG G3 for $45. Verizon model, interesting root. I had to downgrade firmware to achieve root. It's TWRPd, and running Dirty Unicorns 10.6, a nice rom, better once I mod it.
Tried the latest RR rom for it. Nougat was cool, but too early, too many bugs.
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.
Hi!
I just rooted my S8 today for the first time and within 5 mins I got this: Only official released binaries are allowed to be flashed
I know what I did but not why it happened.
Installed:
TWRP
RMM State Bypass
Magisk
Samsung Antiroot removal
Cause:
I open Magisk - Accepted the prompts to update and followed whatever it asked - about 3 options if I recall.
Then it said reboot; then boom! Only official released binaries are allowed to be flashed.
Cant remember what it was but it was the third prompt - first was magisk manager v (****whatever), second I think was similar to magisk manager, third... cant remember but it had a pop up asking how to flash and I hit the "recommended" option.
Then I spent hours trying to fix it Got it after 6 beers and a few hours of screwing around.
But what causes this?
Ive been seeing a lot of XDA threads showing it can happen by a random reboot?? Is this a common thing?
I rooted after using it since launch with no issue so now I'm a little worried about trying to use the S8 rooted if this is something that can happen.
I want to play with xposed and magisk but this reboot hell is a little scary.
I have got it up and running again today - Had to spoof the date to get OEM Unlock to reshow up :good:
Rooted and on Aug 1 security update.
Is there something I should NOT do to avoid this error? I got it within 5 mins because I accepted the update promps then it flashed and reboot.
Damn... Rebooted and same error. Terrible
I think its tied to Knox... Restore and going back to stock
I believe Knox and RMM state are two different security features. The RMM state is for bootloader unlocking control.
I would say the RMM bypass zip didn't work did you allow twrp to make system modifications before flashing.
Also there is a ver 2 rmm state bypass
kingoddball said:
Damn... Rebooted and same error. Terrible
I think its tied to Knox... Restore and going back to stock
Click to expand...
Click to collapse
I've only ever seen this happen when OEM unlock is disabled, then rebooted. That will for sure cause this. But if your OEM unlock was definitely enabled then it's very strange. Aslong as you followed the steps exactly then you should be fine. Did you flash twrp, then format, then after format, copy rmm state fix zip to sd then flash? Other than I see no reason why it's happening
callumbr1 said:
I've only ever seen this happen when OEM unlock is disabled, then rebooted. That will for sure cause this. But if your OEM unlock was definitely enabled then it's very strange. Aslong as you followed the steps exactly then you should be fine. Did you flash twrp, then format, then after format, copy rmm state fix zip to sd then flash? Other than I see no reason why it's happening
Click to expand...
Click to collapse
Yes sir, I was unlocked, did the format and then installed the files.
It is a little odd. Potentially RMM v2 noted above could be the difference but unsure. Not really wanting to try again for a 3rd time
We'll see how bored I get on the weekend, maybe try again.
spawnlives said:
I believe Knox and RMM state are two different security features. The RMM state is for bootloader unlocking control.
I would say the RMM bypass zip didn't work did you allow twrp to make system modifications before flashing.
Also there is a ver 2 rmm state bypass
Click to expand...
Click to collapse
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
kingoddball said:
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
Click to expand...
Click to collapse
There are a few guides for this but try this guide as it incorporates everything in one :.ie installing twrp,rooting,OEM fix and data mount fix for twrp.
This would be better than giving you 3 or 4 seperate threads to look through. With twrp use latest version 3.2.3.0.
Read through the guide and comments just to make sure it suits your needs
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
kingoddball said:
I dont know if I allowed it - I think I left it read only as it's what the instructions said to do. But it flashed magisk correctly so unsure.
Edit: Is there an XDA guide for rooting the S8? I used one from youtube which not have been the best?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
When installing twrp, swipe to allow modifications
callumbr1 said:
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
When installing twrp, swipe to allow modifications
Click to expand...
Click to collapse
Ok... So... I did what that page said, tried out the new file as noted, allowed modifications and... Boom - first reboot red error.
I'm trying to flash back to stock but now I'm trying to fix this: <ID:0/010> Complete(Write) operation failed.
I'll get this flashed back today and leave it there.
NOT sure if this is a consideration but I am on the September 2018 security update.
DOA: Phone is in a dead loop. Cant flash.
galaxy s8 check fail (boot loader) device 4 binary 3
If I skip the BL file I get some other crap errors. What the hell.
Smart Switch wont recognise the phone. says not unrecognised.
FINALLY FOUND A V4 bootloader image!
G955FXXU4CRI5
http://samsung-updates.com/device/?id=SM-G955F
Damn this phone is a *****!
kingoddball said:
Ok... So... I did what that page said, tried out the new file as noted, allowed modifications and... Boom - first reboot red error.
I'm trying to flash back to stock but now I'm trying to fix this: <ID:0/010> Complete(Write) operation failed.
I'll get this flashed back today and leave it there.
NOT sure if this is a consideration but I am on the September 2018 security update.
DOA: Phone is in a dead loop. Cant flash.
galaxy s8 check fail (boot loader) device 4 binary 3
If I skip the BL file I get some other crap errors. What the hell.
Smart Switch wont recognise the phone. says not unrecognised.
FINALLY FOUND A V4 bootloader image!
G955FXXU4CRI5
http://samsung-updates.com/device/?id=SM-G955F
Damn this phone is a *****!
Click to expand...
Click to collapse
Ok so what error did you get
The device 4 binary 3 error in Odin means you are flashing older firmware than what is on your phone
Software updates seem to make things harder
If still interested have a look at this thread below l think this is based on latest update (your firmware version).
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009
Has anyone successfully rooted A9 2018 (A920F)?
Is anyone working on it?
How to root
you can use rooting tool or a application to root your galaxy. But there are pros and cons. So you have to consider about them. You can use a single click rooting applications but i can not guarantee it is safe. So you have to do it at your own risk.
We can start with that. That's a good option. I hope it will work.
Mod edit: Link removed - Untrusted host
Has anyone successfully rooted this model?
varadinum said:
We can start with that. That's a good option. I hope it will work.
Mod edit: Link removed - Untrusted host
Click to expand...
Click to collapse
This is only the firmware, not for root.
TP427 said:
This is only firmware, not for root.
Click to expand...
Click to collapse
You should click further:
How to root Samsung Galaxy A9 2018 SM-A920F via PDA/AP odin ->*Read here
This site has instructions, however the TWRP version for the A920F is not listed on the site.
Yes, there is no twrp for A920F
I have tried KingRoot, KingoRoot, Dr.fone. But all failed
We need to get some traction on this. Has anyone submitted a request to get TWRP on this model?
I managed to get this rooted with EFT dongle. There was no other method that I could find.
Codename_Falcon said:
I managed to get this rooted with EFT dongle. There was no other method that I could find.
Click to expand...
Click to collapse
Excuse me but how are you? What is eft dongle? Can you help us?
This is my first Samsung phone. I do not know myself. Please be so nice and help me. Thanks!
I just send email to support TWRP. Maybe the more they get such messages, the sooner they will deal with it
varadinum said:
Excuse me but how are you? What is eft dongle? Can you help us?
This is my first Samsung phone. I do not know myself. Please be so nice and help me. Thanks!
Click to expand...
Click to collapse
I am doing okay, thank you! Please check out the following for info.
http://forum.gsmhosting.com/vbb/f10...t-dongle-new-exclusive-method-2018-a-2526388/
Codename_Falcon said:
I am doing okay, thank you! Please check out the following for info.
http://forum.gsmhosting.com/vbb/f10...t-dongle-new-exclusive-method-2018-a-2526388/
Click to expand...
Click to collapse
It works? Can step by step instructions, starting with unlocking the bootloader, TvRP and to the end? From the very beginning. Thank!!! Sorry, Google translation.
Codename_Falcon said:
We need to get some traction on this. Has anyone submitted a request to get TWRP on this model?
Click to expand...
Click to collapse
I submitted the request for TWRP on TWRP builder today.
Rooted Successfully
SM-A920F can be successfully rooted by OneClickRoot. If you pay them, they can help you root it manually. My device has been rooted successfully.
But now, the problem is TWRP. Technicians from OneClickRoot told me no TWRP is available for this device and they can't help. So I submitted the request on TWRP builder. But nearly 40 devices are ahead of me waiting for TWRP building.
Is there anyway to get the TWRP faster?
TP427 said:
SM-A920F can be successfully rooted by OneClickRoot. If you pay them, they can help you root it manually. My device has been rooted successfully.
But now, the problem is TWRP. Technicians from OneClickRoot told me no TWRP is available for this device and they can't help. So I submitted the request on TWRP builder. But nearly 40 devices are ahead of me waiting for TWRP building.
Is there anyway to get the TWRP faster?
Click to expand...
Click to collapse
Does it trip knox counter?
Edit: I said screw the knox counter, I'm going with it. Everything was all green until it asked me to register so I entered some name and email. Then it asked me 30$(or 40$ if you're doing it from the computer and not the app). Definitely not worth it to root.
Edit 2: I'm now trying the Magisk boot file patch method, which can work without root and custom recovery. Unlocked developer options, checked OEM unlock option(which needed a factory reset)
downloaded stock firmware, extracted boot.img from it, patched and repacked it using magisk manager and finally flashed it to phone using odin. Knox counter is already tripped. It required another factory reset when I booted it after flashing(It said device integrity was compromised and it needed a factory reset, so I did it) but no bootloops. Aaand after I waited long enough to be able to install magisk manager again, I found out that my attempt was a success! I can now enjoy systemless root on my phone, at the expense of tripping the knox counter of course.
And of course, no luck on twrp side, which could've made the whole process easier for me.
Edit 3: It may sound simple when I write it like this here but it actually is a lengthy process. In fact, I looked up multiple guides on the internet, at least one for each part I talked about above and sometimes more than one since this is my first samsung phone ever.
Edit 4: One last thing, I can pass SafetyNet as well now, which was failing right after I did the OEM Unlocking and factory reset but before I actually rooted it with magisk.
thesingular said:
Does it trip knox counter?
Edit: I said screw the knox counter, I'm going with it. Everything was all green until it asked me to register so I entered some name and email. Then it asked me 30$(or 40$ if you're doing it from the computer and not the app). Definitely not worth it to root.
Edit 2: I'm now trying the Magisk boot file patch method, which can work without root and custom recovery. Unlocked developer options, checked OEM unlock option(which needed a factory reset)
downloaded stock firmware, extracted boot.img from it, patched and repacked it using magisk manager and finally flashed it to phone using odin. Knox counter is already tripped. It required another factory reset when I booted it after flashing(It said device integrity was compromised and it needed a factory reset, so I did it) but no bootloops. Aaand after I waited long enough to be able to install magisk manager again, I found out that my attempt was a success! I can now enjoy systemless root on my phone, at the expense of tripping the knox counter of course.
And of course, no luck on twrp side, which could've made the whole process easier for me.
Edit 3: It may sound simple when I write it like this here but it actually is a lengthy process. In fact, I looked up multiple guides on the internet, at least one for each part I talked about above and sometimes more than one since this is my first samsung phone ever.
Edit 4: One last thing, I can pass SafetyNet as well now, which was failing right after I did the OEM Unlocking and factory reset but before I actually rooted it with magisk.
Click to expand...
Click to collapse
It did trip knox. I don't know if there is a rooting method without tripping knox?
I'm waiting for TWRP. Request has been sent to TWRP builder
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
Wasn't it much easier if you install TWRP first, then root it using magisk?
Thank you for thatsuggestion. I didnt know that I can install TWRP before rooting the phone first
I had trouble rooting with CF auto root on my SM-N910F, not exactly the same problem as you.
Then I did some reading into other root alternatives and basically found out that SuperSU, which CF autoroot uses, was sold to a Chinese company called Coding Code Mobile Technlogy sometime around 2015. As it's closed source and Chinese firms particularly have been known not to respect user privacy, I would go with Magisk instead as it's open source, plus I have had zero problems with it so far.
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
hgroth said:
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
Click to expand...
Click to collapse
I'm no expert myself, in fact I'm new to it! but I'll share with you what I know.
I basically flashed TWRP to the phone using Samsung Odin (Loads of videos Youtube showing the process) Then I used Android Debug Bridge to push the Magisk flashable .zip file over to the phone (I think I could have actually just copied it into /sdcard - Androids name for internal storage bizarrely - through windows just like any other external device) before booting into TWRP on the phone, and simply selecting "install", selecting the Magisk .zip and flashing it from there. Then I just booted into Android and I seem to remember either the Magisk manager app will now be in your app draw, or alternatively there is an app placeholder there which allows you to download the full manager app, I can't remember which it is but small difference. Here is a link to the official Magisk thread on XDA which you can use find the download links you need. Take note that right at the top it states...
"Magisk does NOT have a website. Do NOT download Magisk from unofficial sites"
When I did it I downloaded Magisk from one of the top websites that appears when you search "Magisk" in Duckduckgo (they look very official) however after I read the notice above in the official thread I wiped the phone and did the process over again just to be safe! I hope that is helpful. :good:
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
did you remove battery after the flash?
Thanks for your help. Yes I tried that after the 2nd attempt when I set Odin not to auto reboot, I removed the battery
and then booted the phone after inserting the battery with the same result, not root. I am wondering why it says
boot image not found, aborting....... since I loaded the CF Auto Root which should be the correct boot image