Database Users

[Q] HELP! Nexus 4 won't boot up

Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan

Restore your Nandroid.
Edit: just saw that you said you didn't make one. Lesson learned, I guess. You can adb sideload files from within recovery. Do this, sideload a stock rom, flash it, and it will give you a normal build.prop.
Sent from my iPad 4

Use adb to push the backup build.prop and overwrite the current one.
I'm assuming that u have the backup on your PC? If not, then download the stock ROM and extract the build.prop from /system.
Use the following command to push it:
Code:
adb push /path/to/build.prop \system
Sent from my HTC Desire using xda app-developers app

megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
If it's stock android, you could actually just wipe /system , then using adb in recovery you can push up a zip of the stock 4.2.2 isntall, and just flash that.
If build.prop is all you changed in /system then that should be fine to do, which will be especially easy if you can just grab a pre-rooted flashable zip of 4.2.2 stock.

megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?

megaman1574 said:
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
Click to expand...
Click to collapse
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).

kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
Where should I look to get a stock rom?

megaman1574 said:
Where should I look to get a stock rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4

mitchdickson said:
just saw that you said you didn't make one. Lesson learned, I guess.
Click to expand...
Click to collapse
Yes, definitely. I can't remember why I didn't make a backup...

mitchdickson said:
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
Click to expand...
Click to collapse
Ok, if I can't fix it by tonight I'll download this and flash it (My download limit during the day is too small to download it. That's why I'm trying to fix it without doing that)

kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
I'm not that good with Android, how and when do use this "logcat"?

megaman1574 said:
I'm not that good with Android, how and when do use this "logcat"?
Click to expand...
Click to collapse
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.

kbeezie said:
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
Click to expand...
Click to collapse
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.

megaman1574 said:
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
Click to expand...
Click to collapse
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).

kbeezie said:
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
Click to expand...
Click to collapse
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.

megaman1574 said:
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
Click to expand...
Click to collapse
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31

kbeezie said:
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
Click to expand...
Click to collapse
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?

megaman1574 said:
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
Click to expand...
Click to collapse
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).

Ok... I had managed to move the backup of build.prop into system using TWRP's file manager but after THAT it wouldn't even show the Nexus logo. Hence the reason I said nothing about this (I thought it to be a dead end). Just as I was about to give up, I was reading an obscure post on Androidforums.com and came across a post telling the guy to pull build.prop, edit it, push it back, and chmod it to 644. I haven't the FAINTEST clue what the hell that is, but I remembered that "chmod" and "chmod 755" were two options when you tap on a file in TWRP's file manager. So I raced back in there, deleted the broken build.prop, moved the backup into system, tapped on it and pressed "chmod 755" rebooted and it worked! Anyone have any idea what is was that I did? What is chmod? But basically:
I FIXED IT YAY!!!
Thanks everyone for your help. I've been desperate to fix it, in fact, when I broke it was an hour before I had to leave for a weekend trip, so I had no phone.

kbeezie said:
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Click to expand...
Click to collapse
My Nexus 7 is rooted with TWRP and it received an OTA update. But anyway, if you refer to my last post I fixed it.
Edit: However, it did unroot it. (not hard to reroot though)

[HOWTO] Remove/disable boot up startup sound from HTC One

Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's two different methods to disable it entirely. You could also extend these to replace the sound with one of your own.
1. Alter the xml file that references the sound file
Pre-requisites:
Handset is rooted
Root-enabled file manager app installed (e.g. Total Commander)
Howto steps:
Detailed in this post later in the thread.
2. Remove/hide the startup sound file
Pre-requisites:
Handset is rooted and has a custom recovery partition (e.g. TWRP or CWM)
ADB install and working on desktop computer
Howto steps:
1. Put your phone into recovery
2. Open adb shell
3. Mount /system
4. Change directory to /system/customize/resource
5. Rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?

Thanks for this, worked a charm and didn't need to S-OFF!

Helpful! thank you very much bro.
Helpful! thank you very much bro.
dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse

Brilliant thank you. Will do this soon.

