Database Users

[ROOT] CWM Test 8/Flashable SuperSU

As discovered in the Q&A post found here: http://forum.xda-developers.com/moto-x-2014/help/root-t2886674/page2
Just like the first Moto X, users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.
Bootloader Unlock Guide: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
CWM Test 8: http://d-h.st/XJr
SuperSU flashable ZIP: http://forum.xda-developers.com/showthread.php?t=1538053
I can report that this did work for me and I have achieved root.
Steps I took:
1. Unlock bootloader using Motorola's website
2. boot to bootloader, flash or boot to recovery with fastboot command (fastboot flash recovery cwm.img/fastboot boot cwm.img) *There really isn't a reason to flash this. It is very broken. Consider keeping your original recovery!*
3. boot to cwm and flash superSU zip
4. CWM will prompt to fix root, choose YES
5. Rooted!
Almost everything besides flashing a zip is broken in this CWM release, don't expect to be able to backup with it.

Vultorus said:
This hasn't been posted yet, so I'm just sharing what was found in the Q&A post found here: http://forum.xda-developers.com/moto-x-2014/help/root-t2886674/page2
Users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.
Bootloader Unlock Guide: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
CWM Test 8: http://d-h.st/XJr
I can report that this did work for me and I have achieved root.
Click to expand...
Click to collapse
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?

km8j said:
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?
Click to expand...
Click to collapse
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.

Vultorus said:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Click to expand...
Click to collapse
What are the gaps in security? When you say secure, do you mean safe as in not bricking the phone or security as in data is at risk, etc.?

Vultorus said:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Click to expand...
Click to collapse
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.
edit: also, fix permissions shouldn't be required...

mrvirginia said:
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.
edit: also, fix permissions shouldn't be required...
Click to expand...
Click to collapse
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.

Vultorus said:
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.
Click to expand...
Click to collapse
yeah i'm still awaiting a device so i'm not 100% sure on the persmissions. the zip should do all the work for the user, though, via the update-binary.
btw thanks for posting.

Thanks for posting this, I suggested the guys in Q&A to do that. If anybody needs help, I made the process successfully back on Q&A (when they were testing the recovery)

If anyone notices the permissions making a difference let me know, I'm curious as to why everyone was saying it had to be done..

"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------
rogeriorc said:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
Click to expand...
Click to collapse
ops, forget about it.
the command is "fastboot boot cmw.img"
And I am rooted! :laugh:

Worked for me. I'm now rooted

2/10 needs more Verizon

rogeriorc said:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------
ops, forget about it.
the command is "fastboot boot cmw.img"
And I am rooted! :laugh:
Click to expand...
Click to collapse
I apologize, I did not realize if you are just booting, you don't need the "recovery" part of that command. Glad it worked for you!

You mention that this version of CWM is limited to basically sideband loading and won't do backup. Do you happen to know where I can find a copy of CWM for the X 2014 that gives me shell access? I've already unlocked and rooted my phone, but busted my screen and want to back things up. I went to their rom manager page and can't find either version of the X. Would either a 6.0.5.1 or one of the Nexus ones work?

Locked bootloader & No OS | What could be done?

Hi all,
I'd been using my rooted Nexus 6P on stock ROM+kernel. Unfortunately, I locked the bootloader after installing TWRP and installing SuperSU. I know, it was a huge mistake but it happened.
Yesterday I wanted to unroot and factory reset the phone. I forgot that my bootloader was locked so I didn't flick that "enable oem unlocking" button. I tried "flash-all" directly on bootloader. Obviously it didn't work and after reboot it got stuck on Google screen. I waited for a while but nothing happened. I wiped system, vendor, cache... etc on TWRP upon a tutorial in this forum with the intention to flash stock ROM but again : my bootloader was locked.
Now, I can still use TWRP and push files through adb but cannot use any fastboot commands. I get this error:
Code:
FAILED (remote: device is locked. Cannot flash images)
I tried installing the whole "image-angler-mdb08l" on TWRP but I get this error:
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/image-angler-mdb08l.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error flashing zip image-angler-mdb08l.zip'
Updating partition details...
...done
Is there any way to flash stock ROM with TWRP or should I try flashing a custom ROM and hoping to boot so I can enable that troublesome OEM unlock switch?
Compared to similar situations in 6P forum, I have the advantage of working adb and TWRP but I don't know if they even make a difference. Thanks for sparing time to read and your help.

