Related
Just received my Moto X AT&T shipped from Costco, system version is 139.9.51.ghost_ATT.en.US -so would appear I can root? (and then hopefully take the update without losing root? I recall seeing a thread, hopefully for the version I have)
Can the update be "pushed" onto the device without my accepting it, as to whether I would need to root (if I wanted to root) quickly to block it?
Thanks
M973 said:
Just received my Moto X AT&T shipped from Costco, system version is 139.9.51.ghost_ATT.en.US -so would appear I can root? (and then hopefully take the update without losing root? I recall seeing a thread, hopefully for the version I have)
Can the update be "pushed" onto the device without my accepting it, as to whether I would need to root (if I wanted to root) quickly to block it?
Thanks
Click to expand...
Click to collapse
no but you will get continual pop ups unless you the phone then disable motorola ota 1.0 and updater.apk (i think just updater.apk will suffice) with Titanium back up.
jayboyyyy said:
no but you will get continual pop ups unless you the phone then disable motorola ota 1.0 and updater.apk (i think just updater.apk will suffice) with Titanium back up.
Click to expand...
Click to collapse
Thanks, I thought that was the case, but wanted to confirm quickly (with some, SGS4, it's pushed to the phone whether you accept or not, unless you're rooted.)
Thanks for the quick reply
M973 said:
Thanks, I thought that was the case, but wanted to confirm quickly (with some, SGS4, it's pushed to the phone whether you accept or not, unless you're rooted.)
Thanks for the quick reply
Click to expand...
Click to collapse
not sure if it downloads it automatically or not (i don't think it does but it may). Even if it does download automatically it won't update it unless you click ok when it prompts you. I would root and disable OTiA until you figure out what you are going to do about it.
rooting
looks like it's either with PwnMyMoto, or Motoroot, appears the first is better? Looks like both are done with ADB which was a bit difficult, have only used it once, used it to remove safestrap from the SGS4 I had so I could return it
M973 said:
looks like it's either with PwnMyMoto, or Motoroot, appears the first is better? Looks like both are done with ADB which was a bit difficult, have only used it once, used it to remove safestrap from the SGS4 I had so I could return it
Click to expand...
Click to collapse
You can just install pwnmymoto on your device and run it. Make sure to have unknown sources checked
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also it is wise to get familiar with adb and fastboot!
shane1 said:
You can just install pwnmymoto on your device and run it. Make sure to have unknown sources checked
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also it is wise to get familiar with adb and fastboot!
Click to expand...
Click to collapse
Cool, thanks!
I got the Moto X a couple weeks ago for VZW. I'd like to root the Moto X, because..tether . Witht he 4.4.2 update around the corner, should I root now or wait? I don't on putting any custom ROMS on there, so I'd like the most updated Stock ROM. But I'm sure that's not rooted yet. Also, how hard is it to root the X? If it's that hard and easy to brick the phone, I may just hold off. Thanks guys.
As far as we know of, it's impossible to root the latest OTA. 4.4.2 changed bootloaders. It's going to require a whole new exploit... Which we might not have.
natezire71 said:
As far as we know of, it's impossible to root the latest OTA. 4.4.2 changed bootloaders. It's going to require a whole new exploit... Which we might not have.
Click to expand...
Click to collapse
eek
I didn't think it was that bad. Perhaps I should root now?
blueice5249 said:
eek
I didn't think it was that bad. Perhaps I should root now?
Click to expand...
Click to collapse
If you root 4.4, you can't accept the OTA, you'll brick it. If you're already on 4.4.2, you're out of luck for now.
natezire71 said:
If you root 4.4, you can't accept the OTA, you'll brick it. If you're already on 4.4.2, you're out of luck for now.
Click to expand...
Click to collapse
Thanks. Is this easy to brick in the root process?
natezire71 said:
If you root 4.4, you can't accept the OTA, you'll brick it. If you're already on 4.4.2, you're out of luck for now.
Click to expand...
Click to collapse
How do you block the OTA? I have a rooted VZ moto x with a locked bootloader.
mamba94 said:
How do you block the OTA? I have a rooted VZ moto x with a locked bootloader.
Click to expand...
Click to collapse
Freeze MotorolaOTA and delete the OTA from your /cache folder. To freeze MotorolaOTA, you need an app that can do it. I went ahead and paid the $6.50 for Titanium B/U Pro, which can freeze and is a well regarded app. There are probably free ones you can use.
---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------
blueice5249 said:
I got the Moto X a couple weeks ago for VZW. I'd like to root the Moto X, because..tether . Witht he 4.4.2 update around the corner, should I root now or wait? I don't on putting any custom ROMS on there, so I'd like the most updated Stock ROM. But I'm sure that's not rooted yet. Also, how hard is it to root the X? If it's that hard and easy to brick the phone, I may just hold off. Thanks guys.
Click to expand...
Click to collapse
Do you have a Dev Ed or did you get a Moto Maker/retail Moto X? Totally different processes depending on which you have.
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
blueice5249 said:
Thanks. Is this easy to brick in the root process?
Click to expand...
Click to collapse
Not if you have the Verizon Dev Ed.
Cozume said:
Freeze MotorolaOTA and delete the OTA from your /cache folder. To freeze MotorolaOTA, you need an app that can do it. I went ahead and paid the $6.50 for Titanium B/U Pro, which can freeze and is a well regarded app. There are probably free ones you can use.
---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------
Do you have a Dev Ed or did you get a Moto Maker/retail Moto X? Totally different processes depending on which you have.
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
Not if you have the Verizon Dev Ed.
Click to expand...
Click to collapse
I do not have the Dev Ed.
blueice5249 said:
I do not have the Dev Ed.
Click to expand...
Click to collapse
You have to use Slap My Moto then if you are on 4.4.
Slap My Moto
Cozume said:
You have to use Slap My Moto then if you are on 4.4.
Slap My Moto
Click to expand...
Click to collapse
Wow. That looks really involved and easy to screw up. Perhaps I may stay away for now.
Is there anyway to tether without root?
blueice5249 said:
Wow. That looks really involved and easy to screw up. Perhaps I may stay away for now.
Is there anyway to tether without root?
Click to expand...
Click to collapse
No there is no way to WiFi tether for free if you have unlimited data or a capped data plan without root. You can USB and Bluetooth tether using PDAnet if you run Kit Kat 4.4 and are unrooted. Or if you have a Verizon Share Everything plan you WiFi tether for free.
I am going to root a locked bootloader Moto X here soon and post Step-By-Step Instructions after I do. Don't take the 4.4.2 update if you want root.
Cozume said:
No there is no way to WiFi tether for free if you have unlimited data or a capped data plan without root. You can USB and Bluetooth tether using PDAnet if you run Kit Kat 4.4 and are unrooted. Or if you have a Verizon Share Everything plan you WiFi tether for free.
I am going to root a locked bootloader Moto X here soon and post Step-By-Step Instructions after I do. Don't take the 4.4.2 update if you want root.
Click to expand...
Click to collapse
Thanks, it doesn't need to be WiFi, I'm fine with USB tether.
Is there anything besides PDAnet? I heard you have to pay for that, or reconnect all the time.
I'm definitely going to hold off on the update and hope for a bit easier root method. I'm not too good at the adb thing.
blueice5249 said:
Is there anything besides PDAnet? I heard you have to pay for that, or reconnect all the time.
Click to expand...
Click to collapse
There probably is, but I use PDAnet and you are correct, you have to pay or reconnect all of the time.
blueice5249 said:
I'm definitely going to hold off on the update and hope for a bit easier root method. I'm not too good at the adb thing.
Click to expand...
Click to collapse
There won't be an easier method as jcase isn't going to do one for 4.4.2 and Motorola has with each new update tried to close the hacks that jcase has found.
You either root on 4.4 using Slap My Moto or stay unrooted. After you root on 4.4, you can keep the 4.4 bootloader and selectively upgrade the system to 4.4.2. But there are people on the Verizon 4.4.2 thread claiming they took the OTA and kept root and kept write protection disabled. Others on other carriers said otherwise.
Cozume said:
There probably is, but I use PDAnet and you are correct, you have to pay or reconnect all of the time.
There won't be an easier method as jcase isn't going to do one for 4.4.2 and Motorola has with each new update tried to close the hacks that jcase has found.
You either root on 4.4 using Slap My Moto or stay unrooted. After you root on 4.4, you can keep the 4.4 bootloader and selectively upgrade the system to 4.4.2. But there are people on the Verizon 4.4.2 thread claiming they took the OTA and kept root and kept write protection disabled. Others on other carriers said otherwise.
Click to expand...
Click to collapse
Darn and Darn.
I think I'll hold off for now and maybe hope your step by step is easier to follow. Thanks for the help man! :good:
If anyone else knows of a free tether method let me know.
Cozume said:
Freeze MotorolaOTA and delete the OTA from your /cache folder. To freeze MotorolaOTA, you need an app that can do it. I went ahead and paid the $6.50 for Titanium B/U Pro, which can freeze and is a well regarded app. There are probably free ones you can use.
Click to expand...
Click to collapse
Thanks!
I was just Google searching hoping for some good news... And came across this posted yesterday...
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
... Any truth to that? And is it for any carrier, i.e att?
Sent from my XT1058 using Tapatalk
Links to a thread on here.
Yea I saw that, but they are not the same...
Sent from my XT1058 using Tapatalk
They want you to dl this http://www.cydiaimpactor.com/
Anyone know what it is?
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
jbaumert said:
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
Click to expand...
Click to collapse
There's other threads where this stuff gets talked about, but im pretty sure for things like that it would probably work. But any actual changes to anything would get reversed.
I've always been unlocked....so I don't have firsthand experience though.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
KidJoe said:
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
Click to expand...
Click to collapse
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
Please see my response to you in the 4.2.2 to 4.4.2 thread.
kj2112 said:
Please see my response to you in the 4.2.2 to 4.4.2 thread.
Click to expand...
Click to collapse
Thanks, didn't realize until afterward it was the same voice in both threads.
Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Jumnhy said:
Thanks, didn't realize until afterward it was the same voice in both threads.
Click to expand...
Click to collapse
Where you found another same threads ?
DANIEL AMBRUSO said:
Where you found another same threads ?
Click to expand...
Click to collapse
It was just kj2112 explaining a similar issue to me. Check it out, but essentially my understanding is that there's no root for 4.4.2 if the phone never had root previously (ie, if you naively took the OTA like me without thnking about implications for root.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
KidJoe said:
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Click to expand...
Click to collapse
Solid, thanks for the concise summary. I'd read jcase's posts a while back about a potential exploit--something about using it in a teaching session at BlackHat? He even says though, that the exploit he has will probably never be useful for the average user insofar as it would be too hard to implement and n00bz like myself would end up bricking our phones. So I'm not holding my breath on that one. Ugh. Sad I missed the window for the Chinese connection. Should have jumped on it.
The Tallest said:
Links to a thread on here.
Click to expand...
Click to collapse
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
glarepate said:
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
Click to expand...
Click to collapse
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
KidJoe said:
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
Click to expand...
Click to collapse
Yes, if you have already gone to 4.4.2 you are out of luck.
I'm using the T-Mobile SafeStrap Recovery with my RW Moto X. This was done by a Franken-ROM process that uses the 4.4.2 ROM without using the 4.4.2 bootloader and using the SS recovery to flash a zip file with some components of the 4.4.2 ROM and then flashing SuperSU. Whether or not it should be working, it is. Nothing I can, or want to, do about that.
But I am sure you are right that this resultant ROM would not work on phones from other carriers. Versions for other carriers are being developed though. It may simply be a matter of time and interest by motivated individuals until this is available for just about everyone.
hey guys, i'm currently on 4.2.2 with root (SuperSU + boot to recovery disables write protection). after rooting it, i stopped keeping up with everything, so i never did any of the updates. however, i'm at a point now where i wish to update to the latest, and i'm hoping someone can help me with the steps i need to take to do that. i think i need to unroot and then update, but not sure how. thanks.
Here's a thread to help start you out. A little looking around and you'll find tonnes more about this. An extremely posted about topic.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
hmm OK is there a way to un-root without losing everything?
Q&A for MoFo IMG AT&T XT1097 (root, tether, xposed)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for MoFo IMG AT&T XT1097 (root, tether, xposed). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My /data directory is empty. Can I assume I don't need to follow the steps to delete the two folders?
busybox
Any chance on getting busybox baked in as well?
AlwaysHere said:
Any chance on getting busybox baked in as well?
Click to expand...
Click to collapse
Do you know anyone with an XT1095? If so it is really easy to do and they can make a nandroid of their system and just restore it when they are done.
JulesJam said:
Do you know anyone with an XT1095? If so it is really easy to do and they can make a nandroid of their system and just restore it when they are done.
Click to expand...
Click to collapse
Sadly I don't know anyone around that has one. Looks like I'll have to wait until it's released somewhere on here. Thanks JulesJam.
Newbie questions
I've received my Moto X yesterday (bought a used one on Amazon). Unfortunately I haven't ask the seller which exact model of MotoX it was and it turned out that it is AT&T one and bootloader can't be unlocked.
Tried to go through all topics connected to MotoX but still have a couple of questions. If this this is wrong topic please tell my where to post.
1. Using MoFO, should I be able to install debloated firmwares (without AT&T bloatware) on my phone? I don't need root but I wan't pure stock Android without carrier-specific apps.
2. If I use MoFo and don't like it, can I go back to official stock and receive OTA updates?
3. Do we have any hope that someday (say, in one year) someone (like Sunshine) finds a way to unlock bootloader? Is that hardware-impossible or just such an exploit wasn't found yet?
4. Assuming that such exploit probably will need KitKat, will I be able to downgrade to 4.4.4 later if I update 5.0.2 OTA now?
qyron said:
1. Using MoFO, should I be able to install debloated firmwares (without AT&T bloatware) on my phone? I don't need root but I wan't pure stock Android without carrier-specific apps.
Click to expand...
Click to collapse
Yes but to make it you have to either use another device with an unlocked bootloader like a Nexus 9 or a Moto X 2013, or if you know someone with an XT1095 they can make it for you. Or if you know linux you can make it.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
qyron said:
I've received my Moto X yesterday (bought a used one on Amazon). Unfortunately I haven't ask the seller which exact model of MotoX it was and it turned out that it is AT&T one and bootloader can't be unlocked.
Click to expand...
Click to collapse
Can you return and buy an XT1095 instead? That is what I would do.
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
qyron said:
2. If I use MoFo and don't like it, can I go back to official stock and receive OTA updates?
Click to expand...
Click to collapse
Yes read my noob guide in the General forum (it is linked to in the OP of the MoFo thread).
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
qyron said:
3. Do we have any hope that someday (say, in one year) someone (like Sunshine) finds a way to unlock bootloader? Is that hardware-impossible or just such an exploit wasn't found yet?
Click to expand...
Click to collapse
I don't have any hope. No one is working on it. jcase and beaups aren't interested in motorola phones anymore and they were the only ones pretty much working on it who have the skillz needed to do it.
And maiko1 hasn't been responding to questions about MoFo via the forum or by email. He hasn't been on XDA since 5/27/15 so I don't know what is going on. It is like he abandoned MoFo. Maybe he is sick or in the hospital and can't respond, idk, but he hasn't been responding to anyone in awhile. When 5.1 drops, the copy of MoFo you have now won't work on it. He would need to update the MoFo site and I worry that he isn't interested anymore.
If you have the ability to return the XT1097 and get an XT1095, that is what I would do.
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
qyron said:
4. Assuming that such exploit probably will need KitKat, will I be able to downgrade to 4.4.4 later if I update 5.0.2 OTA now?
Click to expand...
Click to collapse
There is no reason to think that the exploit will be found on KK. jcase and beaups looked for one and didn't find one and gave up.
And no, you will never be able to downgrade your bootloader to 4.4.4 once you upgrade to 5.0.2.
JulesJam said:
Yes but to make it you have to either use another device with an unlocked bootloader like a Nexus 9 or a Moto X 2013, or if you know someone with an XT1095 they can make it for you. Or if you know linux you can make it.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
Can you return and buy an XT1095 instead? That is what I would do.
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
Yes read my noob guide in the General forum (it is linked to in the OP of the MoFo thread).
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
I don't have any hope. No one is working on it. jcase and beaups aren't interested in motorola phones anymore and they were the only ones pretty much working on it who have the skillz needed to do it.
And maiko1 hasn't been responding to questions about MoFo via the forum or by email. He hasn't been on XDA since 5/27/15 so I don't know what is going on. It is like he abandoned MoFo. Maybe he is sick or in the hospital and can't respond, idk, but he hasn't been responding to anyone in awhile. When 5.1 drops, the copy of MoFo you have now won't work on it. He would need to update the MoFo site and I worry that he isn't interested anymore.
If you have the ability to return the XT1097 and get an XT1095, that is what I would do.
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
There is no reason to think that the exploit will be found on KK. jcase and beaups looked for one and didn't find one and gave up.
And no, you will never be able to downgrade your bootloader to 4.4.4 once you upgrade to 5.0.2.
Click to expand...
Click to collapse
You say we can make images using linux, can you make a guide or at least explain quickly how this is done? I'm moderately proficient in linux and I'm thinking about being the guinea pig who tries to make a rom for the XT1097.
darknessrise1234 said:
You say we can make images using linux, can you make a guide or at least explain quickly how this is done? I'm moderately proficient in linux and I'm thinking about being the guinea pig who tries to make a rom for the XT1097.
Click to expand...
Click to collapse
If you're moderately proficient I won't go into too much detail, you basically just use the mount command to mount the ext4 image then modify then unmount then flash.
G4 Man2 said:
If you're moderately proficient I won't go into too much detail, you basically just use the mount command to mount the ext4 image then modify then unmount then flash.
Click to expand...
Click to collapse
So I'm right it has to be an installed image, not a fxz? I have a 5.1 fxz and I was looking to attempt a 5.1 image for our 1097.
Does gravitybox work with on this image?
Sent from my XT1097 using XDA Premium 4 mobile app
QA Bot said:
Q&A for MoFo IMG AT&T XT1097 (root, tether, xposed)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its !
Click to expand...
Click to collapse
JulesJam said:
Do you know anyone with an XT1095? If so it is really easy to do and they can make a nandroid of their system and just restore it when they are done.
Click to expand...
Click to collapse
For some reason the xposed doesn't work for me.
See screenshot from attachment
I got a ATT xt1097
My flash procedure:
1. enter recovery and wipe data/cache
2. flash stock image with just root
3. wipe cache(If I don't do this there will be a bootloop)
4. enter system, turn on Unknown Sources (read from another website), Install Xposed Installer (tried both 2.7 experimental1 and 2.6.1), delete everything in dalvik-cache
5. fastboot flash your mod
6. wipe cache
7. enter system, there is a long updating app process.
8. open Xposed installer and it doesn;t work
lihanchen said:
For some reason the xposed doesn't work for me.
See screenshot from attachment
I got a ATT xt1097
My flash procedure:
1. enter recovery and wipe data/cache
2. flash stock image with just root
3. wipe cache(If I don't do this there will be a bootloop)
4. enter system, turn on Unknown Sources (read from another website), Install Xposed Installer (tried both 2.7 experimental1 and 2.6.1), delete everything in dalvik-cache
5. fastboot flash your mod
6. wipe cache
7. enter system, there is a long updating app process.
8. open Xposed installer and it doesn;t work
Click to expand...
Click to collapse
Are you using mofo?
JulesJam said:
Are you using mofo?
Click to expand...
Click to collapse
Yes. otherwise I can't flash. AT&T sucks
---------- Post added at 01:20 AM ---------- Previous post was at 01:01 AM ----------
JulesJam said:
Are you using mofo?
Click to expand...
Click to collapse
And one thing I notice is that every time there is a 10-second starting app process before loading the launcher after the Moto Earth animation. Similar dialog as updating apps
lihanchen said:
Yes. otherwise I can't flash. AT&T sucks
And one thing I notice is that every time there is a 10-second starting app process before loading the launcher after the Moto Earth animation. Similar dialog as updating apps
Click to expand...
Click to collapse
You need to follow the instructions in the OP exactly as written, by what you posted you aren't doing that. There is no need for instance to enable Unknown Sources.
JulesJam said:
You need to follow the instructions in the OP exactly as written, by what you posted you aren't doing that. There is no need for instance to enable Unknown Sources.
Click to expand...
Click to collapse
I tried turning on/ not turning on unknown sources
Also use ES file explorer/ adb shell to delete dalvik cache
Also wipe cache/ not wipe cache after flashing the mod.zip (second zip)
Can't get it working anyway
JulesJam said:
You need to follow the instructions in the OP exactly as written, by what you posted you aren't doing that. There is no need for instance to enable Unknown Sources.
Click to expand...
Click to collapse
Let's discuss in this post. I accidentally sent a post on the original thread instead of Q&A and can't delete it.
I googled "xposed installer" and clicked the first link, tried both 2.7 experimental 1 and 2.6.1, installed with adb
Also, for last step, I installed "APM+" module and it didn't work.
lihanchen said:
Let's discuss in this post. I accidentally sent a post on the original thread instead of Q&A and can't delete it.
I googled "xposed installer" and clicked the first link, tried both 2.7 experimental 1 and 2.6.1, installed with adb.
Click to expand...
Click to collapse
But what version of the Xposed installer was used when the dev made the image? That may be the issue as the installer has been updated but I am not sure if the image was. Idk the anwer - the dev would know.
JulesJam said:
But what version of the Xposed installer was used when the dev made the image? That may be the issue as the installer has been updated but I am not sure if the image was. Idk the anwer - the dev would know.
Click to expand...
Click to collapse
From the release date, I believe 2.6.1 is the correct one.
Plus, in another post about mofo image of motoX gen1 of the same author, he mentioned explicitly of xposed installer 2.6.1
lihanchen said:
From the release date, I believe 2.6.1 is the correct one.
Plus, in another post about mofo image of motoXat gen1 of the same author, he mentioned explicitly of xposed installer 2.6.1
Click to expand...
Click to collapse
Well if you are using the correct version of the installer and following the instructions in the OP for the image as written it should work. I would flash back to stock system and start again from scratch if it isn't working for you making sure you are following the instructions.