dr_diem said:
Hi all,
Couldn't find this info for this handset specifically, so thanks to Jayshah's howto for the HTC Desire in this post (H/T to him!) I found the equivalent location in the HTC One filesystem for the startup sound audio file.
So then, if, like me, you strongly dislike the HTC "Quietly brilliant" boot sound, here's how to disable it entirely:
Pre-requisites:
Handset is rooted
Put your phone into recovery
Get a working adb shell
1. Mount /system
2. change directory to /system/customize/resource
3. rename or delete HTC_Sense5_Boot.mp3
Code:
mount /system
cd /system/customize/resource
mv HTC_Sense5_Boot.mp3 HTC_Sense5_Boot_mp3.disabled
As noted by Jayshah, you could install Silent Boot from the Play store, but why add something else eating processor cycles when this solution is guaranteed and requires no additional code?
Click to expand...
Click to collapse
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?

M_Shaaban said:
"Get a working adb shell" meaning what? Having a working fastboot? could you please explain?
Click to expand...
Click to collapse
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian

dr_diem said:
Do some searching here on the forums - adb stands for Android Desktop Bridge and is freely downloadable as part of the Android SDK. It enables you to access your Android device in various ways from your desktop computer. adb shell is a way to open an interactive shell (a 'command prompt') on the Android device. There are howtos on these forums (and indeed all over the 'net) that'll explain how to get ADB set up for your desktop OS.
Ian
Click to expand...
Click to collapse
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?

M_Shaaban said:
I did do that and I could reboot to recovery by entering command "adb reboot recovery" but then when I enter adb shell, it says device not found. What should I do? Could there be a quick video tutorial on how to do so?
Click to expand...
Click to collapse
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.

dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
dr_diem said:
Oh okay you're probably almost there. I couldn't say exactly what's causing that message (I see the same myself from time to time by rebooting the phone usually solves the problem). Try booting the phone normally and seeing whether adb shell works when the phone is in it's normal interactive usable state. If that works then you could Google on 'adb shell not working in recovery mode' or somesuch, but you need to confirm that it works at all first of all.
Click to expand...
Click to collapse
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!

M_Shaaban said:
OK will try and do that. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added 16th December 2013 at 12:00 AM ---------- Previous post was 15th December 2013 at 11:35 PM ----------
@dr_diem adb shell works fine with phone is on. Now time to find a solution to be working on recovery. My phone is rooted but I flashed stock recovery back after rooting. Is that OK? Or must it be done via custom recovery? Did it do it via stock or custom recovery? Also my Windows is 8.1 but I can access fastboot (commands and all) without a problem. On stock recovery >adb shell > device not found!
Click to expand...
Click to collapse
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian

dr_diem said:
I've just done some quick Googling and indeed yes a custom recovery is required to use adb whilst in recovery (according to this page that seems pretty sure of itself). Apologies that my howto didn't make that clear (that being because I didn't know about the requirement at the time!); I'll update it in that regard now.
Ian
Click to expand...
Click to collapse
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?

M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
I'm sorry but I am out of ideas on this I can only suggest you do some extended web and/or xda-developers searching to learn reasons for this error. I'm quite sure you'll find the answer given the size of our community; please do post back here when you find it.
Good luck!
Ian

M_Shaaban said:
I flashed CWM custom recovery and still adb device is not found! What could be the problem here?
Click to expand...
Click to collapse
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.

homeslice976 said:
Since this guide requires root anyway, I'm going to assume you already have Root access. If so, just install a root file manager (I like Root Browser), navigate to /system/customize/resource, and rename HTC_Sense5_Boot.mp3 to anything else. As long as it's not called HTC_Sense5_Boot.mp3, it won't play. Save and reboot. If you'd like to disable it altogether, navigate to /system/customize/resource/CID and open default.xml. Find:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" audio="/system/customize/resource/HTC_Sense5_Boot.mp3"/>
</BootConfiguration>
and remove the last part so it looks like this:
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/att_bootup_one.zip" />
</BootConfiguration>
Now save and reboot.
Click to expand...
Click to collapse
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app

M_Shaaban said:
I used Root Browser. I edited the XML file and worked like a charm. But seems like it's taking a bit longer to boot, could editing boot configuration cause this?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire

homeslice976 said:
I certainly wouldn't think so. I've been disabling bootsounds this way since my Inspire
Click to expand...
Click to collapse
Ah OK. Thanks a lot anyway
Sent from my HTC One using XDA Premium 4 mobile app

Hi, I tried to change this with root explorer. First i renamed the audio file. But it was restored after reboot. Then i changed in the xml file. same here restored? wtf? Have just got the latest sense 6 if that can have something to do with Thierry.
Edit: worked from recovery. But still, strange that root explorer didn't work?

You saved me. I was going crazy ... all tips I could find were for Android 2, or were turning sound off at shutdown => does not work after crash.

Thankss
Thnaks for the info

Do I need to be S-OFF to perform that?
Because when I restarted my phone after edition of the XML config file the changes we gone. Original file remains.

[GUIDE] |ROOT + Tethering + MORE| Moto X ver. 4.4.4 for XT1060 and XT1058 (VZW/AT&T)

[GUIDE] |ROOT + Tethering + MORE| Moto X ver. 4.4.4 for XT1060 and XT1058 (VZW/AT&T)
Moto X Root for AT&T/VZW [KXA21.12-L1.26]
This is a rewrite of instructions found HERE by CrashXXL. This will get you PERMANENT[meaning it will not disappear after reboot, but will die if you reflash or upgrade, etc] root on your 4.4.4 AT&T/VZW [KXA21.12-L1.26] Moto X. This will NOT disable system write protection or unlock your bootloader, etc.
The following steps were used by me on Ubuntu 15.04 to root my XT1060 from Verizon:
0. Reinstall your stock rom from HERE you will want the firmware that matches your current 4.4.4 KXA21.12-L1.26 firmware. If you are unsure how to do this HERE is a guide. [NOTE: If you skip this step and you are on 4.4.4 from an OTA then you will be stuck on the M Logo and will have to do this step and all the other steps over]
1. Make sure you have the necessary applications:
Code:
sudo apt-get install android-tools-fastboot python python-serial unrar
2. Download your _Root_<Your phone carrier>_KXA21.12-L1.26_Stock.rar from HERE
3.
-- a) Extract the files
-- b) From the terminal cd into the directory of the extracted files.
-- c) Put your phone into fastboot mode [reboot holding the power and volume down button]
4. Type [NOTE/WARNING: This will softbrick your phone. Which is completely fine if the steps are all followed]:
Code:
sudo fastboot flash sbl2 sbl2.mbn
sudo fastboot reboot
Your phone will have a black screen, but will be in QCOM Emergency mode. You can type in lsusb to confirm this.
5. Type:
Code:
python qdloadRoot.py MPRG8960.bin -ptf _root/partitions.txt
This will take a good 5-15mins. Make sure you are plugged into power and this step is not interrupted. Once this is done your phone will reboot and start up and you will see that SuperSu is installed.
Congrats you have root
NOTE: Read on to the next posts for more info and resources.

