Related
Hello
I've just don't an OTA upgrade to Android 4.3 to my new Sprint HTC One.
After the OTA I rooted the device and installed recovery.
After I restarted the phone and launch the SuperSU I got this message :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3 you need to manually re-root."
I would like to ask what should I do to make the root process sucseful .
I'm a newbe in the Android world and use some root manual I found.
1. What does it mean to re-root?
2. Should I unroot first ? And how it can be done?
3. Is there an 4.3 root manual somewhere to the make the SuperSU work?
Any instructions will be great help.
Thanks
Did you ever figure out how to get root? I am currently experiencing same issue.
Same issue
Same exact problem! Bump.
Any suggestions?
Please don't take OTAs after you've rooted your phone, because almost always it will wipe your root. Here is how I do my rooting.
Step 1: Go to htcdev.com and get your bootloader unlocked (this process will reset your phone back to factory setting, so back up all your pics, music, etc)
Step 2: Right after bootloader is unlocked, install a custom recovery (I prefer TWRP 2.6.3.0 for Sprint HTC One 4.3)
Step 3: As part of TWRP installation, SuperUser will be installed (root)
Step 4: Make a nandroid backup of your phone in TWRP. After that, install a custom ROM of your liking (there are plenty wonderful ones in Development section). This will keep your phone from taking OTA updates from Sprint/HTC. Don't worry, Devs on these forums (and their respective ROMs) are months ahead of Sprint in terms of updates.
For more details, head over to Development section and look for rooting instructions. there are very detailed tutorials there. Hope this helps.
having the same problem! im getting "There is no SU binary installed, and SuperSU cannot install it." from super su! I DO NOT WANT A CUSTOM ROM! i want stock rom but i want to have root. please help! the theres so many devs here im sure someone is kind enough to help
`Ghost` said:
having the same problem! im getting "There is no SU binary installed, and SuperSU cannot install it." from super su! I DO NOT WANT A CUSTOM ROM! i want stock rom but i want to have root. please help! the theres so many devs here im sure someone is kind enough to help
Click to expand...
Click to collapse
If all you want is pure stock with root -- just flash one of the already rooted stock ROMs in your custom recovery (assuming you loaded TRWP or PhilZ or CWM):
http://forum.xda-developers.com/showpost.php?p=48653344&postcount=2
If you want (more or less) stock with a *significantly* better experience (e.g., 30 volume steps, extreme stability, bla bla bla), I'd suggest InsertCoin (the thread is here whereas the download for our phone is here.
For either pick, since your coming in fresh to the ROM, do a full wipe (InsertCoin will do that for you as an option to the install, but I usually do that in recovery anyway).
Also -- note that InsertCoin *might* start the install and seemingly hang. That's a bug in Aroma, just hard restart the phone and try again -- letting the installer perform the wipe. It will work, and you'll be happy -- I'm sure.
---------- Post added at 05:03 PM ---------- Previous post was at 04:22 PM ----------
james341 said:
Hello
I've just don't an OTA upgrade to Android 4.3 to my new Sprint HTC One.
After the OTA I rooted the device and installed recovery.
After I restarted the phone and launch the SuperSU I got this message :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3 you need to manually re-root."
I would like to ask what should I do to make the root process sucseful .
I'm a newbe in the Android world and use some root manual I found.
1. What does it mean to re-root?
2. Should I unroot first ? And how it can be done?
3. Is there an 4.3 root manual somewhere to the make the SuperSU work?
Any instructions will be great help.
Thanks
Click to expand...
Click to collapse
See my previous post (you can just load a rooted stock ROM). But "re-root" is something you do by either flashing the SuperSU.zip file, or letting your recovery take care of re-rooting.
No need to unroot.
My take? Backup your current ROM (stock, unrooted) and then flash one of those I mentioned.
This might be of some help, or at least clarify the issue you are having.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
fyi i realized i was flashing with an older version of supersu. V1.25 to be exact. I slapped supersu v1.86 on my phone and then installed that through TWRP. Root was successful.
Reason for rooting was I wanted to install titanium backup and freeze sprint id and other bloatware apps. I also wanted to eliminate GPU throttling which i did, and I set up the scrips to stop CPU and GPU throttling while im playing games, and then click the other button to shut off the script. Im happy with its performance. Shadowgun and modern combat 4 run much more smooth since doing that.
as for a custom rom im not sure im that brave yet... i thought all the big hubbub was cyanogen. has that mod lost its step? ill look in to the one you suggested, thanks.
after looking at insertcoin im going to have to pass. Ive read that kitkat completely breaks the phone for gaming and performance becomes horribad
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the green square before the thread title. I know it's long but you really should read through the whole thread to get a feel for what people have been doing wrong, etc. For example, you NEED to flash it with Moto's fastboot.exe (often called mfastboot but it's not actually called that when you download it from Moto).
The guide you are referring to seems fine, except the mfastboot command assumes you changed the name of the Moto fastboot executable to mfastboot...
I don't mean to be one of those trolls around here but if the guide seems too complicated, I would encourage you to wait for Moto to release the SBF files for 4.4.2 before rooting. I say this because, without those files, things could get tricky of you're not an expert (I'm not) and you do something wrong. When those files come out, you can follow the simple guide on the Moto site for returning your phone completely to factory specs, should you mess up /system or something.
I'm actually doing what I'm recommending to you. I'm confident I wouldn't mess things up but on the other hand this is my only phone, I'm too poor to replace it, and I'm living abroad so sending it back would be tricky.
[EDIT]: By SBF I mean either the real SBF or the package you can download from the Motorola "return to factory" page. I'm not actually sure if they are the same thing or not as I haven't downloaded. But you don't need RSDLite for them...
droib said:
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the [...]
Click to expand...
Click to collapse
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
TheSaw said:
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
Click to expand...
Click to collapse
Given your experience I don't think there is any real chance of phone death by following those instructions. The issue is, as you say, backup, or what happens AFTER you successfully root. Motorola's SBF files are everything your phone needs to go back to stock, and 4.4.2 is not available yet. So for example if you were on 4.4 and you corrupted something important like your partition table, you could just go to Motorola's website, request the files for 4.4 and flash them all using fastboot (mfastboot as they say here) to get back to a pristine phone. Right now, you can make a recovery backup of /system, etc. right after rooting which SHOULD be fine for correcting OS tinkering errors, but you never know... People have posted on the possibility of flashing, for example, the 4.4 recovery.img on top of 4.4.2 in order get future OTAs, etc, but this sort of thing is very risky. Maybe it works or maybe you hard-brick.
This guide will work on 4.4.2 and has all the files you need to download. If you're already unlocked you can skip those steps of course
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
It doesn't tell you how to root, but when you exit TWRP it will ask "would you like to install supersu?" so select yes. Once you're in Android go to Google play and download supersu from the market. Open it and it will ask if you want to install binaries. Select yes and the twrp/cwm option. Your phone will reboot then you're done
This still works to root if your bootloader is already unlocked -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Now there is a newer version of SuperSU. See this thread -> http://forum.xda-developers.com/showthread.php?t=1538053 and use the link for the CWM / TWRP / MobileODIN installable ZIP.
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
Follow these instructions with clickable links to TWRP and SuperSU
Step-By-Step Instructions for Unlocking and Rooting a Moto X Dev Ed
works for both 4.4 and 4.4.2.
Okay, I have rooted my phone. I've read several articles on the subject, and this is the easiest method I've found to do it:
Cozume said:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
Click to expand...
Click to collapse
After you downloaded the files needed for this from here (make sure they're not outdated, if you're reading this somewhere in the future), you can just follow these steps for a quick root access. UNLOCKED BOOTLOADER ONLY.
Hi,
Have my dev ed xt1060 rooted and running 4.4.2 stock rom with xposed
This morning when I turned on the phone it downloaded the OTA update which I am assuming is kk, 4.4.4
The update has not been applied yet as I don't want to lose root... I had a bad experience with Samsung and the whole Knox bs and that is why I moved over to the MOTO X dev ed.
If I do update the phone, will I lose root? Will it be hard to get root back??
Is there a way to save the update for later if I want to do that??
Just don't want to get screwed again like I did with knox.... once bitten twice shy, right?
Thanks!
drumrjoe
You need to be on stock recovery and system changes undone as well. In other words Xposed needs to be uninstalled and other changes undone. All original system apps need to be there... Etc. If you've done much to the phone, it's best to flash stock 4.4.2 again, take the Ota and yes...flash custom recovery and root again.
Or.... Wait for flashable files for your model and flash in fastboot. Done.
Personally, I always wait and flash the files with fastboot.
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
This guide has a return to stock section if you need help....
http://forum.xda-developers.com/showthread.php?t=2603358
Do not flash firmware older that 4.4.2....or you will more than likely brick.
Thanks for the help!!
I've got this icon on the upper left of my screen to start the system update... Is there a way to remove that without updating yet??
Is there a way to save the update for a later date, when I have backup up everything and also to make room??
Thanks!
dj
Hi folks,
Just got my TF701T from Amazon on the $279 deal. I've connected it to my wifi but have not even set up a google account for it yet. It's doing an initial charge.
Is there any compelling reason not to let the update happen? The main short term use for the tablet will be that my 7 year old son will play games on it. Eventually, I'd still like to unlock it and maybe to a custom OS, but for now it's plain Jane use.
The only special thing I might want to do is get Helium/Carbon going so I can backup / restore game positions for him... I've got his status on several games saved from another tablet that had root and I backed them up. Would like to restore if possible. Does this require root?
Thanks. Looking forward to advice.
Marc
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc
Frankenscript said:
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc
Click to expand...
Click to collapse
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.
royredman said:
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.
Click to expand...
Click to collapse
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You can use any on. I just used the one that was on my tablets before (which was US). 10.26.1.18 is the 4.3 file to grab. Yup, unzip once and put it on the sd root file. For me, when I rebooted it, it let me know that there was a downloaded update detected (NOT the normal "click this button to download the system update")(be really careful about that one). Once I tapped the detected update file, it showed me it was the 10.26.1.18 file and I told it to install it.
If you want to see what to freeze, go into the towelroot thread in the Q&A section and look for my posts on the last page or so. I was asking exactly the same thing and they answered it all for me. Good luck and let me know if it goes well!!
Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You got it.
The .18 firmware is the JB 4.3. But stick to your SKU (US, WW - whatever it is now).
Once rooted freeze DMClient and CMClient and you won't be bothered with OTA updates.
Thanks! It's all done.
For anyone who reads this and needs to do the same thing, it was super easy. Just plugged the new Tab into the PC via USB, opened up to "Internal Storage", copied the UL-K00C-US-10.26.1.18-user.zip file over there, and rebooted. It auto-applied, rebooted again. Eventually I had to delete the .zip file from the internal storage, because on each reboot it would notice it and spend time figuring out if it had new updates or not.
Then Towelroot, SuperSU, and used App Quarantine-Root to freeze DMClient and CMClient. Rebooted again and no more update waiting for download messages.
I'm good to go!
royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!
Hypothetix said:
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!
Click to expand...
Click to collapse
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
To install a custom rom you need to:
A) unlock the bootloader
B) flash a custom recovery in fastboot
C) create a nandroid of your stock rom in recovery
D) wipe cache, Dalvik and data using your custom recovery
E) flash the custom rom (which is rooted anyway).
For general reference on flashing custom roms to the Transformer, check out my guide here:
http://forum.xda-developers.com/showthread.php?t=2688891
NOTE: This is a guide for the TF700!! The general instructions on flashing, fastboot commands etc still apply. The specifics like recovery and version, bootloader and version etc DO NOT.
For TF701 specific instructions check out the OP of the CROMi-X thread in the Development section for the TF701 here on XDA.
berndblb said:
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
Click to expand...
Click to collapse
Thanks. Yes i know. I like the look the stock rom has. Therefore i first wanted to test, if i can stop the battery drain, if i use apps like greenify to send a few apps to deepsleep.
I rooted yesterday and tested it. Unfortunately, even with greenify i have the same problem. Every time i use the keydock, the tablet does not go into deepsleep mode. I checked with wakeup detector if i can find out which app is bad, but there are no apps which wake up the tablet more that 5 or 6 times.... If i use the tablet without the dock i dont have this problem (or just when i use netflix and dont reboot after usage)
Now i will try a custom rom....maybe it helps.
Thanks !
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.