You cannot flash factory image with TWRP. Download any custom ROM, flash it with TWRP. Let it boot and enable unlock in Developer Options.

Witek_M said:
You cannot flash factory image with TWRP. Download any custom ROM, flash it with TWRP. Let it boot and enable unlock in Developer Options.
Click to expand...
Click to collapse
You restored my faith in saving this phone. Is there any custom ROM in particular that won't mess with the recovery partition? It seems that if I loose TWRP, I have nothing to hold on to.

afaruky said:
You restored my faith in saving this phone. Is there any custom ROM in particular that won't mess with the recovery partition? It seems that if I loose TWRP, I have nothing to hold on to.
Click to expand...
Click to collapse
I believe that CyanogenMod wouldn't corrupt TWRP recovery. I've flashed official CM on my Galaxy S4 so many times, and CM never replace TWRP with something else. ????

LeoYL said:
I believe that CyanogenMod wouldn't corrupt TWRP recovery. I've flashed official CM on my Galaxy S4 so many times, and CM never replace TWRP with something else. ????
Click to expand...
Click to collapse
:victory: It worked like a charm. Thanks a lot. :victory:

afaruky said:
:victory: It worked like a charm. Thanks a lot. :victory:
Click to expand...
Click to collapse
Now unlock the bootloader, and leave it unlocked.

afaruky said:
:victory: It worked like a charm. Thanks a lot. :victory:
Click to expand...
Click to collapse
metaphz said:
Now unlock the bootloader, and leave it unlocked.
Click to expand...
Click to collapse
And maybe bookmark my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
A bit of research and knowledge would have avoided this issue in the first place.

Heisenberg said:
And maybe bookmark my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
A bit of research and knowledge would have avoided this issue in the first place.
Click to expand...
Click to collapse
Your guide is amazing and helped a lot.
I had been using N5 with locked bootloader and never encountered any problem but when I switched to 6P I read some articles explaining how dangerous leaving the bootloader unlocked is, so I locked it. Obviously, it was a mistake. I'm glad I didn't have to RMA.

afaruky said:
Your guide is amazing and helped a lot.
I had been using N5 with locked bootloader and never encountered any problem but when I switched to 6P I read some articles explaining how dangerous leaving the bootloader unlocked is, so I locked it. Obviously, it was a mistake. I'm glad I didn't have to RMA.
Click to expand...
Click to collapse
There is risk in involved in having an unlocked bootloader, but as long as you take care of your phone and don't let it fall into the wrong hands you'll be perfectly fine. To say it's dangerous would be a pretty big overstatement.

I'm in the same situation, need some help
Sent from my GT-I9500 using Tapatalk
---------- Post added at 02:30 PM ---------- Previous post was at 02:29 PM ----------
I have twrp working fine with no os
Sent from my GT-I9500 using Tapatalk

So why not do exactly what the OP did? Download a custom ROM, flash it with TWRP then unlock your bootloader?

Pain-N-Panic said:
So why not do exactly what the OP did? Download a custom ROM, flash it with TWRP then unlock your bootloader?
Click to expand...
Click to collapse
Its not connecting to bootloader to transfer custom rom.
Sent from my GT-I9500 using Tapatalk

Updates through custom recovery with a locked bootloader possible?

If I locked my bootloader, can I update SuperSU (zip) or TWRP (img) using TWRP --> Install?
I'm already aware that it won't allow me to flash custom ROMs, custom recoveries or use fastboot commands.
What does having a locked bootloader prevent me from doing?
Thank you