Xposed Install
The original post can be found HERE by Sabissimo.
Assuming the above steps were followed and you now have root. Do the following:
1. Download THIS for AT&T XT1058 or THIS for VZW XT1060
2. Extract the file as in step 3 above
3. Run the same commands from step 4 above.
5. Type:
Code:
python qdloadXposed.py MPRG8960.bin -ptf _root/partitions.txt
Be patient for a few minutes. Your phone will reboot.
6. Install 2.6.1 or 2.7.1 of Xposed from their SITE and install as normal.
Congrats you now have root and Xposed that will survive reboots

Thanks to @Nicene Nerd he put together a nice set of scripts to make custom packages to add/remove packages from system images. Check it out here!
Make a tutorial how to pack new applications onto the system AdAway etc.
-- Tutorial to bake in new apps. Thanks Sabissimo. I might rewrite this in the future to make it easier. If anyone follows that guide and would like to write please let me know and we can share files here.

Flash the same way you do the above.
This is for the xt1060.
Here are a list of addition flashables after you have root/xposed
Download:
This will change your /system/etc/hosts file to point to /data/data/hosts. Change this setting in AdAway and be ad free
Adaway_hosts_Root_4.4.4_VZW_KXA21.12-L1.26.zip
This has the buildprop edited for entitlement bypass (tether check) and has all stagefright options set to false. This also has the CF.lumen driver installed (look on playstore great app):
CF.lumenPLUS_Root_4.4.4_VZW_KXA21.12-L1.26.zip

