Hi guy's so i was able to downgrade from Pie ( One Ui ) to Oreo
( save your media on your sd card or your PC then you check if they are there )
1 - Go to TWRP or Recovery to wipe data
2- Download and unzip
https://drive.google.com/file/d/1FQKt_lWUxxbaZGk37r4tkEMO0Faaci-R/view
and
https://drive.google.com/file/d/1-0sJtCjGrlmS4z_dDO_FXozR1g8u-vm8/view?usp=sharing
Put RMM STATE BYPASSER AND VERITY IN A SD CARD
3- Open Odin and untick auto reboot
4-click start on Odin now it's fully flash and now press power + volume down button and after the screen turn off directly press Power + volume down and Up now you are in download mode and check if the auto reboot is unticked
5- Click on reset on Odin and now on AP put TWRP and click on start now press Power + volume down and after the screen turn off press Power + Volume Up and now you are on TWRP go on wipe and click on format data and now go back and go to install and click on up a level and got extsd and now you flash RMM state bypasser and after verity and now reboot now you are on oreo and you install magisk after first reboot.
Did Pie slow down your phone? I was debating on whether I should update my A8.
nypheral said:
Did Pie slow down your phone? I was debating on whether I should update my A8.
Click to expand...
Click to collapse
Well battery draining issue all one ui device has that and the sound is not louder than oreo
with new always on display features and night mode the battery remains more than 2 days ...
Robert978 said:
with new always on display features and night mode the battery remains more than 2 days ...
Click to expand...
Click to collapse
my battery lasts only 12 hours wtf
587.saboor said:
my battery lasts only 12 hours wtf
Click to expand...
Click to collapse
More than 21 hours on Oreo ?
Lu Han said:
More than 21 hours on Oreo ?
Click to expand...
Click to collapse
but still with oreo its 12hrs
I'm almost doing downgrade because of the GCam, but I'm wondering if I install TWRP will I lost the warranty? Or is it just when I root the phone? And do I really need to install Magisk after that? Thanks
Lanatico said:
I'm almost doing downgrade because of the GCam, but I'm wondering if I install TWRP will I lost the warranty? Or is it just when I root the phone? And do I really need to install Magisk after that? Thanks
Click to expand...
Click to collapse
u lose warranty if u flash twrp
what do you mean install magisk? if u want to root then obviously but if u dont want root and u just want twrp (idk why you'd wanna do that) then don't install magisk
587.saboor said:
u lose warranty if u flash twrp
what do you mean install magisk? if u want to root then obviously but if u dont want root and u just want twrp (idk why you'd wanna do that) then don't install magisk
Click to expand...
Click to collapse
that's because in the tutorial he said to install magisk, i though it'd be necessary. btw, can I do this without TWRP? just using the stock recovery to install RMM? another question, what is RMM? is it really necessary? saw some videos on YT and they just flash some firmware with the same bootloader without this RMM. sorry for not know what it is.
Lanatico said:
that's because in the tutorial he said to install magisk, i though it'd be necessary. btw, can I do this without TWRP? just using the stock recovery to install RMM? another question, what is RMM? is it really necessary? saw some videos on YT and they just flash some firmware with the same bootloader without this RMM. sorry for not know what it is.
Click to expand...
Click to collapse
RMM Was introduced in android nougat and was to have more locked down protection by samsung from accessing root, RMM stands for Remote Monitoring and Management
some devices don't have rmm and/or the videos are old
the rmm fix zip is necessary so that you avoid getting rmm state prenormal and having to wait 7 days again
you cant flash the zip without twrp obviously lol
587.saboor said:
RMM Was introduced in android nougat and was to have more locked down protection by samsung from accessing root, RMM stands for Remote Monitoring and Management
some devices don't have rmm and/or the videos are old
the rmm fix zip is necessary so that you avoid getting rmm state prenormal and having to wait 7 days again
you cant flash the zip without twrp obviously lol
Click to expand...
Click to collapse
i thought flashing with stock recovery would be the same thing as with TWRP
Lanatico said:
i thought flashing with stock recovery would be the same thing as with TWRP
Click to expand...
Click to collapse
lol no, if it was, then there would be no point of twrp lol
Lanatico said:
that's because in the tutorial he said to install magisk, i though it'd be necessary. btw, can I do this without TWRP? just using the stock recovery to install RMM? another question, what is RMM? is it really necessary? saw some videos on YT and they just flash some firmware with the same bootloader without this RMM. sorry for not know what it is.
Click to expand...
Click to collapse
I have a lot test on how to get locked out and I found by flashing a csc that not your country code would get you locked out.
If you do flash just the for example like ap,twrp,root just remove sim card during your hacking .
Maker sure you flash magisk not supersu.
587.saboor said:
my battery lasts only 12 hours wtf
Click to expand...
Click to collapse
587.saboor said:
u lose warranty if u flash twrp
what do you mean install magisk? if u want to root then obviously but if u dont want root and u just want twrp (idk why you'd wanna do that) then don't install magisk
Click to expand...
Click to collapse
your knox counter will increase if you flash pretty much anything in download mode. I flashed a stock tar.md5 in Odin and it tripped knox. Wasnt even trying to root it, just flashing the stock update from sammobile.com/firmewares tripped knox for me. I hadnt even downloaded TWRP for this device at that point LoL
i really dont get this fear of losing the warranty in the first place. Warranty is for mfg defect, so unless the screen craps out or the SOC, then sure, but do you think theyre gonna check for root if you send it in for that kind of defect anyways?
---------- Post added at 11:20 AM ---------- Previous post was at 11:16 AM ----------
if youre only getting 12 hours of use after installing the pie update, then something is wrong. factory reset it in recovery and see what you get after that. if that fails, factory reset it in recovery again and reflash the pie tar.md5 in Odin.
I use my phone a lot, have a gear S3 Frontier constantly connected and i get at least 30 hours out of it. I recharge it at right around that 30 hour mark (give or take depending on what im doing) and still have over 30% of my battery left when i do so.
youdoofus said:
your knox counter will increase if you flash pretty much anything in download mode. I flashed a stock tar.md5 in Odin and it tripped knox. Wasnt even trying to root it, just flashing the stock update from sammobile.com/firmewares tripped knox for me. I hadnt even downloaded TWRP for this device at that point LoL
i really dont get this fear of losing the warranty in the first place. Warranty is for mfg defect, so unless the screen craps out or the SOC, then sure, but do you think theyre gonna check for root if you send it in for that kind of defect anyways?
---------- Post added at 11:20 AM ---------- Previous post was at 11:16 AM ----------
if youre only getting 12 hours of use after installing the pie update, then something is wrong. factory reset it in recovery and see what you get after that. if that fails, factory reset it in recovery again and reflash the pie tar.md5 in Odin.
I use my phone a lot, have a gear S3 Frontier constantly connected and i get at least 30 hours out of it. I recharge it at right around that 30 hour mark (give or take depending on what im doing) and still have over 30% of my battery left when i do so.
Click to expand...
Click to collapse
I'm more worried about the security patches I can receive. My warranty is 2 years, I didn't want to mess it up and someone said it is permanently. Think I ain't got choices since I really need a GCam and Oreo it's the one where it works.
Lanatico said:
I'm more worried about the security patches I can receive. My warranty is 2 years, I didn't want to mess it up and someone said it is permanently. Think I ain't got choices since I really need a GCam and Oreo it's the one where it works.
Click to expand...
Click to collapse
yes, tripping knox is permanent, but i still dont get why people care about the warranty. Like i said, if something goes so wrong that you cant fix it with Odin, its probably something outside of warranty anyways. I havent used GCam, but i do know that people are all about it. I have Open Cam on my A8 along with the stock camera app, but the software running the stock camera is good enough for me, and i take a fair amount of pictures. Software tweaks are nice, but i feel that the biggest limitation is the hardware, and no amount typing code will ever fix that, mitigate it? sure. But not correct it.
youdoofus said:
your knox counter will increase if you flash pretty much anything in download mode. I flashed a stock tar.md5 in Odin and it tripped knox. Wasnt even trying to root it, just flashing the stock update from sammobile.com/firmewares tripped knox for me. I hadnt even downloaded TWRP for this device at that point LoL
i really dont get this fear of losing the warranty in the first place. Warranty is for mfg defect, so unless the screen craps out or the SOC, then sure, but do you think theyre gonna check for root if you send it in for that kind of defect anyways?
---------- Post added at 11:20 AM ---------- Previous post was at 11:16 AM ----------
if youre only getting 12 hours of use after installing the pie update, then something is wrong. factory reset it in recovery and see what you get after that. if that fails, factory reset it in recovery again and reflash the pie tar.md5 in Odin.
I use my phone a lot, have a gear S3 Frontier constantly connected and i get at least 30 hours out of it. I recharge it at right around that 30 hour mark (give or take depending on what im doing) and still have over 30% of my battery left when i do so.
Click to expand...
Click to collapse
Hi there, correct me if I'm wrong, but in latest Odin and newer devices (S7 and up I think) you don't use .tar file but 4 separate files : AP,BL,CSC and CL.
I updated my A8 via Odin, right after flash did hard reset and touch wood have no issues whatsoever. Knox is intact 0x0 and anything else in "original" state...
587.saboor said:
my battery lasts only 12 hours wtf
Click to expand...
Click to collapse
If I push it hard (games,music,browsing and youtube) I get a full day. Without games and YouTube it's 2 full days.
Rexton270 said:
If I push it hard (games,music,browsing and youtube) I get a full day. Without games and YouTube it's 2 full days.
Click to expand...
Click to collapse
tf how
the most battery time i got ever was 16hrs even when i first bought the phone
Related
Hello Everyone. First and foremost, thanks for all the helpful tips you guys have provided, been lurking here for a year or so.
Okay so heres the deal. I used skunkApes rooting method to root my phone last year. I just used the files included there and didn't do any custom roms or anything.
The last OTA update, didnt remove my root so after a few drinks and seeing that notification bar, i said why not. Well this one did. I checked SuperSU and it said no binary files found, must re-root. And my root checker says no root access. In developer menu, i dont see a tab for root to tick.
I tryed unistalling superSU, and that didnt work when i reinstalled. I can get to Download mode, but when I do recovery, it looks like its the stock android recovery.
Any help woul be much appreciated.
oh and sorry if this is in the wrong place, i wasnt sure if should had tagged this in teh "How to root" thread.
Phone infor- Spring G3, USA,
SPH-L710android version 4.3
Thanks
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
cwm
FallenZen said:
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
Click to expand...
Click to collapse
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Praz21 said:
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Click to expand...
Click to collapse
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
FallenZen said:
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
Click to expand...
Click to collapse
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
http://i.imgur.com/qrByUGN.jpg
same issue
I got the same issue here. Did not expect to lose root with the 4.3 OTA update, but I have! I got ODIN to flash CWM recovery and I got into recovery boot mode, and was able to install superuser. Once the phone booted up I got that bullS*it gray shield icon notice about "attempt to access secure area" (KNOX?) and now I cant get root access. WTF?! Please help, I need TrevEMod back in my life!
question
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
onion root
bigpappags3 said:
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
Thanks for the info. Yea, my phone is already a year old so from what Ive read from that thread is that it just voids the warranty.
I guess i have to re-visit the rooting process. I just would like to get root back so I could use my wifi teather and bluput to control my ps3 again.
Any help is much appreciated.
Click to expand...
Click to collapse
Guessing I'm going to wait until a .tar file is released to flash custom recovery and root. I need a flawless phone and a lot of issues being reported in the use of cnex 4.3 rom release.
Sent from my SPH-L710 using xda app-developers app
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
Simple answer I believe is no. ... You have the knox bootloader. . That room will brick you device because ur trying to put an older bootloader on your phone.
http://i.imgur.com/qrByUGN.jpg
Got Root Back
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
SwellVermin said:
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
Click to expand...
Click to collapse
Out of curiosity is your SELinux status "Permissive" or "Enforcing"? Also, tethering is a known issue on 4.3 stock update, TrevEMod probably isn't going to work regardless. Is that the only app giving you problems?
We have a member who figured out a wireless tether fix on Android Forums, check out this link:
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/800923-solved-mk5-4-3-stock-working-wireless-tether.html
It is for Virgin Mobile but should still work for Sprint or Boost for that matter since all three are SPH-L710.
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Mr. Struck said:
Out of curiosity is your SELinux status "Permissive" or "Enforcing"?
Click to expand...
Click to collapse
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
FallenZen said:
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Click to expand...
Click to collapse
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
SwellVermin said:
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
Click to expand...
Click to collapse
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
SwellVermin said:
What? lol Where is this setting found?
Click to expand...
Click to collapse
Settings/About Phone, scroll to the bottom. More of an issue for 4.4 than 4.3, as the default for 4.3 is Permissive and the default for 4.4 is Enforcing. In Enforcing mode it will sometimes block root-related apps, but it can manually be set to Permissive for 4.4 users.
FallenZen said:
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
Click to expand...
Click to collapse
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
SwellVermin said:
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
Click to expand...
Click to collapse
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
yeah I tried that
FallenZen said:
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
Click to expand...
Click to collapse
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
SwellVermin said:
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
Click to expand...
Click to collapse
Shouldn't be... I'm also on a stock recovery and ROM. What version of ODIN are you using?
I was going to use CS-Auto-Root but just had a couple questions. After reviving the tablet today, I did numerous updates. Would CF root still work with the new software? The only thing diffrent I can see is the build numberm does that matter? Details below, and thanks!
Model #: SM-T700
Android Version: 4.4.2
Build number: KOT49H.T700XXU1ANK2
Sorry if i'm posting to the wrong place!
It should work on most firmwares. If it doesnt it work it will not break anything. If cfautoroot doesnt work then you can use the twrp method.
DUHAsianSKILLZ said:
It should work on most firmwares. If it doesnt it work it will not break anything. If cfautoroot doesnt work then you can use the twrp method.
Click to expand...
Click to collapse
Ok, thanks a lot! One question though, why not just use twrp first? Is it a lot harder or something?
I prefer cfautoroot. Its automated in which you just flash it and gives root. With twrp recovery, you have to flash it with odin. Then download a zip called supersu zip on your tab s. Then reboot back into recovery and flash it manually. Theres less steps with cfautoroot
DUHAsianSKILLZ said:
I prefer cfautoroot. Its automated in which you just flash it and gives root. With twrp recovery, you have to flash it with odin. Then download a zip called supersu zip on your tab s. Then reboot back into recovery and flash it manually. Theres less steps with cfautoroot
Click to expand...
Click to collapse
Ok, i'm just afraid that CS will mess up, and brick my tablet!
atech087 said:
Ok, i'm just afraid that CS will mess up, and brick my tablet!
Click to expand...
Click to collapse
It shouldnt break anything. Even if it fails or something happens, it just messes uo your recovery. You can easly fix this and just flash twrp over it. Both root methods will void warrenty so its best to be sure that your tablet isnt deffective. Wait a week or so in case. People had problems with battery and other stuff but they already void warrenty but still got it fixed as it was a hardware problem.
DUHAsianSKILLZ said:
It shouldnt break anything. Even if it fails or something happens, it just messes uo your recovery. You can easly fix this and just flash twrp over it. Both root methods will void warrenty so its best to be sure that your tablet isnt deffective. Wait a week or so in case. People had problems with battery and other stuff but they already void warrenty but still got it fixed as it was a hardware problem.
Click to expand...
Click to collapse
Correct, messing around doesn't void your hardware warranty, even though stores/manufacturers want you to think it does. You are allowed to use the item for which it is designed. If you are allowed to root it and mess around with it. Warranty remains since you used the device for what it is designed. If you hardbrick your device that's not covered, not because you rooted, but because you destroyed it. If your camera fails. That's a hardware issue and is non related to the modifications you made so that would be covered by warranty. Atleast that's how warranty works here in Belgium.
It worked!
Thanks everyone for the help, It rooted successfully!
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?
you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA
JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?
discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?
crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly
Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.
Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though
How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.
discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
I Could Be Dead Wrong But..
epickid37 said:
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
Click to expand...
Click to collapse
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
RaiderWill said:
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
Click to expand...
Click to collapse
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Damn.. It's Been So Long..
epickid37 said:
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Click to expand...
Click to collapse
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
RaiderWill said:
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
Click to expand...
Click to collapse
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
A Virgin...
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
When It Comes To Huawei.. I'm A Virgin...
Every other phone I've seen, the O.T.A. will notify you that your system has been "Modified" and will not attempt the update.
When you root.. Your Phone Becomes Insecure.. and is vernable to Malware, Virus, Hacks and god knows what else.
O.T.A.'s are Signed Packages.. They Ain't Going To Da Hood To Do Business...
Keep it locked if you want everything on day 1.. Then you can Root to your hearts content.
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
epickid37 said:
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
Click to expand...
Click to collapse
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Ah, ok. Thank for your help!
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
MitchiePitchie said:
Hey guys, last week i wanna flash a custom rom on my SM-a520f/DS but my OEM unlock was missing,I thought i just had to wait for 7 days but it won't show even after 7 days
Now i flashed official stock rom and will try to wait again for 7 days, but if this doesn't work then imma bout to lose my mind.
What can i do if it doesnt oem unlock doesnt p
Appear even if you reflashed stock romm
Click to expand...
Click to collapse
Maybe a factory reset would help, I dunno...
TechGuyOnTechIT said:
Maybe a factory reset would help, I dunno...
Click to expand...
Click to collapse
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
MitchiePitchie said:
Just reflashed stock rom and waiting 7 days. I'll update if it works:fingers-crossed:
Click to expand...
Click to collapse
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
TechGuyOnTechIT said:
Well this SHOULD fix the issue. If not, then I suspect the phone's internal clock is messed and needs complicated repair, but this a very very very VERY rare occasion, and I doubt you don't have this issue.
My phone just flashed a ok TWRP, but after I accidentally restarted, the phone didn't put me in OEM jail. Talk about lucky!
Just wait 7 days, activate developer options, click unlock oem, flash twrp via odin and after that is done IMMEDIATELY hold power and plus so it doesn't get you back to oem jail. After you are in TWRP, try not to turn it off to keep the recovery, and either install a zip that removes the 7 day jail or a cudtom rom. If you don't have a microsd to transfer from your pc to your phone, just use adb sideload. If you have any questions, just reply!
Click to expand...
Click to collapse
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
MitchiePitchie said:
WAIT, so you need to wait 7 days before activating developer's option? Does that put you in prenormal rmm state? Because i already activated my developer's option, If thats the case then i already messed up
Click to expand...
Click to collapse
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
TechGuyOnTechIT said:
No, you haven't messed up! The 7 day jail doens't block you access to developer options, but doesn't let you enable OEM unlock. I was suggesting you should do this just to make sure you are not in the 7 day jail. Again, if you can check that option, then there is not a problem. Just try to have your jail patcher zip handy so you won't have to deal with this problem. Again, if you have any questions, just reply!
Click to expand...
Click to collapse
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
MitchiePitchie said:
Okay, the OEM unlock didn't showed up and my rmm state is still prenormal after 7 days even in flashing stock. I might retry this again in another rom carrier. I'm really at the end of my rope here
Click to expand...
Click to collapse
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
I'll try to flash the rom again and wait 7 days, I'll boot ip without sim and sd card first
TechGuyOnTechIT said:
Don't give up! Try to go to download mode, flash a complete Samsung rom (with bootloader, modem, recovery and rom). I guess you can find a stock samsung rom on google or via smart switch. Download mode only blocks installing THIRD PARTY ROMS, not the stock ones. Try that and give a reply.
Click to expand...
Click to collapse
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
MitchiePitchie said:
Man I already flashed stock rom and waited 7 days, I ain't doing that stuff again I'll just sell this phone if I don't find any other way.
Click to expand...
Click to collapse
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options, because any Samsung device SHOULD have the 7 day lift period. If you confirm that you don't see it, the only thing left to do is to contact a samsung expert. Don't feel embarrassed that you ask samsung for a third party thing, they must help you even though that may result in voiding your warranty.
Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
MitchiePitchie said:
I'll try reflashing a carrier rom (Globe) not a XTC (openline) rom and if this doesn't work then i dont know what will:fingers-crossed:
Click to expand...
Click to collapse
Samsung support centre could also help.
TechGuyOnTechIT said:
Seriously? Are you SURE you don't see OEM unlock in developer options...Honestly, this is a pretty uncommon issue :/
Click to expand...
Click to collapse
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Corbynista said:
I have the same issue. Started with Android 7, rooted phone, flashed Hades ROM v6 ( Android 8) which is fine, but I no longer see OEM Unlock in Developer options (presumably I did before installing Hades). Have tried the date fudge:
https://forum.xda-developers.com/samsung-a-series-2017/help/guide-oem-unlock-oreo-t3791774
more than once. No joy. Hades is fine, but I'd like to try the OneUI Android 9 ROM...
Click to expand...
Click to collapse
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
iloveoreos said:
If you are still on hades, the dev removed the OEM unlock toggle to prevent noobs from disabling it which would bootloop your phone and twrp would also not boot. Most if not all custom roms remove it. So you can flash Oneui
Click to expand...
Click to collapse
TechGuyOnTechIT said:
When you are on cfw, as the guy said, there is no need. The rom is third party, meaning it's not official, thus it remains unlocked. But if you are on stock rom, then the oem unlock will be shown.
Click to expand...
Click to collapse
I wondered if this was the case. Thanks to you both.
TechGuyOnTechIT said:
Samsung support centre could also help.
Click to expand...
Click to collapse
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
MitchiePitchie said:
that ain't an option for me since they dont really respond. You know any other option if it doesn't even show this week too?
i reflashed stock rom like 5 times now
Click to expand...
Click to collapse
Punch your phone, return it, and get another one.
SnowFuhrer said:
Punch your phone, return it, and get another one.
Click to expand...
Click to collapse
Nooooo! Don't do that! That would be a waste! Maybe its a bug. Try to flash twrp even though it doesn't show you kem unlock, and if that still doesn't work, give up trying systemless rooting and go full supersu by doing a one-click root (kingroot, etc). Maybe that helps. If it still not working, then I will finally recommend bailing and just getting another one . Sorry...