Database Develop

[Q]Signature Bugs Unavailable

soo i was trying to root my brazilian version of moto x with SlapMyMoto, already updated to 4.4 thanks to some tutorials out there, and when i was trying to star a telnet session with cydia impactator and it just said that there was no signature bugs available any help?

Heres a screenshot of Bluebox, confirming that i do have the "bugs" available

Savassi12 said:
soo i was trying to root my brazilian version of moto x with SlapMyMoto, already updated to 4.4 thanks to some tutorials out there, and when i was trying to star a telnet session with cydia impactator and it just said that there was no signature bugs available any help?
Click to expand...
Click to collapse
This is the error you get when trying to run telnet session while on 4.4. You need to be on 4.2.2 in order to begin SlapMyMoto root process. This is the error message I got when I was trying to root on 4.4 so you need to look into downgrading to 4.2.2 first. Check my post history to see information on downgrading (Where to get 4.2.2 if the link in the SMM thread is still down, tutorial on downgrading to 4.2.2 using RSD Lite and the firmware) You will bootloop if you try to downgrade to 4.2.2 without adding a line to erase userdata, that's also in my post history. Hope this helped, sorry working right now or I'd grab the links. (Apparently you can backup and restore userdata according to this post though http://forum.xda-developers.com/showthread.php?t=2569229 )

Halo
I've done the downgrade to 4.2.2
but when trying to telnet can not because there is a message
"link failed file exist"
what should I do next????

waydhee said:
Halo
I've done the downgrade to 4.2.2
but when trying to telnet can not because there is a message
"link failed file exist"
what should I do next????
Click to expand...
Click to collapse
Unlock your lockscreen then try again

VZW Moto X DE Phone Update?

After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?

There's a bunch of ota threads my friend. Read up. Some are stickies...like the complete Moto x guide thread.
Sent from my Moto X cellular telephone...

SwiftLeeO said:
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
Click to expand...
Click to collapse
If you downloaded the update it's in the cache folder.

Ryno77 said:
If you downloaded the update it's in the cache folder.
Click to expand...
Click to collapse
Well, it just says install. I don't want to install it because I'm rooted with custom recovery and it might brick my phone. I checked the cache folder and there are 3 folders: backup, lost+found, and recovery

SwiftLeeO said:
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
Click to expand...
Click to collapse
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted but you already know that.
What root explorer/browser are you using?

Cozume said:
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted.
What root explorer/browser are you using?
Click to expand...
Click to collapse
Root Browser by JRummy. I normally use ES, but i stopped after it wouldnt let me edit permissions.

Its just a glitch. In your cache it'd have its own folder named after the current os. Wipe cache and dalvic and you should be free of the glitch.

SwiftLeeO said:
Root Browser by JRummy. I normally use ES, but i stopped after it wouldnt let me edit permissions.
Click to expand...
Click to collapse
that is what I am using and I see the exact same subfolders you are seeing in the cache. I take it you don't see the OTA file in any of the subfolders?

Cozume said:
that is what I am using and I see the exact same subfolders you are seeing in the cache. I take it you don't see the OTA file in any of the subfolders?
Click to expand...
Click to collapse
No ota file. Might be a glitch as shane suggested.
False alarm. Went into Software Update to check and I'm up-to-date .-.

Cozume said:
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted but you already know that.
What root explorer/browser are you using?
Click to expand...
Click to collapse
If you are rooted and want to take the OTA, you can flash the stock recovery and the system.img file with mfastboot.exe, and the OTA should install. i.e. if you are on 4.2.2, rooted with a custom recovery, then you should download the factory 4.2.2 image FOR YOUR DEVICE. Then extract it and use mfastboot to flash recovery.img and system. img. When you reboot, the phone will download the 4.4 OTA and it should install no problem. After it installs, just use mfastboot to flash TWRP and let TWRP root your device and you should be good as new with 4.4.
The stock recovery and an unaltered system folder are the key ingredients to a successful upgrade.

Mr. Orange 645 said:
You can absolutely take an OTA while rooted. The only thing that would prevent you from taking an OTA is if you have altered any system files (such as deleting system apps), or if you have messed and around and flashed a bootloader that doesn't match.
If you flash the factory recovery, you can take the OTA no problem even if rooted. You will of course lose root, but that's easily solved with an unlocked bootloader.
Click to expand...
Click to collapse
Ok, this is the kind of stuff that makes it so hard on noobs. On the thread about the OTA it says you have to get rid of root:
[NOOBS][WARNING][OTA]how to accept an ota
I know if the Moto X were a Nexus you could take the OTA while rooted but would lose root. But with the Moto X, it seems like you can't do that.

Cozume said:
Ok, this is the kind of stuff that makes it so hard on noobs. On the thread about the OTA it says you have to get rid of root:
[NOOBS][WARNING][OTA]how to accept an ota
I know if the Moto X were a Nexus you could take the OTA while rooted but would lose root. But with the Moto X, it seems like you can't do that.
Click to expand...
Click to collapse
Ok, so I just downgraded to 4.2.2, rooted, and tried to take the OTA and it failed. So, I stand corrected. You are right, you can not take the OTA if you are rooted. Well, you CAN take it, but it will fail to install. It sees the su app as an alteration to the system folder (which it is).
Easiest fix is to to use mfastboot to flash the stock recovery and flash the system.img file so it is back to stock. Reboot then let the OTA install and you should be good to go.
Sorry for the misinformation, and I will correct my earlier post so as not to confuse the "noobs." LOL.
Thank you, Cozume

OK ,its simple. 1 moto is no nexus device
2 where does the su binary flash to?xbin folder, is that not part of the system? The only reason why some folks on T-Mobile have root afterwards is, the 4.4.2 is a partial update for them as they received 4.4 , it only replaces some files,If you have a carrier such as Rogers that's going from 4.2.2 directly to 4.4.2 then all the system folders are replaced and you need to remove root along with the binary file, there are other carriers as well that are going from 4.2.2 to 4.4.2 directly
Sent on my Gummy running Lenoto X

flashallthetime said:
OK ,its simple. 1 moto is no nexus device
2 where does the su binary flash to?xbin folder, is that not part of the system? The only reason why some folks on T-Mobile have root afterwards is, the 4.4.2 is a partial update for them as they received 4.4 , it only replaces some files,If you have a carrier such as Rogers that's going from 4.2.2 directly to 4.4.2 then all the system folders are replaced and you need to remove root along with the binary file, there are other carriers as well that are going from 4.2.2 to 4.4.2 directly
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yup, sorry for the misinformation. I was mistaken and corrected it. Likely while you were typing up your response.

[Q] Black screen after trying to root, did i hard bricked my moto x?

Hey guys,
So i was interested in installing a custom rom im my moto x and started by trying to root it.
Every thing was going fine, but after i placed the unlock code via CMD, i've got an error during the root process and my phone just died. Now all that i've got is a black screen, no matter if I try to hard reset or anything.
Any idea?
tl;dr my phone just died in the root process, wtf can i do?

Unlock code? Root process?
Which model do you have? Which version of Android was it on? What exactly were you doing or using to root or unlock?

Which model you have used ?

I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.

You will need to be far more specific in what commands you did, if any...and the specific errors.
Only way we'll know what's happened.

It may be of some help if you post the tutorial you followed and say exactly at what step things went wrong.
Sent from my Moto X using Tapatalk Pro

monzillo said:
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
Click to expand...
Click to collapse
The XT1058 has a locked bootloader, so I hope that tutorial didn't have you try to downgrade your ROM in order to use SlapMyMoto/MotoWpNoMo to root and disable write protection.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone anymore. Additionally, 4.4.2 closed the exploits used by SlapMyMoto/RockMyMoto to gain root, and the exploit used by MotoWpNoMo to disable write protection.
As others have suggested, post a link to the turtorial, and any error messages you saw while running the scripts.
Also, try booting into bootloader/fastboot mode. Can you get there? What version bootloader does it say you are on? I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. If you have 30.B4, then your only fix might be using RSDLite to flash the 4.4.2 SBF for your carrier, or mFastboot to individually flash all parts of 4.4.2 on your phone, and then forget about rooting unless Moto's web site gives out the bootloader unlock code for your phone.

4.2.2 to 4.4 Root Nightmare

So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!

HTC-OH_SNAP said:
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
Click to expand...
Click to collapse
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.

kj2112 said:
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
Click to expand...
Click to collapse
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.

HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.

kj2112 said:
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
Click to expand...
Click to collapse
The Safestrap process, and installing a proper safestrap rom does not update the phone's bootloader. I think it also doesn't touch the GPT.BIN.
I know you haven't had experience with Safestrap, so think of it as kind of a Host OS/Guest OS setup, or if it was a PC then kind of like a Virtual PC setup where you could have a PC running real Windows 7 on your C drive that you boot too, plus having Windows 8 in a virtual PC and the Virtual PC's image file being stored on your "D drive". Installing W8 in the virutal PC doesn't touch the W7 "host" os, or its boot partition, etc. (its not 100% exactly the same, but that is the best analogy I can come up with at the moment).
---------- Post added at 06:35 AM ---------- Previous post was at 06:02 AM ----------
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
re: safestrap affecting the bootloader, no, it does not. At least if you are using a ROM made for safestrap, and properly follow the process.
To determine the bootloader version, boot the phone to bootloader mode it should show the version number. I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. As @kj2112 has mentioned, If the bootloader has been updated to 4.4.2, do NOT attempt to downgrade. However when using safestrap properly, its different.
As for the error at step 3... apparently it is common for those who had once used MotoWpNoMo to disable write protection, then trying to run though the SlapMyMoto process.
The actual process for getting a working Safestrap setup is the same for all Moto X's, however the Safestrap roms, and possibly the installer, are model specific... So, for example, if you have a Verizon X with locked bootloader, you could still follow [GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo but using the Verizon specific SBFs, SafeStrap and Safestrap Roms instead of the ones for T-Mobile and RW linked in that thread (like on steps 1b, 3a, 5a, 6b).
Because of that, I'll point you to -> http://forum.xda-developers.com/showpost.php?p=52401229&postcount=30 as it is the quickest link I can find to a work around for slapmymoto if you've already disabled write protection with MotoWpNoMo.
I'm sure if you took the time to read every post in the SlapMyMoto thread or the entire MotoWpNoMo thread you will likely find discussions about your situation and a fix. For example: Post 349 through 357 of the MotoWpNoMo thread is a user having the same issue, but later says it was due to the SlapMyMoto file being the older 0.5c version rather than 1.0.
I'm sorry, I'm just not good with RockMyMoto/SlapMyMoto/MotoWpNoMo/etc and Safestrap as I have an unlocked bootloader, so I never had to mess with them to root and disable write protection.

how do i spf back to 4.2.2?

coolguy71261 said:
how do i spf back to 4.2.2?
Click to expand...
Click to collapse
This is someone's thread with their particular issue. If we start helping you in this thread with your issue....that is called thread hijacking.
You need to ask in a thread relevant to your issue, or start a new thread.
However.....since we don't know anything about your situation or your issue.....advice is hard to give.
You can probably start here tho.... http://forum.xda-developers.com/showthread.php?t=2603358
If that doesn't help, you need to make your own thread. And be as specific as possible with the details. But only start a thread if searching comes up with nothing and no existing threads match your issue.
Just some XDA etiquette.
Good luck.
And sorry to OP for off topic.

If you rooted with rockmymoto and took write protection off. You'll still have it so the only process you'll need to do is slapmymoto on 4.4. Safestrap will work with 4.2.2 and 4.4. If you want root stay there don't go to 4.4.2
MOTO X

KidJoe said:
Great Advice
Click to expand...
Click to collapse
Ok... so here is how the whole thing ended.
Checked my Bootloader - it was still 30.71.
Verified I still had Write Protection off.
Ran SlapMyMoto 1.0.
Took the OTA (From 4.2.2 it is still 4.4 and NOT 4.4.2)
Ran the ADB Shell Commands.
Installed SuperSu from the Play Market, and...
Rooted 4.4 with Write Protection Off.
Thanks!

[Q] Android L with custom recovery.

So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance

You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.

PedroAlba said:
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
Click to expand...
Click to collapse
This is asked every time an new OTA comes out, and we get many threads started covering it.
To date...
For the Motorola X 2013, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
None of the OTA's will install if you have TWRP recovery on your phone. Instead you get stuck in a bootloop. (mfastboot erase cache will get you out of the bootloop). You need to have stock recovery on your phone. NOTE: I don't recall what happens when using Philz or CWM as recovery.
Each OTA so far has included a "Pre-Install Verification Check", a manifest of files and their checksum/hashes which the update compares against your phone. If expected files are missing, or the wrong hash, the OTA will fail to install. - So any removed or modified "bloat", system files, etc. need to be in place. Any apps like Xposed which change /system need to be disabled/removed. In some cases Freezing apps using Titanium Backup cause the OTA to fail, and the apps need to be unfrozen. However, some have not had to unfreeze. Using the phone's app manager to disable an app (Settings -> Apps -> open app listing -> DISABLE) does not have to be undone.
If you have version mismatch between GPT.BIN or Motoboot.img and the ROM on your phone, taking an OTA WILL brick the phone. - Grab the FULL SBF for the Stock Moto ROM which matches the bootloader version on your phone, or a newer SBF (i.e. if you have the bootloader version that corresponds to 4.4.2, grab the 4.4.2 SBF or 4.4.4 SBF), and flash it via mfastboot. You may need some extra steps to flash GPT.BIN and Motoboot.img.
If you've used hacks to root/disable write protection because you have a locked bootloader, you may lose root, and wont be able to re-root until a new exploit is found. Those hacks might also get in the way of the OTA's pre-install validation checks.
If you have unlocked your bootloader via mfastboot oem unlock UNIQUECODE or Sunshine, the bootloader will not re-lock.
There have been some posts (twitter and G+) about how Lollipop poses new security features which are a challenge to rooting, even with an unlocked bootloader. Since I don't know the technical ins and outs, all I can say is.. Even with an unlocked bootloader, I wont jump on Lollipop as soon as its available, until I know if I can still root my X.
(I have a little bit more detail posted here -> http://mark.cdmaforums.com/MotoX-OTA.html)

lowvolt1 said:
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
Click to expand...
Click to collapse
For what it's worth, you don't need to uninstall the modules. Just use the Xposed Disabler zip in your SD card, then install the framework again once you've flashed /system and taken the update.
When I did updated to 4.4.4 I disabled the modules in the Xposed UI (not sure if that was necessary or not), but did not actually uninstall any of the APKs for the modules. When I reinstalled Xposed after updating, all I just turned all my modules back on and rebooted.

Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.

mtpease said:
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
Click to expand...
Click to collapse
Not really a bad practice either way, if you clear stuff out now and again. If you try to take an OTA with a modified /system partition, it usually just fails during the hash checks and never installs/modifies anything.

You started your thread title with a [q].... Perhaps the Q&A section would be the section to ask your question? ?