jahrule said:
3. Go further and make our own system images.
Click to expand...
Click to collapse
If you are interested in MoFo, I first need someone to help me make the "pre-rooted" image. It must be in ext4 format. I have an XT1060 Dev Ed that is rooted. According to maiko1,
maiko1 said:
Simplest way is to make the system block device readable by everyone (chmod 644), and then adb pull the block device to your computer.
For example on the turbo via adb shell as root:
Code:
# ls -l /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-09 20:49 system -> /dev/block/mmcblk0p39
# chmod 644 /dev/block/mmcblk0p39
Then pull it with adb:
Code:
$ adb pull /dev/block/mmcblk0p39 system.img
Click to expand...
Click to collapse
I tried that but I get the error
remote object '/dev/block/mmcblk0p39' not a file or directory
Now, I am not your most experienced adb user so I may have been doing something wrong. What I did was start an adb shell while my XT1060 was running in Android. Then I typed:
su # ls -l /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-09 20:49 system -> /dev/block/mmcblk0p39
then
# chmod 644 /dev/block/mmcblk0p39
But when I went to pull it I got that error above. I just noticed that SuperSu had silently denied root to the adb shell. Not sure how to stop that.
Also, if I can get this to work, then I could put AdAway, Busy Box, etc. on my XT1060 and pull the image and it should be flashable with mofo.

Finally
I will follow this guide and then post results! I wanna root in my XT058 from long time ago!

Alexdream said:
I will follow this guide and then post results! I wanna root in my XT058 from long time ago!
Click to expand...
Click to collapse
If you need help. Just ask, but it is quite simple.
Don't forget to hit thanks!

JulesJam said:
If you are interested in MoFo, I first need someone to help me make the "pre-rooted" image. It must be in ext4 format. I have an XT1060 Dev Ed that is rooted. According to maiko1,
I tried that but I get the error
remote object '/dev/block/mmcblk0p39' not a file or directory
Now, I am not your most experienced adb user so I may have been doing something wrong. What I did was start an adb shell while my XT1060 was running in Android. Then I typed:
su # ls -l /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-09 20:49 system -> /dev/block/mmcblk0p39
then
# chmod 644 /dev/block/mmcblk0p39
But when I went to pull it I got that error above. I just noticed that SuperSu had silently denied root to the adb shell. Not sure how to stop that.
Also, if I can get this to work, then I could put AdAway, Busy Box, etc. on my XT1060 and pull the image and it should be flashable with mofo.
Click to expand...
Click to collapse
Looks like you are trying to dd from a partition that does not exist. We can take this offline as it is off topic from this thread.

jahrule said:
Looks like you are trying to dd from a partition that does not exist. We can take this offline as it is off topic from this thread.
Click to expand...
Click to collapse
/dev/block/mmcblk0p39 exists - I can see it in ES File Explorer.
Bottom line is this - I have an XT1060 Dev Ed unlocked and rooted and was trying to help those of you who have unlockable XT1060's to be able to use MoFo. I don't need it for my XT1060 and it looks like you all have another option, although I am not sure how good of an option it is.
If someone wants to enlist my help, I would be willing to help but the ball in your court.

Does anyone has succesfully rooted Moto X1060 (VZW) using this tutorial?

JoseLoarca97 said:
Does anyone has succesfully rooted Moto X1060 (VZW) using this tutorial?
Click to expand...
Click to collapse
Other than me? You can check the original thread. Many other people have done it there.

I can root successful my XT1058 following this guide. Thank you so much! Finally I have xposed and GravityBox.

Post 3 updated with guide to bake in new system applications!

Where should I get the files in step 1 of the root process?

abuttino said:
Where should I get the files in step 1 of the root process?
Click to expand...
Click to collapse
The links are all in post 1. The first step are the packages you need. In my case I was running Ubuntu. If you are running Windows. The you can check the linked original thread and try to do it like that.

