Related
Hi all,
I have a P10 Lite that is running Nougat, EMUI 5.1. The phone displays the very ominous 'This phone has been unlocked and is therefore not secure' message at every boot. I would like to get rid of this message as we are putting it back on sale within the store and do not want to scare customers with this warning. I have the bootloader lock/unlock code but whether it is locked/unlocked, the message still appears AND OEM unlocking is greyed out in developer settings. Additionally after 'locking' it in fastboot, when put back into fastboot mode it still displayed as 'Phone Unlocked'. I have tried updating it through SD card but that did nothing. Is it basically stuck in this state now?
Just flash official firmware to replace bootloader.
Skyhuppa said:
Just flash official firmware to replace bootloader.
Click to expand...
Click to collapse
How can I flash if OEM unlocking is greyed out?
pandatechrma said:
How can I flash if OEM unlocking is greyed out?
Click to expand...
Click to collapse
I think flashing it original full firmware will work for you, whether OEM unlocking at settings has greyed or disappear. Ones the device drivers can be recognize by computer at this stage it should support full flash. That is why is always advisable to keep device full backup before tempering with it. Download the device original firmware online, use it supported flash tool and flash through computer.
Since you are also on sale point or shop, you can take same phone from shop if available, backup then restore the files to the OEM greyed phone.
But before performing full flash make sure you keep backup of exiting firmware, so that you can restore back when new firmware does not support your device.
I think flashing it original full firmware will work for you, whether OEM unlocking at settings has greyed or disappear. Ones the device drivers can be recognize by computer.
Check this link but follow all instructions and comments
https://forum-xda--developers-com.c...pilation-firmware-flasheables-huawei-t3736754
Hi! My name is Bautista.
This is my first post well explained, I already asked this question before but I did not express myself well (I hope to do it correctly in this attempt)
My problem happens with my Samsung Galaxy A01 SM-A015M, Running on OneUI 2.0/Android 10 with 2gb of ram, a Snapdragon 439, the stock rom/firmware and 32GB of storage, from Argentina.
Things I tried so far, and didn't work for me:
Unlocking the bootloader by following the Gearallnews and Cyanogenmods guides to the letter.
When trying to unlock the bootloader with the guides on the aforementioned pages, when starting the device a sign should appear saying that the bootloader is unlocked, which did not appear.
The device started correctly in the process to configure the device the first time it is turned on, connect the wifi as the guides said. Followed by that I went to the developer options and the option "Oem unlock" was still activated and in blue (which should not happen, it should appear grayed) I heard that some Samsung devices with snapdragon processors had a bootloader that cannot be unlocked
Unlocking the bootloader using ADB AND Fastboot. (ADB detects my device fine, but fastboot doesn't detect it at all)
Using Fastboot from Windows 7, Windows 10, and Kali Linux.
Installing TWRP.
Use rooting apps. (the ones that appear on the XDA rooting page)
What I am going to with this thread, is:
Can my device's bootloader be unlocked? And if so, how?
If the bootloader cannot be unlocked, how can I root or install TWRP?
Please, if you don't understand something or need more information, let me know by replying to this thread or sending me a private message.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
it's the same as Gearallnews and Cyanogenmods guides, i already did that, it dont work
Like the original poster I also have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) Panama. I have gone through all the aforementioned procedure and the bootloader does not unlock. There is no bootloader unlock warning on reboot and the OEM Unlock in developer option does not grey out. Does the Snapdragon processor not allow bootloader unlock or is anyone aware of a solution. Thanks for any assistance.
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
jwoegerbauer said:
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
mullerh said:
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
Click to expand...
Click to collapse
Hi! Did you manage to find a way to unlock the bootloader?
I have not been able to unlock the bootloader on this SM-A015M/DS (Latin American) model with Snapdragon processor. I have done a lot of searching but found little info except articles stating Samsung had gone through some extra effort to secure their latest phones. That also means I can not root it. I was hoping to get some feedback from other who may have had a better experience,
have you tried using the twrp app to install twrp?
i had an old galaxy grand prime which was impossible to unlock, but the app worked without issues
the only thing i had to pay attention is to turn it off right before ir reboots after installing and then loading into recovery
letting the mobile startup without doing this overrieded the command to install twrp
Thanks for your response. It is my understanding (I could be wrong) that before TWRP can be installed the Bootloader needs to be unlocked. The older Samsung usually allowed the Bootloader to be unlocked even if there was difficulty in rooting them. It appears that some of the newer Samsung's with the Snapdragon processors have added an additional security feature called SecureBoot which blocks the Bootloader from being unlocked.
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
For what it's worth, when I flashed the firmware onto the phone in the first place, I had to enable the developer option manually- I did this by booting into download mode and then a long press on the volume up button when prompted by the menu. I don't see why this wouldn't work for other devices. There are youtube videos that explain in greater detail if you haven't tried this yet.
Newiser7 said:
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
Click to expand...
Click to collapse
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
jwoegerbauer said:
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
Click to expand...
Click to collapse
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
mullerh said:
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
Click to expand...
Click to collapse
You are right: I was mistaken.
Thank you for clarifying that the bootloader is still locked. But how can I unlock it? Odin will let me flash the files, but I keep getting AUTH errors when I try to flash magisk patched files to root the phone. I'm assuming this is because the bootloader preventing the files from transferring. Is there a way to unlock it using ADB without fastboot, or a way using Odin? It seems crazy that unlocking the bootloader is enabled but I am still unable to actually unlock it.
I have also tried the CROM Service app (couldn't get it to install on my phone, error 3003 with ADB install), as well as the bootloader unlock method where I boot into download mode, hold the volume up key, and unlock the bootloader that way. I have done the latter at least 5 times and the bootloader is still locked. Ridiculous.
This prop apparently only confirms that the phone supports being unlocked, not that it is actually unlocked.
adb shell "getprop ro.oem_unlock_supported"
Check a few others, also see the official docs.
sys.oem_unlock_allowed
androidboot.flash.locked (the docs say this, but I think Samsung uses something different)
ro.boot.flash.locked
ro.boot.other.locked
Maybe also check these:
ro.boot.verifiedbootstate
ro.boot.veritymode
The docs indicate that the verifiedbootstate should be orange if the bootloader is unlocked. I don't know much about it, though.
You can always use grep to search for any interesting values, like "lock" or "boot" or "flash":
adb shell getprop | grep lock
adb shell getprop | grep boot
adb shell getprop | grep flash
Maybe report any interesting values you have with and without OEM Unlock checked. Maybe someone smarter than us will find it useful.
I would really like to see an A01 root happen, it's such an affordable and accessible device for all sorts of things. Great as a backup device or for a project. You think someone would've released some goods for it by now. It's been out all year.
And for the 16GB model, it's absolutely terrible because Samsung eats up so much space, then has the nerve to remove the Adoptable Storage feature. So even if you get a fast SD card, you can't install apps on it. Other than that, it's a perfectly serviceable phone. I would think with root we could get Adoptable Storage working.
To summarize what has been previously stated the Samsung Galaxy A01, version SM-A015M/DS is the Latin American version of this cellphone. This cellphone has a Snapdragon processor. This version is very similar to the versions (also Snapdragon processors) used by some US Carriers. Many current versions of Samsung cellphones have an additional security feature called "SecureBoot" which blocks bootloader unlocking. Some say this features was added at the request of US Carriers
The Asian version of the A01 has a Exynos processor. It is my understanding that with these it is very easy to unlock the bootloader and root the phone using the usual conventional methods. The Asian variant unfortunately does not cover some of the wireless bands used in the US/Canada/Latin America.
I have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) for Panama.
My research indicates that there is not yet an available bootloader unlocking and easy root method for this (A01) phone. For some other current Samsung models there does appear to be a method of flashing certain custom ROMs without a bootloader unlock but they appear to come with problems which include loss of some cellphone functions and a reduction in the charged battery life. So it seems hardly worth it.
It also appears that it is current well known that all current Samsung phones with Snapdragon processors have not allowed bootloader unlocking and rooting due to the enhanced security feature.
At this time we can only complain and/or not buy any additional Samsung phones
Perhaps with time skillful developers will come up with a method to solve this problem with this inexpensive A01.
Please provide any new or updated info if you have it.
Any solution for rooting Galaxy A01 ?
I use A015f region SER (Russia) In Russia, too, the device is locked (bootloader) of course, give any solution
One thing I know is that a fellow SM-M015f, which is almost identical, which is with the same Snapdragon 439, except for the battery capacity and screen size and gigabytes of internal memory, successfully unlocks and gets Magisk root.
this phone actually has a fastboot mode, from recover mode select reboot to bootloader, it will boot to fastboot mode,but ive still been unsucessful in getting fastboot mode to work, devices manager reports device error,
I can start the unlock proccess.
But after it is done and the data is wipped,
It keeps locked.
Sad
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
glhelinski said:
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
Click to expand...
Click to collapse
follow instructions from ChazzMatt's thread, they have LG UP dual linked and the instructions to flash kdz
Thanks. He has lots of threads. Do you have a link?
I believe it's the one/main thread he maintains on how to root/unlock the phone. You'll have to do some thinking on how to go "backwards" from there, but the software and steps are all in there.
Generally speaking, it's NOT recommended to relock the BL because if the phone isn't 100% stock ROM, I believe you could end up bricking or bootlooping. I think you can leave the BL unlocked and just KDZ flash US998 and leave it unrooted (no Magisk, etc). This should look "stock" to anyone who cares to have a stock-specific phone anyway.
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
glhelinski said:
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
Click to expand...
Click to collapse
Yes, re-locking the bootloader will get rid of the warning screen. Just make sure you are 100% complete stock (all partitions) before you re-lock it. Otherwise the phone may brick itself.
Also, make sure you remove your Google account in the OS before you wipe/re-flash the phone. Otherwise it will trigger FRP and require the new user to enter the previous username and password.
I might be in the same boat here, would love to know how to just return to stock and relock bootloader (for someone who didn't make an initial backup)
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Thank you
TheDannemand said:
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Click to expand...
Click to collapse
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
johnp357 said:
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
Click to expand...
Click to collapse
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
TheDannemand said:
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
Click to expand...
Click to collapse
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
johnp357 said:
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
Click to expand...
Click to collapse
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
TheDannemand said:
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
Click to expand...
Click to collapse
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
ldeveraux said:
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
Click to expand...
Click to collapse
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
johnp357 said:
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
Click to expand...
Click to collapse
It voids whatever warranty existed between you, Verizon, and LG, but I haven't seen anything about trade ins. Where'd you read that?
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
TheDannemand said:
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
Click to expand...
Click to collapse
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
johnp357 said:
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
Click to expand...
Click to collapse
That is indeed puzzling. I did this twice on my old H932 before sending it in for warranty, and never saw that problem.
I am sorry I don't have more suggestions to offer
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
Once again, enable developer options and make sure that both OEM Unlocking and USB Debugging is enabled.
Open the ADB Powershell window mentioned before and make sure that your device is still recognized by using the command:
Code:
adb devices
Once your device shows up, put it back into the bootloader state by using the command:
Code:
adb reboot bootloader
Your phone will now enter the bootloader state once again.
We can now relock our bootloader by using the command:
Code:
fastboot flashing lock
This will prompt you to use your volume rocker and power button one more time. Select the option LOCK THE BOOTLOADER and press the power button to confirm. Your device will now format for the last time and load you into OxygenOS 13.
Note: I personally had an issue where after flashing and relocking the bootloader, my phone decided to bootloop(device stuck at OnePlus logo and keeps on turning on and off again), I solved this by holding the volume down and power button and setting it to restart. After loading into the operating system, I updated my device by using OTA updates and installing C4515_11_C.23. This allowed for my device to install the latest update and it seemed to have fixed the bootlooping problem for me.
Another method to fix the bootlooping issue after flashing your phone if you already have the latest update installed is to enable developer options after flashing and applying the same update using the local update feature.
To do this, enable developer options first, the instructions to do that were described earlier in this guide. Transfer the .bin file by drag and dropping your .bin file to a location on the device that you are familiar with. (Placing the .bin file in the downloads folder is a foolproof method)
From there onwards, you want to go into Settings > About Device > Tap on the blue OxygenOS banner > 3 dots menu in the top right corner > Local Install > Select your .bin file you used to flash the device with earlier. Your device should then update with said .bin file and the bootlooping issue should be solved.
Credit to thegreatn_ for this discovery.
Edit: Some of you may experience that your OEM unlocking is still enabled even after flashing your device and relocking your booloader. Remember earlier when your bootloader was in an unlocked state, the OEM unlocking option would be on by default and greyed out so that you could not turn it off which may present a security risk.
Rest assured that you can turn off OEM unlocking once your device has been relocked and everything will function as intended. YOUR DEVICE SHOULD NOT BE ROOTED IF YOU INTEND TO TURN THIS OFF! ONLY DO THIS WITH THE OFFICIAL FIRMWARE INSTALLED! Not having the official firmware installed and turning off OEM unlocking can brick your device!
Credit to Adly1991 for this information.
Please let me know if there's any questions you'd like to ask. This is my first time flashing and it may seem daunting at first, but I believe with a little bit of confidence, you too will be able to successfully flash your Ace Pro.
Good luck!
I'm 8T user , but thanks for sharing your experience and the information.
Abdo Ismail said:
I'm 8T user , but thanks for sharing your experience and the information.
Click to expand...
Click to collapse
It was really hard for me to find a place where I could get all the information I needed about flashing my phone as a noob. If this post helps even just a single person I'd be over the moon. Thanks for the feedback!
Thanks so much. Followed the instructions and worked perfectly!
breadsnack said:
Hello everyone!
I recently had the pleasure(pain) of flashing my Ace Pro and I wanted to share the steps I took in doing so. This post will act a as guide/discussion area regarding flashing the Ace Pro(Chinese Release) into the OnePlus 10T 5G(Global Release).
Henceforth, I will refer to the OnePlus Ace Pro as Ace Pro, and the OnePlus 10T 5G as 10T.
A little bit of backstory:
I currently live in China and have no way of purchasing a device overseas and having it shipped in. Instead, I did a little bit of research and decided to purchase an Ace Pro and have a go at flashing it myself. As far as I can tell, the Ace Pro and 10T are identical hardware-wise and flashing between the 2 different market varients can be done with a little bit of effort and headache.
Before we go any further, let me link some useful articles and resources I've found along the way in order to successfully flash your own Ace Pro:
Fastboot Enhance, a powerful tool that will allow you to flash your device with your desired OS
ADB Platform Tools, a tool used to unlock your bootloader
OnePlus USB Drivers, an USB driver used to allow for your phone to communicate with your computer seamlessly(Even though not officially supported, the Ace Pro and 10T work with the 1.0 Release of the USB Drivers)
2415_11_C.22 Update, a stable release of Oxygen 13 that I personally recommend to be flashed on your 10T
Daxiaamu Tools and ROMs, a Chinese enthusiast that has developed his own tools to aid in unlocking, flashing and relocking of devices.
Disclaimer: I am not responsible for any damage that you may inflict upon your own device, proceed with caution and at your own risk! Back up all data before proceeding!!
We begin our journey by first unlocking the Ace Pro's bootloader, unlocking the bootloader is an essential step in flashing your device.
To do this, we need to first enable Developer Tools by going into: Settings > About Device > Version > And tapping the Build Number box until you have become a developer.
After this, navigate to Developer Options. If you cannot find this option, I recommend using the search bar at the top of the settings menu to find this option. Once you're in this menu, enable OEM Unlocking and USB Debugging. This allows for our computer to communicate with our Ace Pro.
Here I recommend installing your Oneplus USB Driver. This will allow your phone to communicate with your PC for the upcoming step.
After installing the drivers, plug your phone into your computer using either the USB cable that came in the box, or a reliable cable that you know will carry data.
Press on Transfer Files/Android Auto when prompted.
Allow for debugging on your device after plugging it into your computer with the prompt that shows up.
Once you are sure that both OEM Unlocking and USB debugging have been enabled, run your ADB Platform Tools by performing the following steps:
Unzip your ADB Platform Tools and have it placed in a memorable place(preferably the desktop)
View attachment 5844957
Holding Shift + Right Click in an empty space brings up this option menu. Click on Open PowerShell window here.
This brings up a Windows Powershell terminal that allows you to enter commands that will directly affect your Ace Pro.
Run the command
Code:
adb devices
This show bring up an entry with a mess of both numbers and characters. This shows you that both your computer and ADB tool recognizes your device and you can move forward.
Now we want to put the device into the bootloader by using:
Code:
adb reboot booloader
This will now run on your device putting it into the bootloader state.
Note: DO NOT UNPLUG YOUR DEVICE IN THIS STATE
After making sure that your device is in the bootloader, run the command:
Code:
fastboot flashing unlock
You will be presented with a prompt asking you if you are sure that you want to unlock your bootloader. Using the volume rocker as a selector and the power button as a confirmation button, highlight the UNLOCK THE BOOTLOADER option using the volume rocker and confirm it by pressing the power button.
Your Ace Pro's bootloader is now unlocked.
NOTE: YOUR DEVICE WILL BE FORMATTED ONCE YOU UNLOCK THE BOOTLOADER! ALL EXISTING DATA WILL BE LOST!
Once unlocking your bootloader, your phone will enter 'Orange State' where it lets you know that your device is untrusted due to its unlocked nature. Do not be alarmed by this.
Proceed by setting your phone up as normal and repeat the earlier step where you become a developer and enable USB Debugging.
This time, OEM unlocking will be enabled by default, this is due to the nature of your device being unlocked.
We now want to put our device into fastboot mode by using ADB. In the Powershell window, type:
Code:
adb reboot fastboot
This will once again change the state of your phone and put it in fastboot mode where 3 language options are available. Do not configure your phone in this state, we will come back to it later.
Now, run Fastboot Enhance as an administrator on your PC. The window should open up and you should be able to see your device with the device name being labeled as 'fastboot'.
Double click this option and another Window should show up.
Make sure that the status of the device is as follows:
Secure Boot: Disabled
Seamless Update: Yes
Current Slot: a
In Fastbootd: Yes
System Update Status: None
Once in this state, we want to click on the partitions tab above and search for 'cow' in the search bar. Results will pop up if you have used/updated your device in ColorOS. You want to highlight these results and press delete on the right hand side. Having them remain in your device will have the possibility of bricking your device when flashing the new OxygenOS ROM.
Once done deleting, return to the Basic Properties tab and press Flash Payload.bin. This will open a browser in where you need to find the zip file containing the ROM that you want to flash.
Find your payload.bin file and open.
Your device will now begin to flash, it took me around 10 minutes before the device was done flashing.
Once flashed, go to your phone and select your language of choice. For most of us, it will be English. This option can be selected like earlier, using the volume rocker as a selector and the power button as a confirmation switch.
Select the option to format your phone once again. Enter the pass code that is present on the screen and confirm the formatting procedure.
The device should still be in Orange State since we have not relocked our bootloader, instead we will now see the OxygenOS boot animation before proceeding to set up our device.
From this point onward, your device is now flashed with OxygenOS.
If you would like to relock your bootloader, read on.
The benefits of relocking your bootloader is that you will be able to receive OxygenOS updates as normal and be able to use NFC functions such as Google Wallet.
مرة أخرى ، قم بتمكين خيارات المطور وتأكد من تمكين كل من إلغاء تأمين OEM وتصحيح أخطاء USB.
افتح نافذة ADB Powershell المذكورة من قبل وتأكد من أنه لا يزال يتم التعرف على جهازك باستخدام الأمر:
Code:
أجهزة adb [/ CODE]
بمجرد ظهور جهازك ، أعده إلى حالة أداة تحميل التشغيل باستخدام الأمر:
[كود] adb reboot bootloader [/ CODE]
سيدخل هاتفك الآن في حالة أداة تحميل التشغيل مرة أخرى.
يمكننا الآن إعادة توصيل محمل الإقلاع الخاص بنا باستخدام الأمر:
[كود] قفل وميض fastboot [/ CODE]
سيطالبك هذا باستخدام زر التحكم في الصوت وزر الطاقة مرة أخرى. حدد الخيار LOCK THE BOOTLOADER واضغط على زر الطاقة للتأكيد. سيتم الآن تنسيق جهازك لآخر مرة وتحميلك إلى OxygenOS 13.
ملاحظة: لقد واجهت شخصيًا مشكلة حيث بعد وميض أداة تحميل التشغيل ، قرر هاتفي تشغيل bootloop (الجهاز عالق على شعار OnePlus ويستمر في التشغيل وإيقاف التشغيل مرة أخرى) ، لقد قمت بحل هذه المشكلة عن طريق الضغط على زر خفض الصوت وزر الطاقة وتعيينه لإعادة التشغيل. بعد التحميل في نظام التشغيل ، قمت بتحديث جهازي باستخدام تحديثات OTA وتثبيت C4515_11_C.23. سمح ذلك لجهازي بتثبيت آخر تحديث ويبدو أنه قد أصلح مشكلة bootlooping بالنسبة لي.
يُرجى إعلامي إذا كان هناك أي أسئلة تود طرحها. هذه هي المرة الأولى التي تومض فيها وقد يبدو الأمر شاقًا في البداية ، لكنني أعتقد بقليل من الثقة ، أنك أيضًا ستكون قادرًا على وميض Ace Pro بنجاح.
حظ سعيد!
[/QUOTE]
أ Do you provide phone costum recovery Oneplus 10T
Click to expand...
Click to collapse
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
Hey there, I'm not 100% sure on how to solve this issue but I'll try my best.
First of all, please ensure that your phone is plugged into your computer at all times.
Make sure that your cable supports data transfer and try other cables and see if this problem persists.
The fact that ADB is recognizing your device tells me that your cable is probably not to blame.
Make sure that your phone is on beforehand and that USB debugging and OEM Unlocking are both enabled in the developer settings.
You have to also make sure to select allow on your phone when it asks whether the connected computer is allowed to debug your phone. This is important since it allows your computer to run commands on your phone itself.
Does your phone go into the fastboot screen when you run the adb reboot bootloader command?
Let me know so I can narrow your problems down further and solve the issue!
@thk202 I'm not a vendor of any type. This was just my personal experiences. Can you describe what's gone wrong?
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Adly1991 said:
thank you, i finally did it following your steps .. and i think recommendation of 2415 version solved my problem and also instantly got C.26 update through OTA
since i tried 2413 before and alwayes got modem issue.
Click to expand...
Click to collapse
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
breadsnack said:
I remember reading somewhere that 2413 gets updates quicker than 2415 for some reason. But I for one was used to the slow update schedule from Samsung for years so it never affected me. 2415 C22 was a stable OxygenOS 13 release that allowed for OTA to C26 to fix any sort booting issues after relocking your bootloader. I remember relocking my bootloader and having it go into a constant bootloop/soft brick after the C22 flash but after OTA to C26, the bootlooping fixed itself and everything was stable again.
Click to expand...
Click to collapse
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Adly1991 said:
shall i disable OEM option in developer option after relock .. already locked the device but i am afraid to disable OEM option since a read somewhere that it bricked someone device ..
Click to expand...
Click to collapse
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
breadsnack said:
Erm I've actually got no clue, I know for a fact that if your bootloader is unlocked, OEM unlocking is on by default and greyed out so you cannot turn it off while the bootloader is in it's unlocked state. I did re-enable developer options after locking my phone again and OEM unlocking was turned off by default. This hasn't bricked my phone and I'm assuming that if it had the potential chance to, OnePlus would have greyed it out. See below:
View attachment 5859683
Click to expand...
Click to collapse
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
thegreatn_ said:
How I fixed my "bootloop" problem:
I flashed C.26 through Fastbootd and wiped data, and... bootloop!
Looks like device is trying to access wrong slot A or B and unable to.
You need to hold power button + volume up, it should reboot normally. It's a temporary solution, you will face it again after another reboot.
Then you need to transfer the same zip you used to flash into root directory of the phone (where all the folders are living). Go to settings -> About device -> Status -> Tap 7 times on build number to unlock local update feature.
Next, tap on big OxygenOS banner -> Three-dots menu at the top right -> Local install. After, select the zip file you previously copied. Confirm and wait for phone to update itself.
Update will be installed and bootloop issue should be fixed.
Click to expand...
Click to collapse
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Adly1991 said:
for my case OEM did not turn off by default, however, i did it and there is no issues .. thanks
Click to expand...
Click to collapse
Sweet, will append this information to the guide!
breadsnack said:
This is another method of solving the bootlooping issue. I'm assuming that the device just automatically unscrews itself when it receives an update through within the OS. The bootlooping issue is probably because its trying to find a bootable OS through both slot A and B until it manages to fix itself. I personally just flashed C22 and updated to C26 and it had the same effect as flashing C26 and flashing C26 again in local updates.
Thanks for the info! I'll append it to the guide in a bit...
Click to expand...
Click to collapse
I'd like to point out that there is no need to unpack the zip file, Updater will do everything automatically.
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
Wonderful lemme know if you run into any more issues and I'll be glad to help
Adly1991 said:
This is to inform that i got update c.26 and c.27 through OTA with no issue ..
View attachment 5882617
Click to expand...
Click to collapse
thk202 said:
Hello, Im facing this issue when tried to unlock.
The code fastboot flashing unlock not be proceeded but show the whole line with options as below image.
Could you please help !!1
View attachment 5856125
Click to expand...
Click to collapse
how you fixed this issue ? i got same problem .
Currently, RSA does not support XT2311-3 for unknown reason. However, I found a ROM for Tracfone, but the boot works with unlocked version.
Download: https://www.androidfilehost.com/?fid=10620683726822053015
MD5 60f8e629cbe7e969923c07538d6c3c7c
Bootloader unlock required. However, VPN disappeared after bootloader unlocked. You have to set up user account if you need VPN
Note: your phone is wiped during bootloader unlock process. Since RSA does not work with this phone at this time, you may not be able to rescue if something goes wrong.
Note: Titanium Backup does not work with Android 13. You need Swift Backup (pay $2.5 a year to use your choice of cloud service)
You should do it before initial setup. Wi-Fi connection and/or data connection needed for Magisk. Transfer the boot.img downloaded to your phone and patch it with Magisk, and transfer the patched boot back to host computer.
Now reboot the phone to bootloader or fastbootd
Code:
adb reboot fastboot
Flash patched boot
Code:
fastboot flash boot
Press space once, drag-and-drop the patched_boot onto command window, and press enter.
Post process:
Install the following as modules and you should install Fox's Magisk Module Manager
ADB fastboot
shamiko (you can setup Deny List but you don't have to enable because shamiko takes care of it)
Universal SafetyNet Fix 2.4.0
Systemless host within Magisk
liboemcrypo disabler is not required as it plays Netflix fine after these modules added, and it appears L1 on mine (good)
You can complete setup after root is done. Make sure you add Play Store and Play Services into Deny List as well as any app can detect root
How do you unlock the bootloader on this phone? When I copy & paste my device ID into the Motorola bootloader unlock page and click on "Can my device be unlocked" button, I get a message saying, "Your device does not qualify for bootloader unlocking".
dmw_4814 said:
How do you unlock the bootloader on this phone? When I copy & paste my device ID into the Motorola bootloader unlock page and click on "Can my device be unlocked" button, I get a message saying, "Your device does not qualify for bootloader unlocking".
Click to expand...
Click to collapse
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
basixs_2 said:
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
Click to expand...
Click to collapse
I got mine from Best Buy
Now there's a workaround for missing VPN
Get App Ops from Play Store and add sui (zygisk) module on Magisk
Check the list on App Ops and allow VPN on app needed
Moreover, Netflix works after USNF @Displax mod added, added Play Store and Play Services in Deny List, and Shamiko module added.
Mine shows L1 and Netflix (and cable TV app) work
basixs_2 said:
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
Click to expand...
Click to collapse
I bought mine at Best Buy, but that shouldn't make any difference. It's the unlocked version for use on any carrier, so it should be bootloader unlockable.
I enabled Developer Options, but I noticed that "OEM Unlocking" is grayed out. When trying to Google this and find out why, I came upon a Lenovo forum where people were asking the exact same thing, and Lenovo's response was that the phone needs an Internet or Wi-Fi connection for 7 days before the "OEM Unlocking" option will become available(?!).
Now, I'm wondering if that's what's going on here, and why I'm getting the message that my phone isn't eligible for bootloader unlocking. I guess I'll see in a few days, LOL!
dmw_4814 said:
I bought mine at Best Buy, but that shouldn't make any difference. It's the unlocked version for use on any carrier, so it should be bootloader unlockable.
I enabled Developer Options, but I noticed that "OEM Unlocking" is grayed out. When trying to Google this and find out why, I came upon a Lenovo forum where people were asking the exact same thing, and Lenovo's response was that the phone needs an Internet or Wi-Fi connection for 7 days before the "OEM Unlocking" option will become available(?!).
Now, I'm wondering if that's what's going on here, and why I'm getting the message that my phone isn't eligible for bootloader unlocking. I guess I'll see in a few days, LOL!
Click to expand...
Click to collapse
I know this is weird.
Mine takes 7 days and it's on internet/SIM active
Back then my situation was more difficult because even RSA was not ready for the phone (it says not supported). I needed boot.img for rooting
I think I'm on day 2 of waiting... It's only on WiFi as I need the SIM for my old phone. Kind of frustrating that it's not a more immediate result/change.
Yesterday was 7 days from when I bought my Moto G Power 5G, and I checked it this morning - lo and behold, OEM Unlocking is available!
I don't understand the reasoning/desire behind Lenovo's wanting to impose this 7 day waiting period, but it is what it is. Time to {hopefully!} go unlock my bootloader.
dmw_4814 said:
Yesterday was 7 days from when I bought my Moto G Power 5G, and I checked it this morning - lo and behold, OEM Unlocking is available!
I don't understand the reasoning/desire behind Lenovo's wanting to impose this 7 day waiting period, but it is what it is. Time to {hopefully!} go unlock my bootloader.
Click to expand...
Click to collapse
Good Luck!!!
I'm still waiting (on day 5) but this is great to hear
basixs_2 said:
Good Luck!!!
I'm still waiting (on day 5) but this is great to hear
Click to expand...
Click to collapse
What a pain in the a$$!! I had to keep trying over and over before it would work. It worked the first or second time (gave me the option to get an unlock code), but I forgot to put it in bootloader mode, so I got an error. Then, I had to try multiple times before it would give me another chance to get the unlock code (kept telling me my device wasn't eligible for unlock). Finally got it unlocked, and then rooted!