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
Related
Who knew a MONDAY would be such an awesome day! New OTA Update MF9 as 1st reported HERE by @jonathanhtc . Any questions can go here guys....
I'll start off with a question I have: Does this mean that all of our mods will have to be re-done to be able to be flashed on the new update? ie: Hotspot mod, 4 in 1 reboot mod, etc. all have to be re-done to be able to work on the new software update?!
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
That's why I'm definitely waiting till the devs take a look at it before I download it. It definitely wasn't there with MDC and MDL.
Sent from my SPH-L720 using xda app-developers app
Yes same here. BUT some new things that were reported are: Transparent notification bar with any wallpaper, new smart pause toggle, smoother UI (less lag), move apps to SD card, and KNOX is finally deployed along with Briefing and SPDclient.
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
garwynn said:
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
Click to expand...
Click to collapse
I already posted in his thread about an hour ago that source is up
Sent from my SPH-L720 using Tapatalk 4 Beta
I wonder if this is basically the same update that the international version got. Hopefully it is, and it fixes the "smearing issue" and also we get the HDR video recording!
I heard people were unable to unlock to use internationally. Some said sprint unlocked but software restrictions remained. Do you think this update might fix that? And im not talking for use withing the U.S. mainly outside (Europe)
Sent from my SPH-L720 using Tapatalk 2
Okay, new bootloader, modem, kernel.
2 secondary bootloaders updated as well as rpm and tz.
Interesting that everything backs up to mmcblk0p22 before writing the new one.
Don't recall seeing that in updates for other devices.
New Fingerprint is just swap out MDL with MF9.
As mentioned, Knox is there. Makes me wonder what else was locked down with it.
Updated OCR among many updated binaries.
A lot of the binaries - in particular, vendor blobs - have an update.
I'll need someone to dump the system partition once it's patched for the new vendor files.
Hopefully good news for AOSP builds.
I'm asking to see if the previous sources have any info - but they've already stated not to expect anything.
There are a few questions that need to be figured out:
1) What is in the new bootloader? Are we locked like most of the others?
2) Can we revert bootloaders after flashing - and if so, what does it take to do so?
3) Root on new build?
All of this is going to require a test device, which sadly at the moment I am now without.
All the problems with the N2 left me with a Spare N2 and now without an S4.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Could you post the steps you used to update & restore root please?
illdini said:
Could you post the steps you used to update & restore root please?
Click to expand...
Click to collapse
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
shabbypenguin said:
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
Click to expand...
Click to collapse
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
chenry944 said:
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
Click to expand...
Click to collapse
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash.
I have the same question BTW I'm rooted, with TWRP recovery, but stock ROM. Have installed a few mods (hotspot, camera shutter sound disabled. Had XPosed framework installed with a couple of mods, but removed those later).
What would be the safe way for me to install the new update? I actually like some of the features that Samsung added, so not looking to switch away from stock ROM for now.
I'm hoping that knowledgeable developers will provide guidance in the next few days
jj14 said:
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash
Click to expand...
Click to collapse
Yea I read that post I am just trying to get clarification for myself and everyone else in which way he did flash it.
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Best news of this thread! Thanks for taking the chance!
Sent from my SPH-L720 using Tapatalk 4 Beta
yea i was stock odex from crawj and i hit errors while flashing it twrp, i flashed stock kernel and stock recovery and tried and it still failed so i modded teh zip to forcibly install, i now have no mobile data and my modem isnt updated. so my suggestion, dont follow my lead
im currently flashing MDC stock tar to fully update all the way.
Got the Modem Updated to MF9 using Odin without going back to Stock, uploading the odin package now, and will be updating the thread here -> http://forum.xda-developers.com/showthread.php?t=2338919
Does this include the security update Google announced would be coming to OEMs?
Now if i update to mf9, will it affect custom roms that are built around MDL, or AOSP?
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
krazie1 said:
This is a thread to see if anyone has ideas on porting CWM or TWRP to our device? Any ideas of getting a custom recovery on this phone is welcomed. We have Root for the At&t/Verizon variants, custom recovery would be topping to the cake.
Click to expand...
Click to collapse
Dont we need an unlocked bootloader first?
chrisexv6 said:
Dont we need an unlocked bootloader first?
Click to expand...
Click to collapse
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
EDIT: I thought about it and your right, you always have to unlock the bootloader before you install the Custom Recovery.
krazie1 said:
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
Click to expand...
Click to collapse
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
kexec is required to flash a kernel.
Safestrap is a way to flash somewhat custom ROMs (without kexec you need to use stock kernel) without recovery installed but it needs to be adapted to each specific phone. Right now I think they are working on a version that will work with the S4, not sure how attractive the G2 is (or will be).
krazie1 said:
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2443165 <---- these guys are the ones who worked most of the magic for Optimus G (and Pro?).
You guys first need Root to do anything (which i believe you have). Then you need a Custom Recovery. Installing a Custom Recovery can be accomplished via a workaround or by unlocking the bootloader. A workaround like loki by djrbliss on the Galaxy S4 which isn't an unlock but more so a bypass or like Safestrap by Hashcode.
Here is the man djrbliss.
http://forum.xda-developers.com/showthread.php?t=2358871
https://twitter.com/djrbliss
Is there any news on this? I cant even find a good place to look for info about this phone yet.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Darkestred said:
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Click to expand...
Click to collapse
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
WACOMalt said:
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
Click to expand...
Click to collapse
I found it. server is chat.freenode.net room is lg-g2. Not very much going on in there at the moment.
i completely agree with the said explanation. but I'm having difficulties with my device i.e. LG G2 (D802).
I'm rooted with custom recovery TWRP and unable to install most of AOSP roms based on 4.4 KitKat. New Custom roms are coming up very frequently now for this device but so far I'm able to flash ParanoidAndroid Rom and modifited stock rom... Apart from this I always gets error while flashing the rom.
Most of the time Error comes up saying 'Status 7 Error' and 'unable to execute update binary'.
I did google on this subject and tried everything i found but the problem still exist.
I never had these problem flashing LG Stock or Android 4.3 based roms. Need advise on this subject. By the way any help on unlocking the bootloader????
thanks:good:
krazie1 said:
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
Click to expand...
Click to collapse
This post is to try to sort out the questions, concerns and troubles that users come up against when using.the "SlapMyMoto" rooting method to gain "Root" on the Moto X.
[Question]What happened to my "Recovery"--
[ANSWER]- It's gone. There's no "Recovery". Now you have read/write access to /system instead of a recovery. Your system will boot normally, except /system will be read-write accessible.
[Question ] - Can I flash Xxx-xxx.zip through recovery like it says here - xxxxxx.com/yada/yada/instructions (with link to. Zip file) .com
[Answer] No.
[Question ] Why not?
[Answer] Because you have a "Custom" Recovery that does nothing more than provide read-write access. to the /system partition , ..period.
[Question] -- Can I use some other"Recovery"?
[Answer ] -- ? DUNNO? Maybe jcase will chime in and clarify that. As it stands, maybe the 4.4 recovery, don't know for sure what it will do to your root. Whether it is the 4.4, or 4.2 recovery, without unlocking your Boot loader it will have to be a signed. zip file for system security.
Where else can I turn for answers?
Hopefully, here: http://forum.xda-developers.com/showthread.php?t=2538896
SlapMyMoto 0.5c Beta (4.4 root, RW to system)
As it stands, jcase is attending to family/personal matters. I'm sure he will be back sometime. Until then, just have to wait it out.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Question- Why with a locked bootloader do I need recovery?
Answer- You don't!
Comment- Good, because you don't have one now that you used SlapMyMoto to root. Your recovery has been replaced by write protection off.
lowvolt1 said:
Question- Why with a locked bootloader do I need recovery?
Answer- You don't!
Comment- Good, because you don't have one now that you used SlapMyMoto to root. Your recovery has been replaced by write protection off.
Click to expand...
Click to collapse
Unless you want to clear cache, flash a signed update.zip you really don't need it. Until you do.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
dtrud0h said:
Unless you want to clear cache, flash a signed update.zip you really don't need it. Until you do.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Or I could just use adb
via my slapped KIT KAT moto X rockin on Verizon
Yup, you sure could. What I'm trying to get across to the masses is, its not all about you lowvolt1, there are many new, or people that don't known their way around all this that read the "How-to" from xyz.com and expect it to work.
If you can read, apply your good judgement, and move on then great.
There are other people that can't yet wrap their heads around the bootloader/recovery thing that just got a phone, have no clue, and want help or answers. This is the thread for them.
Maybe you should start a thread for stuff that's all about you if that's what you want.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
dtrud0h said:
Yup, you sure could. What I'm trying to get across to the masses is, its not all about you lowvolt1, there are many new, or people that don't known their way around all this that read the "How-to" from xyz.com and expect it to work.
If you can read, apply your good judgement, and move on then great.
There are other people that can't yet wrap their heads around the bootloader/recovery thing that just got a phone, have no clue, and want help or answers. This is the thread for them.
Maybe you should start a thread for stuff that's all about you if that's what you want.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
My narcissistic nature is not in question here. What is in question is why you are trying to help new people or people with questions, yet you continue to blurt out false truths.
Maybe you should listen to the people that have alot more knowledge than you and I put together and do a little more research before you continue to confuse people.
via my slapped KIT KAT moto X rockin on Verizon
lowvolt1 said:
My narcissistic nature is not in question here. What is in question is why you are trying to help new people or people with questions, yet you continue to blurt out false truths.
Maybe you should listen to the people that have alot more knowledge than you and I put together and do a little more research before you continue to confuse people.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
OK I for one found your (original) explanation quite helpful as I didn't pick up on the recovery/bootloader thing. I'm still not rooted...
The recovery I can live without - I think you've explained it well.
What happens to the bootloader? it looks like (in step "5") it is downgraded to the 4.2.2 bootloader? So we're running 4.4 with a 4.2.2. bootloader when all said and done?
tdiman said:
OK I for one found your (original) explanation quite helpful as I didn't pick up on the recovery/bootloader thing. I'm still not rooted...
The recovery I can live without - I think you've explained it well.
What happens to the bootloader? it looks like (in step "5") it is downgraded to the 4.2.2 bootloader? So we're running 4.4 with a 4.2.2. bootloader when all said and done?
Click to expand...
Click to collapse
Yes. As I understand it your statement is correct.
via my slapped KIT KAT moto X rockin on Verizon
Guys-
I don't feel like going through all 80+ pages on the slapmymoto thread, so I will ask it here.
I have the at&t version with 4.4 on it. Can I root at the moment with the 0.5 slapmymoto, if not, is 1.0 going to be solving this issue?
Thanks in advance-
Dodolom said:
Guys-
I don't feel like going through all 80+ pages on the slapmymoto thread, so I will ask it here.
I have the at&t version with 4.4 on it. Can I root at the moment with the 0.5 slapmymoto, if not, is 1.0 going to be solving this issue?
Thanks in advance-
Click to expand...
Click to collapse
I am assuming your on the non Dev edition. I am not familiar with at&t, so I will ask this. Can you unlock the boot loader on that version? If not then yes I believe you can root using slap. But you have to downgrade to 4.2.2 first.
via my slapped KIT KAT moto X rockin on Verizon
lowvolt1 said:
I am assuming your on the non Dev edition. I am not familiar with at&t, so I will ask this. Can you unlock the boot loader on that version? If not then yes I believe you can root using slap. But you have to downgrade to 4.2.2 first.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
Yeah, this is jus the retail at&t version on the Cyber Monday sale. I had the GSM DE from day 1 but sent it to a friend in england to play with and then Cyber Monday deal popped up, so I ordered one but this time I went with the custom design which only comes with the carriers.
Anyways, how can I know if I can unlock the bootloader or not?
Dodolom said:
Yeah, this is jus the retail at&t version on the Cyber Monday sale. I had the GSM DE from day 1 but sent it to a friend in england to play with and then Cyber Monday deal popped up, so I ordered one but this time I went with the custom design which only comes with the carriers.
Anyways, how can I know if I can unlock the bootloader or not?
Click to expand...
Click to collapse
Try Google searching it. I don't think you can. Verizon can't and since you made mention of a Dev edition I am guessing you can't unlock.
via my slapped KIT KAT moto X rockin on Verizon
lowvolt1 said:
Try Google searching it. I don't think you can. Verizon can't and since you made mention of a Dev edition I am guessing you can't unlock.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
I think I will wait for the 1.0 and see what happens or if I get some time this week, I will give it a shot with the downgrading and all that.
Thanks
Dodolom said:
I think I will wait for the 1.0 and see what happens or if I get some time this week, I will give it a shot with the downgrading and all that.
Thanks
Click to expand...
Click to collapse
You may be waiting awhile for 1.0. If it comes at all.
via my slapped KIT KAT moto X rockin on Verizon
I just recieved a Moto X on Verizon in the mail and I really would like to root it to debloat and run a custom rom but I have always had Samsung and worked with odin. How do we go about rooting this? What do you think is the easiest way? For some reason ADB isnt working on my computer. Thanks in advance! I REALLY NEED SOME HELP!!
ehusidic said:
I just recieved a Moto X on Verizon in the mail and I really would like to root it to debloat and run a custom rom but I have always had Samsung and worked with odin. How do we go about rooting this? What do you think is the easiest way? For some reason ADB isnt working on my computer. Thanks in advance! I REALLY NEED SOME HELP!!
Click to expand...
Click to collapse
1. There are no custom roms at the moment. Unless you have the Verizon Dev edition.
2. You will only gain root access and RW permissions
3. The easiest way is slap my motto is the only way if you want to be rooted on kit Kat 4.4
4. You will definitely need adb
Sent from my GT-P3110 using Tapatalk 4
[Q] Say if you boot into "recovery," otherwise write protection-off mode, then you reboot. Do you boot back into normal mode? Or does it default into write protection-off mode until you explicitly tell it to boot normally?
erikikaz said:
[Q] Say if you boot into "recovery," otherwise write protection-off mode, then you reboot. Do you boot back into normal mode? Or does it default into write protection-off mode until you explicitly tell it to boot normally?
Click to expand...
Click to collapse
That depends, are you rebooting in to recovery again, or rebooting in to Android? Android = WP on. Recovery = WP off.
A couple of non-SlapMyMoto questions have been asked here so... (dtrud0h, feel free to add these to your OP)
[Q] What is the best way to root my Moto X?
[A] Depends what Rom is on your X. Generally there are 3 "stock" motorola rom versions for the X. The ROM it shipped with (android 4.2.2), the "camera fix" update (4.2.2), and Kit Kit (4.4). And it depends on if you have a locked bootloader or not.
Locked Bootloader with KitKat (4.4) see SlapMyMoto -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Locked Bootloader with "Camera Update" see -> [Root] RockMyMoto (Yes, even the first OTA)
Locked Bootloader with initial shipping rom see -> [Root/Write Protection Bypass] MotoX (no unlock needed)
UNLOCKED bootloader see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
NOTE: these should work across all carrier variants of the Moto X. that means ATT, VZW, TMO, TIM, Rogers, etc.. should be able to use these. You just need to pick the right process based on your ROM or locked vs unlocked bootloader.
[Q] Once I root, can I accept an OTA update on my phone?
[A] If you have rooted with SlapMyMoto, RockMyMoto, PwnMyMoto, or have otherwise replaced stock recovery, then please do not let your phone try to install any OTA updates!!!
As stated in another Question/Answer, using JCASE's SlapMyMoto, RockMyMoto and PwnMyMoto to root will replace your recovery to allow for the ability to boot with R/W permitted. When the OTA update downloads to your phone, and it tries to reboot to install it, the phone/update is trying to use the stock recovery to install the update. Since it is not there, the update will fail and the phone will reboot and it will likely try to reboot and try to install again. This can often result in the phone being stuck in a boot loop of continually retrying to reboot and install the update. There are ways to fix this posted in other threads. NOTE: there may be ways to get around this and install the OTA zip but that is a topic for another thread.
If you have an unlocked bootloader and have installed a custom recovery, it might be possible to install the OTA ZIP manually, but again that is a topic for another thread.
[Q] Can I unlock the Bootloader on my Moto X? or How do I know if I can unlock my bootloader or not?
[A] If you have a Developer Edition Moto X, yes you can unlock the bootloader and it doesn't void your device warranty. If you have a MotoMaker or Carrier Branded model, it depends on IF your carrier allows Motorola to do it, and it will void your warranty. For example, Verizon and ATT does now allow Motorola to unlock your boot loader. T-Mobile users can unlock their bootloader but it will void their warranty.
To see if your Moto X bootloader can be unlocked visit -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth You can step through the process until you get to the final submit WITHOUT voiding your warranty. Based on the site's wording, once you hit the final submit to request the code, your warranty is voided (unless your phone is a developer edition)
[Q] How do I run a custom rom on my X?
[A] SlapMyMoto and the like is/are not a process to allow you to run custom roms.
Unless you have an unlocked bootloader, you can't remove the Stock Motorola ROM and run a completely custom rom. And because most X owners generally agree the stock X ROM is very good, there are not many custom roms available for the X, even for those with unlocked bootloaders. Any available custom roms are posted in -> http://forum.xda-developers.com/moto-x/development so please use those threads for info/discussions.
If you have locked bootloader, there are a few options for using Safestrap to allow for some customization or "alternate roms", but that is a topic which doesn't apply to this thread.
So what can we really do after we gain root. The obvious is run apps that require root but what else? I am a user and follow directions from devs on how to do things. So without the knowledge or experience of the deep pits of android what can I do with root? This root process looks a little tough but I could figure it out once I piece all the threads together to understand it better.
Sent from my vzw moto X
---------- Post added at 10:00 AM ---------- Previous post was at 09:54 AM ----------
Will this work on a non developer vzw phone?
http://forum.xda-developers.com/showthread.php?t=2521509
Sent from my vzw moto X
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723
Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??
khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol
khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Leraeniesh said:
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Click to expand...
Click to collapse
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Eclipse00 said:
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Click to expand...
Click to collapse
is the CWM 100% operational ?
Last time I checked it was half baked still.
Give the Devs some time. =) atleast we got KK officially =) Loving it.
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
j27h said:
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
Click to expand...
Click to collapse
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the forum he was using to post that update. I sent him a PM letting him know about the resolution issue(XHDPI).
http://forum.xda-developers.com/showthread.php?p=53245960
It's here
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Just used it this morning to install root on 4.4.2. Worked fine.
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader. I had that same issue after the initial upgrade to the new OTA and bootloader. I ran through a few steps like unlocking the bootloader again (may have not done anything), I used a pre-rooted RSD flash of stock and I used the ADB method of installing the recovery instead of using fastboot.
To use the adb method I downloaded the batman 1.2 recovery tool, just renamed the version of TWRP (in this case TWRP2710-RAZR_M-KITKAT.img) to TWRP.IMG and placed it in the root of the batman folder, then I ran the flash TWRP recovery option. Note that the batman tool was designed for older firmware and you should probably not run any other functions on it if you are on the new firmware.
Batman 1.2
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
You need to remove or rename,
Code:
/system/[COLOR="Red"][B][I]recovery-from-boot[/I][/B][/COLOR]
Thanks I will give this a try. I may hold off for now I read there was a possible update coming. I would guess you would need the stock recovery to get the update to work.
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
ezdi said:
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
Click to expand...
Click to collapse
Two weeks at best, considering it's the 4.4.3, which is probably the last update we'll get from Moto, unless a miracle occurs and we're given the 4.5 or 5.0, which shouldn't land until at least 5 months after it's release (if it does release next week).
I can't believe they're already planning another update. Sitting on jb we were all pretty sure that the kk update would be the last
Sent from my DROID RAZR M using Tapatalk
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
GnatGoSplat said:
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
Click to expand...
Click to collapse
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Sent from my DROID RAZR M using Tapatalk
thewraith420 said:
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Click to expand...
Click to collapse
Yeah, I'm hoping the update is because there were bugs that were too big to ignore, but Verizon forcing them to patch the exploit is probably more likely. Definitely a shame to close it on a 2yr old phone. IMO, we need some kind of consumer protection law that forces VZ and AT&T to allow BL unlocks once a device reaches EOL. It would even be better for the environment as it does keep devices relevant for much longer and less likely to end up in a toxic Chinese burn pile.
I feel like the reason we got the exploit back was a Moto dev saw the device is reaching EOL and decided it wouldn't hurt to help the community by putting the exploit back in, because it would almost have to have been deliberate.
Well it's actually lucky that 4.4.4 didn't patch towelroot, so root, I THINK, will stay, but for the bootloader unlock, it's better now than wait with Verizon.