AndrewDam said:
If I locked my bootloader, can I update SuperSU (zip) or TWRP (img) using TWRP --> Install?
I'm already aware that it won't allow me to flash custom ROMs, custom recoveries or use fastboot commands.
What does having a locked bootloader prevent me from doing?
Thank you
Click to expand...
Click to collapse
The better question is why would you have a locked bootloader? If you have any kind of boot loop or error you will end up with a paper weight that will have to be sent off for repairs when its easily fixed with an unlocked bootloader.

murphyjasonc said:
The better question is why would you have a locked bootloader? If you have any kind of boot loop or error you will end up with a paper weight that will have to be sent off for repairs when its easily fixed with an unlocked bootloader.
Click to expand...
Click to collapse
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).

AndrewDam said:
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
Click to expand...
Click to collapse
I would say it's much more likely you brick your phone due to having a locked bootloader than someone else getting their hands on your phone and actually having the knowledge to cause trouble for you.

to relock your bootloader you must have FULLY STOCK firmware back on your device, relocking with anything in the phone being custom can result in a paperweight

Having a rooted phone is more vulnerable than a unlocked bl phone. Dont lock bl back unless you are full stock (I would still say dont though)

AndrewDam said:
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
Click to expand...
Click to collapse
It's more secure, sure. But if you take care of your phone it doesn't fall into the wrong hands. Plus, if you have TWRP installed still a tech savvy thief (one who understands what a locked bootloader means) can easily flash a ROM and boot into the phone. As sometime else pointed out, the chances of you ending up with a brick are higher than the chances of someone getting your phone.
Sent from my Nexus 6P

Ok that makes sense to not lock the bootloader. Thanks for the information everyone!

[V29a only] I managed to relock the bootloader without any backups.

While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs Before doing this make sure EVERYTHING is stock! This includes custom recoveries. I do not claim any responsibility if anything goes wrong!
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.

Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)

Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs

OsiBasi said:
Interesting to say the least, is there any drm locked content that you now can use? (not sure if g4 has any)
Click to expand...
Click to collapse
I didn't use any drm content while it was unlocked, so I can't tell. Sorry

steadfasterX said:
Tbh you can relock even without loosing data (at least on LL and MM).
Just reflash the misc partition from either a previous backup (recommended) or from a extracted stock kdz partition will do so.
You should backup misc and the persistent partition before doing so just for the case.
Never written it down because I thought its something no one would like to do but that's verified to work...
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail

alex2000robert said:
Yes, it's totally possible but this method doesn't need any backups. I understand it might be hard to believe it worked, even for me it was hard to believe having tried this method on previous ROMs to no avail
Click to expand...
Click to collapse
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.

steadfasterX said:
yes using fastboot command is new (for OUR device) coming with that modified N release.
btw my described method does not necessarily need a backup. you can do even without..
.
Click to expand...
Click to collapse
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.

alex2000robert said:
Didn't see you mention flashing misc partition. But if I don't remember wrong it gets flashed everytime we install a KDZ with LGUP anyways this method should be somewhat safer as it doesn't involve flashing anything.
Click to expand...
Click to collapse
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
btw you should consider to add a [N only] or similar in the thread title
.

steadfasterX said:
no - not every partition u see in a KDZ will be flashed.
Especially when you have an unlocked bootloader.
well the fastboot command will erase all data. flashing misc not nvm i don't care about which is better just wanted to add that there is a method which works on LL and MM (fastboot command will not work there).
.
Click to expand...
Click to collapse
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.

alex2000robert said:
I don't care either, now the good thing is that we suddenly got from 1 method involving backups to 3 methods of which 2 don't involve backups. Hurray :highfive:
I just included [V29a only], just in case. Maybe on V30a/b/c from Korea this won't work.
Click to expand...
Click to collapse
lol yes true so true :highfive: :victory:
title is perfect now

"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol

pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
Click to expand...
Click to collapse
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Edit: Oh I just saw your added post about not being able to boot into the Download mode, I can't help you at the moment. Haven't figured out why some devices refuse to boot into the Download mode...

Mr.FREE_Bird said:
Go to my Q&A, Help & Troubleshooting thread ---> https://forum.xda-developers.com/g4/help/help-imei-0-t3660318/page2
All the info you need is there. Your IMEI probably got corrupted.
Click to expand...
Click to collapse
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working

alex2000robert said:
While using the v29a ROM, @kessaras said it should be possible to lock the bootloader using "fastboot oem lock", which didn't work for me on any ROM. I decided to give it a try anyways and it actually worked! It wiped my data, and after restoring and all that I rebooted the phone to see if it was actually locked. "fastboot getvar unlocked" gave me a result of "no". Try it out, but beware, your data will be lost. Proof video: https://youtu.be/Tr6E9LaGWRs
Steps (assuming you already have v29 rom installed):
1. Download ADB and fastboot, along with LG drivers (if you don't have them). Connect your phone and start CMD. CD to the folder where your adb and fastboot files are. (pretty obvious isn't it? )
2. Type "adb reboot bootloader".
3. Type "fastboot oem lock". This WILL wipe your data, and I'm NOT responsible for it!
4. Enjoy your locked phone.
Click to expand...
Click to collapse
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.

steadfasterX said:
you should add a big warning that re-locking the bootloader will lock the bootloader
yea I know.. just make it clear that this means:
BEFORE you do so you have to ensure that everything is completely STOCK! Even no TWRP flashed etc.
.
Click to expand...
Click to collapse
Thanks, just added that.

pedrogcsb said:
"Your device is corrupt. It cannot be trusted and may not work properly". Using that resulted on this.. Can't even access recovery
---------- Post added at 02:05 PM ---------- Previous post was at 01:54 PM ----------
Also cant access download mode. So i think this **** ruined my phone lol
Click to expand...
Click to collapse
Sorry, don't know how to help you here. I read about this error snd supposedly after 10 seconds this message should go away by its own... Try to boot it and wait a little. Then unlock back the bootloader with the unlock.bin and flash the stock recovery from the ZIP file of V29a (which should've flashed by itself, did you remove it?) and only then lock the bootloader. Make sure everything is stock.

pedrogcsb said:
What do you mean? I can't even turn on my phone, or acces TWRP or Download mode. Nothing is working
Click to expand...
Click to collapse
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka

Hello,
Is it still possible to unlock the boot loader of an LG G4? Their site is not working.

Minto107 said:
Well, I guess you hard bricked your phone. You had modified firmware(TWRP, kernel) and relocked. Not even surprised you're phone is bricked. Only shot would be send it to LG but they will 99% know you messed with firmware
Wysłane z mojego LG-H815 przy użyciu Tapatalka
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/development/unbrick-lg-g4-h815-9008-qualcomm-t3452853 I think I will try this next in the morning

Did anyone try unlocking the bootloader as well?
Sent from my iPhone using Tapatalk

Freshly bought Mi A1 - to OTA or not to OTA?

Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?

zroice said:
Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
Click to expand...
Click to collapse
If security matters for you yes
The only thing you'll share with a custom ROM is the bootloader
Since may update locking or relocking the bootloader will wipe your data
It's your choice

but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?

zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
You have to enable it in Developer settings.

zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader

Dead-neM said:
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Click to expand...
Click to collapse
alright. thanks very much for explaining in details - exactly what i was looking for.

What's the use of your android one device if you will not update it, that's what you pay for.

HidekiRyuga said:
What's the use of your android one device if you will not update it, that's what you pay for.
Click to expand...
Click to collapse
hahahaaa exactly the point :laugh:

well once you have everything "perfectly set up" updates can ruin it. but yea relocking the bootloader really was a stupid idea - it was the idea to make it tamper proof but since custom kernels wont boot with locked bootloader that wouldnt work.