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
Related
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
collins521 said:
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
Click to expand...
Click to collapse
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Jersey846 said:
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
jco23 said:
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
Click to expand...
Click to collapse
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
RikRong said:
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
Click to expand...
Click to collapse
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
jco23 said:
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
Click to expand...
Click to collapse
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
RikRong said:
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
Click to expand...
Click to collapse
100% agreed on the warnings - but I also understand why folks may have been skittish beforehand (took me 3 months of reading before I rooted my first device). given that this phone is now offered for free, I can see many new folks to this community, but they'll be SOL unless we are blessed with the help from a dev to unlock their bootloader.
that being said, the devs are not required to create a hack or make their ROMs SS-compatible, but I would not be surprised if locked bootloader phones soon begin to outnumber the locked one. i'm just thankful that they are here.
To be fair, the droid razr m that I'm working on has its bootloader locked because my girlfriend is skittish about me touching her phone. Women
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
AK47sForAll said:
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
Click to expand...
Click to collapse
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
collins521 said:
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
Click to expand...
Click to collapse
What do you consider reasonable? And have you tried eBay?
AK47sForAll said:
What do you consider reasonable? And have you tried eBay?
Click to expand...
Click to collapse
Ya I've been watching eBay and other sites for a good deal on a white one. Under $200 and in great shape is where I'm looking to get one. I'm in no real rush so I can wait for a deal to pop up
http://www.droidrzr.com/index.php/t...calm-v14-7172013-412-base/page-30#entry333531
That being said.
An activated DC is a path to this & you take your data with you.
http://forum.xda-developers.com/showthread.php?t=2246081
Edit Yet this is a backup made by the full twrp. Yet again they are supposed to be compatible....
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
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
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
hill180 said:
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
Click to expand...
Click to collapse
I believe you have. But first I need to ask you 1) were you rooted and 2) did you have a custom recovery (TWRP) on your phone before you ODIN'd NI2? If you had TWRP on your phone before ODIN can you get into TWRP recovery now? Just an FYI, Samsung does not send out, in any form (OTA or otherwise) updates to the Developer Edition phones. The explanation for why they don't is long and no one except for Samsung knows for sure and they are not commenting on the issue. Dev owners keep their phones up to date by flashing custom ROMs released by our Dev community for retail and dev edition phones.
hill180 said:
Did I relock the bootloader?
Click to expand...
Click to collapse
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Misterxtc said:
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Click to expand...
Click to collapse
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
jpcalhoun said:
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
Click to expand...
Click to collapse
That doesn't sound too promising. They really need to change their policy on that.
im not sure why you would have flashed a ne9 tar when instructions clearly say NOT to flash odin tars on a dev edition s5 because it will lock the bootloader
Sent from my SM-G900V using XDA Free mobile app
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
hill180 said:
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
Click to expand...
Click to collapse
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
jpcalhoun said:
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
Click to expand...
Click to collapse
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
hill180 said:
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
Click to expand...
Click to collapse
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
jpcalhoun said:
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
Click to expand...
Click to collapse
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
hill180 said:
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
Click to expand...
Click to collapse
That's a great question and one that I have been trying to figure how to do. I am not sure about this, but in order to backup a stock recovery you would have to use ADB and do a total backup of the phone that way. I have never tried that and I don't know for sure if it will even work using ADB. Here is how I look at it...who would want to pay $550 (or less) for a Developer Edition phone and never replace the stock recovery with a custom recovery? It doesn't make sense. In fact, the only way you can tell that a Developer Edition phone has not been inadvertently "locked" (not trying to stick a finger in your eye here) is to ask/see if a custom recovery is installed. If not, then there is no guarantee to the buyer that the bootloader is truly unlocked. SafeStrap does not count!
Hello,
My wife has RAZR M running stock and rooted 98.15.66 rom. Bootloader was never unlocked but I think it's still possible with this version of rom. am I right? Last time I was doing something with her phone was almost 2 years ago and I'm more samsung guy so need some directions here She loves this phone and doesn't want to get anything new. Phone is getting to run slower so it needs cleanup. Is it worth to upgrade it to KK rom or just do factory restore and set it up from scratch on this 4.1.2 rom? Any major bugs on stock KK rom? CM12 has too much bugs as of now for her. What about CM11, is there fully functional and bugs free version for RAZR M available?
.66 is indeed unlockable right away, but just so you could experience stock KitKat and see if it's more fitting, simply upgrade to 183.46.10 (ATTENTION: not .15!!!) and unlock the bootloader there. Guides are there in the General section. Note that you will lose data and internal storage contents, so back up properly.
After that if you feel uncomfortable with KitKat, you can freely downgrade to Jelly Bean whenever you prefer.
Haven't met any serious bugs even in CM12, let alone CM11. Don't know what kind of deal-breaking bug you're talking about.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
.66 is indeed unlockable right away, but just so you could experience stock KitKat and see if it's more fitting, simply upgrade to 183.46.10 (ATTENTION: not .15!!!) and unlock the bootloader there. Guides are there in the General section. Note that you will lose data and internal storage contents, so back up properly.
After that if you feel uncomfortable with KitKat, you can freely downgrade to Jelly Bean whenever you prefer.
Haven't met any serious bugs even in CM12, let alone CM11. Don't know what kind of deal-breaking bug you're talking about.
Click to expand...
Click to collapse
According to Strife89 post here: http://forum.xda-developers.com/showpost.php?p=58531079&postcount=80 there are couple of bugs that I know my wife is not gonna like for example microphone level and able hear own voice when using headphones.
Do you think it's better to unlock bootloader before upgrading to KK or it's doesn't matter? Thanks.
SotYPL said:
According to Strife89 post here: http://forum.xda-developers.com/showpost.php?p=58531079&postcount=80 there are couple of bugs that I know my wife is not gonna like for example microphone level and able hear own voice when using headphones.
Do you think it's better to unlock bootloader before upgrading to KK or it's doesn't matter? Thanks.
Click to expand...
Click to collapse
I would suggest that you unlock the bootloader now before you upgrade.
Sent from my Moto G™
Unlock unlock unlock. It worth the candle. I think your wife will be happy with cleaned up 4.1.2 or 4.4.2. Last one is more stylish, and comfortable in use, as for me.
OK is that correct order to get it upgraded?
1. Unlock boot loader using apk or Motopocalypse from this thread: http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
2. Flash KK firmware using RSD Lite but I'm not sure which image from this: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/ website is safe to use. Can I use latest one 20.62-15.1 after unlocking boot loader or do I have to stay stay with 20.62-10?
3. Flash TWRP from this thread: http://forum.xda-developers.com/showthread.php?t=2776515
4. FLash SuperSU from recovery
Is that correct way to handle it?