Hi, all. Please help me with some issues. Have Sonim XP5s dualsim gsm phone ATT locked.
1 Bootloader. Trying to unlock it.
*#*#2387#*#* activated USB debug. Set OEM unlock, but bootloader locked. fastboot unlock, fastboot oem unlock, fastboot flashing unlock do nothing. How i can unlock it?
2 Firmware. Does anyone have image to flash with QFIL? I try to flash empty one but QFIL say timeout and take no action. EDL started but ignore all requests. Bootloader issue?
3 SIM2 activation. Phone disable second SIM at all. Need correct firmware?
4 ATT unlock. How i can do it, with correct firmware installed?
5 Root. Kingroot, kingoroot no success. Custom recovery not found. Flashing\booting custom recovery is locked.
Thanks.
bumpity-bump
I have the same phone that I just bought and (sheepishly) just found out has wi-fi calling disabled by AT&T. That was a main reason for getting it, but unfortunately I went by the Sonim website's info and not AT&T's regarding that feature. Verizon's version has it enabled, but it's also much scarcer on the secondary market. The XP5800 doesn't seem to be a popular phone for tinkering judging by the lack of info on doing so.
Does anyone know if wi-fi calling could hypothetically be activated by rooting and then toggling some values, or is it more likely that the involved code was omitted entirely? I saw something to the former about tethering.
Bit_Basher said:
be activated by rooting and then
Click to expand...
Click to collapse
Still have found no rooting way. Bootloader locked, so no custom recovery can be used. Very unpopular phone, as you see, thread dead.
SpectralUA said:
Still have found no rooting way. Bootloader locked, so no custom recovery can be used. Very unpopular phone, as you see, thread dead.
Click to expand...
Click to collapse
Each Android can get rooted by means of SuperSU ZIP. Only requirement is to have successfully USB debugging option enabled in Android->Settings->Developer options. You install this ZIP via phone's stock recovery.
To access developer mode, google "developer mode sonim xp5s". Open article: kb.eschat.com "Open Developer Options Tab on Sonim XP5, XP5s or XP3...". The device will then open the Developer Options tab. Ensure the take bug report option is enabled, and that USB debugging is also enabled. You may also add a menu button to the Power tab for future access to this feature.
Be sure you use a clean SuperSU ZIP to avoid malware. Suggest getting one from the xda forum.
Hi. Is there any success with rooting or enabling second sim to working 2 sims together?
jwoegerbauer said:
Each Android can get rooted by means of SuperSU ZIP. Only requirement is to have successfully USB debugging option enabled in Android->Settings->Developer options. You install this ZIP via phone's stock recovery.
Click to expand...
Click to collapse
How i can do it? Stock recovery have no menu. /cache access denided from user. Putting update.zip do nothing without /cache/recovery/command. Did you know some trick to proceed install? ADB debugging enable, but no root rights there.
haikkk said:
Hi. Is there any success with rooting or enabling second sim to working 2 sims together?
Click to expand...
Click to collapse
Nothing.
Here are the firmware images for the Sprint XP5s
5SA.0.4-05-8.1.0-29.33.00_USER_PST.zip
Root has been achieved with Magisk!
ytagger said:
Root has been achieved with Magisk!
Click to expand...
Click to collapse
Is there any way to get Android Auto to work on the XP5s?
Hello All.
sorry for off topic, but can’t find anywhere.
does anybody know how to remove PIN on Sonim XP5s? Can’t access phone without entering PIN.
I would really appreciate for any help.
Thank you.
bkarshibaev said:
how to remove PIN on Sonim XP5s?
Click to expand...
Click to collapse
Recovery mode. Power + volUp long to show menu. Factory reset.
SpectralUA said:
Recovery mode. Power + volUp long to show menu. Factory reset.
Click to expand...
Click to collapse
Hello SpectralUA,
Does it really remove PIN?
I’m planning on buying Sonim XP5s and send it overseas. I just want to be 100% sure that Recovery mode will remove PIN.
Thank you.
bkarshibaev said:
Hello SpectralUA,
Does it really remove PIN?
I’m planning on buying Sonim XP5s and send it overseas. I just want to be 100% sure that Recovery mode will remove PIN.
Thank you.
Click to expand...
Click to collapse
Yes, it does, except if Factory Reset is blocked by Scout
ytagger said:
Yes, it does, except if Factory Reset is blocked by Scout
Click to expand...
Click to collapse
Is there way to check if Scout has restriction?
also, do you know which XP5s (AT&T, SouthernLinc, Sprint or Verizon) has wifi calling enabled and 2nd sim card slot is unlocked? I mean unlocked version of those 3 carriers.
Thank you.
bkarshibaev said:
Is there way to check if Scout has restriction?
Click to expand...
Click to collapse
Not if the device is PIN locked and you don't know it, obviously .
If it's open, just try to reset the phone from the regular menu and you'll see if it's restricted
bkarshibaev said:
2nd sim card slot is unlocked?
Click to expand...
Click to collapse
2nd sim usable without 1st. Found no way to enable both at same time.
Maybe anyone know how to dualsim (standby mode, etc) this unit?
ytagger said:
Here are the firmware images for the Sprint XP5s
5SA.0.4-05-8.1.0-29.33.00_USER_PST.zip
Click to expand...
Click to collapse
The link is not working. Do you have a different one?
Related
Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.
I'm new to this, and I just wonder if I can unlock a phone and make it usable again if the original owner doesn't know his gmail password? I would be happy to try the root option, but is that the only option at this point?
baldoomba said:
I'm new to this, and I just wonder if I can unlock a phone and make it usable again if the original owner doesn't know his gmail password? I would be happy to try the root option, but is that the only option at this point?
Click to expand...
Click to collapse
Hint: Google FRP bypass + your model.
In any case, if owner forgot his password it should be fairly easy to retrieve
You can, it depends on the model but almost all model enter in recovery by shutting down the phone and then press volume down and power button, if it's samsung then home button too. After you enter the recovery just factory reset
PeterJ74 said:
You can, it depends on the model but almost all model enter in recovery by shutting down the phone and then press volume down and power button, if it's samsung then home button too. After you enter the recovery just factory reset
Click to expand...
Click to collapse
Ok thanks for your help.
Also, do you know if the textnow phones are able to be used under another carrier like AT&T? Does this require a root?
baldoomba said:
Ok thanks for your help.
Also, do you know if the textnow phones are able to be used under another carrier like AT&T? Does this require a root?
Click to expand...
Click to collapse
root doesn't unlock anything but access to all of the files in the phone, the system files, similar to the windows folder in microsoft windows. it's not some kind of magic, you still need to know the password of the phone if you want to use it.
baldoomba said:
I'm new to this, and I just wonder if I can unlock a phone and make it usable again if the original owner doesn't know his gmail password? I would be happy to try the root option, but is that the only option at this point?
Click to expand...
Click to collapse
Use this link to know ways to unlock
http://www.yogadz.com/how-to-unlock-android-pattern-lock-without-factory-reset/
This will also unlock without having to do a factory reset
Regards milkyway3
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
What variant s6 do you have?
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
It's not that easy, the option is called "Allow OEM unlocking" which I already have turned on. All that option does is allow the bootloader to be unlocked.
sofir786 said:
What variant s6 do you have?
Click to expand...
Click to collapse
920T Unlocked.
I know. A rare S6 model, bought in Panama.
iLoveMuffinz said:
920T Unlocked.
I know. A rare S6 model, bought in Panama.
Click to expand...
Click to collapse
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
Click to expand...
Click to collapse
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
iLoveMuffinz said:
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
Click to expand...
Click to collapse
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
Click to expand...
Click to collapse
Thanks for pointing that out. I don't know why I expect people to be grateful on XDA, just because someone tries to help them.
Using a Mac, you flash files using Heimdall: http://glassechidna.com.au/heimdall/
Ok so I think I'm good to go:
I attached some screenshots checking if everything is correct. Also, is http://glassechidna.com.au/heimdall/ the correct and official site to get Heimdall? And my device's build is G920TUES5DQD1 which was released a few days ago, and I'm not sure if the CF auto root file was based on an earlier update. Will I still be able to use it?
is g920v bootloader unlockable?
is it possible to downgrade thanks to this oem unlock?
sofir786 said:
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
Click to expand...
Click to collapse
My phone has the front tripped, is there any way to reset it? I can't even figure out how to pull up the system info, I can pull up the recovery menu and hard reset but I don't know how to, if possible, reset the front. Any advice?
Sent from my LGE LG-LS777 using XDA Labs
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
Install Windows in a Virtual Machine, Use ODIN to flash TWRP, flash Magisk.
help with unlock bootloader s6 920v
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
joeknz said:
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
Click to expand...
Click to collapse
As far as I know, and what has been the fact since the release of the 920V, there's has been no known case where the bootloader has been unlocked. Due to Verizon's restrictions, the S6 is hardlocked. The only way that it might ever be unlocked is if someone reverse engineers the bootloader software, creating an unlocked version that can be flashed, and that will still pass the phone's security checks. I wouldn't hold your breath for it though, because it's been 3 years and no solution yet.
i had same issues
i have been trying to unlock my s6 smg 9208 everything that i tried failed need really your help i can't use my keyboard and mouse ????
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
mzayd786 said:
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
Click to expand...
Click to collapse
That is incorrect, what you are referring to is carrier locked. and is done to most phones sold in the US. Most can be unlocked once fully paid for and after 90 days of service.
Bootloader lock has nothing to do with sim cards at ALL!! It does have everything to do with being able to install other roms and firmware via non official sources.
Sprint Samsung Galaxy S6 model SM g920p FRP lock is blocking me from enabling OEM unl
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
Hello to you super techs I'm a newbie to this hope i'm not posting out of place but my question is how do I set up my Windows PC with ADB to use ADB fastboot unlock to unlock my bootloader because FRP protection has me locked out of the phone and I can't use the build number 2 unlock OEM or is that even possible I have been searching the web and XDA 2 try and find a way to open this phone I bought for myself for Christmas not knowing anything about a phone being FRP locked to a Google account is it possible to unlock this phone so that I can Flash it and maybe be able to use it I checked the IMEI number and it comes back good so say Sprint customer service but they couldn't help me with the FRP because I bought the phone second hand could you guys please point me in the right direction if I'm in the wrong spot posting my apologies to the thread host
So I'm trying to unlock my bootloader to root my phone with Magisk (which also patches VBmeta, which is important for me to do). Originally the OEM unlock option was not appearing in my phone's settings, but I fixed that with the date hack (set the phone's clock to 2022-05-01 instead of 2022-08-05). But now when I reboot into the first stage of download mode, the option to unlock the bootloader does not show up, it just has the option to reboot, enter download mode, or show the barcode. When I enter download mode, the KB status shows as ACTIVE. The CSC I'm using is BTU and I'm on the latest CVG2 firmware of Android 12 (OneUI 4.1).
Any ideas?
Anything?
Make sure that USB debugging in developer options is enabled.
Turn off your device.
Hold volume up and down buttons and keep holding them.
While holding them, connect your smartphone to a PC using USB cable.
There will be a warning message.
"... to continue press volume up ..."
Don't just press volume up button, but keep holding it.
Zdrawko0o said:
Make sure that USB debugging in developer options is enabled.
Turn off your device.
Hold volume up and down buttons and keep holding them.
While holding them, connect your smartphone to a PC using USB cable.
There will be a warning message.
"... to continue press volume up ..."
Don't just press volume up button, but keep holding it.
Click to expand...
Click to collapse
Yeah I do that and the unlock bootloader option doesn't show up. Pressing and holding volume up goes into download mode, as described in the original post...
Can't help you, sorry.
Zdrawko0o said:
Can't help you, sorry.
Click to expand...
Click to collapse
No worries lol
Is the A526B (Snapdragon) as sold in the UK using BTU as the CSC considered a US device?
CapAdamT said:
Is the A526B (Snapdragon) as sold in the UK using BTU as the CSC considered a US device?
Click to expand...
Click to collapse
It's not. The U.S. variant is A526U and U1.
ShaDisNX255 said:
It's not. The U.S. variant is A526U and U1.
Click to expand...
Click to collapse
Did you try flashing other firmware from another region?
Zdrawko0o said:
Did you try flashing other firmware from another region?
Click to expand...
Click to collapse
Odin will only let you flash U and U1 firmware on them.
ShaDisNX255 said:
Odin will only let you flash U and U1 firmware on them.
Click to expand...
Click to collapse
He said that his device is SM-A526B, not SM-A526U1.
Zdrawko0o said:
He said that his device is SM-A526B, not SM-A526U1.
Click to expand...
Click to collapse
Ummmm did you check the post I was replying to. The question was, is this device a U.S. variant and I said no, the U.S. variant models are U and U1.
ShaDisNX255 said:
Ummmm did you check the post I was replying to. The question was, is this device a U.S. variant and I said no, the U.S. variant models are U and U1.
Click to expand...
Click to collapse
Yep. So he can flash another firmware.
Zdrawko0o said:
Yep. So he can flash another firmware.
Click to expand...
Click to collapse
Ah Ok, I see I misunderstood your question. I assumed you asked me can you flash firmware from another region on U.S. variant devices because you quoted my post where I mentioned the U and U1 variants.
So yeah, any region can be flashed on SM-A526B as long as it's the same model.
CapAdamT said:
Is the A526B (Snapdragon) as sold in the UK using BTU as the CSC considered a US device?
Click to expand...
Click to collapse
BTU doesn't relate to US at all. BTU is just a region code, code for UK.
CapAdamT said:
Is the A526B (Snapdragon) as sold in the UK using BTU as the CSC considered a US device?
Click to expand...
Click to collapse
I'm assuming this question was asked because you weren't getting the option to unlock the bootloader in download mode. Probably the date code wasn't working properly. What I suggest doing is flashing stock firmware with Odin. Completely wipe the phone. Then when you're setting up the phone for the first time, connect to a WiFi network on the setup screen. I've noticed that sometimes OEM Unlock gets bugged when this is skipped and it seems that topjohnwu also caught on to this because he explicitly includes it in his installation instructions of Magisk
Quote from Magisk Installation on Samsung devices:
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Click to expand...
Click to collapse
topjohnwu mentions Internet during the setup but I think it's worked for me better when I connect to a Wi-Fi network.
So after completely wiping the phone with Odin I suggest you connect to WiFi on setup and then check your developer settings again. Hopefully, OEM Unlock will be there without the need to do the date trick.
ShaDisNX255 said:
What I suggest doing is flashing stock firmware with Odin. Completely wipe the phone. Then when you're setting up the phone for the first time, connect to a WiFi network on the setup screen.
Click to expand...
Click to collapse
I actually tried that a while back... Had it connected to the internet using mobile data as well as WiFi, no luck. I'll try again in a few days time once my phone has been repaired by Samsung (warranty).
CapAdamT said:
I actually tried that a while back... Had it connected to the internet using mobile data as well as WiFi, no luck. I'll try again in a few days time once my phone has been repaired by Samsung (warranty).
Click to expand...
Click to collapse
Well, that warranty repair took longer than expected. I can now report that I am still facing the same issue. I tried setting it back up while connected to WiFi (speed shouldn't be an issue, I get gigabit speeds and on WiFi I've seen 400mbps).
After checking the bit in the download mode menu, seeing that there is no `unlock bootloader` option, and then booting into Android again, the setting just disappears again, after having enabled it before shutting the phone down.
Any ideas?
CapAdamT said:
Well, that warranty repair took longer than expected. I can now report that I am still facing the same issue. I tried setting it back up while connected to WiFi (speed shouldn't be an issue, I get gigabit speeds and on WiFi I've seen 400mbps).
After checking the bit in the download mode menu, seeing that there is no `unlock bootloader` option, and then booting into Android again, the setting just disappears again, after having enabled it before shutting the phone down.
Any ideas?
Click to expand...
Click to collapse
This is really strange, but I just wanted to add that I'm a U1 US variant owner that was just now looking into rooting and I came across this thread.... before even trying anything I'm already noticing I too have no OEM unlocking option in my dev settings. Really odd. I guess there's the very remote possibility my BL is already unlocked as I bought it used off eBay but I doubt it. I've run several OTAs so that seems very unlikely lol.
For me root is only desired to run Viper4Android so I'm not even 100% sure I want to bother with that now if it's going to be that steep an uphill battle.
---Edit--- Sorry, nevermind I'm dumb, the U1 Us models just aren't BL unlockable. Saw in another thread. All I want is root though, I don't need to flash roms or TWRP usage. Anyone know if that's still doable?
benjmiester said:
All I want is root though, I don't need to flash roms or TWRP usage. Anyone know if that's still doable?
Click to expand...
Click to collapse
That still needs an unlocked BL...
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.