Database Develop

Trying to flash VZW FW on ATT MotoX (to get languages)

Gentlemen,
I brought a brand new, unlocked ATT MotoX to a friend out of the country, only to find out that the ATT version only has 4 languages compiled into it (ridicolous).
I've done some research and it seems like flashing the VZW ROM on the phone should do the trick (right?).
I've put the phone in fastboot and selected "recovery". After seeing the little Android image with "no command", I held the volume up button for about 6 seconds, followed by a tap of the power button (while still holding the volume button). It gave me the selection screen.
I picked "apply update from sdcard" and selected the "VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip" file I downloaded from here.
Here's the result:
{
"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"
}
Guys, my friend's English is not good. He needs the OS to be in his native language.
I am leaving town soon and would like to get the issue resolved and return the phone to him with all the languages, and able to work with non-US SIM Cards. Can you point me in the right direction? It will help us save time, since it's running fast.
Thanks in advance!

You can't flash AT&T phones with VZW firmware directly. You need to "port" the VZW firmware to the other model.
Sent from my Moto X

imnuts said:
You can't flash AT&T phones with VZW firmware directly. You need to "port" the VZW firmware to the other model.
Click to expand...
Click to collapse
Thanks man.
I am reading threads that explain porting, but it seems like a steep learning curve, at least for the limited time I have at my disposal before departure.
I'll continue reading and try to figure this out. I am following this guide. I will report back if I encounter any issues.
In the mean time, if someone knows of a pre-ported VZW ROM that would work in my case - or - of a better guide to follow, please let me know, it would be immensely appreciated.
Cheers!

Ok, 1st issue: I extracted the Zip archives of both ROMs (ATT stock and VZW). Inside the archives is a few ".img", ".bin" files, one ".mbn" and one ".xml" file. I assume the directories and files mentioned in the guide are in the system.img file (1.1GB), correct? Should I extract it and work on those, or is there a better way?

IlChengis said:
Gentlemen,
I brought a brand new, unlocked ATT MotoX to a friend out of the country, only to find out that the ATT version only has 4 languages compiled into it (ridicolous).
I've done some research and it seems like flashing the VZW ROM on the phone should do the trick (right?).!
Click to expand...
Click to collapse
Fist question... Is the ATT XT1058 you have SIM Unlocked or Bootloader unlocked?
SIM unlocking allows you to use the SIM from another carrier in your phone.. i.e. use a T-Mobile sim in an ATT branded X. That process does require you to have a different carrier's sim so the phone will prompt you to enter the unlock code. SIM unlock codes are available from many places around the web. It has no impact on rooting.
Bootloader unlocking allows you to flash a custom recovery, 3rd party roms, etc. By virtue of being able to flash a custom recovery you can easily root your phone. When it comes to the ATT XT1058 there is only only one place you can get a bootloader unlock code.. the Chinese Middleman (not as reliable as it once was, there is a BIG thread discussing it already).
If you are NOT bootloader unlocked, you will not be able to flash anything but the ATT XT1058 rom on that phone, no matter what you try. You will not be able to fully root and can not disable write protection once you have 4.4.2 on the phone.
As for adding languages, I thought there was another way, but I also thought that needed root and write protection disabled too.
---------- Post added at 03:15 PM ---------- Previous post was at 03:10 PM ----------
IlChengis said:
I am reading threads that explain porting, but it seems like a steep learning curve, at least for the limited time I have at my disposal before departure.
I'll continue reading and try to figure this out. I am following this guide. I will report back if I encounter any issues.
Click to expand...
Click to collapse
And you'll need an unlocked bootloader to flash the ported rom you make if you follow those instructions.. (since it says you're ready to flash via CWM... and you can't flash CWM, TWRP or other custom recovery to the phone unless the bootloader is unlocked)
Edit: this is the other thread for adding languages.. basically its suggesting flashing the VZW ROM and then your modem files for your device -> http://forum.xda-developers.com/moto-x/moto-x-qa/how-to-add-languages-to-moto-x-t2437807 which again needs unlocked bootloader.

Hey bud, thanks for taking the time to help me out and explain.
KidJoe said:
Fist question... Is the ATT XT1058 you have SIM Unlocked or Bootloader unlocked?
Click to expand...
Click to collapse
I'm not entirely sure, but I'd venture to say that it's SIM Unlocked.
Is there a quick way to tell for sure?
If it turns out being bootloader LOCKED, we're pretty much screwed then, right?
Thanks again man.

