Related
I am not allowed to post on MoKee thread so I will post my question here.
http://forum.xda-developers.com/showthread.php?t=2761807
I am not a newbie and have been following XDA for 6 different devices and more than 5 years. But I just didn't post enough.
I am currently on SONY Xperia ZR (C5502) 4.4.2 (rooted). I have been trying to flash MoKee 4.4x for the past few weeks but in vain. I bricked my device few time already by trying and have to revital it with all kind of tools (Flashtool, Sony Update Service, fastboot).
I guess now my question is - "Does MoKee ROM requires Unlock Bootloader?" In the last post of that thread, someone said that it MUST be Unlock Bootloader. Is that true? The only reason I care so much about this is because I screwed up my device every time I unlocked it.
I was using the "fastboot.exe -i 0x0fce oem unlock 0xKEY" method.
I am currently using 10.5.A.0.230.
Your answer will be really appreciated.
lcpchang said:
I am not allowed to post on MoKee thread so I will post my question here.
http://forum.xda-developers.com/showthread.php?t=2761807
I am not a newbie and have been following XDA for 6 different devices and more than 5 years. But I just didn't post enough.
I am currently on SONY Xperia ZR (C5502) 4.4.2 (rooted). I have been trying to flash MoKee 4.4x for the past few weeks but in vain. I bricked my device few time already by trying and have to revital it with all kind of tools (Flashtool, Sony Update Service, fastboot).
I guess now my question is - "Does MoKee ROM requires Unlock Bootloader?" In the last post of that thread, someone said that it MUST be Unlock Bootloader. Is that true? The only reason I care so much about this is because I screwed up my device every time I unlocked it.
I was using the "fastboot.exe -i 0x0fce oem unlock 0xKEY" method.
I am currently using 10.5.A.0.230.
Your answer will be really appreciated.
Click to expand...
Click to collapse
Yes just like any other rom out there you will need an unlocked bootloader. The reason is because you have to flash a custom recovery such as CWM and to do that you need to unlock your bootloader. I recommend unlocking you bootloader using flashtool instead of the command. Because it is just easier. When I was trying to unlock my bootloader I experienced problems doing it the way with the cmd. And what problems does it give you after unlocking and how does it screw your device? Thanks!!
PS: Try flashing a custom recovery because maybe your bootloader is already unlocked.:good:
gurinderhans said:
Yes just like any other rom out there you will need an unlocked bootloader. The reason is because you have to flash a custom recovery such as CWM and to do that you need to unlock your bootloader. I recommend unlocking you bootloader using flashtool instead of the command. Because it is just easier. When I was trying to unlock my bootloader I experienced problems doing it the way with the cmd. And what problems does it give you after unlocking and how does it screw your device? Thanks!!
PS: Try flashing a custom recovery because maybe your bootloader is already unlocked.:good:
Click to expand...
Click to collapse
I have installed -=[XZDualRecovery]=- with locked bootloader, so I don't think the reason is about the flashing of the recovery, maybe is something related with kernel flashing. but I'm not sure.
anancr said:
I have installed -=[XZDualRecovery]=- with locked bootloader, so I don't think the reason is about the flashing of the recovery, maybe is something related with kernel flashing. but I'm not sure.
Click to expand...
Click to collapse
maybe but I wasnt able to write the boot.img unless I unlocked my bootloader.
confirmed that it REQUIRES Unlock Bootloader to install MoKee
gurinderhans said:
maybe but I wasnt able to write the boot.img unless I unlocked my bootloader.
Click to expand...
Click to collapse
Thanks for the advise from gurinderhans
Yes, I have confirmed that it REQUIRES Unlock Bootloader to install MoKee.
I unlocked my bootloader with Flashtool this time, instead of commend line this time. That fixed the problem I used to have.
But I used the CWM comes with XZDualRecovery to install MoKee 4.4.4. It works out fine.
lcpchang said:
Thanks for the advise from gurinderhans
Yes, I have confirmed that it REQUIRES Unlock Bootloader to install MoKee.
I unlocked my bootloader with Flashtool this time, instead of commend line this time. That fixed the problem I used to have.
But I used the CWM comes with XZDualRecovery to install MoKee 4.4.4. It works out fine.
Click to expand...
Click to collapse
Good to know everything worked out fine.
Any custom rom requires boot loader unlock.
[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
How about looking around a little bit. Come on man
uncalex said:
[Disclaimer-this is my first android device, thus i will be a total newbie at this stuff, second, this is my second time posting on a forum-type website so excuse me if this has already been asked and answered, plz just link the thread then]
So. Is this possible?
Detailed explanations would be much appreciated.
(I am also using a MAC, so if that affects anything....)
Click to expand...
Click to collapse
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
eksasol said:
For rooting the Moto X it is a bit difficult compared to the Nexus. You need to realize that the Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently (hardware) brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. When I had the Moto X 2013 version, it is possible to brick the phone by downgrading the phone to an older version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update patch for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone image you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory image of the phone.
Click to expand...
Click to collapse
Thank you for being so nice and providing this information
eksasol said:
The Moto X have locked bootloader that prevent you from making changes to the "system" partition. So generally you need to unlock the bootloader first, which is a separate process.
Just a note, that generally when you unlock a phone's bootloader, you void the warranty. Some person here claimed that a Motorola manager confirmed with him that you will not void it with the Moto X Pure edition, however, I do not believe it. The best thing to do is read the fine print and warnings when you goes to unlocked your bootloader from Motorola website.
Another warning, is it easier to permanently brick a Motorola than a some other phones if you flash things incorrectly, such as corrupting the CID partition. With the Moto X 2013 it is possible to brick the phone by downgrading the phone to a too old version. I have never tried this with Moto X, but with Nexus devices, you could softbrick the phone if you root it and then do an over the air update, it generally required to use TWRP recovery to apply the over the air update zip for it to work, or reflash the "system" partition of the phone to stock before doing the update. I don't know if this is the same for the Moto X, but I would take the same precaution.
To unlock the bootloader, you can do it at the website here: https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Read through this guide to help you: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
For step 2 and 3 from that guide, it linked to files required by Windows. Instead, you can get the Moto X driver for Mac here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
You will also need "fastboot" and "mfastboot" for Mac. Fastboot is the program used to lock/unlock bootloader and flash images for (stock based) Android phones. The ADB/Fastboot link in my signature have the mac/linux/windows version included (adb_fastboot.zip file). I think you only need to use the regular fastboot to unlock the phone, but to flash the phone images you will need mfastboot.
To root the phone, check in the Development sections of this device forum: http://forum.xda-developers.com/moto-x-2014
Also, you DO NOT need to unlock the phone bootloader to reflash the factory images.
Click to expand...
Click to collapse
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
uncalex said:
Quick question,
I've seen people use towelroot to root any android device. Will towelroot work with the Moto X? I'm just really hesitant now since you said it was easier to permanently brick and Moto device.
Click to expand...
Click to collapse
I never use that. The safest thing is to do what is tested and available for that device, so use the current available method here:
http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
Generally. I don't do any of these, because I do the default Nexus root method which is:
1. Unlocking bootloader
2. Flash TWRP recovery: fastboot flash recovery twrp.img (not yet available for this phone, but soon will be, check the development sections.)
3. Then copy the Chainfire's SuperSU.zip (link in my signature) into the phone and flash while in TWRP recovery.
You shouldn't worry about bricking the device provided if you don't mess around, just stick with rooting and flashing factory firmware if you are new. As long as you don't flash a rom / firmware made for a different phone, or mess with the CID partition or something like that. Or downgrading the firmware after you've already update, which should be fine with a Nexus, but it did kill some Moto X when they downgraded to a firmware that is too old.
If you ever run into issues, you can flash the factory firmware, which is not available yet, but will eventually show up here: http://sbf.droid-developers.org/phone.php?device=37
You will have to download the correct version since there are different variations, but flashing incorrect ones should not brick your device. You can use these instruction to flash the firmware, this is for the Moto G, but the steps are the same: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657. After you install stock firmware, depend on if you were having issues, you can access the phone's Recovery and do a factory reset, this will wipe all your data, but also clear all the settings which may be required for the phone to boot correctly.
Normally, if your phone is rooted, when you received an over the air update, the first thing I would do before applying that update is to flash the system.img and recovery.img partition of the device back to stock, this will ensure the OTA gets updated successfully, afterward you can re-root the phone. Some people avoid this and flash the OTA's zip file using TWRP recovery, but it is not the official way and not guarantee to work all the time.
I used to own an Xperai Sola. Before unlocking the bootloader I didn't know that I had to backup the DRM keys so that I can get back the "Bravia Engine" and "Download music Info option for Walkman" after the bootloader was unlocked. The information that we can backup our DRM keys came 6 months after I unlocked my bootloader.
These are my questions:
On Moto G 2nd gen do we need to backup something similar like the DRM keys of Xperia Sola?
What function do we lose when we unlock the bootloader other than Warranty? Does OS/Android update still work?
Does re-locking bootloader takes the phone back to its previous unlocked state?
@Falcon G
@vinaybaboo
@bhavin192
2. You can update phone after unlocking bl if you don't make changes to OS i.e. Xposed etc.
If you update even you have made changes to OS your phone will go into Bootloop
3. Yes Re locking and flashing stock firmware takes it to locked state
@NWKENT can answer this Questions more clearly
I´m also with similar doubts. I came from Samsung-way of unlocking bootloader.
Just to ensure if get it right, If I just put root on device, I still be able to update original rom from Motorola ?
It´s a pity we can change anything with xposed (in order to keep upgradable), bcos it´s small things we get used to, and we miss on stock roms...
Thanks,
leandrocn said:
I´m also with similar doubts. I came from Samsung-way of unlocking bootloader.
Just to ensure if get it right, If I just put root on device, I still be able to update original rom from Motorola ?
It´s a pity we can change anything with xposed (in order to keep upgradable), bcos it´s small things we get used to, and we miss on stock roms...
Thanks,
Click to expand...
Click to collapse
Thanks for your input.
Please @NWKENT @Falcon G @vinaybaboo can you kindly answer this question?
I guess if you wipe data and unnistall xposed and then flash stock recovery, you will be able to flash via OTA. No need to unroot
pleomaxell said:
I used to own an Xperai Sola. Before unlocking the bootloader I didn't know that I had to backup the DRM keys so that I can get back the "Bravia Engine" and "Download music Info option for Walkman" after the bootloader was unlocked. The information that we can backup our DRM keys came 6 months after I unlocked my bootloader.
These are my questions:
On Moto G 2nd gen do we need to backup something similar like the DRM keys of Xperia Sola?
What function do we lose when we unlock the bootloader other than Warranty? Does OS/Android update still work?
Does re-locking bootloader takes the phone back to its previous unlocked state?
@Falcon G
@vinaybaboo
@bhavin192
Click to expand...
Click to collapse
pleomaxell said:
Thanks for your input.
Please @NWKENT @Falcon G @vinaybaboo can you kindly answer this question?
Click to expand...
Click to collapse
1. No you don't need any DRM keys
2. U lose nothing rather than your warranty. Ota works if you don't install custom recovery and change the kernel
3. The new locked state is different than the OEM locked one
Falcon G said:
1. No you don't need any DRM keys
2. U lose nothing rather than your warranty. Ota works if you don't install custom recovery and change the kernel
3. The new locked state is different than the OEM locked one
Click to expand...
Click to collapse
Falcon G, thanks a lot for replying.
If the new locked state is different than the OEM locked one, then if a user wants to unlock the phone a second time, does he follow the same method he used to unlock the first time?
So, once the phone has been unlocked it is not possible to lock the phone to back to its OEM locked state?
pleomaxell said:
Falcon G, thanks a lot for replying.
If the new locked state is different than the OEM locked one, then if a user wants to unlock the phone a second time, does he follow the same method he used to unlock the first time?
So, once the phone has been unlocked it is not possible to lock the phone to back to its OEM locked state?
Click to expand...
Click to collapse
Yes you will be able to unlock the device.
And no you cannot get back to the original oem locked state
I have a moto xt1064 and took some pictures yesterday morning. There were a few I didn't want and when I selected a few to delete ALL of them were deleted. The pictures were on internal memory and I've read the only way to access mass storage to undelete and recover the photos is to root the phone. So i want to root the phone but also want to make sure I am able to unroot afterward to receive updates etc. I have not used the phone since the photos were deleted.
I did search before posting and didn't find anything on this particular phone.
Any help would be appreciated! thank you in advance.
This is the forum for the 1st gen Moto G. The sub forum you're looking for is called Moto G (2014).
MODERATOR EDIT: Thread moved to Moto G 2014.
Root and unroot moto g 2014
linuxgator said:
This is the forum for the 1st gen Moto G. The sub forum you're looking for is called Moto G (2014).
MODERATOR EDIT: Thread moved to Moto G 2014.
Click to expand...
Click to collapse
thank you...was in the assist forum and moderator directed me here. will go to Moto G (2014)
pccoach said:
I have a moto xt1064 and took some pictures yesterday morning. There were a few I didn't want and when I selected a few to delete ALL of them were deleted. The pictures were on internal memory and I've read the only way to access mass storage to undelete and recover the photos is to root the phone. So i want to root the phone but also want to make sure I am able to unroot afterward to receive updates etc. I have not used the phone since the photos were deleted.
I did search before posting and didn't find anything on this particular phone.
Any help would be appreciated! thank you in advance.
Click to expand...
Click to collapse
The usual way would be unlock Bootloader (on motorola page: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728 ), flash custom recovery (TWRP) then flash superSU 2.4.6 through TWRP.
In your case I would recommend (after unlocking bl) to use TWRP 2.8.5.0 (only this version: https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img.html ) and just boot into this recovery ( http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243 ) and flash latest superSU: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip .
So your stock recovery stays untouched and you have one thing less to change afterwards.
Now look for your pics, make no other changes, then use the full unroot function of superSU.
Your bootloader is still unlocked,even if you lock it you´ll never get the unlock state as before again. You can do (look for lock lollipop bootloader) but it doesn´t matter, you will get OTA and will be able to install them with a unlocked bl. If the "Bootloader unlocked warning" annoys you use this: http://forum.xda-developers.com/moto-g-2014/general/fix-remove-unlocked-bootloader-warning-t2875385
Wolfcity said:
The usual way would be unlock Bootloader (on motorola page: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728 ), flash custom recovery (TWRP) then flash superSU 2.4.6 through TWRP.
In your case I would recommend (after unlocking bl) to use TWRP 2.8.5.0 (only this version: https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img.html ) and just boot into this recovery ( http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243 ) and flash latest superSU: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip .
So your stock recovery stays untouched and you have one thing less to change afterwards.
Now look for your pics, make no other changes, then use the full unroot function of superSU.
Your bootloader is still unlocked,even if you lock it you´ll never get the unlock state as before again. You can do (look for lock lollipop bootloader) but it doesn´t matter, you will get OTA and will be able to install them with a unlocked bl. If the "Bootloader unlocked warning" annoys you use this: http://forum.xda-developers.com/moto-g-2014/general/fix-remove-unlocked-bootloader-warning-t2875385
Click to expand...
Click to collapse
thank you!
Root and unroot moto g 2014
Wolfcity said:
The usual way would be unlock Bootloader (on motorola page: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728 ), flash custom recovery (TWRP) then flash superSU 2.4.6 through TWRP.
In your case I would recommend (after unlocking bl) to use TWRP 2.8.5.0 (only this version: https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img.html ) and just boot into this recovery ( http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243 ) and flash latest superSU: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip .
So your stock recovery stays untouched and you have one thing less to change afterwards.
Now look for your pics, make no other changes, then use the full unroot function of superSU.
Your bootloader is still unlocked,even if you lock it you´ll never get the unlock state as before again. You can do (look for lock lollipop bootloader) but it doesn´t matter, you will get OTA and will be able to install them with a unlocked bl. If the "Bootloader unlocked warning" annoys you use this: http://forum.xda-developers.com/moto-g-2014/general/fix-remove-unlocked-bootloader-warning-t2875385
Click to expand...
Click to collapse
So I'm supposed to unlock using bootloader and then proceed to steps in second paragraph? I thought bootloader erased all personal data?
pccoach said:
So I'm supposed to unlock using bootloader and then proceed to steps in second paragraph? I thought bootloader erased all personal data?
Click to expand...
Click to collapse
Yes,you're absolutely right, unlocking bl will erase all user data.I didn't thought about the fact you want to save data. In this case I see no way to get the pics back when your bootloader is locked, I'm sorry. Every root method needs the bl unlocked.
Hi.
I am gong to sell my Moto X but I want to relock the bootloader first.
How do I do this?
I think you need to follow a guide to return 100% stock, there's a thread on (I think) general section with RDS lite
Hi.
I did that but it is still locked. I'll ask in the thread.
Thanks.