I tried it the Windows way and everything went very smoothly. Thanks.
I just don't have the experience to run Ubuntu yet. Been running Windows since v3
Sent from my XT1060 using Tapatalk

Thx! @jahrule
Any chance we can modify it so it will work for the XT1052?

dagoban said:
Thx! @jahrule
Any chance we can modify it so it will work for the XT1052?
Click to expand...
Click to collapse
I think the xt1052 is Europe version and can have the bootloader unlocked. It is then trivia to root.

jahrule said:
I think the xt1052 is Europe version and can have the bootloader unlocked. It is then trivia to root.
Click to expand...
Click to collapse
Yep, 1052 is the Europe one. I have 2 lying around here, for one the BL is unlockable, but the other one has an error and the moto page says that device is not unlockable even thou its a xt1052.
So I would really appreciate something for the xt1052
Thx again!
And let me know if you need any files from the xt1052 partitions / sbfs

dagoban said:
Yep, 1052 is the Europe one. I have 2 lying around here, for one the BL is unlockable, but the other one has an error and the moto page says that device is not unlockable even thou its a xt1052.
So I would really appreciate something for the xt1052
Thx again!
And let me know if you need any files from the xt1052 partitions / sbfs
Click to expand...
Click to collapse
If it shows error try the US support site instead of the one in your country.. Worked for me

How to block ads without root

Since this is a vanilla android phone, the only real modification I wanted was to change the hosts file to block ads. Turns out you can do that without rooting your phone, but you DO need an unlocked bootloader.
After you're unlocked, you'll need the TWRP recovery image:
http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3230471
and the flashable hosts file:
http://forum.xda-developers.com/showthread.php?t=1916098
Reboot into the factory bootloader, then into TWRP:
Code:
fastboot boot twrp-2.8.7.0-bullhead.img
Start ADB Sideload in TWRP and push the flashable hosts file:
Code:
adb sideload MoaAB_ADBlocking_12October2015_R4.zip
Reboot, DON'T install superuser when prompted, and you're done! You'll still have the factory recovery, but you will get the device is corrupt message since this changes the system.
There may be an easier way to do this, but just wanted to put it out there if there's anyone else looking to do the same thing.

I seem to lose adb access when I am in TWRP, do I type "adb sideload MoaAB_ADBlocking_12October2015_R4.zip" in the command prompt on my computer or is there a way to type this within TWRP?

The command prompt. I've had driver issues with adb in recovery on some computers, check in device manager and see if it shows up. You may have to update the driver (right click on the phone in device manager) and manually select adb. Not at my computer, so I can't give specific steps, sorry.
Sent from my Nexus 5X using Tapatalk

Yup you were right, driver issues, fixing right now, thanks!

If you use the Amazon app, it will be broken with MoaAB, unless it was fixed.

Seems to work fine, so they must have updated the list.
Sent from my Nexus 5X using Tapatalk

thanks for posting this , will try it soon!

Can I load this if I am on unlocked bl, unencrypted, and rooted?

Yup, then you can just flash it in TWRP. Or use an app like AdAway.
Sent from my Nexus 5X using Tapatalk

Can anyone tell me if flashing this host file will prevent future OTA's from installing successfully?
If so, would saving the original host file as a backup and pushing that back via ADB allow the OTAs?
Thanks!

I can't tell you for sure, but it's certainly a possibility. Having a backup is always a good idea, but there is a flashable stock hosts file in the same thread as the ad blocking file.
Personally, I'll probably just flash the factory system.img when it's time for an update.
Sent from my Nexus 5X using Tapatalk

Rbrowser is a good alternative, if you'd prefer to keep everything stock for updates. Does an excellent job at blocking ads, and very Chrome like.

As an avid flasher and owner of all the Nexus this is the first time I'm trying to go non-root and I was able to find any alternative for ad blocking. I'd recommend you install AdGuard, it blocks websites and apps but it redirects the traffic through its vpn server so Google battery stats will determine it's eating all the juice. This however is simply not true, after extensive use I can still do 3-4hrs SOT, so give it a shot if you want ad blocking non-root.

