HI there, so I have a Galaxy S6 G920AZ, and recently I checked if there was any progress in rooting this device, I found in the Chainfire(https://autoroot.chainfire.eu/) site that It can be rooted but must be done with the build: G920AZTUU6DQF3, so I flashed that build, and so far so good, the problem is that when I try to flash the cf-auto-root with odin it says fail, and doesn't root it obviously. I have USB Debug enabled, but there is no "ALLOW OEM UNLOCK" under developer settings.
Can someone tell me if I missunderstood something, or maybe the g20az isn't rootable at all?
Thank you in advance
elflois said:
HI there, so I have a Galaxy S6 G920AZ, and recently I checked if there was any progress in rooting this device, I found in the Chainfire(https://autoroot.chainfire.eu/) site that It can be rooted but must be done with the build: G920AZTUU6DQF3, so I flashed that build, and so far so good, the problem is that when I try to flash the cf-auto-root with odin it says fail, and doesn't root it obviously. I have USB Debug enabled, but there is no "ALLOW OEM UNLOCK" under developer settings.
Can someone tell me if I missunderstood something, or maybe the g20az isn't rootable at all?
Thank you in advance
Click to expand...
Click to collapse
i have the same problem, do you found a solution?
I didn't found a solution. I saw that some people had same problem with a motorola, and they did a factory reset, cleared cache and then OEM unlock apeared, but I tried that with no luck , I hope it works for u
I have USB Debug enabled, but there is no "ALLOW OEM UNLOCK" under developer settings.hellp
Related
What's up guys, I purchased a Nexus 6 during the black friday deal on Amazon for $200.
I tried unlocking my Nexus 6 via WugFresh's RootToolkit. Unfortunately it doesn't seem to be working properly, the adb and fastboot both connect and everything works as it should (prompt wise) but when I received the option to confirm whether I want to unlock my bootloader, after clicking yes it goes through the reboot but nothing happens. I'm back to where I started (nothing wiped, all apps still there, nada).
USB Debugging is enabled, app verification is off (tried it with both on and off) and enable OEM unlock is also enabled.
Drivers are properly configured and any other discrepancies have been removed via the RootToolkit. Not quite sure what the issue is, I'd appreciate any help on the matter!
Also the bootloader status is displayed like this: Bootloader - Locked [Status Code: 2]
Other info:
Currently on 6.0
Build number: MRA58N
Android Security Patch level: November 1st, 2015
Thanks in advance guys.
Necrodox said:
What's up guys, I purchased a Nexus 6 during the black friday deal on Amazon for $200.
I tried unlocking my Nexus 6 via WugFresh's RootToolkit. Unfortunately it doesn't seem to be working properly, the adb and fastboot both connect and everything works as it should (prompt wise) but when I received the option to confirm whether I want to unlock my bootloader, after clicking yes it goes through the reboot but nothing happens. I'm back to where I started (nothing wiped, all apps still there, nada).
USB Debugging is enabled, app verification is off (tried it with both on and off) and enable OEM unlock is also enabled.
Drivers are properly configured and any other discrepancies have been removed via the RootToolkit. Not quite sure what the issue is, I'd appreciate any help on the matter!
Also the bootloader status is displayed like this: Bootloader - Locked [Status Code: 2]
Other info:
Currently on 6.0
Build number: MRA58N
Android Security Patch level: November 1st, 2015
Thanks in advance guys.
Click to expand...
Click to collapse
Stop using root kits and learn to do things properly. It is as simple as changing a setting and then doing one command prompt imput. A search will show you what you need to know.
zelendel said:
Stop using root kits and learn to do things properly. It is as simple as changing a setting and then doing one command prompt imput. A search will show you what you need to know.
Click to expand...
Click to collapse
Already tried running from the terminal, no luck.
Necrodox said:
Already tried running from the terminal, no luck.
Click to expand...
Click to collapse
Did you change the setting in developer settings to allow bootloader unlocking?
zelendel said:
Did you change the setting in developer settings to allow bootloader unlocking?
Click to expand...
Click to collapse
Yup, mentioned that in my original post.
I'm going to uninstall all the drivers and reconfigure everything, maybe that'll help.
Necrodox said:
Yup, mentioned that in my original post.
I'm going to uninstall all the drivers and reconfigure everything, maybe that'll help.
Click to expand...
Click to collapse
What was the error the command prompt gave you?
zelendel said:
Did you change the setting in developer settings to allow bootloader unlocking?
Click to expand...
Click to collapse
zelendel said:
What was the error the command prompt gave you?
Click to expand...
Click to collapse
No error, but I just figured out what I've been doing wrong. Had such a herp derp moment. One of the guides I read explained that volume up was the button to press for continuing the bootloader unlock, upon checking the phone screen both volume down and up will cancel the operation. I should have double checked instead of trusting a guide so mindlessly.
I wasn't receiving any error codes and it was rebooting as if it was completing the operation so I assumed everything was working as it should and something else was the problem. Lol that's what I get for not touching the android terminal for two years.
Thanks for the replies!
I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Just to clarify, are you actually attemping to unlock it? You have to first enable that option in developer settings, but you still have to put the phone in bootloader mode and run the command "fastboot oem unlock", then use the buttons on the phone to confirm it. I think all your data wipes first time you unlock your bootloader too so just be careful.
SilverSix said:
I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Click to expand...
Click to collapse
Depending the Android build installed, sometimes the option has been greyed out. Don't know why...
You said you tried to get the "OEM unlock" slider working... But did you try issuing the unlock command in bootloader?
Good luck...
Yeah, I'm aware it wipes your device. Also, don't burn me but I was using a Toolkit to start the process but I just gave up and did it the old fashioned way. After restarting into bootloader and sending the fastboot command it prompted the question to unlock it, so everything went smoothly.
Somewhere I had read that Android purposely locks OEM unlocking after n reboots, and I thought I was completely out of luck, but everything went smoothly. Thanks for your time!
Dear all,
i got into trouble with a frind of mine and had to give him back his old Motorola G2 (XT1072).
First of all i have removed all data from the device and then made a factory reset. I think this was the biggest failure of all.
After turning power on, the phone is asking for a registered google mail account. As it was his google mail account i gave him back the phone and was wondering as he called me a few days later and said "for such broken devices i have no use". After researching a little more i found out that he had forgotten all login info for this account so there was no chance to get past this step in the phone. So i got my phone back, but unfortunately useless after all and he was laughing about my pitty.
I have tried several ways (with adb and sdk) but always had to stop at the point where it says that "Allow OEM Unlock" was not enabled. As faar as i remember i never ever went to the developer options or have enabled the OEM Unlock on this phone.
Do you know a way how i can enable USB debugging or the OEM unlock via the adb mode? I have already tried the motorola website to generate the unlock code for the bootloader, but oh wonder... "Allow OEM Unlock has not been enabled" :crying:
For some former Samsung phones i used to flash a stockrom with ODIN. Is there a chance to do this with the G2 also?
Thank you so much for all your comments and help in recovering my beloved motorola G2 XT1072
Kind regards
Sebastian
Pepask2000 said:
Dear all,
i got into trouble with a frind of mine and had to give him back his old Motorola G2 (XT1072).
First of all i have removed all data from the device and then made a factory reset. I think this was the biggest failure of all.
After turning power on, the phone is asking for a registered google mail account. As it was his google mail account i gave him back the phone and was wondering as he called me a few days later and said "for such broken devices i have no use". After researching a little more i found out that he had forgotten all login info for this account so there was no chance to get past this step in the phone. So i got my phone back, but unfortunately useless after all and he was laughing about my pitty.
I have tried several ways (with adb and sdk) but always had to stop at the point where it says that "Allow OEM Unlock" was not enabled. As faar as i remember i never ever went to the developer options or have enabled the OEM Unlock on this phone.
Do you know a way how i can enable USB debugging or the OEM unlock via the adb mode? I have already tried the motorola website to generate the unlock code for the bootloader, but oh wonder... "Allow OEM Unlock has not been enabled" :crying:
For some former Samsung phones i used to flash a stockrom with ODIN. Is there a chance to do this with the G2 also?
Thank you so much for all your comments and help in recovering my beloved motorola G2 XT1072
Kind regards
Sebastian
Click to expand...
Click to collapse
Bump
Any solutions?
I have the same issue.
lo solucionaste ???
same issue here..
-no developer options
-no oem unlock
-reset by seller without known google data (original packaging is available)
-fastboot flash with stock rom is working, but also requests last google account after flashing
seller didnt recognize google settings at all
is there any chance without known google data?
Hello XDA, I hope that you could help me troubleshoot my Note 8 (N950F).
So it's been 7 days and oem unlock toggle has finally appeared.. The only issue is it is greyed out and unselectable.
When I got this device I wasn't able to see developer options by pressing build number (though I got the notification that it was enabled), I was only able to access the setting by downloading an app short cut for it via the play store and on initial launch it said developer options are disabled. But then second launch it worked. Idk if this is significant but maybe the country this is meant for disabled it? Regardless of the sim card being in/out the phone, it is still greyed out. Also, I was able to factory reset the phone through the settings after downloading an OTA (I did this in hopes of developer options being enabled about a week ago.)
I tried to boot into download mode but it seems I can't boot into it (following the steps only lead to a normal reboot, and when I select that option from the stock recovery or through adb, it only boots the phone up normally. I purchased the phone off of swappa, in brand new/like new condition. Any ideas? Thank you for your help.
Edit: added screenshots.
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Eddygraphic said:
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Click to expand...
Click to collapse
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Negroid said:
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Click to expand...
Click to collapse
That's weird I've never seen a Galaxy that can't enter download mode.
Eddygraphic said:
That's weird I've never seen a Galaxy that can't enter download mode.
Click to expand...
Click to collapse
Exactly. That's why I'm so concerned.
Have you logout your Samsung Account and Google account？sorry for my poor English.:crying:
Do you use any of the KNOX stuff? Did you do any factory reset?
Can you "clear data" on "settings" app? this would make the "developer option" menu hidden again. Then re-show it by tapping build number numerous time again. Hoping that OEM is now editable.
Hi, could you solve this problem? My Note 8 has the same problem and I have not found any solution :llorando:.
I would appreciate it if you can help me.
Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Hey there! been lurking xda for ages but your post just made me register! Thanks a lot for sharing mate.
I just downloaded the update and tried this method, worked fine. Btw there's a new security patch as latest update (5/19), didnt bother doing it as they could have patched it probably.
So, i tried flashing twrp and noticed it still wouldn't let me and flashing get_unlock_ability returns 0. Did you manage to get past this?
This actually works. Havent flashed anything yet, as I'm scared of bricking it.
I just love the good old days when I had the Tmobile G2x with the Nvidia chip, flashed the darn thing so many times, even bricked it numerous times, but I was able to go into recovery and reflash it again. That phone was "Flash and Brick Proof"
thanks for sharing, spent countless hours trying to fix with usb driver setups and cmd lines from other tutorials.
question is what's next?
That's a dummy command,
You still need to properly Unlock it, I'm afraid all the options are paid service
Sent from my Xperia 1 using XDA Labs
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
alexben_007 said:
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
Click to expand...
Click to collapse
Try fastboot oem unlock
Mod edit - translated by https://www.deepl.com/translator:
Unlock the bootloader
****************************
Разблокировать загрузчик -358536084114397 -nokia5_nd1
I am N.E.E.T said:
Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Click to expand...
Click to collapse
pretty usefull tip bro, it worked on my nokia 6 TA-1000