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.
Related
I alreaydy by an unlock code via internet and tried to unlock my m9. But i had one problem. When i put a blocked simcard in. It doesnt show the unlock pin pad. One message was showed off nad said i had to use the Device Unlock app to unlock my phone via system. Did anyone try to unlock your phone? Only one thing i saw was a blocked-key on signal bar.Please help me.thanks
haido1191 said:
I alreaydy by an unlock code via internet and tried to unlock my m9. But i had one problem. When i put a blocked simcard in. It doesnt show the unlock pin pad. One message was showed off nad said i had to use the Device Unlock app to unlock my phone via system. Did anyone try to unlock your phone? Only one thing i saw was a blocked-key on signal bar.Please help me.thanks
Click to expand...
Click to collapse
Hmm, maybe we have to disable the T-Mobile Sim unlocker then it'll prompt on other Sims? Disable this app, reboot and try again.
{
"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"
}
Please provide screen shots, your dialogue is a bit confusing.
Sent From My HTC One (M9)
i already did what you said before post this question. i'll upload some pictures to let you see
haido1191 said:
I alreaydy by an unlock code via internet and tried to unlock my m9. But i had one problem. When i put a blocked simcard in. It doesnt show the unlock pin pad. One message was showed off nad said i had to use the Device Unlock app to unlock my phone via system. Did anyone try to unlock your phone? Only one thing i saw was a blocked-key on signal bar.Please help me.thanks
Click to expand...
Click to collapse
This is some picture
haido1191 said:
This is some picture
Click to expand...
Click to collapse
You disabled the very application you need to use to unlock your device. How do you expect to ever do this when you have the application disabled. Re-enable the application access it from your app drawer and follow the on-screen instructions!
Since this is a tmobile device, its setup to be unblocked through T Mobile's method. You could try pushing a new default XML with a generic SKU instead of T Mobile's and perhaps you would get a traditional unlocked menu but as long as you have a tmobile SKU, you won't.
See here for more information:
https://support.t-mobile.com/docs/DOC-14011
The point is i want to unlock the m9 with out the apps. I already did what you said. Enabled the apps and unlock via the app but it was failed because its a new device and im not eligable to unlock the phone.
haido1191 said:
The point is i want to unlock the m9 with out the apps. I already did what you said. Enabled the apps and unlock via the app but it was failed because its a new device and im not eligable to unlock the phone.
Click to expand...
Click to collapse
Friend, I explained it quite clearly in my post above. Your default XML has set your device with the tmobile SKU. there is no way to unlock the device outside of T Mobile app with that sku. it is designed this way on purpose! You must modify your sku and I'm not going to walk you through that process. just as you said you are INELIGIBLE to unlock and that is why it won't work for you. You're trying to trick your way around and frankly well you're going to need a hack for that. Sunshine version 3.1 will support s-off as well as GSM network unlock. maybe look into that but as long as you don't modify your sku you can't unlock the old way you want.
guyz any update on unlocking the t mobile htc one m9 without the app. ???
I already contact the customer service and got an email that said i can unlock my phone but when i tried using the app,it was fail. Anyone get other methods????
unlocked HTC One M9 Tmobile
I was able to get my Tmobile HTC One M9 S-OFF, and change SuperCID it (11111111), but haven't been able to figure out how to unlock it via fastboot command. I might try to load the HTC AT&T RUU to see if that works. Will keep you posted
---------- Post added at 12:50 AM ---------- Previous post was at 12:48 AM ----------
haido1191 said:
I already contact the customer service and got an email that said i can unlock my phone but when i tried using the app,it was fail. Anyone get other methods????
Click to expand...
Click to collapse
I'm afraid that this is the direction Tmobile is going. The HTC One M9 is the second device they use the unlock app, instead of the unlock pin code like before. First it was the Samsung Avant, and now this phone. Have any one tried to see if the Tmobile Galaxy S6 is the same?
Thanks
h4ng0ver said:
I was able to get my Tmobile HTC One M9 S-OFF, and change SuperCID it (11111111), but haven't been able to figure out how to unlock it via fastboot command. I might try to load the HTC AT&T RUU to see if that works. Will keep you posted
---------- Post added at 12:50 AM ---------- Previous post was at 12:48 AM ----------
I'm afraid that this is the direction Tmobile is going. The HTC One M9 is the second device they use the unlock app, instead of the unlock pin code like before. First it was the Samsung Avant, and now this phone. Have any one tried to see if the Tmobile Galaxy S6 is the same?
Thanks
Click to expand...
Click to collapse
How did you soff the M9? I want to get mine soff but don't know how
Same question. Lol
Sent From My HTC One (M8)
Nilsonf said:
How did you soff the M9? I want to get mine soff but don't know how
Click to expand...
Click to collapse
with a java card
---------- Post added at 01:00 AM ---------- Previous post was at 12:09 AM ----------
h4ng0ver said:
with a java card
Click to expand...
Click to collapse
Okay guys. I was able to unlock the phone with the unlock code (which purchased online). You don't need the phone to be S-OFF, but need to unlock bootloader (at htcdev.com), and flash the TWRP recovery, make sure you download and flash the latest beta TWRP 2.8.6.4 from Captain_Throwback.
Once that's done, need to download the Android Evolution HD 4.1 from HTC One M9 development forum, and flash it. It will ask for the unlock code with SIM card that is not Tmobile
I will try to flash back the original stock ROM to see if it still asks to unlock the phone with the unlock app, but so far it works great.
h4ng0ver said:
with a java card
---------- Post added at 01:00 AM ---------- Previous post was at 12:09 AM ----------
Okay guys. I was able to unlock the phone with the unlock code (which purchased online). You don't need the phone to be S-OFF, but need to unlock bootloader (at htcdev.com), and flash the TWRP recovery, make sure you download and flash the latest beta TWRP 2.8.6.4 from Captain_Throwback.
Once that's done, need to download the Android Evolution HD 4.1 from HTC One M9 development forum, and flash it. It will ask for the unlock code with SIM card that is not Tmobile
I will try to flash back the original stock ROM to see if it still asks to unlock the phone with the unlock app, but so far it works great.
Click to expand...
Click to collapse
Like I said in my first post you don't need to do any of that. You need to unlock your device root your phone and change your SKU in default.xml from tmobile (11) to any other
You flashed an international based ROM so your sku is likely set to 6
It didn't work. I also tried to remove freeze the Tmobile unlock app, but the phone would not ask for unlock code. Have not tried other rom, but Android Evolution rom did ask for the unlock code.
h4ng0ver said:
It didn't work. I also tried to remove freeze the Tmobile unlock app, but the phone would not ask for unlock code. Have not tried other rom, but Android Evolution rom did ask for the unlock code.
Click to expand...
Click to collapse
I never said anything about freezing the app
I didn't say you did. I said i tried your method which did not work, and I ALSO tried to freeze the unlock app. Anyway, i don't care at this point because I have found a way that works for me.
Thanks
I flashed the phone back with original Tmo RUU, and unlock appears to stick. It works with AT&T 4G LTE, and no snag screen from the annoying unlock app.
Hope that helps, good luck
h4ng0ver said:
I flashed the phone back with original Tmo RUU, and unlock appears to stick. It works with AT&T 4G LTE, and no snag screen from the annoying unlock app.
Hope that helps, good luck
Click to expand...
Click to collapse
Oh nice. Good to know. Hopefully you hit the thanks button on that RUU thread. ?
Sent From My HTC One (M8)
Question
h4ng0ver said:
with a java card
---------- Post added at 01:00 AM ---------- Previous post was at 12:09 AM ----------
Okay guys. I was able to unlock the phone with the unlock code (which purchased online). You don't need the phone to be S-OFF, but need to unlock bootloader (at htcdev.com), and flash the TWRP recovery, make sure you download and flash the latest beta TWRP 2.8.6.4 from Captain_Throwback.
Once that's done, need to download the Android Evolution HD 4.1 from HTC One M9 development forum, and flash it. It will ask for the unlock code with SIM card that is not Tmobile
I will try to flash back the original stock ROM to see if it still asks to unlock the phone with the unlock app, but so far it works great.
Click to expand...
Click to collapse
Dear sir, would you please tell us with more detail the process that you used to unlock your m9? I've been trying to unlock my 4 M9s for a month now, and I would truly appreciate a detailed walk through.
Thank you so much, and god bless you.
i took my note 3 back to 4.4.2 and got the root on it and pulled and unpacked the boot and recovery img with carliv kitchen (http://forum.xda-developers.com/and...wm-based-recovery-t2973804/page8#post68550781)
I am following that guide. This is my first go at building a recovery and, hopefully, eventually a rom.
Just testing my feet before i jump into working on my note 4 and note 5. *im a samsung guy... all samung are belong to me... lol*
im stuck at the part where he is talking about building the fstab and init.rc.
not sure if this needs to be custom or not. I just want to create a stock rom with CWM recovery. Thats all. Can i just unpack the the stock recovery and boot and shove the CWM custom stuff in and repack it?
thanks for the help
Since the n900a has a locked bootloader, would cwm or twrp be possible?
don't really know if its locked... since i pulled the boot and recovery and it its flashable via odin....
I am having more issues with the basics of building here. not really the full application of the build.
if the boot loader was locked the why was i able to downgrade it? it was running 5.0 now on 4.4.2 and rooted.
don't know if others were not able to do the same but... really just need help understanding the next steps in building the custom recovery.
Even though the bootloader is locked, it may allow a downgrade to 4.4.2 from 5.0. Downgrading the bootloader doesn't automatically mean TWRP or CWM can be flashed to the phone.
People whose phone have a locked bootloader are using safestrap to flash the 900a.
audit13 said:
Even though the bootloader is locked, it may allow a downgrade to 4.4.2 from 5.0. Downgrading the bootloader doesn't automatically mean TWRP or CWM can be flashed to the phone.
People whose phone have a locked bootloader are using safestrap to flash the 900a.
Click to expand...
Click to collapse
well if it helps... i have a unlocked symbol and the word custom that show on the screen when it boots up.
This is kinda irregardless. I can emulate the test... that isn't an issue. I want to work on the basics of building... so my question isn't about the boot loader being locked or not.
I have the Boot.img and the Recovery.img on my local machine, unpacked with carliv kitchen. i just need to know what i need to copy over or what needs to be completely customized by hand. I am really new to the process of creating a custom recovery.
I'll worry about the flashing to device later.
It's my understanding that TWRP and CWM cannot be flashed to a phone with a locked bootloader which is why there is no TWRP build for this particular Note 3.
I wish you luck in your endeavour as I am sure a lot of users will be happy with something other than safestrap.
audit13 said:
It's my understanding that TWRP and CWM cannot be flashed to a phone with a locked bootloader which is why there is no TWRP build for this particular Note 3.
I wish you luck in your endeavour as I am sure a lot of users will be happy with something other than safestrap.
Click to expand...
Click to collapse
you keep talking about the boot loader but never even mention my question. my question has nothing to do with the boot loader or flashing the device.
I am asking about building. not the bootloader... this question is indifferent to even the phone i am on.
I am stuck on the instructions. I am just trying to figure out all the stuff that would need to be copied to the build device tree recovery/root. This should be standard in all phones or devices... I need to know what it is that makes the CWM recovery custom. are there files i need to replace with the original files. my original post has the link in the guide i am following. so if anyone can help answer that question i would appreciate it.
but thank you for the luck... it looks like i need it just to get somebody to answer some basic building questions.
I mention the bootloader because that seems to have been a stumbling block for users that want to use twrp to flash ROMs.
I will be the first to admit that I don't know anything about building twrp.
I will bow out now and leave you to your task.
Thanks for replying to my posts.
Building cwm I can't help you with. But cwm for note 3 att is useless. You can't flash it. Who uses cwm these days? Twrp isn't a preference it's the only real option anymore other than adb and fast boot.
Sent from my DROID Turbo using XDA-Developers mobile app
Some pics. But is not the point of my question. Please read the question.
Ok... this is going to seem like a noob question.... How can i prove that my bootloader is unlocked.
What would i need to do to prove or disprove it. Is there a log or something. This is literally my first go. Show me why it can't be flashed. I am not seeing the answer to this in any of the instructions.
You can't just say something is locked and that be the end of it. How is it locked. I can get into boot loader.
besides. This is solely to help me learn the basics of building a custom recovery. I have another device I want to work on but thats the device i don't want to brick. I am using this as a testing device to learn. I only want to learn to create the thing... i already know how to install the custom stuff... and to answer the question of who uses it... well... obviously.. me... when I am working on an old device learning the basics and building for android 4.4.2...
I am still working on this.
{
"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"
}
Even though the bootloader is locked, this does not prevent a user from entering download or recovery mode.
To verify the bootloader version on your phone, you can install and run the Samsung Info App from the Play store.
audit13 said:
Even though the bootloader is locked, this does not prevent a user from entering download or recovery mode.
To verify the bootloader version on your phone, you can install and run the Samsung Info App from the Play store.
Click to expand...
Click to collapse
I got that installed. I am not sure what i am looking for. bootloader version?
Also, if the bootloader isn't unlocked... what does the picture i posted with the unlocked lock with the word custom beneath it mean?
I believe that, starting with a stock 4.3 ROM, the bootloader was locked. Maybe your phone is running an older ROM before AT&T locked the bootloader?
It looks like your bootloader may be unlocked but I'm not 100% sure as I don't have the n900a, I have an n900w8.
A sure fire way to see if the bootloader is locked would be to flash a stock LP ROM to the phone and then try to flash non-officlal software; however, I don't recommend doing this as it may hard brick the phone.
As far as I know, no one has claimed the XDA bounty for unlocking the AT&T Note 3 and S4 bootloader.
http://forum.xda-developers.com/showthread.php?t=2708609
Notice here that there is no mention of TWRP or CWM: http://forum.xda-developers.com/showthread.php?t=2710972
Well. I sent the OP on that post a message as the thread is locked. since july i think?
I think the thread was locked because safestrap is a viable recovery for the n900a.
I believe there is a version of TWRP for the n900a but it can only be installed on a phone without a locked bootloader.
well i sent the OP and the perosn who locked the thread... Ironically... the guy that locked the bootloader lives about 30 minutes from me...
I wish that more people would see this thread... or perhaps someone could just help me out with the building part... I have figured out most of it.... im just having a hard time understanding some of the small concepts.. what files need to be changed and what files need to be left alone.
therealtaynak said:
well i sent the OP and the perosn who locked the thread... Ironically... the guy that locked the bootloader lives about 30 minutes from me...
I wish that more people would see this thread... or perhaps someone could just help me out with the building part... I have figured out most of it.... im just having a hard time understanding some of the small concepts.. what files need to be changed and what files need to be left alone.
Click to expand...
Click to collapse
Yep that phone still has a locked bootloader
Ok... My question was about building anyway... i don't really care about flashing it... I am only using it because i am trying to learn the building process...
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.
Here's the tool. Freshly modded by yours truly.
https://mega.nz/#!uNwERIDK!1fbu5KGWH441r0EFwHb_rgEamjax068RAjT-Ze9ELVc
You know what to do - power down, hold volume up and volume down, connect USB, run it.
This will convert you to the T-Mobile firmware. T-Mobile users with the non-TMO phone who run this tool and convert will get better WiFI Calling support + T-Mobile bloat + possibly working RCS. You will lose dual SIM support.
If you wind up wanting to restore back to international firmware, grab the international (GM1917) MSM tool from the 'Guac For All' thread. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Enjoy!
how's RCS working for you? i have the international version too and thinking about switching to see if its better for my MMS and calling
This works great! Don't know if I will keep it TMobile or not, but working great so far.
Sent from my GM1917 using Tapatalk
RCS chat seams to be working. Although I don't know anyone else that has it to test it out.
{
"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"
}
Sent from my GM1917 using Tapatalk
I did notice that the fingerprint sensor is not nearly as good with the T-Mobile firmware. It worked almost every time when it was international, but with the T-Mobile firmware installed, it failed most times, so I disabled it.
Sent from my GM1917 using Tapatalk
DTop said:
T-Mobile users with the non-TMO phone who run this tool and convert will get better WiFI Calling support
Click to expand...
Click to collapse
On the stock T-Mobile ROM does it turn off the cellular radio and disconnect from the tower when wifi calling is connected?
I remember my old T-Mobile Samsung doing this and it would save a lot of battery life.
Doesnt that msm tool in slayers thread do the same thing or is this easier? Also quick question ...i have a tmobile op7pro unlocked bootloader , rooted and on intl fw 9.5.8 ....what i want to do is go back to tmobile 9.5.8 and root /twrp ..... not used to this whole A/B slot thing...so what are my options? Msm tool back to tmobile boot device, turn on dev options make sure usb debugging/ oem unlock is on etc at this point is this where i can just flash twrp in fastboot? Or does this not work on tmobile fw?....because if so thats cool..im sure once twrp is installed i can flash maqisk etc
sarni84 said:
Doesnt that msm tool in slayers thread do the same thing or is this easier? Also quick question ...i have a tmobile op7pro unlocked bootloader , rooted and on intl fw 9.5.8 ....what i want to do is go back to tmobile 9.5.8 and root /twrp ..... not used to this whole A/B slot thing...so what are my options? Msm tool back to tmobile boot device, turn on dev options make sure usb debugging/ oem unlock is on etc at this point is this where i can just flash twrp in fastboot? Or does this not work on tmobile fw?....because if so thats cool..im sure once twrp is installed i can flash maqisk etc
Click to expand...
Click to collapse
From I can see, yes this is the same thing as slayer's thread. This thread is directed at T-Mobile users with the international model who want the T-Mobile software. Whereas slayer's thread is directed at those with the T-Mobile model who need to get back to stock.
As far as I know they both are the same, its just two different threads for two different reasons.
So either will work the same. It shouldn't matter if they're both the same T-Mobile firmware.
EDIT: Model number shows different on this build. See OP response.
If you just want rooted stock with Magisk and TWRP, once you're back on T-Mobile stock you can use the all in one tool to flash TWRP and install Magisk.
You shouldn't need to oem unlock the bootloader again. Once you unlock it, it always stays unlocked unless you manually relock it yourself.
All in one tool here: https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3930862
Extract that download and open tool all in one.
It should show adb device Oneplus 7 Pro at the top. Check fastboot drivers and usb connection if it doesn't. Also make sure your screen is on with usb debugging allowed.
Then click Recovery Flasher and Device Rooter.
Select "TWRP OP7P" from the list where it shows "MANUAL" in all caps.
Then check the box to root after boot, select the latest Magisk version from the drop down menu.
Click the button to start the process. It may ask to reboot into fastboot/bootloader, choose yes. If it works as it should, it will automatically download TWRP and Magisk and load them onto your phone.
Thanks bro yeah I know I won't have problems with the bootloader I was just worried about the stock boot image.... I thought I saw somewhere that you needed a modified one
KemikalElite said:
From I can see, yes this is the same thing as slayer's thread. This thread is directed at T-Mobile users with the international model who want the T-Mobile software. Whereas slayer's thread is directed at those with the T-Mobile model who need to get back to stock.
Click to expand...
Click to collapse
It is not the same thing. The tool in Slayer's thread will only work for converting from T-Mobile (GM1915) to international (GM1917 software, but the phone still displays the GM1915 model number in settings). The tool in this thread will only work for converting from International (GM1917) to T-Mobile (GM1915 software, but the phone still displays the GM1917 model number in settings).
Feel free to give it a try, you'll see XD
sarni84 said:
Thanks bro yeah I know I won't have problems with the bootloader I was just worried about the stock boot image.... I thought I saw somewhere that you needed a modified one
Click to expand...
Click to collapse
The stock boot image is injected when Majisk is installed, making it modified. It should install fine with the stock boot image/kernel. :good:
KemikalElite said:
The stock boot image is injected when Majisk is installed, making it modified. It should install fine with the stock boot image/kernel. :good:
Click to expand...
Click to collapse
Cool. U the man thanks:good:
Is it possible this can be modded for T-Mobile devices converted to International to go back to T-Mobile firmware? I ask for troubleshooting the sleep-of-death issue some of us have been experiencing and also in case of needing to warranty the device.
Link to the Sleep-Of-Death thread added.
https://forum.xda-developers.com/oneplus-7-pro/how-to/poll-phone-randomly-powered-off-t3940427
Se7eN43 said:
Is it possible this can be modded for T-Mobile devices converted to International to go back to T-Mobile firmware? I ask for troubleshooting the sleep-of-death issue some of us have been experiencing and also in case of needing to warranty the device.
Link to the Sleep-Of-Death thread added.
https://forum.xda-developers.com/oneplus-7-pro/how-to/poll-phone-randomly-powered-off-t3940427
Click to expand...
Click to collapse
If you have the T-Mobile version you should use this download instead to return to stock:
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
------------------------------------------------------
I loaded this on my phone and for anyone who wants to know, Safetynet works and L1 widevine (HD Netflix) works. I'm not sure how this happened, but the bootloader relocked on its own. (maybe after a factory reset, maybe I clicked something by accident) Either way you can lock the bootloader running this if needed as long as you aren't rooted or don't have a custom recovery, and it will work okay.
Edit: Locked bootloader wants unlock token to unlock now. Do NOT lock bootloader.
RCS works as well but visual voicemail doesn't even work on the stock ROM. I know this isn't a fault of the ROM, its a Oneplus or T-Mobile issue, but if Android supports built-in visual voicemail without using the terrible T-Mobile VVM app, it should work as intended. I remember visual voicemail working fine on my Nexus 5.
T-Mobile please fix this.
KemikalElite said:
If you have the T-Mobile version you should use this download instead to return to stock:
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
------------------------------------------------------
I loaded this on my phone and for anyone who wants to know, Safetynet works and L1 widevine (HD Netflix) works. I'm not sure how this happened, but the bootloader relocked on its own. (maybe after a factory reset, maybe I clicked something by accident) Either way you can lock the bootloader running this if needed as long as you aren't rooted or don't have a custom recovery, and it will work okay.
RCS works as well but visual voicemail doesn't even work on the stock ROM. I know this isn't a fault of the ROM, its a Oneplus or T-Mobile issue, but if Android supports built-in visual voicemail without using the terrible T-Mobile VVM app, it should work as intended. I remember visual voicemail working fine on my Nexus 5.
T-Mobile please fix this.
Click to expand...
Click to collapse
Wow! I can't believe I missed this. Thank you for prompt reply.
KemikalElite said:
If you have the T-Mobile version you should use this download instead to return to stock:
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
------------------------------------------------------
I loaded this on my phone and for anyone who wants to know, Safetynet works and L1 widevine (HD Netflix) works. I'm not sure how this happened, but the bootloader relocked on its own. (maybe after a factory reset, maybe I clicked something by accident) Either way you can lock the bootloader running this if needed as long as you aren't rooted or don't have a custom recovery, and it will work okay.
Edit: Locked bootloader wants unlock token to unlock now. Do NOT lock bootloader.
RCS works as well but visual voicemail doesn't even work on the stock ROM. I know this isn't a fault of the ROM, its a Oneplus or T-Mobile issue, but if Android supports built-in visual voicemail without using the terrible T-Mobile VVM app, it should work as intended. I remember visual voicemail working fine on my Nexus 5.
T-Mobile please fix this.
Click to expand...
Click to collapse
Ok so basically u can flash back to tmobile but it locks the bootloader... .so now if u want to unlock and STAY on tmobile u have to get an unlock token from one plus.....or just flash international and unlock again with command easily.....thats what i was worried about happening. Crazy how the bootloader gets locked again
Quick question to any one on the TMO version. Do the TMO firmware have video calling like must of TMO phones.
mario1634 said:
Quick question to any one on the TMO version. Do the TMO firmware have video calling like must of TMO phones.
Click to expand...
Click to collapse
Yes. and yes it sucks like other TMO phones
sarni84 said:
Ok so basically u can flash back to tmobile but it locks the bootloader... .so now if u want to unlock and STAY on tmobile u have to get an unlock token from one plus.....or just flash international and unlock again with command easily.....thats what i was worried about happening. Crazy how the bootloader gets locked again
Click to expand...
Click to collapse
Has anyone had any luck getting an Unlock Token for a GM1917? I tried the unlock site and it says I need a valid IMEI, and when I called OnePlus, the support rep said they only have the tools for the 6t.
Might try calling again today in case the late night call center was just ill equipt
Tardeaux said:
Has anyone had any luck getting an Unlock Token for a GM1917? I tried the unlock site and it says I need a valid IMEI, and when I called OnePlus, the support rep said they only have the tools for the 6t.
Might try calling again today in case the late night call center was just ill equipt
Click to expand...
Click to collapse
Any luck ?
Hello! Friends!
Because our language is not English
Even if my English is not good, please understand with your kindness!
First of all, I bought a Pixel 4 xl (Renew) factory unlock from Amazon.
but because of bad seller
I was very disappointed to find out that my phone was at&t locked.
Because my nationality is Korea
No one could solve this problem.
Because I don't know how to contact at&t and I can't.
Selling at&t unlocked service on eBay
I paid for it and tried to unlock it.
And it worked. I'm very happy!
Finally, the Pixel 4 is available.
And set one by one
Can't download e-sim.
Apparently at&t was unlocked (I checked it on the at&t website!)
My phone imei is fine!
But is this another issue with at&t unlocking?
What should I do?
As I've said before, I have no and no way to contact at&t.
So that I can use all the features of my Pixel 4
Thank you very much for your help.
I want help from friends here like the Avengers!
Thanks for reading the long post.
{
"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"
}
whitemilk_kor said:
Hello! Friends!
Because our language is not English
Even if my English is not good, please understand with your kindness!
First of all, I bought a Pixel 4 xl (Renew) factory unlock from Amazon.
but because of bad seller
I was very disappointed to find out that my phone was at&t locked.
Because my nationality is Korea
No one could solve this problem.
Because I don't know how to contact at&t and I can't.
Selling at&t unlocked service on eBay
I paid for it and tried to unlock it.
And it worked. I'm very happy!
Finally, the Pixel 4 is available.
And set one by one
Can't download e-sim.
Apparently at&t was unlocked (I checked it on the at&t website!)
My phone imei is fine!
But is this another issue with at&t unlocking?
What should I do?
As I've said before, I have no and no way to contact at&t.
So that I can use all the features of my Pixel 4
Thank you very much for your help.
I want help from friends here like the Avengers!
Thanks for reading the long post.
Click to expand...
Click to collapse
Sorry, but it looks like your phone is still carrier locked to AT&T. Until the phone is unlocked you will not be able to use it. If you access the developer options and you toggle the "allow OEM unlocking"? If this is greyed out or you are not able to toggle on, your phone is still carrier locked. The carrier lock has to be removed before you can use a different SIM or bootloader unlock. IF YOU CAN TOGGLE then bootloader unlock the phone and flash an image for your region.
There may be other methods to carrier unlock your phone on the black market but you won't find any information regarding that here.
v12xke said:
Sorry, but it looks like your phone is still carrier locked to AT&T. Until the phone is unlocked you will not be able to use it. If you access the developer options and you toggle the "allow OEM unlocking"? If this is greyed out or you are not able to toggle on, your phone is still carrier locked. The carrier lock has to be removed before you can use a different SIM or bootloader unlock. IF YOU CAN TOGGLE then bootloader unlock the phone and flash an image for your region.
There may be other methods to carrier unlock your phone on the black market but you won't find any information regarding that here.
Click to expand...
Click to collapse
Already my pixel has bootloader unlocked
It's not a global ROM, is there a ROM for each country?
Ooh, a fact I didn't know!
I wonder where to download Korean roms.
whitemilk_kor said:
Already my pixel has bootloader unlocked
It's not a global ROM, is there a ROM for each country?
Ooh, a fact I didn't know!
I wonder where to download Korean roms.
Click to expand...
Click to collapse
​Annyeonghaseyo!
How do you know your phone is unlocked? You didn't answer my question about the OEM unlocking toggle. Have you enabled USB debugging? In fastboot mode does it say "Device state: unlocked" If so, good!
If not, make sure usb debugging is enabled (dev options) and type the following commands in fastboot mode and post the exact responses:
fastboot get_unlock_ability
fastboot oem device-info
fastboot getvar cid
There are no Korean images, but some region specific for your carriers. There you will find for some months there are region specific images. Not every month. Just grab the latest one (July) and you may be able to fix your issue. Follow one of the guides here on flashing. Do not edit the flash-all.bat script. If you get any errors, capture those errors and post here.
Thank you very much for your interest in my problem!
The unlock toggle is like the picture.
Also like unlocked device state in fastboot.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I installed all of them in July, June, and May from this link
But when I scan e-sim qr, at&t is not activated like the picture.
Ironically, I bought the first one and used the e-sim.
And after factory reset, e-sim does not work for no reason
Why is the e-sim that was working fine, not activating after factory reset?
thanks again for your kindness
whitemilk_kor said:
Why is the e-sim that was working fine, not activating after factory reset?
thanks again for your kindness
Click to expand...
Click to collapse
I don't know anything about using an e-sim. I do know that if you factory reset from recovery mode it prompts you whether or not to delete all e-sim data. Maybe if you factory reset and delete all e-sim data you will have the opportunity to use your e-sim again? Just a guess. Also, why not try using a physical SIM card?