Since AdAway always did a great job for me, I made a script that grabs all the same sources and builds a single hosts file to push to the phone. You'll need Linux or another UNIX to run it though.
http://www.jimsrandomcrap.com/2015/12/12/ad-blocking-without-root-on-the-nexus-5x/

wow you are the best

beavis9k said:
Since AdAway always did a great job for me, I made a script that grabs all the same sources and builds a single hosts file to push to the phone. You'll need Linux or another UNIX to run it though.
Click to expand...
Click to collapse
:good:

No problem; I'm glad other people find it useful. Maybe I should make a post for it in the development section.

@beavis9k: I followed your tutorial and I was able to push the hosts file to my phone but ads still do not get blocked.
Should there be some kind of a response after applying the "adb shell chmod 644 /system/etc/hosts" command?
If I open the hosts file the only entry is "127.0.0.1 localhost::1 localhost". I guess that isn't correct and the script is not able to grab the sources when I run it.
UPDATE: Solved it. There was a problem with cygwin running the script.

Norlam said:
@beavis9k: I followed your tutorial and I was able to push the hosts file to my phone but ads still do not get blocked.
Should there be some kind of a response after applying the "adb shell chmod 644 /system/etc/hosts" command?
If I open the hosts file the only entry is "127.0.0.1 localhost::1 localhost". I guess that isn't correct and the script is not able to grab the sources when I run it.
UPDATE: Solved it. There was a problem with cygwin running the script.
Click to expand...
Click to collapse
Ahhh... thanks for letting me know. I never did try it under cygwin. I figured it would just work. If the generated hosts file only has localhost in it, I would guess that wget isn't installed with cygwin.

Yeah that was the problem. I forgot the check the "wget" package during the installation of cygwin
After installing the package the hosts file was working as it should :good:

[GUIDE] Easiest way to root Pixel 2 XL and disable the carrier tether check!

