Heres how to get wifi on the stock rom without root.
Type these commands! and make sure you have fastboot setup on your computer.
Code:
fastboot oem unlock (Unlocks bootloader if your not already unlocked if your just skip this)and now do fastboot flash bootloader WIFIGWR.img
And now you can go do
Code:
fastboot oem lock
if you want to relock your bootloader.
Now enjoy wifi !
Thread closed as member has been proven to supply damaging files
Related
I have the XT-1052 version of Moto X and its running the Asia Retail firmware. I had unlocked the bootloader and flashed CM12 but returned to stock rom through this guide http://forum.xda-developers.com/moto-x/general/retail-firmware-uploaded-xt1052-t2976596. I will be selling the device and want to re lock the bootloader. Can i type the ''fastboot oem lock'' command in mfastboot tool and re lock the bootloader? Also, will it erase the whole data on the device?
KD25 said:
I have the XT-1052 version of Moto X and its running the Asia Retail firmware. I had unlocked the bootloader and flashed CM12 but returned to stock rom through this guide http://forum.xda-developers.com/moto-x/general/retail-firmware-uploaded-xt1052-t2976596. I will be selling the device and want to re lock the bootloader. Can i type the ''fastboot oem lock'' command in mfastboot tool and re lock the bootloader? Also, will it erase the whole data on the device?
Click to expand...
Click to collapse
Yes, fastboot oem lock will lock it, and no it will not wipe data. Only unlocking wipes data.
But you status code will show relocked you can never get status code back to locked once unlocked.
Travisdroidx2 said:
But you status code will show relocked you can never get status code back to locked once unlocked.
Click to expand...
Click to collapse
Correct. Whoever has the phone will be able to see the "tamper seal" that shows the bootloader was previously unlocked, but is now locked again.
I would provide whoever you sell the phone to the bootloader unlock code so they can unlock in the future if they so desire. Not sure if they can request the code from Motorola again or not.
fury683 said:
Correct. Whoever has the phone will be able to see the "tamper seal" that shows the bootloader was previously unlocked, but is now locked again.
I would provide whoever you sell the phone to the bootloader unlock code so they can unlock in the future if they so desire. Not sure if they can request the code from Motorola again or not.
Click to expand...
Click to collapse
I tried it but it asks me to flash the signed images. The link i mentioned above comes with an XML file which dictates the steps RSD should be following, right? So if i upload the XML file can you edit the command line and add the command? I am not an expert in this stuff.
i have relocked flashing manually with fastboot, not sure if you add the oem lock cmd to the xml will work.
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
hbenz2008 said:
i have relocked flashing manually with fastboot, not sure if you add the oem lock cmd to the xml will work.
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
Click to expand...
Click to collapse
The files that are present in the rom folder are boot.img, fsg.mbn, gpt.bin, logo.bin, motoboot.img, NON-HLOS.bin, recovery.img and system.img. Can you modify the list of commands to add the aditional files. Thanks.
just flashing the above is enough to relock. Flash away
Wireless...
hbenz2008 said:
just flashing the above is enough to relock. Flash away
Wireless...
Click to expand...
Click to collapse
Thanks man. Will update about how it goes.
I have read all of the info about unlocking and relocking the bootloader, but i have a question, if i was 100% stock with a locked bootloader and wanted to flash the latest factory image would i still need to enable developer options and enable allow oem unlock even if i was to run the commands below from fastboot mode.
fastboot oem unlock
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot oem lock
fastboot reboot
The reason i ask is that you are not booting into android until the bootloader is relocked, so in theory the oem unlock option shouldn't have an effect in this scenario?
@d.chatten,
Yes, you have to unlock the bootloader to use fastboot to flash .img files, or to sideload via ADB.
d.chatten said:
I have read all of the info about unlocking and relocking the bootloader, but i have a question, if i was 100% stock with a locked bootloader and wanted to flash the latest factory image would i still need to enable developer options and enable allow oem unlock even if i was to run the commands below from fastboot mode.
fastboot oem unlock
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot oem lock
fastboot reboot
The reason i ask is that you are not booting into android until the bootloader is relocked, so in theory the oem unlock option shouldn't have an effect in this scenario?
Click to expand...
Click to collapse
You really should boot into Android before re-locking. This is where people have run into trouble. Following the re-lock guide is recommended.
Thanks for your reply, much appreciated, but my question wasn't about the need to unlock the bootloader ot flash, my question was, do i still need to enable "allow oem unlock" in developer options if i use the commands listed above when flashing the latest factory image on a Nexus 6 when 100% stock a locked bootloader, this in theory should work as you are not booting into android until the bootloader is relocked?
The main thing to remember, is to remove all security locks and your Google account beforehand. With this device, when fastboot oem lock is issued, the device is wiped again. This is why it is important to be sure you have a working OS before locking. :good:
Evolution_Freak said:
You really should boot into Android before re-locking. This is where people have run into trouble. Following the re-lock guide is recommended.
Click to expand...
Click to collapse
Thanks for that, i will follow the guide, so this option would effect things regardless?
d.chatten said:
Thanks for your reply, much appreciated, but my question wasn't about the need to unlock the bootloader ot flash, my question was, do i still need to enable "allow oem unlock" in developer options if i use the commands listed above when flashing the latest factory image on a Nexus 6 when 100% stock a locked bootloader, this in theory should work as you are not booting into android until the bootloader is relocked?
Click to expand...
Click to collapse
I understand completely. In a sense, you have outlined the process that is shown on the factory image page, by Google. This information needs to be updated as it does not reflect the security changes made in 5.1. I wouldn't risk your device for a few extra minutes needed to verify the OS boots.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
d.chatten said:
Thanks for that, i will follow the guide, so this option would effect things regardless?
Click to expand...
Click to collapse
I can confirm that several people have bricked by trying to do it the way you were thinking of trying. If for any reason, during the flashing process something didn't flash just right, and a bootloop occurred, you wouldn't be able to fix it with a locked bootloader. That's why it's best to ensure your OS boots before locking.
Evolution_Freak said:
I understand completely. In a sense, you have outlined the process that is shown on the factory image page, by Google. This information needs to be updated as it does not reflect the security changes made in 5.1. I wouldn't risk your device for a few extra minutes needed to verify the OS boots.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
I can confirm that several people have bricked by trying to do it the way you were thinking of trying. If for any reason, during the flashing process something didn't flash just right, and a bootloop occurred, you wouldn't be able to fix it with a locked bootloader. That's why it's best to ensure your OS boots before locking.
Click to expand...
Click to collapse
Thank you for clarification, much appreciated, the process is still easy enough even with these extra steps.
Hey guys
I have a Moto X XT1052- The Indian Version.
I rooted my phone a few weeks back and I've decided that I don't want root access anymore.
I have unrooted my phone from the SuperSU app by clicking the clean up button.
Now I can't find anything as to how to relock the bootloader. I don't really need the warranty to be active again but if there is a way to do that it would be appreciated.
Also I need help to remove the bootloader unlocked warning message to be removed as well.
Please be clear in your explanations as I'm new to all this.
I have attached details about my phone to this post.
Thanks in advance
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
bronko15344 said:
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
Click to expand...
Click to collapse
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as you are re-flashing the EXACT same rom that is on your phone, and your battery is 100% charged before starting. In other words,as always, if the battery goes dead during the process, there is a potential to brick, and DOWNGRADING your ROM is not good.
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
KidJoe said:
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as your battery is 100% charged before starting. (in other words,as always, if the battery goes dead during the process, there is a potential to brick)
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
Click to expand...
Click to collapse
Thank you so much
RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
If you used the "Full Unroot" option in the app it should revert all changes which are made during the root process. To be sure that your system partition is completely stock you can flash it with fast boot (this won't delete your installed apps and data)
To do this look into this guide
guide-moto-x-return-to-100-stock
Short version:
1.
Download and extract the sbf flies matching your phone and carrier from here:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
To decide which file you need to download:
info-tip-web-sites-official-leaked-roms
2. (this step is necessary to remove your warning message)
ghost-original-bootanimations-unlocked
download the standard boot animation and extract the logo.bin and overwrite the logo.bin from the sfb files.
3.
now flash the system partition, kernel, recovery and the new logo (without the warning) with the following commands: (Note: For flashing system.img you MUST use mfastboot instead of fastboot. It's to big for the normal fast boot. So no typo here)
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
Don't execute the following command as this will delete all your data/installed apps etc.
Code:
fastboot erase userdata
That should be sufficient to revert everything what was changed during the root process. Check if everything looks like it was was on stock rom (including the recovery and the bootlogo)
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
But actually I would not relock your boot loader since you gain nothing and if you want to unlock it again all your data will be erased during the unlock process. and since you are not rooted you can't backup everything before...
Edit: Like @KidJoe said. If you accepting an OTA than the warning comes back. so if you relock your bootloader you can't hide that message without unlocking (and loosing all your data) again. Just stay on the unlocked bootloader
bronko15344 said:
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
.
Click to expand...
Click to collapse
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
KidJoe said:
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
Click to expand...
Click to collapse
Oh wasn't aware that you directly have to flash a firmware to relock the bootloader. Thank you
hey how u do u unlock ur moto x t1052 .
Hi,
How do i lock the bootloader with a custom rom, is it possible without flashing stock firmware?
also, does locking the bootloader erase data?
Thanks
If you lock your bootloader, the bootloader dont erase data, its very simple to lock, you must have adb&fastboot installed on your pc, you put you phone in fastboot mode and you put: fastboot oem lock
I used this two command to unlock
fastboot flashing unlock
fastboot flashing unlocl_critical
So when i want to return to stock
flash stock rom via miflash flsh_all
Then type this
fastboot flashing lock_critical
fastboot flashing lock
fastboot oem lock
Is this the correct one?
amnher said:
I used this two command to unlock
fastboot flashing unlock
fastboot flashing unlocl_critical
So when i want to return to stock
flash stock rom via miflash flsh_all
Then type this
fastboot flashing lock_critical
fastboot flashing lock
fastboot oem lock
Is this the correct one?
Click to expand...
Click to collapse
Download stock fastboot rom, flash with flash_all_lock option
q0kHaN said:
Download stock fastboot rom, flash with flash_all_lock option
Click to expand...
Click to collapse
But does it lock critical to? Cause I used the following commands:
fastboot flashing unlock
fastboot flashing unlock_critical
So do i need to revert also those two?
amnher said:
But does it lock critical to? Cause I used the following commands:
fastboot flashing unlock
fastboot flashing unlock_critical
So do i need to revert also those two?
Click to expand...
Click to collapse
if you do fastboot oem lock, it locks both (flash_all_lock does that)