Is there a way to enable the camera2 API on the moto g5s plus xt1805 version? The methods I've found that edit the build.prop file require root. I've tried one-click root methods but all have failed. I want to avoid a custom recovery or a custom rom.
Any replies appreciated
You cannot avoid rooting your phone if you want to enable cam2api, therefore you must unlock your bootloader and get a custom recovery in case you want this. DO NOT TRY ONE CLICK METHODS, these don't work for this phone, not a single one of them. Also don't be afraid of rooting your phone, if you follow every step correctly you won't have any trouble. You also don't need to use a custom rom, you can root stock and keep it unmodified if you wish, but you will still lose warranty and OTA updates with a custom recovery.
Related
I've been doing a lot of reading and searching but still can't find a definite answer...
My understanding is that I need to root the device to flash a custom rom
But from the instructions for noobs, they don't usually specify that I have to root
I assume that rooting is a pre-requisite for everything...but then some roms advertise that they are rooted (for example, LeoFroYo)
So it the rooting process tied to the rom itself and I have to root everytime I flash a new rom (if the rom is not rooted)? Or is it universal like HSPL on WinMo?
Rooting is per rom. What is required to flash a custom rom is having an unlocked bootloader and a custom recovery image. From there you can flash a pre-rooted rom.
The root instructions assume that you're gonna keep using the stock version with root abilities added on top. Whereas if you're using flashing something like CM, that already has root and OS tweaks.
FaJu said:
Rooting is per rom. What is required to flash a custom rom is having an unlocked bootloader and a custom recovery image. From there you can flash a pre-rooted rom.
The root instructions assume that you're gonna keep using the stock version with root abilities added on top. Whereas if you're using flashing something like CM, that already has root and OS tweaks.
Click to expand...
Click to collapse
Thanks! So does that mean when I get my phone out of the box, I have to root it once over the stock rom before I can flash any custom rom?
You need to root the phone originally and flash a custom rom. The "pre-rooted" means the rom is rooted. So if you flash that rom then you wont lose root. If you flash an un-rooted rom then you will lose it. So go through the steps and unlock your bootloader then flash a custom recovery image. Then decide which rom you wanted and flash it. All the custom roms are rooted.
futango said:
You need to root the phone originally and flash a custom rom. The "pre-rooted" means the rom is rooted. So if you flash that rom then you wont lose root. If you flash an un-rooted rom then you will lose it. So go through the steps and unlock your bootloader then flash a custom recovery image. Then decide which rom you wanted and flash it. All the custom roms are rooted.
Click to expand...
Click to collapse
That explains it. Thanks for your answer
one more question:
I take it as when bootloader is unlocked, there's no way to lock it again? Not even flashing the stock boot image?
No, once you unlock the bootloader, it stays unlocked.
Just to be clear here you don't _have_ to "root your phone once"
On _most_ phones you need an exploit to be able to get to the bootloader, this exploit is often referred to as rooting. After the exploit you generally have superuser access until you reboot, on some phone this may allow you to get at the bootloader and write anything you want there (E.G. an OS that give you superuser access at boot time)
However the N1 lets you issue the command "fastboot oem unlock" that unlocks the bootloader, from there you can flash a recovery image that will allow you to flash the main OS without having access to Google's release signing keys. Hence you _could_:
1. Bootloader unlock
2. Flash Custom recovery
3. Flash Custom OS
Without ever actually having "root" access, it just happens that most Devs prefer having root access available in both recovery and any custom rom they cook up.
I have an N1 that I unlocked and rooted and was running CM7 RC1 when I decided to try the stock Gingerbread. This switch went perfectly, but now I don't think I want to stay on the stock GB but I can't seem to get ROM Manager to boot into recovery to allow me to flash another ROM. Do I have to do something differently now? BTW, I do not have root on the 'new' GB.
Thanks.
Unless you flashed a pre-rooted version of Gingerbread, you will have lost root and your custom recovery...
If this is the case, you have two options:
1 - Flash a custom recovery through an unlocked bootloader.
2 - passimg back to an older version of Android and root again...
Sent from my Nexus One using XDA App
tsprks said:
BTW, I do not have root on the 'new' GB.
Click to expand...
Click to collapse
This is your problem. ROM Manager installs a custom recovery, but only when your phone is rooted. You need to re-root GB.
Can I ask them how people flash custom recoveries without having root? I see threads all over the place that say that you don't have to root your phone to run these custom ROM's.
tsprks said:
Can I ask them how people flash custom recoveries without having root? I see threads all over the place that say that you don't have to root your phone to run these custom ROM's.
Click to expand...
Click to collapse
You have to root, but you don't have to unlock your bootloader.
You have to do one of the things:
1) Root.
2) Unlock the bootloader.
Rooting allows you to bypass security mechanisms from within the OS, and flash the custom recovery from there.
Unlocking the bootloader turns off the security mechanisms, and you can flash whatever you want directly from bootloader.
Both achieve the same thing, but in different ways.
Root privileges in OS are lost upon official upgrades.
Unlocked bootloader is never lost.
Unlocked bootloader allows for an easy way to gain root in the first place, regardless of the ROM.
How does an unlocked bootloader allow me to flash whatever ROM I want? ROM Manager won't run without root? Am I missing something? I've read the wiki's and threads about rooting an N1 and they all just seem to stop at unlocking the bootloader, well, my bootloader is unlocked but I can't get it to boot into CWM so that I can select another ROM. Is there another way to do this?
ROM Manager is only one, and not the most successful nor most powerful, way to flash ROMs or recovery. ROM Manager was made for non-understanding people to make the process look and feel easier. The most powerful way is directly from bootloader - which needs to be unlocked to allow it.
If you read all the threads, you'll see that unlocking the bootloader is just a first step - you can look carefully at "installing custom ROM" guide in Wiki. Or, for example, here:
http://forum.xda-developers.com/showthread.php?t=636795
Read the Wiki, look for recovery installation instructions using unlocked bootloader, execute. I suggest Amon_Ra's.
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Any help will be appreciated.
Timsteels
Figure out if you can, and want to unlock your bootloader.... Then go to the One Stop Shop root thread sticky at the top of the general section. It has all your options.
---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------
And root methods have nothing to do with your model. It mostly has to do with locked or unlocked bootloader state.
timsteels said:
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
Click to expand...
Click to collapse
Process to root the X is the same whether you have an XT1052, XT1053, XT1056, XT1060, etc. As KJ said, with 4.4.4 its all about can you unlock your bootloader or not. (and do you mind voiding your warranty doing so since you don't have a Developer Edition X).
See the One Stop Shop thread, in particular this post -> http://forum.xda-developers.com/mot...-confusion-t2826159/post54671918#post54671918
timsteels said:
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Click to expand...
Click to collapse
And you do NOT WANT TO DOWNGRADE!!!!! Doing so you will risk bricking your phone now, or when you later take an OTA. There are many warnings posted in the forums to not downgrade, and many threads started by those who have ignored the warnings and tried to downgrade and have bricked their phones!!!
Besides that, two key parts, GPT.Bin (partition table), and Motoboot.img (contains bootloader, TZ and a few other parts) will NOT downgrade successfully once on 4.4.2, 4.4.3 or 4.4.4. so any past exploits requiring the older roms wont work anyway.
So unlocking the boot loader is the same process as the us variants of the moto x? I just don't want to turn my phone into a paperweight! I'm not too worried about the warranty, as I am usually careful with my phones.
Unlocking and recovery and ROOT is all the same on any X. What matters is Android version (cause locked 4.4.4 guys can't root in any way), locked or unlocked bootloader and that's about it.
An unlocked X is the same no matter a Dev Edition or any other. All the same.
As far as bricking... The only time that's a giant threat is trying to downgrade. Not saying an X has never been bricked another way, cause everything we do has some risk to it. But most issues are curable.
Ok thanks for the info! And in terms of custom roms, do I need to install one built for the xt1052, or will other ones also work?
That is not something I know about. Never flashed one. Just stock and gravity box.
Read the opening post of rom threads, should have what devices it's for. ?
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
I think many rooted X members here use Gravity Box while on stock rom... So they can customize some things. ?
Ok cool. I will have a look and decide if I want to go ahead. Thanks for all the assistance
timsteels said:
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
Click to expand...
Click to collapse
Many root, install Xposed and some modules to customize their phone rather than running any Custom Roms because the custom roms often lose the Moto features like the notifications and such.
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
timsteels said:
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
Click to expand...
Click to collapse
First you can't install an OTA with a custom recovery (like TWRP, CWM, Philz) on the phone. You'll get stuck in a boot loop.
Next, in every OTA there is a "pre-validation check" (a manifest file which contains a list of items to be checked and a SHA type hash code for a type of check sum verification of each part/file its looking at.)
Anything that alters your phone from what the Pre-Validation check is looking for will cause the OTA to fail. So if you modify or remove and system files, have the wrong recovery, etc., those parts would not pass the pre-validation check so the OTA would fail.
Xposed also needs to be disabled, or it will cause the OTA's pre-validation checks to fail.
So it really comes down to what you do after you root.
If you flash TWRP, Root, install Xposed and a few modules, and nothing else, then to take an OTA, you'll need to disable Xposed (there is a flashable zip on your /SDcard to do this), then flash stock recovery.img back on your phone, then you can take the OTA. Once the OTA is successfully installed, you can re-flash custom recovery, re-root if necessary, and re-enable Xposed.
If you rename/delete/modify files from /system (like some do to get rid of bloat), you'll need to un-do that.
If you're like me, I just unlocked, rooted, and installed apps that use root (like Root Explorer, Greenify, Wifi Tether for root), so all I do is flash stock recovery on, take the OTA, and if I lost root, flash TWRP and re-root.
For more see -> http://mark.cdmaforums.com/MotoX-OTA.html
Ok that's good to know. I'll have a think about it. I may wait until lollipop comes out for the moto x.
I've searched and found variations on these questions in other posts, but I didn't come across any pertaining quite to my situation, so I wanted advice before I do something wrong and brick my phone.
I have a Sprint Moto X, unlocked & rooted, running 4.2.2 (I think pre-camera update). I'd like to upgrade to stock Sprint Lollipop (when it comes out) & stay unlocked & rooted.
My understanding of the steps that need to be taken:
1. Unroot my device
2. Re-lock my device
3. Flash TWRP and boot to recovery
4. Flash stock Sprint Lollipop
5. Unlock, then re-root device
Is any of this extraneous, or am I leaving anything out? Do I need to upgrade to KitKat before going to Lollipop?
I also have Xposed installed and I have tweaked the PRL on my device ... this shouldn't complicate the upgrade, right?
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
imnuts said:
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
Click to expand...
Click to collapse
i have a sprint X and if i am going to update this is how i have allways done it with no issues at all.
you can leave your bootloader unlocked that is no a issue. but i always take OTA's and you cant take a OTA with a modded system. so i allways just flash my stock firmware package. that way it removes my custom recovery. Root, and all Xposed changes. Then i take the OTA and just reinstall TWRP, then SuperSU then what ever else you want.
this is the safest way i have found to update, the nice thing about Unlocked Sprint phones is we can easily Root are phones via TWRP and SuperSu.
just my .02 you can do it how ever you like but this is how i am going to do it when the OTA finally comes out if it ever does.
Hello,
I would like to root my phone, but do I also have to unlock the bootloader and install a custom recovery? I don't want to install custom roms, and I want to be able to install updates from Google. The phone is also unlocked, but I'm not sure if unlocking the bootloader is a totally different thing. Basically I just want to root to get features such as the notification light and install exposed.
NOTE: This will only work on lollipop, for M preview you need a modified kernel, otherwise it won't boot!
If you only need root then use Chainfire's CF-Auto-Root (https://download.chainfire.eu/628/CF-Root/CF-Auto-Root/CF-Auto-Root-shamu-shamu-nexus6.zip).
To install root, you need to unlock the bootloader (CF-Auto-Root will do it for you if it's locked), but it will wipe you entire phone, and do a factory reset. So backup everything before you root it.
This will leave your stock recovery unchanged.
Thank you. This is exactly what I wanted.
You might want to consider installing twrp also, at least you can do a backup before you start messing around with stuff. Just rooting the phone will allow you to do everything you need /want but if you change something that makes things go south you have no reference point to return to.
Also, just to clarify: You will NOT be able to recieve OTA updates after rooting your phone. Rooting, using custom recovery, custom kernel or anything at all that tampers with the system prevents OTA updates from installing.
If any of the above has occured, the only way to be able to start updating through OTA again is to flash a factory image (or at least relevant parts of one).
Unlocking the bootloader will not affect the ability to update through OTA.