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
Related
I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?
I am here to give a quick warning to all users. Please, do not revert to older versions of Android. This can cause your device to brick when you take an ota. The reason for the brick is because the ota process flashes secure elements and these elements can not be mixed. Once, you mix these you will brick. Also, if you have reverted the only safe way to update is thru a full xml.
If anyone would like to extend on this point please do. I am writing this up before class as I see people are bricking.
Sent from my XT1053 using Tapatalk
papi92 said:
I am here to give a quick warning to all users. Please, do not revert to older versions of Android. This can cause your device to brick when you take an ota. The reason for the brick is because the ota process flashes secure elements and these elements can not be mixed. Once, you mix these you will brick. Also, if you have reverted the only safe way to update is thru a full xml.
If anyone would like to extend on this point please do. I am writing this up before class as I see people are bricking.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
1+^
Sent on my Gummy running Lenoto X
I'll only add that the first few bricks from this were just bad luck.....but after the posts about it.....the further bricks can be blamed on poor research, reading and self learning. These things are what XDA is supposed to be about. Blindly flashing this and that without doing homework first is a recipe for disaster with what we do here.
Sometimes people, like me, are brushed off as jerks or know it all's when we remind people of these things, or tell them to read and search instead of answering their questions.....but really we're just trying to help people help themselves and learn more about what they are doing.
Anyway.....personally ...I'll continue to be a "jerk" and remind people of this stuff occasionally, cause it just may get through to some people.
Also.....XDA rules state to search before posting....Wow has that been forgotten these days. LOL
Peace all!
Sent from my Moto X cellular telephone...
My sentiments too, at this rate I think the moto x will have the world record for hard bricks
Sent on my Gummy running Lenoto X
flashallthetime said:
My sentiments too, at this rate I think the moto x will have the world record for hard bricks
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
No kidding! LOL. I despise Samsung....but it was very hard to brick. LOL. This bootloader version mixed with OTA stuff on the X is a mess.
Sent from my Moto X cellular telephone...
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Oh...throw in unlocked bootloader methods, vs locked bootloader methods and the x can get pretty confusing. Personally.....I think people should avoid the phones that can't be boot loader unlocked like the plague. LOL
Sent from my Moto X cellular telephone...
Avoid flashing firmware at the least, there's now a flashable 4.4.2 stock ROM too, so you have options to safely flash roms
Sent on my Gummy running Lenoto X
If you are going play then you must be read to play. As for people who want to use otas there's a trick. Remove all secure elements from the zip just keep the patches to system boot and modem. That way you do not brick. But please don't return your X when you do brick because of taking OTAs on a Frankenstein device with this bootloader and that gpt
Sent from my XT1053 using Tapatalk
i think it's always a good idea not to go back in android versions!
Reading this makes me feel sad. I come from a SGSII, on which I could flash anything, without braking it .
So let me get this straight: if I have the Sprint version (no dev version available) and want root without voiding the warranty I have to downgrade to 4.2.2 and use RockMyMoto, flash 4.4, and use SlapMyMoto. However, if I do that, any future OTA upgrades will cause a brick so while I can flash future ROMs I will be stuck on the current firmware?
ahecht said:
So let me get this straight: if I have the Sprint version (no dev version available) and want root without voiding the warranty I have to downgrade to 4.2.2 and use RockMyMoto, flash 4.4, and use SlapMyMoto. However, if I do that, any future OTA upgrades will cause a brick so while I can flash future ROMs I will be stuck on the current firmware?
Click to expand...
Click to collapse
No , the problem happens when you upgrade your boot loader to 4.4.2, you can not downgrade. As long as you stay with 4.4 BOOTLOADER you can downgrade to 4.2.2 post camera ota. If you flash the 4.4.2 BOOT LOADER and decide to Frankenstein your phone and flash an older boot loader , you're SOL, 4.4.2 BOOT LOADER is a one way ticket
Regardless if your boot loader is unlocked or locked. Just because I have a unlocked boot loader does not give me Amy extra ability to flash an older boot loader ,it gves me a better way of rooting and flashing roms
Sent on my Lenoto A2109 tablet
flashallthetime said:
No , the problem happens when you upgrade your boot loader to 4.4.2, you can not downgrade. As long as you stay with 4.4 BOOTLOADER you can downgrade to 4.2.2 post camera ota. If you flash the 4.4.2 BOOT LOADER and decide to Frankenstein your phone and flash an older boot loader , you're SOL, 4.4.2 BOOT LOADER is a one way ticket
Regardless if your boot loader is unlocked or locked. Just because I have a unlocked boot loader does not give me Amy extra ability to flash an older boot loader ,it gves me a better way of rooting and flashing roms
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
Thanks. My motomaker Moto X is on its way, hopefully it won't have the 4.4.2 boot loader from the factory.
Personally I think that anyone even remotely interested in hacking, flashing, or anything of that nature should have gotten a developer edition. Especially if you're not sure of what you're doing. No company has ever offered something that makes being a phone geek so easy and yet, not many have taken advantage.
I also feel that not enough people try to do things the "hard way". But I find fastboot way easier and safer than many of the tools provided. And once you learn it it's useful on many devices and similar to Odin etc. I just don't want Motorola getting a bad rap for other people's foolishness
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
SymbioticGenius said:
Personally I think that anyone even remotely interested in hacking, flashing, or anything of that nature should have gotten a developer edition. Especially if you're not sure of what you're doing. No company has ever offered something that makes being a phone geek so easy and yet, not many have taken advantage.
I also feel that not enough people try to do things the "hard way". But I find fastboot way easier and safer than many of the tools provided. And once you learn it it's useful on many devices and similar to Odin etc. I just don't want Motorola getting a bad rap for other people's foolishness
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
Click to expand...
Click to collapse
It makes no difference having a DE edition or a Rogers unlockable boot loader moto as I have , they are essentially the same beast, I can do everything you can do, a DE edition will brick as fast as any other moto variant. I think people who have no common sense is the problem, they assume that flashing firmware is like flashing custom ROMs and its not
Sent on my Lenoto A2109 tablet
papi92 said:
If you are going play then you must be read to play. As for people who want to use otas there's a trick. Remove all secure elements from the zip just keep the patches to system boot and modem. That way you do not brick. .........
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Out of curiosity. Have you done this with your X? From what I gather it seems to be a "safe(r)" way of upgrading without compromising the bootloader, yet I haven't read where anyone has actually tried doing it. The threads where those on 4.2.2 flashing 4.4.x firmwares from other carriers is coming to mind. Why risk it if what you are saying works? I have a new VZ dev ed that I'm trying to figure out how to handle the 4.2.2 update on, if it ever comes.
edthesped said:
Out of curiosity. Have you done this with your X? From what I gather it seems to be a "safe(r)" way of upgrading without compromising the bootloader, yet I haven't read where anyone has actually tried doing it. The threads where those on 4.2.2 flashing 4.4.x firmwares from other carriers is coming to mind. Why risk it if what you are saying works? I have a new VZ dev ed that I'm trying to figure out how to handle the 4.2.2 update on, if it ever comes.
Click to expand...
Click to collapse
He's a developer, staying with only system images and modems your safer, modems do not always work in specific locations, UK modem will not work in Brazil, so keep your existing modem , the system files are all basically the same with minor changes, T-Mobile and rogers have no bloat, rogers has the carrier logo, where T-Mobile doesn't, at&t has at&t bloatware. As for Verizon,spring and us cell I have no idea as its CDMA and I have the gsm variant
Sent on my Lenoto A2109 tablet
flashallthetime said:
He's a developer, staying with only system images and modems your safer, modems do not always work in specific locations, UK modem will not work in Brazil, so keep your existing modem , the system files are all basically the same with minor changes, T-Mobile and rogers have no bloat, rogers has the carrier logo, where T-Mobile doesn't, at&t has at&t bloatware. As for Verizon,spring and us cell I have no idea as its CDMA and I have the gsm variant
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
It's starting to come together...
Knowing this I still don't quite get why so many people seemed to be flashing firmware from other carriers when they could have cherry picked what they "needed".
It would be nice to figure out how to use the system.img from other carriers as VZ's firmware appears to have about 100MiB of "added features" that I'd prefer not to have.
Being that the risk appears to be negligible I may attempt to push the system.img from another carrier to see what happens.
edthesped said:
It's starting to come together...
Knowing this I still don't quite get why so many people seemed to be flashing firmware from other carriers when they could have cherry picked what they "needed".
It would be nice to figure out how to use the system.img from other carriers as VZ's firmware appears to have about 100MiB of "added features" that I'd prefer not to have.
Being that the risk appears to be negligible I may attempt to push the system.img from another carrier to see what happens.
Click to expand...
Click to collapse
You can flash other carrier images, sprint and us cell are 2 CDMA carriers without any issues, system IMG ,boot IMG and non_hlos.bin are the files you need (not motoboot.IMG that's the bootloader)
Sent on my Lenoto A2109 tablet
So many of the brick stories I'm reading about could have been avoided had people trying to expedite the upgrade to 4.4.2 just flashed everything but the bootloader?
At some point I need to figure out how to get one of the bloatless system files VZ X as I'm not sure where the 100MB of stuff comes from.
Next steps, tell self "yes this phone is worth keeping" and unlock the bootloader.
Again, thanks for your patience
edthesped said:
So many of the brick stories I'm reading about could have been avoided had people trying to expedite the upgrade to 4.4.2 just flashed everything but the bootloader?
At some point I need to figure out how to get one of the bloatless system files VZ X as I'm not sure where the 100MB of stuff comes from.
Next steps, tell self "yes this phone is worth keeping" and unlock the bootloader.
Again, thanks for your patience
Click to expand...
Click to collapse
Yes but people always jump in head first, the only issue is if they happen to flash the old system.img 4.4 and have the 4.4.2 boot loader, chances are they will end up hard bricked, why? Going back to 4.4 will ping moto servers for the ota, it gets downloaded and installed, bam hard bricked,
If you flash just system.img , do not take any ota at all
Sent on my Lenoto A2109 tablet
Yes this is for Locked Bootloaders! But on Verizon only!! Yes 100% working ROM with root safestrap and write protect OFF!
You must be on or revert back to 4.2.2, root it with RockMyMoto, then run MotoWpNoMo, then install safestrap or do the same with 4.4 first... Then follow KrYpToNiTe's guide here http://rootzwiki.com/topic/116025-romsafestrapxt1060-stock-rooted-vzw-164552-kitkat-442/
PS. If you have 4.4, rsd back to 4.2.2 AND IF...you updated to 4.4.2 you might be out of luck sorry.
Thanks to KrYpToNiTe for this wonderful work as thanks as well to: jcase for root, Hashcode for safestrap and beups and fuses for MotoWpNoMo.
This isn't rooted 4.4.2, this is a Safestrap ROM. Unless I'm missing something here?
tekhna said:
This isn't rooted 4.4.2, this is a Safestrap ROM. Unless I'm missing something here?
Click to expand...
Click to collapse
Ok however you may want to call it, this method gives locked bootloader Verizon phones stock 4.4.2 Rooted with wp off. It is the same exact thing as if you had updated ota then ran the exploits...it just came out like 2 days ago, and it helps people that been wanting to upgrade from 4.4 without loosing the goodies. And no its not just a ROM its a guide because you must run several steps besides just flashing the ROM.
Pretty misleading thread title. This is just a 4.4.2 rooted Safestrap ROM, not a root method for current 4.4.2 users.
I was disappointed to learn this wasn't a root method and rather just a safestrap rom that I was already aware of. I would suggest changing the thread title or removing the thread altogether.
I guarantee all you guys with this negativity either have an unlocked bootloader or aren't even on Verizon, the title is as is because this is the only way so far to have 4.4.2 with root and WP off Stock OTA working and stable as of right now. If you had a locked VZW you would be happy no matter the title, all u guys that got it made are irrelevant to this thread and stay off... I will change the title upon XDA requesting it...Not everyone has DE motos like y'all..One thing though mine is customized with the colors I like and chose, from the body to the buttons and camera ring I even have a slogan on the back and Im on VZW unlimited everything with tethering! I use about 13 gigs of LTE a month..So beautiful...I'm not stuck with that ugly black front and white back with silver buttons..What is that??? Pshhh... It's alright though its not your fault blame Motorola.
PS you guys with those ugly Motos kill me with your reveal or clear cases...your back is WHITE! BRO...lol you don't got it like us Moto Maker fellas stop it!! No swag
flacco40 said:
I guarantee all you guys with this negativity either have an unlocked bootloader or aren't even on Verizon, the title is as is because this is the only way so far to have 4.4.2 with root and WP off Stock OTA working and stable as of right now. If you had a locked VZW you would be happy no matter the title, all u guys that got it made are irrelevant to this thread and stay off... I will change the title upon XDA requesting it...Not everyone has DE motos like y'all..One thing though mine is customized with the colors I like and chose, from the body to the buttons and camera ring I even have a slogan on the back and Im on VZW unlimited everything with tethering! I use about 13 gigs of LTE a month..So beautiful...I'm not stuck with that ugly black front and white back with silver buttons..What is that??? Pshhh... It's alright though its not your fault blame Motorola.
PS you guys with those ugly Motos kill me with your reveal or clear cases...your back is WHITE! BRO...lol you don't got it like us Moto Maker fellas stop it!! No swag
Click to expand...
Click to collapse
I'm actually a locked bootloader verizon variant. Still think this thread is dumb.
Not sure where the hostility is coming from. Thread title seems pretty straightforward to me. The RootzWiki thread flacco40 linked to allows those people on non-dev Moto Xs still running 4.2.2 or 4.4 to update to 4.4.2, without updating the bootloader, thereby retaining root and the ability to keep write protection disabled. I used it myself to allow my motomaker phone to run the newest 4.4.2 version of Eclipse ROM.
Not working on XT1058, because not flashing kernel:crying:
But Eclipse rom v3.1.2 working on XT1058
WHY???
cascade128 said:
Not working on XT1058, because not flashing kernel:crying:
But Eclipse rom v3.1.2 working on XT1058
WHY???
Click to expand...
Click to collapse
No offense but this is why I didn't post the ROM here because of questions like this, but I will explain it to you now that I have enough posts to reply!
First reason why it doesn't work for you is the thread title says VZW only that means XT1060 not XT1058. Second reason is Eclipse v3.1.2 is 4.4 base, not 4.4.2 like the thread title says, Eclipse v3.2+ is 4.4.2.
I will be making a version for the XT1058 once the sbf is released and a tester confirms it works.
kwyrt said:
Not sure where the hostility is coming from. Thread title seems pretty straightforward to me. The RootzWiki thread flacco40 linked to allows those people on non-dev Moto Xs still running 4.2.2 or 4.4 to update to 4.4.2, without updating the bootloader, thereby retaining root and the ability to keep write protection disabled. I used it myself to allow my motomaker phone to run the newest 4.4.2 version of Eclipse ROM.
Click to expand...
Click to collapse
I stand corrected, I originally titled it wrong which even that title was not saying that you can OTA to 4.4.2 then root, on the contrary I've always been saying that you should not take the ota, but I did word it incorrectly but fixed it. Although this thread is in RootzWiki no one bothered to post it on this website and I did trying to help and people started bashing me. Lol
The part that sucks is OP made a post on XDA with zero original content, referencing someone elses post on Rootzwiki who specifically asked it not be posted here. TLDR, OP is trying to gain credit for zero work. Thanks for making a thread linking to someone elses work and passing it off as your own, OP.
anotherfiz said:
The part that sucks is OP made a post on XDA with zero original content, referencing someone elses post on Rootzwiki who specifically asked it not be posted here. TLDR, OP is trying to gain credit for zero work. Thanks for making a thread linking to someone elses work and passing it off as your own, OP.
Click to expand...
Click to collapse
Nah man the OP did what I asked on rootzwiki and that was to link them to that thread. Makes it easier to manage problems that arise, and I didn't have enough post until today to post in this section.
@flacco40 you really should clean up the op to reference the latest and most accurate instructions. There is no need to RSD back to 4.2.2.
Sent from my Moto X
Are you bricked after the OTA? Here's how to unbrick it, locked or unlocked.
One other note: this is NOT an official 183 FXZ, so if this doesn't work, it won't make things worse, but you'll just have to wait for the "official" 183 FXZ.
Thanks go to stras1234 for providing a KK FXZ for those that needed it to unbrick their phone.
Another big thanks goes to SamuriHL for providing a tool to use the FXZ provided by stras1234 to make your job easier to unbrick your phone and get you running with KK.
Go here to get the FXZ and tool to help you profit in the glory that is Kit Kat on the XT926 Droid RAZR HD -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I have removed all my instructions as they are useless and no longer necessary with the FXZ being released.
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
hi @iBolski i just want you to know that i share your post on the kk tracking post!
cmchance said:
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
Click to expand...
Click to collapse
If you're already on stock 9.30, then it should work. I think the hang-ups for many who are manually loading it themselves via taking the OTA directly, were where if you were pushed the OTA and immediately accepted it and allowed it to go through and update it, it might have worked as long as you were unrooted on stock 9.30.
However, I chose to save the OTA off to the side (from the /cache directory) and hence, booted into the recovery manually, not realising that it installs a newer stock recovery and that's where I got hung up at. I thought the install failed, when in reality, I had to go back into the recovery and install it again. Of course, I tried using vol-down + vol-up and it wouldn't work.
If you currently have root though under 9.30, you might want to hold off until someone verifies if root can be obtained again. Because, without an unlocked boot loader, you will more than likely lose your access to root, especially if the latest "exploit" for 9.30 doesn't work under KK.
Your mileage may vary, but I don't have a locked bootloader phone to test this out on, so please, I do not accept any responsibility for what may happen if you try it, whether you have a locked or unlocked bootloader.
Thanks!
Just what I was needing to hear! I am currently rooted so I'll probably hold off. I've got a used Moto X on order though, should get it in today. After I test it out and verify that I can tolerate it and the smaller battery, then I might do some experimenting with the xt926 model I have and report back. Though, as anticipated as this update is, I'm sure someone will have already beat me to all the testing within a few hours from now lol
I'm on 9.30 with locked bootloader. I've tried your method but can't get pass signature verification. It just won't be installed on 9.30 firmware. There must be anything can be mess in updater script to avoid error signature.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Sabissimo said:
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Click to expand...
Click to collapse
I can't share the file, but if you look in the KitKat Tracking thread, you should find it there somewhere.
As an official soak tester, I'm not supposed to share the update. Technically, I'm not supposed to share ANY info, but I wanted to share this with other users who were having the same issue as I.
Thanks!
I do not believe the KK update for 9.30 has been shared anywhere.
No where that I can find. I've been scouring and following the forums waiting to find one myself.
sent from my ? and rooted XT1080 that thinks it's an XT1060
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
I'm not worried about it right now, Moto Verizon just posted saying they approved the soak test and updates would be rolling out.
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
http://www.droid-life.com/2014/05/1...id-razr-hd-and-razr-m-on-verizon/#more-139933
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
Sabissimo said:
There you go, found it:
https://drive . google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Sabissimo said:
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
I got it! I used this link 'below' to finally get it to update while using this thread for advice. Thank so much!
http://sbf.droid-developers.org/phone.php?device=5
Now to try saferoot...???
For all my 9.30.1 people, I love you guys too.http://pan.baidu.com/s/1eQimdea
Enjoy that official KK ota for 9.30.1 over that slow ass chinese server and stop trying to get the 9.18.94 to work.
bweN diorD said:
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Click to expand...
Click to collapse
I flashed to 9.30. When I received the OTA from the soak push, I saved the OTA off to the side and didn't apply it immediately. Then, when I attempted to apply it (after using House of Moto to fastboot it back to 9.30 stock), it rebooted after it started applying and then went back to the recovery screen, but at that point, they had changed how you get into it. It's now volume-up + power, not volume-down + volume-up.
In any case, that second step needs to happen where you go back and re-apply the OTA.
I'm thinking if I would have taken the OTA automatically right after it downloaded, it was probably automated. That, or maybe Motorola/Verizon decided to make it a game and see if people could figure it out? :silly:
Safe root for me was a no go. But kitkat is pretty nice!
Sent from my DROID RAZR HD using Tapatalk
Thanks for all the info. Got KK up and running
I used these instructions - http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1
and I used this file - http://forum.xda-developers.com/showpost.php?p=52610188&postcount=11
All last night I tried using the leaked file someone put up from that "slow ass Chinese server" haha. Long story short, it didn't work at all.
This morning I tried again, and nothing. So I tried this file (the one I linked up top) and it worked like a charm. I installed it via recovery, phone rebooted, used vol up + power to get into new KK recovery, applied leaked file again, and boom I got KK.
As someone in another thread said, during the update it does say "Phase 1 possibly complete". WTF is that all about?
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
huatz84 said:
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
Click to expand...
Click to collapse
Glad it's all working for you now. It definitely performs better than JB ever did.
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