I don't know if it's for real. And I don't know if I did it today or a few days ago. Nonetheless, according to developer options, I unlocked the bootloader on my Snapdragon S7. So I need some assistance to determine if this is the case. I have no idea how to tell if I did unlock it and I've no idea where to go or what to do from here.
Yes. You can install twrp now from Snapdragon development section
I ended up breaking the screen so i need to get it replaced. Here are the steps I took before i broke it:
1. Make sure OEM unlock is toggled on
1. Oreo, eng rooted, I Changed in build.prop, build type to userdebug.
2. Added 3 lines in build prop:
Code:
ro.oem_unlock_supported=1
sys.oem_unlock_allowed=1
ro.boot.flash.locked=0
3. Factory reset through recovery.
If that works i have a theory as to why. With an engineering kernel, it probably already allowed it, we just didn't know. These are legitimate build prop codes and are referenced the android source code. This has potential to work on other devices where you have the ability, without root, the manipulate the sys values and add some through adb shell using 'setprop'. I was able to add sys.oem_unlock_allow to a friends Alcatel.
That toggle has always been available to SD users, it's just never actually done anything. It's a switch not connected to anything.
Beanvee7 said:
That toggle has always been available to SD users, it's just never actually done anything. It's a switch not connected to anything.
Click to expand...
Click to collapse
Yes i know it's always been there. But The toggle never said the bootloader was already unlocked.
I'd be very surprised if you were the first person ever to unlock a SD device, and that of all methods it was accidental.
I find it more believable you accidentally toggled this in the past and forgot.
You could always try the files from the Chinese variant, but prepare for bootloops.
Beanvee7 said:
I'd be very surprised if you were the first person ever to unlock a SD device, and that of all methods it was accidental.
I find it more believable you accidentally toggled this in the past and forgot.
You could always try the files from the Chinese variant, but prepare for bootloops.
Click to expand...
Click to collapse
I wouldn't be that surprised. I always suspected it was stuck in limbo waiting for something to give it the ok to unlock, especially geven it being persistent. If the toggle was truly inoperable, it wouldn't do anything and a box wouldn't pop up. Given the engineering kernel, this unlocking seems very possible. From Android:
"The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock. ro.oem_unlock_supported should be set to "0" if flashing unlock is not supported on the device or "1" if flashing unlock is supported.
If the device supports flashing unlock (i.e. ro.oem_unlock_supported = 1), then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked (or the /firmware/android/flash.locked DT property) to "1" if locked or "0" if unlocked."
Click to expand...
Click to collapse
https://source.android.com/devices/bootloader/unlock-trusty
so, have you tried to flash twrp via odin yet? which device do you have?
Im on oreo too and mine says "Allow the phone to be OEM unlocked" my device is a 935V
Maxissc said:
so, have you tried to flash twrp via odin yet? which device do you have?
Im on oreo too and mine says "Allow the phone to be OEM unlocked" my device is a 935V
Click to expand...
Click to collapse
Not until i can get the screen fixed unfortunately. Just my luck. G930T to a G930U.
DragonFire1024 said:
I ended up breaking the screen so i need to get it replaced. Here are the steps I took before i broke it:
1. Make sure OEM unlock is toggled on
1. Oreo, eng rooted, I Changed in build.prop, build type to userdebug.
2. Added 3 lines in build prop:
Code:
ro.oem_unlock_supported=1
sys.oem_unlock_allowed=1
ro.boot.flash.locked=0
3. Factory reset through recovery.
If that works i have a theory as to why. With an engineering kernel, it probably already allowed it, we just didn't know. These are legitimate build prop codes and are referenced the android source code. This has potential to work on other devices where you have the ability, without root, the manipulate the sys values and add some through adb shell using 'setprop'. I was able to add sys.oem_unlock_allow to a friends Alcatel.
Click to expand...
Click to collapse
Im about to try your procedure. i'll update my results
edit: After applying the build.prop lines and rebooting (didn't do factory reset) my OEM unlock switch now says "Bootloader is already unlocked"
Im wondering if that is because the bootloader got really unlocked, or if it's because of any of the added lines and it's just text
edit2: tried to flash twrp via odin 3.13 3B and it fails
Maxissc said:
I ended up breaking the screen so i need to get it replaced. Here are the steps I took before i broke it:
1. Make sure OEM unlock is toggled on
1. Oreo, eng rooted, I Changed in build.prop, build type to userdebug.
2. Added 3 lines in build prop:
Im about to try your procedure. i'll update my results
edit: After applying the build.prop lines and rebooting (didn't do factory reset) my OEM unlock switch now says "Bootloader is already unlocked"
Im wondering if that is because the bootloader got really unlocked, or if it's because of any of the added lines and it's just text
edit2: tried to flash twrp via odin 3.13 3B and it fails
Click to expand...
Click to collapse
Damn. Perhaps its the version of TWRP. I guess we'll have to wonder until something else comes along.
case closed.
Maybe someone needs to build twrp for our fevice for it to work
maXDAmn said:
case closed.
Click to expand...
Click to collapse
Not really. I didn't expect nor did I think the experimental TWRP to work.
DragonFire1024 said:
Not really. I didn't expect nor did I think the experimental TWRP to work.
Click to expand...
Click to collapse
Just to confirm I tried this and got the same results I could not flash twrp with odin(none of the versions worked) So I installed the twrp img with the official twrp app and it failed to boot into twrp.
i would really like to try this, but i dont really understand the instructions^^
could someone put the instructions down once again?
tko said:
i would really like to try this, but i dont really understand the instructions^^
could someone put the instructions down once again?
Click to expand...
Click to collapse
Make sure OEM unlock enabled in settings.
Add to build.prop:
ro.oem_unlock_supported=1
sys.oem_unlock_allowed=1
Factory reset
You also could try adding this to build.prop:
ro.boot.verifiedbootstate=0
Like any mods, be prepared for the potential to brick. Im not responsible for anything that breaks.
Good news fellas! TWRP files for snapdragon devices is avaiable here TWRP files for Snapdragon so if anyone knows how to compile this we good.
Well, I'm erring on the side of "There's no way it was THIS simple all along" and assuming it means nothing, but still...it's interesting, I'll give it that.
FWIW, I can't seem to replicate the "Bootloader Is Already Unlocked" message for some reason. I've got SM-G935R4 (US Cellular S7 Edge, though these are sold unlocked straight out of the box so the carrier is more like a technicality...) and I'm still running Nougat. What I get is a greyed-out box, switched to "On" and not adjustable, with the normal "Allow the device to be OEM unlocked" text still present (but also greyed out). I also didn't factory reset, just a few reboots.
I added all four lines suggested here (the original three, plus "ro.boot.verifiedbootstate=0") and found that A). the ro.boot.verifiedbootstate one doesn't have any discernible effects from a purely visual standpoint, and B). If I remove/comment-out the "ro.boot.flash.lock" line, the ability to switch OEM Unlock On/Off returns and the setting isn't greyed out.
Does any of that matter or mean anything? Hell if I know, I'm just chiming in.
lugnut2099 said:
Well, I'm erring on the side of "There's no way it was THIS simple all along" and assuming it means nothing, but still...it's interesting, I'll give it that.
FWIW, I can't seem to replicate the "Bootloader Is Already Unlocked" message for some reason. I've got SM-G935R4 (US Cellular S7 Edge, though these are sold unlocked straight out of the box so the carrier is more like a technicality...) and I'm still running Nougat. What I get is a greyed-out box, switched to "On" and not adjustable, with the normal "Allow the device to be OEM unlocked" text still present (but also greyed out). I also didn't factory reset, just a few reboots.
I added all four lines suggested here (the original three, plus "ro.boot.verifiedbootstate=0") and found that A). the ro.boot.verifiedbootstate one doesn't have any discernible effects from a purely visual standpoint, and B). If I remove/comment-out the "ro.boot.flash.lock" line, the ability to switch OEM Unlock On/Off returns and the setting isn't greyed out.
Does any of that matter or mean anything? Hell if I know, I'm just chiming in.
Click to expand...
Click to collapse
No idea. This does tell us a bit though. OEM toggle isn't disabled. Has anyone who tried this do a factory reset?
Related
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.
There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.
plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.
Hi,
I have once rooted my google pixel, but I changed my mind, and decided to unroot it and lock the bootloader.
I chose "lock" in the twrp menu, and I entered an endless loop.
Now the bootloader is locked and won't boot. The phone just splashes the initial screen and off, a few seconds after that, splashes the screen, and off,.....repeatedly. It looks like as soon as the initial "GOOGLE" screen appears, the phone resets itself.
I turned on with the volume down button on, and connect to the desktop computer (I use linux with adb and fastboot installed which work perfectly) and enter "fastboot flashing unlock", but it returns
Code:
$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.009s
I also tried to enter recovery mode, but it began to splash initial screen on and off again.
How can I recover from this situation?
Thanks in advance!
edit:
"fastboot flash recovery twrp-3.3.0-0-sailfish.img" now returns like this.
Code:
$ fastboot flash recover twrp-3*img
Sending 'recover' (31000 KB) OKAY [ 0.892s]
Writing 'recover' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.074s
edit2:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Thanks. I'll give it a try. I'm almost abandoning.....
junglism93 said:
Have a search using "bricked pixel locked bootloader" and trawl through the threads it throws up for workarounds etc. Some people have had some success depending on what the device was running but it's usually a non recoverable scenario.
Click to expand...
Click to collapse
I tried it now. Most of the procedures were fine, but the important parts (write .img) failed. I attach the logfile. I abandoned....
maverick6664 said:
Looks like I unchecked "OEM UNLOCK" in Development Option and locked......can I recover from this?
Click to expand...
Click to collapse
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
matusala said:
I am on Android Q beta 5 now and i do not have that option in the development options at all.
I also have Nexus 3, 4 & 5 and i played so much with them i can't even remember. Never had any problems. I have repartitioned them, changed mac addresses and many things but they never bricked. Do i have to worry about google pixel when i'll unlock bootloader? I got it about 3-4 days ago. I thought they are as cool to play with as Nexus 4 & 5 were. Is it not right?
Click to expand...
Click to collapse
I've learned. "Don't root. Don't unlock bootloader."
@matusala you can unlock the bootloader and flash stuff as you did on the nexus line of devices. I'm on Q beta 5 with bl unlocked, I've had lineage running on it for a while and also had magisk etc installed. The key with these pixel A/B slot devices is that your system must be 100% stock before relocking the bootloader. If it is not It will end up bricked as you will no longer have a working boot image or recovery as they are in the same partition. The rule is to never relock the bootloader unless you are 100% sure that your system is 100% back to full stock.
I certainly won't be re locking my bootloader, ever!
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
matusala said:
@junglism93 How did you unlock on Q beta 5? There is no "OEM UNLOCK" option in Development Options in here. Do i have to just run fastboot flashing unlock and that's it?
I know this pixel A/B slot thing. My router has exactly same layout and when i flash system on it i get to choose where to flash. I can have different version in A/B slot of my router. Is on google pixel the same? Do you have to choose which slot to flash? Can you have custom rom on A slot and full stock rom on B slot?
Click to expand...
Click to collapse
I unlocked my bootloader back on stock pie, i have it on mine but it's greyed out as already unlocked so no idea on that one! My knowledge on A/B slot ain't great, it's just what I've read on here re the pixel bricking scenario so I didn't do the same when I unlocked my bootloader etc. I doubt running a separate ROM on each slot works as when you perform an update it will write to slot a or b (the slot you aren't using) and then hop onto the updated slot upon reboot, alsoif the update borks you can roll back to the previous slot and still have a working system.
That's about as far as my knowledge of it goes mate
Leaving the bootloader unlocked doesn't void the warranty or things like that, also it's a life saviour if *anything* goes wrong, even with official updates. Why not leaving that on?
The lesson here is not "don't root" or "don't unlock the bootloader", cause with an unlocked bootloader you can recover from pretty any kind of software malfunction.
Unfortunately, with a locked bootloader I've never seen anyone succesfully recover the device, cause you cannot send commands.
maverick6664 said:
I've learned. "Don't root. Don't unlock bootloader."
Click to expand...
Click to collapse
Hmmm......correction.
I would say:
"Root with caution. Otherwise don't root."
Rooting doesn't necessarily cause a trouble. Usually it helps. But my Google Pixel used to show alert screen message upon every boot. It's a bit messy.
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.
It seems these pixel phones are garbage compared to nexus line. Those were so much better!
matusala said:
@TENN3R I have Android Q beta 5 on my pixel and i can't unlock bootloader. OEM unlock is not in my developer options menu. How can i unlock it's bootloader?
I tried unlocking and now i see that option in developer options, but it's greyed out and i can't press it. What can i do.!
Click to expand...
Click to collapse
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
TENN3R said:
I think I read somewhere in the android beta subreddit that is a Q beta related problem, and in Pie should work.
How did you unlock it since it wasn't there? Is the toggle grayed out in "off" position or "on"? Cause if it's enabled than you're ok
Click to expand...
Click to collapse
I followed this guide and it worked. It unlocked my bootloader. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Now option is greyed out again in "off" position but it says "Bootloader already unlocked"
Maybe i got verizon model but in cell-unlocked state, because seller had written that it's unlocked. He meant provider lock of course.
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
junglism93 said:
@matusala Happy days mate, have fun and remember the first rule of pixel club 'Never re lock the bootloader'
Click to expand...
Click to collapse
Good luck @matusala from me also, and don't give in the first "Don't keep bootloader unlocked' alert screen!! Otherwise you might fall into a bad luck "bricked pixel" like me!
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
Nice to hear that. It was a good lesson to me. I have two xperia's (after google pixel dies, I bought one.) Somehow xperia's are not re-lockable. It is also mentioned in Sony Xperia forum. I guess it must be a warning from Sony. :laugh:
matusala said:
@junglism93 @maverick6664
Thanks guys. Of course i won't re lock it. I had many nexus phones and i always had them in unlocked state. I was disappointed in google when i heard this issue about pixel phones. Nexus phones (Except nexus 5x and 6p) were immortal. This pixels are so easy to brick and kill. I immedeatly started searching for ways to unlock it's bootloader. What if something goes wrong during update process? Anything can happen and if system gets damaged, you are screwed. It's always better to have bootloader in unlocked state.
P.S.
To check if pixel is verizon version
Download terminal emulator and run
getprop ro.boot.cid
if result is "VZW__001" then it's verizon. My pixel is verizon.
Click to expand...
Click to collapse
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
BTW, "adb oem lock" doesn't work with xperia. Sony seems to like leaving their products unlocked.
maverick6664 said:
But reading this page, relocking by "adb oem lock" looks safe. At least this is a google's page. Google is responsible for it. And you can avoid the annoying boot message.:laugh:
I'm sure that is safe if you're updating from full stock to full stock, with mods on board a relock is almost suicidal and the threads about bricked pixels back that up.
If you don't like the warning screen, do what I do, don't watch your phone reboot
Click to expand...
Click to collapse
Want to buy this phone. Need it rooted to do a couple things. Has anybody gotten TWRP and root on it yet?
You can root it by first unlock the bootloader then install magisk via patch boot image method.
How should I get the boot image to actually use that method?
You can download the firmware here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/
Inside zips, find boot.img
Does anyone know anything about custom recovery TWRP yet that's what I'm looking for
there is no custom recovery
ahalol said:
You can root it by first unlock the bootloader then install magisk via patch boot image method.
Click to expand...
Click to collapse
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Thereplierbro said:
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Click to expand...
Click to collapse
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
Does the Verizon one have a greyed out "OEM Bootloader unlock"
Because I bought one off offer up that had the button available but it was purchased from Verizon
Also I asked Motorola for the unlock website an they said they haven't released it yet for Moto z4
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
wraith1932 said:
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
Click to expand...
Click to collapse
All other phones, if the button is not greyed out and you can press the option (and it asked for your password) then it's unlockable. I know because I got a few freaking pixel phones with non usable Bootloader. Wasted about $1,000 looking for a cellphone to use with Sprint that I can root. Every one of them is Verizon.
https://support.motorola.com/us/en/solution/ms87215
DM Verity disabled too?
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Jade Eyed Wolf said:
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Click to expand...
Click to collapse
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Thereplierbro said:
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Click to expand...
Click to collapse
One of my main reasons for waiting to get one
Jade Eyed Wolf said:
One of my main reasons for waiting to get one
Click to expand...
Click to collapse
It's basically useless until then
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
battleof3 said:
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
Click to expand...
Click to collapse
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
ahalol said:
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
Click to expand...
Click to collapse
Dug a little deeper and bootloader is locked tight, no flashing for me. Returning and buying a secondhand LG V30 for cheap. It's unfortunate that carriers love their walled gardens.
See, this is why I was asking about DM Verity. You need to disable that first before flashing anything via ADB/Fastboot.
With DM Verity on, at system startup, the device generates a hash of the /system and /root directories. If the hash does not match the one from the factory, due to changes pushed via ADB or Fastboot or patching other system files with something different, the system reboots, again and again.
I had this same issue with my Z2 Play, which is why I brought it up here.
Rooting these devices is useless, unless you also disable DM Verity.
I tried to follow this method and ended up flashing the wrong boot image (I did go to the right software variant but it was outdated) so i had to go through and try all the images they had and none of them worked so i had to look elsewhere.
After some digging i found a VERY handy tool made by lenovo themselves that lets you update and recover the firmware.
If you use the rescue option and enter your phones info (it seems to verify your phones info so you can only download for devices you have) and it'll download the latest zip for you so you can get the boot image.
Here's the link to the smart assistant
TL;DR Open smart assistant, click flash, click "Go rescue", Click "Moto Phone", enter your phone's info (make sure your phone is connected in fastboot mode), click the download icon next to the file name.
Make sure you DO NOT click the rescue button when the download is finished as that will factory reset your phone, just copy the zip or boot image and close it
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Seriously... So there's no way to unlock for free, or by waiting...?
Not a bootloader unlock. Its not just Tmo that are locking these down tighter.
You can unlock it for free if you can figure out whatever they do ;-)
Nah idc about a network unlock since I don't have service for this phone, I just wanna know if its possible to unlock the bootloader... I've tried everything
Who is talking about a network unlock?
TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
You said not a "bootloader unlock" so I was assuming you're talking about network unlock... Sorry, but should I just give up, there's seemingly NO WAYY to unlock the bootloader of a T-Sh*t phone.
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
TimmyP said:
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
Click to expand...
Click to collapse
That's kinda sad, I think I'm gonna just give up, but thanks for the information... Hopefully something happens in the future that allows it to be unlocked soon... Thanks man
I doubt they'll bring it back. OEM unlock that is. My phone is over 7 days old and I did the factory reset by holding the volume down and power buttons and then the volume up and power button and did the full factory reset. OEM unlock is still gone. Yes I got the developer options turned on. I rooted a couple of Nexus 6p's which of course are obsolete now since they were 3G and there is no backward capability. At least I got them used, replaced the batteries myself and can use them as WiFi phones with Talkatone through my WiFi. Read some blurbs about Kingo root working but I'd like to see that someone has pulled it off with the A32. Am under a 2 year obligation but I bought a second one to experiment on. I did that before I found out there was no OEM unlock. Well, if I break one, I'll have a backup. Except the phone is tied to the SIMM and I'd have to bring the backup in to have it reprogrammed.
TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
iabhua said:
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
Click to expand...
Click to collapse
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
TimmyP said:
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Click to expand...
Click to collapse
Do you have any device with an unlock bootloader or unlock? I am trying to get a ram dimp for days nobody have an device.
andioshelp said:
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
Click to expand...
Click to collapse
I have two SM-A236U’s but unfortunately one has binary 6 FW and the other binary 7.
1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
There was a similar procedure to unlock bootloader on a samsung mtk (A125U) same carrier as yours (T-Mobile TMB and the same applies to MetroPCS TMB) basicaly, you had to flash BL files from the A125W (canadian version) then unlocking bootloader using testpoint (bootrom mode) then using any paid or free app (in my case i use a paid one because i run a repair shop). even if you unlock bootloader using paid tools, it gets locked again when it turns on. (i tested it without flashing BL files)
sadly, i dont have a A326U lying arround to test said procedure.
1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
DjoFight said:
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
Click to expand...
Click to collapse
In case people need the procedures for those processes, I wrote this up recently to help others do it easier than it was for me to figure out.
How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode
Has any one made any progress regarding the missing oem unlock? I know what parameters to add to our kernel v1 to v3 during building to enable oem unlock and add access to fastbootd. Because of project treble our options have changed.
Sources:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
Sign in
DOCUMENTATION
Docs
More
Getting Started
Security
Core Topics
Compatibility
Android Devices
Reference
GO TO CODE ➚
Overview
Architecture
Overview
Hardware Abstraction Layer (HAL)
Kernel
HIDL (General)
HIDL (C++)
HIDL (Java)
Configuration
Device Tree Overlays
Vendor NDK
Vendor Interface Object
AIDL
Bootloader
Overview
Boot Reason
Boot Image Header
Implementing Bootconfig
Recovery Images
DTB Images
Supporting OTA Updates
Locking and Unlocking the Bootloader
Version Information in AVB Properties
Fastboot in Userspace
Partitions
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Virtualization
Tests
Updates
AOSP
Docs
Core Topics
Was this helpful?
Locking/Unlocking the Bootloaderbookmark_border
On this page
Unlocking the bootloader
Locking the bootloader
Setting lock/unlock properties
Protecting critical sections
By default, most Android devices ship with a locked bootloader, meaning that users can't flash the bootloader or device partitions. If needed, you (and device users with Developer options enabled) can unlock the bootloader to flash new images.
Unlocking the bootloaderTo unlock the bootloader and enable partitions to be reflashed, run the fastboot flashing unlock command on the device. After setting, the unlock mode persists across reboots.
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the get_unlock_ability to 1). After setting, this mode persists across reboots and factory data resets.
When the fastboot flashing unlock command is sent, the device should prompt users to warn them that they might encounter problems with unofficial images. After the user acknowledges the warning, the device should perform a factory data reset to prevent unauthorized data access. The bootloader should reset the device even if it can't reformat it properly. Only after a reset can the persistent flag be set so that the device can be reflashed.
All RAM not already overwritten should be reset during the fastboot flashing unlock process. This measure prevents attacks that read leftover RAM contents from the previous boot. Similarly, unlocked devices should clear RAM at every boot (unless this creates an unacceptable delay), but should leave the region used for the kernel's ramoops.
Locking the bootloaderTo lock the bootloader and reset the device, run the fastboot flashing lock command on the device. Devices intended for retail should be shipped in the locked state (with get_unlock_ability returning 0) to ensure that attackers can't compromise the device by installing a new system or boot image.
Setting lock/unlock propertiesThe ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device supports flashing unlock, set ro.oem_unlock_supported to 1.
If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0.
If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or to 0 if unlocked. This variable must be set in bootconfig instead of in the kernel command line in Android 12.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
evnStevn said:
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
Click to expand...
Click to collapse
I'm wondering too. Could you please pm me what you were trying to post?