Related
This thread is for the development for a Moto X(2013) port for Android Lollipop.
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
2nd test build in the works
Everyone who wants to test builds needs to add [email protected] to hangouts
WARNING! tests builds,if they work, will be very unstable. Please remember to backup your system before flashing
In order to flash your phone must
-Have an Unlocked bootloader
- TWRP Recovery installed
If you meet those requirements then add him to hangouts and join the development process
Android 5.0 will come to the 2013 Moto X before the end of november , if not early december, so the amount of work that i believe is required, i dont really think its worth it.
^^^^^agreed. This has already been discussed in the GENERAL section. Mods should move this to general. No development here.
---------- Post added at 05:39 AM ---------- Previous post was at 05:37 AM ----------
And after putting android L on my N7 all locked devices will not have root anymore or safestrap. Currently only way to root is with a custom rooted kernel.
Does TWRP still work with 5.0? What about SuperSU?
lowvolt1 said:
Does TWRP still work with 5.0? What about SuperSU?
Click to expand...
Click to collapse
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
lowvolt1 said:
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
Click to expand...
Click to collapse
Correct, now to root you will need to flash a rooted kernel.
Any word on xposed and L?
Xposed use davilk not art. So with Android Like you can't use xposed mod
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Travisdroidx2 said:
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Click to expand...
Click to collapse
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Vekhez said:
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Click to expand...
Click to collapse
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
perfoliate said:
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
Click to expand...
Click to collapse
I hope you are correct. Last night was my first time flashing and rooting L. I hope root is not lost for locked phones. But you still need to be unlocked to have a custom recovery to flash root. So time will tell I guess.
---------- Post added at 05:49 PM ---------- Previous post was at 05:42 PM ----------
Looks like I am still correct: straight from chain fire:
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Posted 1 hour ago. https://plus.google.com/113517319477420052449/posts/EC5MhqFFqMK
Another example of the 14' X just got root and it has to be unlocked boot loader.
http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Seriously!!! I do agree beggars cannot be choosers... But... The attitude of Moto X owners is Why do it when eventually we will get it!! But isn't it the same condition of other phones like Xperia Z, Nexus 4, Nexus 7, One Plus One? They know they will all eventually get it... But still people ported the ROMs without the binaries or the kernel!! I personally feel the whole point of XDA was to be independent! Not depending on an OEM for what u want! But lack of development makes me really sad, cuz the Moto X was Motorola's baby! It almost brought them back from the dead!!! Its got such brilliant hardware, just enough to be awesome n give a smooth experience! Anyways... All wanna enjoy their Motorola Goodies I guess... Let's just see what people think about development for this phone once its no longer supported By Motorola! Anyways at this point according to Motorola's time line its Droid Turbo next n then the Moto X.... Hoping to see lollipop soooon!
I am learning android programming right now... Just started playing around with codes.... I was messing with stock rom with few mods but no luck.... Let's see how it goes with AoSP source code.. ?
Sent from my XT1053 using XDA Premium 4 mobile app
Megatron007 said:
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Click to expand...
Click to collapse
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Travisdroidx2 said:
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
Click to expand...
Click to collapse
Yeah that's the thing you need to have an unlocked bootloader. That's the reason for L being such a pain to get root on. You need to either have an unlocked bootloader so that you can flash a custom recovery and flash the SuperSU Beta.zip, or you need an unlocked bootloader so you can flash an insecure boot.img which allows for root. But with a locked bootloader, I can see that getting root, is going to be somewhat of a difficult task, especially with some parts of Android becoming closed source.
atrix2man said:
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Click to expand...
Click to collapse
I am interested in testing
flipm00de said:
I am interested in testing
Click to expand...
Click to collapse
Ill pm u when its ready. Make sure u have a backup of your rom incase it doesnt boot lol
My phone is on the way. It's perfectly timed with the imminent update to Marshmallow.
My plan is to get the OTA update first, and then root the phone. Can I still rely on the existing guides to root the phone? Or would I have to wait until root becomes discovered/available again on the new OS version?
You should be able to root it but we really won't know until the OTA arrives.
I've had the phone for a few days now, and happily I've received the 6.0 update OTA.
Is there any current info how whether Heisenberg's rooting guide still works? (completely, partially, ???)
nibunnoichi said:
I've had the phone for a few days now, and happily I've received the 6.0 update OTA.
Is there any current info how whether Heisenberg's rooting guide still works? (completely, partially, ???)
Click to expand...
Click to collapse
yea root works if you read some more you have 2 options to root
patt2k said:
yea root works if you read some more you have 2 options to root
Click to expand...
Click to collapse
The only 6.0 root option I've found is the systemless root.
What is the other? Is there regular root for 6.0?
I have not found a thread on that. I have only been reading for a few days, tho.
My MXPE arrives Thursday! I would like to use it some, before having to root, but I am certain the 6.0 OTA update will be soon to show.
Is there a way to stop the OTA, prior to bootoader unock and root?
Do I just need to unlock/root/flash ROM right away?
I have not even picked a ROM yet.
pizza_pablo said:
The only 6.0 root option I've found is the systemless root.
What is the other? Is there regular root for 6.0?
I have not found a thread on that. I have only been reading for a few days, tho.
My MXPE arrives Thursday! I would like to use it some, before having to root, but I am certain the 6.0 OTA update will be soon to show.
Is there a way to stop the OTA, prior to bootoader unock and root?
Do I just need to unlock/root/flash ROM right away?
I have not even picked a ROM yet.
Click to expand...
Click to collapse
You flash SuperSU 2.52 + boot_root img. TruePureX rom has already built in Root,also sabissimos rom as well. Just pick rooted one or TruePure
patt2k said:
You flash SuperSU 2.52 + boot_root img. TruePureX rom has already built in Root,also sabissimos rom as well. Just pick rooted one or TruePure
Click to expand...
Click to collapse
TruePureX is actually one of the ROMs I was thinking of flashing.
So, if I take the 6.0 update, I can still root in a relatively normal way?
systemless root does not sound like a path I wish to take.
How does the OTA come to this device? A Moto app, I presume?
Does Moto ram it down one's throat, like verizon?
I was just reading on the moto forum, about simply unlocking the bootloader will stop the OTA. I haven't finished the thread, but others were skeptical.
pizza_pablo said:
TruePureX is actually one of the ROMs I was thinking of flashing.
So, if I take the 6.0 update, I can still root in a relatively normal way?
systemless root does not sound like a path I wish to take.
How does the OTA come to this device? A Moto app, I presume?
Does Moto ram it down one's throat, like verizon?
I was just reading on the moto forum, about simply unlocking the bootloader will stop the OTA. I haven't finished the thread, but others were skeptical.
Click to expand...
Click to collapse
I have tried both OTA and the stock rooted rom that is here in the development section, there are users who have had great success using the SU version 2.62...I personally have used 2.62, then 2.64 with great success...I have not used the system-less SU in these cases (although I have tested previously and they also worked)
so, feel free to flash the stock rom found in the development section, then flash 2.6(whatever works for you)...none of what I state is an endorsement of one rom over another, as all members here have contributed great efforts to get us this stuff...:good:
Naddict said:
I have tried both OTA and the stock rooted rom that is here in the development section, there are users who have had great success using the SU version 2.62...I personally have used 2.62, then 2.64 with great success...I have not used the system-less SU in these cases (although I have tested previously and they also worked)
so, feel free to flash the stock rom found in the development section, then flash 2.6(whatever works for you)...none of what I state is an endorsement of one rom over another, as all members here have contributed great efforts to get us this stuff...:good:
Click to expand...
Click to collapse
I am not really following....I think you are saying that the ROMs are safe.
Are you saying that a "regular" root method, for 6.0 OTA is available and stable and I shouldn't be worried about taking the 6.0 OTA?
If I were to take the 6.0 OTA, could I get back to 5.1, since unlocked bootloader is available?
Could this be done with the return to stock tool, even after 6.0?
pizza_pablo said:
I am not really following....I think you are saying that the ROMs are safe.
Are you saying that a "regular" root method, for 6.0 OTA is available and stable and I shouldn't be worried about taking the 6.0 OTA?
If I were to take the 6.0 OTA, could I get back to 5.1, since unlocked bootloader is available?
Could this be done with the return to stock tool, even after 6.0?
Click to expand...
Click to collapse
My point is, if you are rooted and unlocked, why take the OTA if you could just flash the 6.0 stock rom? why would you want to go back to 5.1?
Naddict said:
My point is, if you are rooted and unlocked, why take the OTA if you could just flash the 6.0 stock rom? why would you want to go back to 5.1?
Click to expand...
Click to collapse
I just want to learn what I can, before I start doing anything. I've read much, but I'm still confused as to what is possible and what is not. I've not had a phone this new, with the capability of unlocking the bootloader.
I believe that if the MXPE is on 5.1.1 when I fire it up, it will soon want to install the update.
I would like some time with the phone before I have to jump into unlocking and rooting, but I don't think I'll have it, so I would like to be prepared.
Did they lock the bootloader in 6.0?
I'm in the same boat as the op. Seems like there's no clear tutorial or anything. I just want stock with everything included (factory) 6.0 with xposed and root. I didn't even see a flashable stock MM zip with root anywhere.
20degrees said:
Did they lock the bootloader in 6.0?
I'm in the same boat as the op. Seems like there's no clear tutorial or anything. I just want stock with everything included (factory) 6.0 with xposed and root. I didn't even see a flashable stock MM zip with root anywhere.
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 here is stock in several flavors...if you do not have root, there are several options to try...systemless, or the latest beta SU's...some have stated that version 2.62 has been good for them...I have tried 2.62 and have also flashed 2.64 and both worked for me. Do some reading in these threads, plenty of guidance and info already about these issues.
Naddict said:
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 here is stock in several flavors...if you do not have root, there are several options to try...systemless, or the latest beta SU's...some have stated that version 2.62 has been good for them...I have tried 2.62 and have also flashed 2.64 and both worked for me. Do some reading in these threads, plenty of guidance and info already about these issues.
Click to expand...
Click to collapse
Believe me, when I say that I AM reading. I had shoulder surgery, last Wednesday, so I've got time on my hands. How else do you think I ended up finding and buying a relatively new Motorola, with unlockable bootloader?
There is just so much info and while reading, I keep going down rabbit trails of other interesting things to know about rooting it, but may not be the most important question I have. I read the entire thread on the (De)Odex Stock / Rooted / Debloated 6.0 MPH24.49-18, last night and am still confused.
It just seems to be unclear whether or not 6.0 is fully rooted and if there is any going back, once you're there.
I am leery, because if the Note 3, in safestrap. Once a LP ROM was flashed there was no going back to KitKat, even tho, early on, many stated that it was possible.
I've been away from Motorola rooting, since my RAZR M. I don't recall all the PC steps.
pizza_pablo said:
Believe me, when I say that I AM reading. I had shoulder surgery, last Wednesday, so I've got time on my hands. How else do you think I ended up finding and buying a relatively new Motorola, with unlockable bootloader?
There is just so much info and while reading, I keep going down rabbit trails of other interesting things to know about rooting it, but may not be the most important question I have. I read the entire thread on the (De)Odex Stock / Rooted / Debloated 6.0 MPH24.49-18, last night and am still confused.
It just seems to be unclear whether or not 6.0 is fully rooted and if there is any going back, once you're there.
I am leery, because if the Note 3, in safestrap. Once a LP ROM was flashed there was no going back to KitKat, even tho, early on, many stated that it was possible.
I've been away from Motorola rooting, since my RAZR M. I don't recall all the PC steps.
Click to expand...
Click to collapse
6.0 is rooted...see attached
Naddict said:
6.0 is rooted...see attached
Click to expand...
Click to collapse
I believe that 6.0 is rooted.
My question is how.
Which root methods are available?
Is systemless the only choice?
What is the exact (step by step) flash order?
Once the 6.0 OTA is taken, is it possible to go back to 5.1.1 stock or rooted, if desired?
here are my offerings to your questions...
My question is how.
Which root methods are available? SU silly!
Is systemless the only choice? No -- (note my previous screenshot is not systemless and is beta 2.64) see my previous posts on this
What is the exact (step by step) flash order? see this link, http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792 but note it is for the 1572 device, steps are the same...you will need the 1575 Stock rom found here instead http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Once the 6.0 OTA is taken, is it possible to go back to 5.1.1 stock or rooted, if desired? look in this thread, but start with this post...http://forum.xda-developers.com/showpost.php?p=64463125&postcount=179
here are my responses to your offerings to my questions...
My question is how.
Which root methods are available? SU silly! yeah, I meant traditional or systemless, silly
Is systemless the only choice? No -- (note my previous screenshot is not systemless and is beta 2.64) see my previous posts on this got it, thanks!
What is the exact (step by step) flash order? see this link, http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792 but note it is for the 1572 device, steps are the same...you will need the 1575 Stock rom found here instead http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 ok, I've read most of the second link
Once the 6.0 OTA is taken, is it possible to go back to 5.1.1 stock or rooted, if desired? look in this thread, but start with this post...http://forum.xda-developers.com/showpost.php?p=64463125&postcount=179[/QUOTE] I've read most of this one, too.
I really appreciate you hanging with me, thru my confusion and apprehension!
Hello hello,
So I reverted to my old i337 (ATT) because my S6 is defect and Samsung are hanging me out to dry (whole other story there). That being said, this i337 was on CM 11 4.4.4 but had the home-brew version, a slew of issues and so on. It did have root though.
I managed to install TWRP 2.8, CM 12.1 official build and it works flawlessly up until now. Except, I lost root. I'm puzzled too because running Motochopper tells me it's already rooted, and if I install Superuser form Play it seems to recognize the root, but then tells me I need to update, which fails. If I try to install any root app, nothing works.
Interestingly, I had to temporarily downgrade to CM 11 throughout this to troubleshoot a bug with GApps, and even after "losing" root to CM 12, in 11 I still had root! Back to CM 12 and out the root again. I've looked through threads and the only thing I found remotely close was to go back to 4.2.2 stock, then flash, then upgrade again... I'm trying to find another way since everthing else works fine...
Seems like it's a question of root method having changed in Lollipop, but that's really the extent of my knowledge.
As always, any help would be appreciated!
Denis
Edit: BB is I337UCUAMDL
Did you enable developer options, then go down to root access and enable it from there?
njf789 said:
Did you enable developer options, then go down to root access and enable it from there?
Click to expand...
Click to collapse
That is such a noob comment!! Did I enable... pfff! Of course... I... uh... oh. Yeah I guess that's a new option then, is it? *nervously whistling away*
PS: thanks! had no idea that was a thing I've updated my sig to celebrate.
DenisEhm said:
Hello hello,
So I reverted to my old i337 (ATT) because my S6 is defect and Samsung are hanging me out to dry (whole other story there). That being said, this i337 was on CM 11 4.4.4 but had the home-brew version, a slew of issues and so on. It did have root though.
I managed to install TWRP 2.8, CM 12.1 official build and it works flawlessly up until now. Except, I lost root. I'm puzzled too because running Motochopper tells me it's already rooted, and if I install Superuser form Play it seems to recognize the root, but then tells me I need to update, which fails. If I try to install any root app, nothing works.
Interestingly, I had to temporarily downgrade to CM 11 throughout this to troubleshoot a bug with GApps, and even after "losing" root to CM 12, in 11 I still had root! Back to CM 12 and out the root again. I've looked through threads and the only thing I found remotely close was to go back to 4.2.2 stock, then flash, then upgrade again... I'm trying to find another way since everthing else works fine...
Seems like it's a question of root method having changed in Lollipop, but that's really the extent of my knowledge.
As always, any help would be appreciated!
Denis
Edit: BB is I337UCUAMDL
Click to expand...
Click to collapse
Wait! So you have CM12 on your ATT S4?
I spent 6 hours yesterday and managed to instal golden eye 53. But I'd like to try installing cm12.
Can you point me the link of the relevant thread?
Thanks
Sarfarash said:
Wait! So you have CM12 on your ATT S4?
I spent 6 hours yesterday and managed to instal golden eye 53. But I'd like to try installing cm12.
Can you point me the link of the relevant thread?
Thanks
Click to expand...
Click to collapse
Yes and I can say that aside from very minor bugs (such as I can't get weather to work) it's by far the best ROM I've had on this phone! The nice thing too is it's officially supported.
First you can download the ROM here; I used the last stable release for 12.1, right at the top.
For instructions I would suggest to go on the official wiki for the jflteatt, but make sure you are using TWRP version 2.8.7.0. I was on a CWM custom recovery which worked fine for 4.4.4, but when I flashed 5.1 it was plagued with crashes and GApps were completely useless - even if it did technically work. Trust me, this will save you a lot of time and it's not really mentioned anywhere.
Also stay away form TWRP version 3.0; when I tried to install it it re-locked my boot loader (somehow) and I had to fiddle-fsck around a lot with it to bypass it again.
But outside this, it was a flawless install for me! Hope this helps.
DenisEhm said:
That is such a noob comment!! Did I enable... pfff! Of course... I... uh... oh. Yeah I guess that's a new option then, is it? *nervously whistling away*
PS: thanks! had no idea that was a thing I've updated my sig to celebrate.
Click to expand...
Click to collapse
No problem man. There is also a setting in Super User to override the CM root setting iirc. Just FYI
njf789 said:
No problem man. There is also a setting in Super User to override the CM root setting iirc. Just FYI
Click to expand...
Click to collapse
Yeah I had tried that but it wouldn't do anything. I've followed your advice and now it works perfectly. Thanks again!
DenisEhm said:
Yes ......
For instructions I would suggest to go on the official wiki for the jflteatt,
..... I was on a CWM custom recovery which worked fine for 4.4.4
Click to expand...
Click to collapse
Thank you very much,
I got excited for few minutes, then I followed the instructions link, and saw that big red banner of warning saying only MDL and MDB can use it.
And I am on OC3 (5.0.1) so I guess I'm out of luck!
Sarfarash said:
Thank you very much,
I got excited for few minutes, then I followed the instructions link, and saw that big red banner of warning saying only MDL and MDB can use it.
And I am on OC3 (5.0.1) so I guess I'm out of luck!
Click to expand...
Click to collapse
Ah yes that's true, I'm on MDL... bummer...
Hey all,
I used towel root immediately when I got the phone in 2014 and have not made any system updates since. Holding off on phone upgrade to see what the new nexus phones are about, but wondering what you guys would recommend I do to update my current phone. I messed around here with root and roms when I had a sprint hero, but have not continued same level of involvement with the S5. Probably different opinions but looking for most stable, most updated, daily driver rom recommendation. Current setup https://drive.google.com/open?id=0B94_4ssT0e6mOWFuWGxBRzI2Tm8
Thanks!
Download the EMMC brickbug check app and tell me the first 2 numbers of your CID, then I can tell for sure if you can update to MM and root or not.
15 = good
11 = bad
Since you bought your phone in 2014, and the first batch of phones had 15, you probably have a 15 (I have a 15 and I bought on release date).
Thanks for the help. Yep, CID begins with 15, so what next? Allow OTA update and re-reroot (via some means)?
cantplay said:
Thanks for the help. Yep, CID begins with 15, so what next? Allow OTA update and re-reroot (via some means)?
Click to expand...
Click to collapse
No. Are you OK with loosing your data?
Lightn1ng said:
No. Are you OK with loosing your data?
Click to expand...
Click to collapse
Either way, I can back up, or upgrade in a way that preserves data.
cantplay said:
Either way, I can back up, or upgrade in a way that preserves data.
Click to expand...
Click to collapse
Well first you need to decide what ROM you want
Currently I'm on resurrection remix, however there is VanirAOSP, CM13, Phoenix ROM, to name a few.
Decide what ROM you want (that's your choice ) and then download the stock PB1 5.0 tar from SamMobile. Flash it thru Odin and do a full factory reset.
Then follow the instructions here
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 (Skip supersume)
Then follow here
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909 (I use the ADB method because it "just works" but you can use any method you like)
Then wipe everything in twrp and install a ROM. (If you're installing an aosp rom then you will also need Gapps...)
Ok, I'll give it a whirl. Thanks for shortcutting me on this.
I'm trying to get this device up to date. Coming out of storage it's on Android 6.0 Security Patch 2/1/2016... TruPureXMM 2.9 Build. Is there a quick and easy way to get this device onto a current ROM?
MARKREIF said:
I'm trying to get this device up to date. Coming out of storage it's on Android 6.0 Security Patch 2/1/2016... TruPureXMM 2.9 Build. Is there a quick and easy way to get this device onto a current ROM?
Click to expand...
Click to collapse
Flash one??? You want stock or custom?
Stock please.....
i'll try custom as well....
Assuming you have the XT1575, you can try here. This will bring you up to stock nougat with an OTA out there if you choose to take it.
Just a couple of caveats if you flash nougat: Once you do so it limits the availability of custom roms greatly. As far as I know this is the last available stock flashable images so if you take the OTA, flashing it again could cause issues as it is considered "downgrading". I personally wanted to root so I did not relock my bootloader and froze my phone taking the OTA so I could always flash the full image should anything go wrong.
Thanks..,. Yes I am talking about the XT1575. Can you also point me in the direction of maintaining my current Root status..... While upgrading to what you would consider the best current rooted ROM.
Thanks
MARKREIF said:
Thanks..,. Yes I am talking about the XT1575. Can you also point me in the direction of maintaining my current Root status..... While upgrading to what you would consider the best current rooted ROM.
Thanks
Click to expand...
Click to collapse
I personally stick with rooted stock. Mileage varies person to person on custom so I just play it safe.
If you go stock rooted, make sure you pay attention when flashing the stock nougat and do the steps in the post that keeps your bootloader unlocked. After stock ROM is flashed, temp flash TWRP, do a backup, then TWRP again and flash root option of your choice. I personally use Magisk to root so apps pass the SafetyNet checks.
all's well went with ResurrectionRemix staying on 6.0 quite pleased - thanks for your help
MARKREIF said:
all's well went with ResurrectionRemix staying on 6.0 quite pleased - thanks for your help
Click to expand...
Click to collapse
RR is a good choice from what I've read. Glad all is well. Enjoy.