***PIXEL 2XL ONLY!!!*** ***PIXEL 2XL ONLY!!!*** ***PIXEL 2XL ONLY!!!***
Confirmed this works with Android O and P!
UPDATE 3/17/2020: Now confirmed this works with Android Q, but with slight modification!
It took me many hours to piece together the various forums and articles, but these instructions will have you up and running in 30 mins max!
*Below instructions assume brand new phone out of the box, everything stock.
1. Download adb and fastboot on your computer. You don't need the whole SDK and don't need to install anything; Google now provides them in a simple zip file. Get it here for Windows, Linux, Mac. If you're using a Mac, all you have to do is open Terminal, cd into the directory where you unzipped the files, and type ./adb [command] from there. EX: If you downloaded the zip file into your Downloads folder, and extracted the zip also in your Downloads, you'd type the following on a Mac:
Code:
cd ~/downloads/extractedfoldername
Code:
./adb version
with your phone plugged in via USB to the computer to test adb works. Make sure to enable developer mode on your phone, and also enable USB Debugging. NOTE: For all below references to adb and fastboot, make sure to include the "./" before the command from the extracted directory. EX: "./adb" and "./fastboot"
2. Unlock bootloader. Follow the directions provided here in the "Unlock the bootloader of the Pixel 2 / Pixel 2 XL" section. (Don't waste your time reading the rest of those instructions, since that will confuse you and they don't work anyways.) I did unlock_critical at first, but the bootloader still said it was locked. Then I did "flashing unlock" and that unlocked the bootloader. Make sure device status in fastboot on the phone says "unlocked." Reboot the phone.
3. Download the latest Magisk Manager from here to your computer. I used 5.6.4.
4. Type
Code:
./adb push <path_to_file> /sdcard/Download
5. On the phone, go to your Downloads app and install the Magisk Manager apk.
6. Open the manager. Click the Install button. It will ask if you want to "install Magisk-vXX.zip now". Click Install and then select Download Zip Only at the next prompt.
7. Download the TWRP image here to your computer. NOTE: You only need to download the IMG file! Don't need the zip file.
7.5 From your computer, run:
Code:
./adb reboot bootloader
8. From your computer, run:
Code:
./fastboot boot path/to/twrp.img
9. Once phone boots into TWRP, go to Install. Then go to the MagiskManager directory. In there, you should see the "Magisk-vXX.zip" file you downloaded in Step 6.
10. Now reboot your phone and open up the Magisk app. You should now see it says "Latest Version: vXX.X" and "Installed Version: vXX.x" with green check marks next to the items. Open the Magisk settings (3 bars on the top left) and you should see a bunch of options, one of them says #SuperUser. This means you now have root!!
11. To enable the tethering:
For Android 8 and 9:
Code:
./adb shell
Code:
su
**(grant permission if phone asks)**
Code:
mount -o rw,remount /system
Code:
echo "net.tethering.noprovisioning=true" >> /system/build.prop
Very important step! You must reboot for the changes to take effect.
Code:
reboot
For Android 10
It seems like you can no longer mount /system as rw. So it's a little more complicated. If you fully installed Magisk (not the way I did it above), then from Magisk Manager, go to Modules and download MagiskHide Props Config and busybox-ndk. Follow the instructions here to run the Props Config.
If you followed my rooting instructions above, running the Props Config won't work, but there is a workaround.
You could still use the module, but instead of using the props command and the terminal UI, you just use the configuration file to set everything up. Download the settings file, extract it from the module zip (in the /common folder) or copy it from the module directory under /data/adb (in the /common folder), add
Code:
net.tethering.noprovisioning=true
to the CONFPROPS variable, place it in the root of your internal storage (/sdcard) in /data or in /cache (or /data/cache if you're using an A/B device) and reboot.
Another option is to just use a simple boot script. Put the following in a file (doesn't matter what you name it) in /data/adb/service.d:
Code:
#!/system/bin/sh
resetprop net.tethering.noprovisioning true
Give it execution permission (chmod 755 is usually the goto) and then that prop will be set at each boot. If it doesn't seem to work, put the script in /data/adb/post-fs-data.d instead.
Very important step! You must reboot for the changes to take effect.
Code:
reboot
[email protected]##
Giant shoutout and thank you to @Didgeridoohan for helping me debug and figuring this out! You're a life saver.
References:
MagiskHide Props Config Documentation thread
MagiskHide Props Config README
Thread where Didgeridoohan explains the process and help me debug

Codes
Hi im having trouble with getting the commands right, I seem to be getting the message stating the command push requires argument but im not sure why, can you provide the actual command in full how it should be input.
Thanks

I didn't even bother using the commands. All I did was root as given in the guides for this device. I then used a file manager with root capability to access build.prop and edit the file directly to add the line. Afterward I rebooted and was all set.
Of course, with my service provider I may not have needed to do this as their provisioning doesn't seem to touch tethering, even though they don't allow it. I'll find out next month when the security update comes through.

Excellent guide, except for one crucial missing step:
7.5 Reboot back into the bootloader:
Code:
adb reboot bootloader

I'm on a grandfathered att unlimited plan, which does not allow tethering. I have edited the build prop to enable it, but does anyone know if they can detect that I am tethering?

Need help.
i accidentally used this for a pixel 2 and now cannot get past the white startup screen with the google logo. Any ideas?

ashayden said:
I'm on a grandfathered att unlimited plan, which does not allow tethering. I have edited the build prop to enable it, but does anyone know if they can detect that I am tethering?
Click to expand...
Click to collapse
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.

Strephon Alkhalikoi said:
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Click to expand...
Click to collapse
This is a true statement.

frankygoes said:
Need help.
i accidentally used this for a pixel 2 and now cannot get past the white startup screen with the google logo. Any ideas?
Click to expand...
Click to collapse
I'm having the same issue. I previously used the build.prop updated a number of times, but after doing it with the July factory images, I get stuck on boot. Anyone figure out a way around this?

I did this method and have root but I have no recovery.
According to this: https://twrp.me/google/googlepixel2xl.html I needed to install twrp zip after fastboot boot twrp.img and I can't do it now because I'm rooted and need to reflash boot image. dang!
/necro

soccercake7 said:
I did this method and have root but I have no recovery.
According to this: https://twrp.me/google/googlepixel2xl.html I needed to install twrp zip after fastboot boot twrp.img and I can't do it now because I'm rooted and need to reflash boot image. dang!
/necro
Click to expand...
Click to collapse
You don't need reflash your boot image. Just put your phone into recovery, then go back to temporary twrp by fastboot boot twrp.img. Then flash twrp.zip

Strephon Alkhalikoi said:
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Click to expand...
Click to collapse
Not entirely true if your device is fresh out the box. On my previous phone when we were all trying to unlock the bootloader on the Verizon variant, I did it accidentally. I failed to unlock the bootloader lol, but if you never put a Sim in the device and delete the radio file to temporarily "un-grey" the OEM unlock ticker, and then install a vpn (I used the cracked adguard plus from revdl) and turn on basically everything, then factory reset to get the radio back, then reinstall the vpn and enable all the ad masking options and THEN put your sim in for the first time...
I don't know how or why it works but I went almost three months tethering my heart out on Verizon for like 400-700 gigs/month without being throttled one bit or subjected to their bull**** priority system. An added peculiarity was I also had glasswire data moniter installed before ever inserting the sim and both it and the Verizon built in data meter both just stayed at zero. Unfortunately, I was sending a file to a friend with sendanywhere and we were having trouble getting it to accept the access code so I turned off the adguard protections just for like two minutes and both data monitors started spitting out numbers and I got throttled into Oblivion the following bill cycle.
Again, I don't know how many of those steps are needed or what exactly to turn on in adguard, but I do know that it somehow let's you in the data door and keeps the traffic source anonymous until you give the device a window to phone home with your account. Wish I could be more specific with directions but it absolutely worked, somehow. I haven't used sendanywhere since that day and never will again because it ruined something so beautiful for me.
I tried for probably two dozen hours to reset and recreate the circumstances and get those sweet, sweet zeroes back, but to no avail, so I would assume that it can't ever work on the device once it's had a Sim installed even for a moment, and once working you must keep the vpn running from startup forever...probably can't ever factory reset or you will lose it. I really don't know. I'm sure one of the techier peeps here could figure out how and why it works or already knows, but doesn't want to post it because then it will get fixed and ruin his or her own beautiful thing.

8wrlobo said:
Not entirely true if your device is fresh out the box.
Click to expand...
Click to collapse
https://android.stackexchange.com/q...-companies-detect-tethering-incl-wifi-hotspot
You got lucky.

Strephon Alkhalikoi said:
https://android.stackexchange.com/q...-companies-detect-tethering-incl-wifi-hotspot
You got lucky.
Click to expand...
Click to collapse
I use NordVPN and VPN Tether on rooted (Magisk) stock Google Pixel 2 XL . Carrier doesn't see my tethering.

n2music said:
I use NordVPN and VPN Tether on rooted (Magisk) stock Google Pixel 2 XL . Carrier doesn't see my tethering.
Click to expand...
Click to collapse
A VPN if I recall doesn't prevent the carrier from using the number of hops (i.e. the TTL number) to detect tethering. It does prevent them from seeing what data you are pushing across the network however.

My total data use increases, but tether usage does not. I rarely use more than 30gigs altogether each month anyway, not an abuser.

n2music said:
My total data use increases, but tether usage does not. I rarely use more than 30gigs altogether each month anyway, not an abuser.
Click to expand...
Click to collapse
Not an abuser, but in the eyes of the carriers that don't want you tethering without paying you are a thief. It's silly because in the end it's still data, and just a way for the carriers to gouge you.

Strephon Alkhalikoi said:
Not an abuser, but in the eyes of the carriers that don't want you tethering without paying you are a thief. It's silly because in the end it's still data, and just a way for the carriers to gouge you.
Click to expand...
Click to collapse
I actually do pay for it. I am on beyond unlimited. But I agree with you.

n2music said:
I actually do pay for it. I am on beyond unlimited. But I agree with you.
Click to expand...
Click to collapse
Sorry for assuming you didn't pay for the privilege. Since the discussion started by others centered on ways to prevent carriers from detecting tethering, I ran on that assumption.