IlChengis said:
Hey bud, thanks for taking the time to help me out and explain.
I'm not entirely sure, but I'd venture to say that it's SIM Unlocked.
Is there a quick way to tell for sure?
Click to expand...
Click to collapse
Boot the phone into Fastboot/Bootloader mode (see -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm ) The status code will be there.
If you have an ATT XT1058, they are shipped Bootloader locked, and the only way to unlock them is to use the Chinese web site or Middeman selling the codes. So unless you bought the phone USED from someone who already did this, its bootloader is locked.
IlChengis said:
If it turns out being bootloader LOCKED, we're pretty much screwed then, right?
Click to expand...
Click to collapse
Pretty much, unless you don't mind voiding your phone's warranty, and then depending on the age of the phone, see the Chinese Middlman thread to buy a BOOTLOADER unlock code..
I've not tried to add languages to my phone, so I can't help you to do it. Just that based on the quick searches I've done, the results have always needed the phone's bootloader unlocked.

Nexus 6 unlocked without "Enable OEM unlock"

I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?

Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.

JulianPascal said:
I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?
Click to expand...
Click to collapse
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.

simms22 said:
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.
Click to expand...
Click to collapse
No, the developer options were not enabled. I got into fastboot mode, made sudo fastboot oem unlock, clicked yes and it was unlocked. I flashed the Android 6 image manually and after that i couldn't relock it. I had then to activate the developer options to relock the device.

gee2012 said:
Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.
Click to expand...
Click to collapse
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.

JulianPascal said:
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.
Click to expand...
Click to collapse
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?

gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?
Click to expand...
Click to collapse
i think ive read about two more phones that had that "glitch", but its not common for sure.

simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
I`am glad there is still some magic left in this world

gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch
Click to expand...
Click to collapse
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)

JulianPascal said:
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)
Click to expand...
Click to collapse
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?

simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?

JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
Thats probably it, had that on a N4 too once when i used CF Auto-Root (not wiped)

JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.

gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
I did a full wipe before flashing, so I'm not shure if the upgrade process itself reseted the device.

gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
simms22 said:
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.
Click to expand...
Click to collapse
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.

JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.

simms22 said:
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.
Click to expand...
Click to collapse
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?

JulianPascal said:
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?
Click to expand...
Click to collapse
mistakes do happen. ive seen people buy a n6 from tmobile but receive an att version, with all the att trimings. if you want to check if locking it is possible, you probably should. but, i think it probably is safe to use.

Theoretically someone could have bought it, opened it, unlocked it and did what ever with it, somehow reasealed it and returned it to the retailer(you have the right to return something you bought online in a 14 day period in germany).
I noticed something there are two numbers which are each 11 digits long, one on the the bottom and one on the side of the packaging.
(I covered them on the pictures, but marked where they are)
The two numbers differ at my packaging, Is this normal or should the two numbers be the same?
{
"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"
}

JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
I have read this as well.

Hardbricked G6 Plus

Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!

Can you still boot in the bootloader?

Thomas Hunter said:
Can you still boot in the bootloader?
Click to expand...
Click to collapse
Yes, bootloader is working fine.
Just Recovery isnt working, it goes in but wont load menu.

You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
OEM unlock is unticked so... I cant really unlock the bootloader..

The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk

Xplorer4x4 said:
The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
I tried to unlock it but i always got an error, something like "go to Settings and activate OEM Unlock" or something like this..

Could you provide a image

Thomas Hunter said:
Could you provide a image
Click to expand...
Click to collapse
Sure!
{
"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"
}

TrueGodFlow said:
Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!
Click to expand...
Click to collapse
Hi, Dan...
I really do wish I had some good news to impart, but sadly I suspect your Moto G6 Plus is probably not recoverable.
The OEM Unlocking setting in Developer Options is part of Googles Factory Reset Protection scheme. Ostensibly, it's designed to prevent lost or stolen devices from being reflashed back to stock and dishonest individuals then claiming the device as their own.
I ran afoul of this myself, four years ago, with my (then) new Nexus 9 tablet which originally shipped with Android 5, Lollipop and it was the first device I'd owned that required OEM Unlocking to be enabled in Developer Options before the bootloader could be unlocked.
I won't bore you with the details here, but if you have a mind to, you can read about my thwarted endeavours to resurrect my Nexus 9 here...
https://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Fortunately, my Nexus 9 was still new, and I had a no-quibble warranty that I'd paid extra for, so I was able to get it replaced at the store from which I'd bought it.
-----------------------------------------
Around 2015 a solution (of sorts) was eventually found for this problem, for both the Nexus 6 phone and the Nexus 9 tablet, however it required a very specific set of criteria for it to work.
The OEM Unlocking setting in Developer Options flips a binary state flag, from either ON (Enabled) or OFF (Disabled) and it's stored in a special Persistent (PST) partition, which doesn't get touched when factory resetting the device, when receiving OTA updates or when reflashing it. As the name suggests, it 'persists'.
So it required somebody to create a dump image file of the PST partition with the OEM Unlocking flag already set to ENABLED on their device. This dump image file would be created by using a <dd, if, of> command in a terminal shell.
The person whose device was semi-bricked, would download this dump image file of the PST partition, and flash it to their device using a similar <dd, if, of> shell command, via ADB in TWRP Custom Recovery. This would overwrite their PST partition, where the OEM Unlocking flag is NOT enabled...
...with a version where it IS enabled, and consequently fastboot flash commands would then work.
*****
It required root on both devices, and TWRP custom recovery to be already flashed on the semi-bricked device, since ADB shell commands can not be run in the normal stock recovery.
You can read about the technical details here...
https://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
-----------------------------------------
Theoretically, the method detailed above could perhaps be adapted for the Moto G6 Plus ~ you'd just need to find somebody with an already rooted Moto G6 Plus prepared to create a dump image file of their PST partition, with the OEM Unlocking setting enabled, and your G6 Plus would also need to be able to boot into TWRP to run the necessary ADB shell command to flash it.
And which is impossible, since (due to your locked bootloader) you can't either remotely boot TWRP from a laptop using fastboot boot twrp.img or flash it directly using fastboot flash recovery twrp.img
As I say, I wish I had better news for you.
-----------------------------------------
I hope all of the above makes sense; it is a little technical.
If I have any ideas that may be helpful, I'll post them here. But as it stands right now, and knowing what I know about this topic, I'm not optimistic there is a solution to your problem.
Ged.

The only other thing I can think of that may or may not work is a blankflash. Search the forums for it.
Sent from my moto g(6) plus using Tapatalk

You don't need to unlock oem as I got the same problem a year ago with my moto g5 plus so basically what I did was keep trying to flash a different fimware and eventually it worked with installed a firmware with oem locked.

X50 RMX2144 Bootloader access

Hi
I'm looking for a method to access bootloader on the RMX2144 model (European version I think).
The in-depth app does not work, the model is not supported by the application.
I tried to run adb reboot bootloader but the phone reboot, show a message during half a second and then restart.
Can someone help me ?
Thanks in advance
EDIT : Here is the displayed message
{
"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"
}
In english :
Has entered Fastboot
Long press the power button for 6~10 seconds or reload the battery to exit

useless

xam666 said:
Hi
I'm looking for a method to access bootloader on the RMX2144 model (European version I think).
The in-depth app does not work, the model is not supported by the application.
I tried to run adb reboot bootloader but the phone reboot, show a message during half a second and then restart.
Can someone help me ?
Thanks in advance
EDIT : Here is the displayed message
In english :
Has entered Fastboot
Long press the power button for 6~10 seconds or reload the battery to exit
Click to expand...
Click to collapse
Im having the same problem here with my rmx2025 (China model) Im really sad i cant install custom roms on this phone

ROM_gamer987 said:
Im having the same problem here with my rmx2025 (China model) Im really sad i cant install custom roms on this phone
Click to expand...
Click to collapse
Mine is RMX2025 as well. If you can unlock bootloader, please share the method. Thanks in advance.

siamese007 said:
Mine is RMX2025 as well. If you can unlock bootloader, please share the method. Thanks in advance.
Click to expand...
Click to collapse
Sadly i don't think there is a method method for this phone, i asked in the Chinese forums and I'm waiting for a response

ROM_gamer987 said:
Sadly i don't think there is a method method for this phone, i asked in the Chinese forums and I'm waiting for a response
Click to expand...
Click to collapse
Thank you for your quick reply. I will wait for your future solution hopefully.
I did everything about unlock bootloader from Chinese post but the depth test apk said my phone is not supported! what the....

siamese007 said:
Thank you for your quick reply. I will wait for your future solution hopefully.
I did everything about unlock bootloader from Chinese post but the depth test apk said my phone is not supported! what the....
Click to expand...
Click to collapse
yea same for me, its very weird lets just hope someone finds something, I have managed to go on QDL (QUALCOMM usb flash mode) I think with the right tools twrp could be installed from there without even unlocking the bootloader, for now we just have to wait

ROM_gamer987 said:
yea same for me, its very weird lets just hope someone finds something, I have managed to go on QDL (QUALCOMM usb flash mode) I think with the right tools twrp could be installed from there without even unlocking the bootloader, for now we just have to wait
Click to expand...
Click to collapse
I am not sure if installing TWRP without unlocking bootloader will be useable for installing Custom ROMs or GSI ROMs. Without unlocking bootloader, installing these Custom ROMs may brick the phone. :crying::crying::crying:
Well I will keep looking for the solution for this also. Thanks for the update. :highfive:

ROM_gamer987 said:
yea same for me, its very weird lets just hope someone finds something, I have managed to go on QDL (QUALCOMM usb flash mode) I think with the right tools twrp could be installed from there without even unlocking the bootloader, for now we just have to wait
Click to expand...
Click to collapse
Hello Bro,
There is a link here on XDA that explains how to unlock bootloader.
I just sold my phone so I don't have one to try. Please try this if this works on your RMX2025. If the app works on your model, then I will order the new X50 5G to unlock bootloader.
By the way, have you heard any updates from Chinese post for the problem unlocking bootloader?
I am looking for a solution to unlock bootloader on RMX2025.
:highfive:

The problems of unlocking the bootloader come because they are rmx2025?
The RMX2144 can be unlocked with the realme apk? He has problems? Is there a bootlop?
The only solution would be to access the recovery and install a rom for otg?
Thanks friends

totmakina said:
The problems of unlocking the bootloader come because they are rmx2025?
The RMX2144 can be unlocked with the realme apk? He has problems? Is there a bootlop?
The only solution would be to access the recovery and install a rom for otg?
Thanks friends
Click to expand...
Click to collapse
My RMX2025 was not supported by the deep testing app for no reason. I have no RMX2144 but my best guess is this model is good to go with the deep testing app.
If you wanna install custom ROMs or GSI, unlocking bootloader is very necessary from my experiences so far. I have never been able to flash Android phones with no unlock bootloader once.
I would not recommend to flash custom ROMs via ADB, this may cause the phone to brick. And while your phone is not unlocked bootloader, unbricking it will be nighmare and hardcore. :crying::crying:

Unlocking boot is essential in order to install twrp or custom roms.
If the smartphone fails and brick, I think it could be restored through an otg installation from recovery stock.
I will risk unlocking the boot with the realme tool on the RMX 2144. If there is success I will comment on it
Thanks!

totmakina said:
Unlocking boot is essential in order to install twrp or custom roms.
If the smartphone fails and brick, I think it could be restored through an otg installation from recovery stock.
I will risk unlocking the boot with the realme tool on the RMX 2144. If there is success I will comment on it
Thanks!
Click to expand...
Click to collapse
Hello Pal,
Any updates for unlocking bootloader for RMX2144? Now I have RMX2144. The phone is great except there is no custom ROMs yet. So sad. :crying::crying:
Edit: If we can unlocking bootloader, we can flash GSIs which are close to specific custom ROMs.

Hi. Friend. Unable to unlock bootloader with the tool. I understand that Realme no longer grants this option. Return the mobile and buy the POCO X3. Tomorrow I will have the permission to open the boot and be able to flash TWRP. Besides, POCO already has custom roms. I intend to install Q LeOs in the bit and not depend on Google services

totmakina said:
Hi. Friend. Unable to unlock bootloader with the tool. I understand that Realme no longer grants this option. Return the mobile and buy the POCO X3. Tomorrow I will have the permission to open the boot and be able to flash TWRP. Besides, POCO already has custom roms. I intend to install Q LeOs in the bit and not depend on Google services
Click to expand...
Click to collapse
Hi friend. Thanks a lot for your updates.
I will probably do the same. :good: For me, I don't mind if there is no Custom ROMs for this phone. As long as I can unlock bootloader I will be able to flash GSI. Xiaomi phones will be my replacement as well.
By the way, RMX2051 can unlocked but there is no Custom ROMs for this phone anyways. :crying:
Laters,

No good news yet so I guess we won't get any custom roms for this unit. To bad for a good phone otherwise but the lack of root/custom rom make me wanna cry, why doesn't realme help the community out. Think I will try to make a refund and get a xiaomi 10 lite or a poco instead.

Need Help Unlocking Bootloader and Rooting ROG Phone 3 by Asus

Update:
____________________________
FINALLY SUCCESS!
Downgrading my ROG Phone 3 to android 10 and using the unlock too (NOT OBIWAN) and finally success! For other peoples reference, the Firmware version I used was:UL-ASUS_I003_1-ASUS-18.0823.2104.147-1.1.95-user.zip, and the unlock tool I used was AsusUnlock_1.0.0.7_210127_fulldpi(1).Zip.
Many thanks for all the assistance and suggestions!! If this thread needs to be marked in someway to show the issue was fixed, please let me know, I'm still a little new here. Thanks!
I do have one final question ( for now)
If I upgrade to android 12 via dropping the file and running the upgrade through the phone like normal, the boot loader should STAY unlocked, correct?
Original Post:
_____________________________
Alrighty! I'm average linux user with a ROG Phone 3, I'm not completely sure as to whether it's the strix edition or not - at first I didn't think so but I got the model "ASUS_I003DD" so? Not really sure what to make of it. I'm not a pro with adb but any advice and pointers that can be offered I'd really appreciate - end goal is to root the phone but I feel confident I can figure that out if I can get the bootloader unlocked... which all traditional and googled answers seem to not work.
I've tried unlocking the bootloader with both Strix and normal Asus bootloader unlock apps(links at the botttom). I even downgraded to Android 11 because I noticed that Asus had a separate tool specific for android 11 but to no avail, I run
(bashshell)~$ adb reboot-bootloader
(bashshell)~$ fastboot oem device-info
and every time it has returned:
(bashshell-output):
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Device Authorized: false
I am not sure what steps to take next. Suggestions? Advice from someone who has unlocked the rog3 before??
Strix firmware/support and app
ROG Phone 3 Strix Edition | ROG Phone 3 Strix Edition | Gaming Phones｜ROG - Republic of Gamers｜ROG Global
ROG Phone 3 Strix Edition is everything you’ve always wanted for mobile gaming! Play Cooler. Play Faster. Absolute Control.
rog.asus.com
Normal Rog3 firmware/support and app
ROG Phone 3
ROG Phone 3 sets the new standard for mobile gaming! Absolute Power. Absolute Visuals. Absolute Control.
rog.asus.com

Is the device original Global version or converted from a Chinese version that has been unlocked and then re-locked before you bought it? That may be the explanation. My guess is your device id is not being validated by the ASUS server when using the unlock tool. These devices cannot be unlocked through the conventional OEM unlock methods (unfortunately) because ASUS have removed that as an option.

I think this is not a problem since my rog and the Chinese version that was converted I used, I used Asus' own app to unlock it, I rooted everything perfect

hermam said:
I think this is not a problem since my rog and the Chinese version that was converted I used, I used Asus' own app to unlock it, I rooted everything perfect
Click to expand...
Click to collapse
What steps did you take? What firmware did you use? I’ve used both versions of android (11 & 12) and both unlock apps (for 11 and for 12) and the boot-loader remains locked. What steps did you take? What information can I relay to you to help? The most that ever happens, is unless there’s a “network error” for the app, it will reboot the phone, not reset and not unlock the phone.

Andrologic said:
Is the device original Global version or converted from a Chinese version that has been unlocked and then re-locked before you bought it? That may be the explanation. My guess is your device id is not being validated by the ASUS server when using the unlock tool. These devices cannot be unlocked through the conventional OEM unlock methods (unfortunately) because ASUS have removed that as an option.
Click to expand...
Click to collapse
What would you recommend to test if that is the situation or not? If it is, do we know how to unlock it “unconventionally”?

meisnerwest said:
What would you recommend to test if that is the situation or not? If it is, do we know how to unlock it “unconventionally”?
Click to expand...
Click to collapse
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.

Andrologic said:
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Click to expand...
Click to collapse
The Asus unlock tool will either (A) reboot the phone, but change nothing (nothing is reset, bootloader still locked) or (B) run a error that it complains could be a network error.
When you say "change the device fingerprint" do you mean the firmware? so if it is a China model or UK model for instance, flashing it back to that models firmware, running the unlock, and then flashing it the user's preference?
If so-> Do we have a way to tell what the appropriate firmware for the devices should be?( UK,CN, etc)
If someone does have "unconventional" methods I have LG phone I'd love to unlock at some point smh. One phone at a time! I'll troll the forums some more.

Andrologic said:
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Click to expand...
Click to collapse
By the way! I did some looking and the strix and normal edition appear to have writing on the back of the phone on the sim tray side - "strix edition" and "areodynamic '???'tek" - which my phone apears to have neither?? I have attached the photo i took as well as the photos I'm referencing. Could I get some thoughst on this? Does this help knowing where this phone came from? (CN WW TW etc)
{
"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"
}
QUICK UPDATE: I did a little digging on this page:https://forum.xda-developers.com/t/...-ww-with-final-android-9-1910-64-raw.4002279/
and attached a screenshot of my device hardware info. From that am I to believe that the phone already has the global fingerpint and global firmware?

@meisnerwest
my phone is from tencent CN version Rog3 and it is irrelevant even if it's strix or whatever. if nothing is working for you try to downgrade to A10 , that's the firmware i had when i unlocked my bootloader using the applicatiom from their website.
if it just reboot and nothing happen try the older version of the application.

meisnerwest said:
By the way! I did some looking and the strix and normal edition appear to have writing on the back of the phone on the sim tray side - "strix edition" and "areodynamic '???'tek" - which my phone apears to have neither?? I have attached the photo i took as well as the photos I'm referencing. Could I get some thoughst on this? Does this help knowing where this phone came from? (CN WW TW etc)View attachment 5796715View attachment 5796717View attachment 5796721
View attachment 5796717
QUICK UPDATE: I did a little digging on this page:https://forum.xda-developers.com/t/...-ww-with-final-android-9-1910-64-raw.4002279/
and attached a screenshot of my device hardware info. From that am I to believe that the phone already has the global fingerpint and global firmware?
Click to expand...
Click to collapse
this is strix edition. did you manage to root your phone?

osomakohj said:
this is strix edition. did you manage to root your phone?
Click to expand...
Click to collapse
I have gotten the boot loader unlocked but I have not rooted it yet. If you have advice I'm all ears!

meisnerwest said:
I have gotten the boot loader unlocked but I have not rooted it yet. If you have advice I'm all ears!
Click to expand...
Click to collapse
we're on same boat. I've used the app you mentioned and unlock my a12 rog3. Just confuse about rooting. Does rooting active slot enough? Or should I root both slot? Because I am afraid about flashing TWRP. The root method I like to do is to patch the booting ang flash via fastboot

osomakohj said:
we're on same boat. I've used the app you mentioned and unlock my a12 rog3. Just confuse about rooting. Does rooting active slot enough? Or should I root both slot? Because I am afraid about flashing TWRP. The root method I like to do is to patch the booting ang flash via fastboot
Click to expand...
Click to collapse
Gotcha, I’ll let y’all know if I come across anything good then I’ll let y’all know what happens.

meisnerwest said:
Update:
____________________________
FINALLY SUCCESS!
Downgrading my ROG Phone 3 to android 10 and using the unlock too (NOT OBIWAN) and finally success! For other peoples reference, the Firmware version I used was:UL-ASUS_I003_1-ASUS-18.0823.2104.147-1.1.95-user.zip, and the unlock tool I used was AsusUnlock_1.0.0.7_210127_fulldpi(1).Zip.
Click to expand...
Click to collapse
Hi, this method works for me, April 10 2023
Thank you very much

Faye Reagan said:
Hi, this method works for me, April 10 2023
Thank you very much
Click to expand...
Click to collapse
Not working for me, on the same firmware and using the latest unlock tool.