yashsingh1/xdaforums huggingface dataset:
[Xperia Z Q&A, Help & Troubleshooting] Nauju:
Will try it bro
[Xperia Z Q&A, Help & Troubleshooting] androidtweaker1:
Is your issue solved?
[Xperia Z Q&A, Help & Troubleshooting] Nauju:
Nope:( i change the nav bar size but no luck so far..
[General Questions and Answers] KingEB:
Hey there, just wondering if anyone has a solution to a bluetooth auto connect issue. My problem is that no matter what bluetooth device I connect my phone to, it will work fine until I turn bluetooth off on the phone. When I turn bluetooth back on it will try to reconnect, but just hangs there.

For example, I pair my phone to my car, listen to music no problem, then when I get home I turn bluetooth off to save battery. Then if I get back into my car later and switch bluetooth on, it refuses to auto connect, even though the car bluetooth is still listed as a paired device on the phone. This also happens with my bluetooth headphones! It won't even connect if I manually try in the bluetooth settings page, I have to manually unpair and repair again and the process starts all over again.

I'm using DoomLords Stock 4.3 on an XperiaT. Anybody got any ideas??
[Android Apps and Games] giogio87:
Betterfish helps to overcome the obstacles and reach the Betterworld.

https://play.google.com/store/apps/details?id=com.fato.betterfish
[8125, K-JAM, P4300, MDA Vario General] makisupa:
I'm one of those people who had an MP3 association problem with ringtones after I installed a 3rd party MP3 player. I took the proper steps to correct the file associations and got the device working with the proper ringtones. My contacts who have personalized ringtones all work and work after the device reboots; however, my phone's deafult ringtone won't stay after reboot. I have it set to OldPhone; however, after a restart the device always put it back to Windows Default ring. Any ideas what's causing this?
[8125, K-JAM, P4300, MDA Vario General] meschle:
If you are used to do registry tweaks change it here HKCU\control panel\soundcategories\ring\defaultsound

put the name of your preferred default sound there

Or take a look in HKCU\control panel\sounds\ringtone0\sound

when you change the phones ringtone in settings\phone the change should appear here.
[8125, K-JAM, P4300, MDA Vario General] makisupa:
Bump.

Even after a hard reset this problem is happening again. I've even tried changing the settings directly with a Reg editor but they don't stick. Any help/solution? I hate the default t-mobile jingle.
[8125, K-JAM, P4300, MDA Vario General] meschle:
Should have been fixed after a hard reset - you must somehow have a corrupted rom - take it back to t-mobile or flash with original (keeps warranty) or new rom.
[Galaxy Y GT-S5360 General] saurabhkolhe17:
Hello All ,

I am new to root.I have rooted my phone...Can anyone tell me the difference between the Soft Brick and the Hard Brick.I know that if someone is soft bricked he can install the whole samsung original software using ODIN.Bur what if some one is HARD Bricked.Does USB Jig helps to turn on the phone in the downloading mode...

What are the matters in which a phone is hard bricked...?

Does updating different kernels leads to Hard Bricks...?I havent changed the kernel also as i am scared of bricking my phone...If someone updates a custom ROM does it changes the kernel...?

Guys please atleast reply me..I have seen no one replies me on my doubts..Just I can see that the views have increased but no one have replied on my posts...

Thanks.
[Galaxy Y GT-S5360 General] TheFixItMan:
soft brick = your phone will not boot but recovery or download mode is available

hard brick = your phone will not enter any recovery or download mode and needs professional repair or is just a paperweight

A usb jig will put phone into download mode if it is soft bricked

you can soft brick by not flashing a rom or kernel correctly or if they are not compatible with each other/baseband

you will only hard brick if you flash a totally wrong stock firmware via odin or try and repartition or just muck up the boot - its highly unlikey this would happen

your kernel will only change if you flash a different kernel or the rom contains a kernel - look in the root of the rom zip for boot.img - if its not there the rom does not contain a kernel and your kernel will not change

and next time please post in correct section - questions go in Q & A NOT general section

Its also much quicker if you search for answers - eg typing in google what is the difference between soft and hard brick - you would of found the answer instantly
[Sony Xperia P, U, Sola, Go] grzychu:
My problem with wifi lies in the fact that when I turn on my wifi searches for available networks and trying to connect to any network and entered the password the phone stores the network and instead connect me with wifi, cleans up other networks and shows from a network is inaccessible.

It happens since I got the phone on all ROMs, on open networks and closed.

Anyone knows the solution to this? none programs didn't helped :(

P.S sorry for my english a long time i didn't used.
[Android Q&A, Help & Troubleshooting] kareemkimo39:
Do you want two whats app accounts on one device WITHOUT ROOT ?

Then if you want message me and I will send you the link !
[Sony Xperia T, TL, TX, V] 87Fra87:
I have flashed xperia v with android stock 4.1.2 (fw .140). The bootloader after flash of 4.1.2 is unlocked. After reboot and first setting i start wifi and notification bar show me that there is an update to 9.2.A.0.295, so i update, immediately smartphone reboot but smartphone show me message : impossible installation. I have tried to use sony companion but program show me message of error that it says: software is not original and it can't update software.

So i decided to install custom rom, so i have root my smartphone with DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit and then i have installed recovery (i have used this guide: http://xdaforums.com/showthread.php?t=2012738). Then i have try to flash many roms but althought i have (everytime do wipe data, cache, dalvik) i can't install any rom.

I have error: Symlink: some symlink failed...(status 7) installation aborted.....

What i can do to update my rom?
[Sony Xperia T, TL, TX, V] BakiSaN:
You can't update through updates/PC companion becoz u have BL unlocked. Just download some of the FTF fws and flash through flashtools, that's easiest imo...Unless you get **** erros like i do :(
[Sony Xperia T, TL, TX, V] 87Fra87:
I have flash ftf .140 from but after flash bootloader remain unlocked. Where i can find ftf 4.1.2 with bootloader locked? Is there any possibility to flash ftf with android 4.3 and bootloader locked? ...please help me i am desperate........can you post ftf with bootloader locked?

Inviato dal mio GT-N8000 con Tapatalk 2
[Sony Xperia T, TL, TX, V] 87Fra87:
I have solved i have use 9.2.A.0.295 - Unbranded - Nordic (1268-6904) for my italian unbranded smartphone
[Moto X General] tekhna:
The other thread was just too messy with too much cross information.

So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.

It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.

There's lots of other info, but this thread is just designed to separate out the discussions.
[Moto X General] KidJoe:
Just to add..

Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"

Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )

Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.
[Moto X General] evandena:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?

I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.

I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
[Moto X General] KidJoe:
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.

The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.
[Moto X General] fury683:
I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.

I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.

I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.

One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
[Moto X General] Mayze23:
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick
[Moto X General] evandena:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
[Moto X General] KidJoe:
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.

Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.

---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------

No. Put your phone in bootloader mode... then...

mfastboot erase cache
[Moto X General] evandena:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
[Moto X General] KidJoe:
Have to enter that command from the PC
[Moto X General] Reserved Name:
Wifi Tether require Write Protection?

I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
[Moto X General] andino:
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.
[Moto X General] pyro6128:
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.
[Moto X General] evandena:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.

*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...

*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
[Moto X General] evandena:
Yep, was. It was booting to safe mode when Recovery was selected.
[Moto X General] Reserved Name:
I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.
[Moto X General] kendokan:
If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?
[Moto X General] KidJoe:
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/

I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.

I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.
[Moto X General] Deleted member 2351944:
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.

You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.
[Moto X General] mercado79:
You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!

Sent from my Moto X
[Moto X General] jideay:
Stupid question... If we could downgrade from 4.4, why can't we downgrade from 4.4.2?
[Moto X General] lucky13:
That's what I'm currently doing, works fine.
[Moto X General] pricematthew4143:
If you can go without root, as nuts as I sound, the 4.4.2 update is much smoother and way better on the battery...the phone is more fluid in everything
[Moto X General] tu3218:
Yeah I gotta agree with this. Sucks I don't have root cause now I can't tether :/. But the phone is more smoother and definitely has better battery. Especially in standby.
[Moto X General] pricematthew4143:
To be honest I was really surprised how much it improved the phone...actually impressed with moto on this..did a great job and for VZN...this is like a glacier overtaking hell..

---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------

Not much of a camera guy so haven't tried it but seems to be auto focusing a lot however pic seems clearer too..

---------- Post added at 10:25 PM ---------- Previous post was at 10:17 PM ----------

If this helps...totally dark hall way no light but flash
[Moto X General] lucky13:
I disabled framework before I updated.
[Moto X General] evandena:
Does that mean we won't have access to any of the Moto apps, or can they be downloaded from the store?

Also, how can one tell if they have Safestrap? I rooted my phone back in November, using Jcase method. Apparently I have a modified recovery, but that's all I know.
[Moto X General] TheDave1022:
You would have to install the safestrap apk and install the recovery. the recovery is similar to TWRP, but you get rom slots which you can load a safestrap rom into and boot off it. You can also make a backup copy of your current stock rom and then boot off that. If you mess something up, you revert it. Only downside is it reduces the amount of storage space available on your phone.
[Moto X General] 640k:
This is not completely accurate and mostly speculation. The nature of the locked bootloader prevents the Android OS firmware from downgrading in order to preserve the integrity of the device. This has been the case for as long as locked bootloaders have been a thing and has relatively little to do with Moto, in general. I know there are a quite a few threads that discuss this very topic that likely date all the way back to 2010 as this has been a constant issue since locked bootloaders were introduced (think moving from DROID1 to DROID2).

Manufacturers like Motorola have little to do with the patching of exploits at the OS level anyhow, unless they've provided their own software which caused the exploit to begin with. Instead, Google/Android must work together with Manufs to identify, log and classify vulnerabilities, bugs and defects and prioritize them accordingly. This is evident in past Android OS releases that allowed the same exploit to work for many devices, across many iterations and point releases.

I'm going to be doing my share to figure out 4.4.2 and next steps as I'm basically "crippled" from upgrading my device and I desperately want 4.4.2 due to all of the bug fixes (such as Exchange).
[Moto X General] jideay:
The reason I initially asked this dumb question is because now that I have 4.4.2, it kind of bothers me not having R/W. I don't want to pay $400 more just for that, and I'd rather just go back to 4.4, if it were even possible... Maybe a little OCD hahaha.
[Moto X General] 640k:
I don't want to derail this thread too much, but the community was "shocked", in general, that 4.4 could be downgraded to 4.2.2. I don't remember the details, but I believe the binaries were similar enough to bypass the locking mechanism within the bootloader. the ability to downgrade on a locked bootloader is more times than not impossible to do. this was a flaw that was exploited by the processes you mentioned.

we're talking two different subjects. yes, manufacturers own the bootloaders as they are device specific.

what I said was

the bootloader has little to do with the OS in general. patching the OS is up to Google/Android. Moto is not accountable for patching Android but they are responsible for building a firmware that incorporates the patch provided and when it is available.
[Moto X General] mattlgroff:
Verizon Moto X (Retail) 4.4.2 firmware added to the Moto X Restore Utility. If you just want the firmware itself you can find it on sbf.droid-developers.org when it updates or grab it at http://batakang.com/ftp/MOTOX/LatestVZWFirmware.zip
[Moto X General] Mayze23:
I retained root and I agree. This is the smoothest phone I've owned thus far after the update. Everything is faster and much more fluid. The camera opens way faster after the wrist twist and the battery life is much improved. Feels like a new phone :D
[Moto X General] dverson:
Trying to take the OTA, but running into problems since rooting modified my recovery image. Had the bootloop issue, but fixed that by erasing the cache with fastboot. Now trying to flash the stock recovery in fastboot (I know, it'll probably take root away) but I'm getting errors:

$ ./fastboot flash recovery recovery.img

(bootloader) Variable not supported!

target reported max download size of 805306368 bytes

sending 'recovery' (10240 KB)...

OKAY [ 0.823s]

writing 'recovery'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 1.833s

I've got the recovery.img from the official 4.4 SBF, and everything else from it in the same directory as fastboot. Anything obvious that I'm missing?
[Moto X General] :
I couldn't flash the 4.4 recovery.img either. I could successfully flash the 4.2.2 + camera update recovery.img, so I'm guessing there was a dependency that wasn't there (maybe flash the 4.4 motoboot + boot first?)... but I'm at the point on my phone where most of my stuff is cloud sync'd, so I just said eff it, blew the phone away, put the full 4.4.2 SBF on there, and am in a happy place. I don't need root anymore, so it's easiest if I'm just fully stock with no modifications.
[Moto X General] stonesaber:
I had to flash the 4.4.2 recovery found in the zip herehttp://sbf.droid-developers.org/phone.php?device=0

because of the update borking the recovery. I kept getting an error about a security downgrade or something, but flashing that one fixed both of my x's.
[Moto X General] Mayze23:
Did you flash the recovery using flashify? Also did it break root?
[Moto X General] titanshadow:
Is it possible to get around the bricking issues by flashing everything but the bootloader via mfastboot?
[Moto X General] ConstantHero:
Flashify worked to get my recovery back after 442 on locked vzw still rooted
[Moto X General] stonesaber:
Flashed recovery through adb. I still have root. I did use supersu pro and check survival mode.
[Moto X General] titanshadow:
Are you able to make changes to the system partition after upgrading?
[Moto X General] stonesaber:
No, write protection is re-enabled. I chose to give it up when I upgraded. Unfortunately, there may be no way to upgrade and keep write protection disabled.
[Moto X General] akhenax:
I am thankful this thread exists. Is this a sticky yet?

What I have learned so far:

1. If you have a non Dev Edition of the Moto X for Verizon, and you are rooted, you should not accept the OTA for 4.4.2 or you will lose root.

2. If you want to stop being harassed about the OTA, you should go to Settings --> Apps --> All Apps and Force stop the MotorolaOTA app, and uncheck notifications.

3. You should wait until there is a 4.4.2 Stock Rom available to install via Safestrap when this method becomes available.

If any of this is incorrect, please correct. If correct, I would suggest it be added to the OP.

Thanks!
[Moto X General] xpsychox:
quick question, skimmed threw this and didn't see it but may have passed it.. anyway to get 4.4.2 to STOP poping up for download/install since i want to keep (full) root, and wifi hack?
[Moto X General] syntrix:
I have a non Dev Edition of the Moto X for Verizon, and I am rooted. I accepted the OTA for 4.4.2 and I still have root. I did check the root survival thing, and maybe something else (I mentioned in the dual thread)... but probably just the survival thing.

I did lose the ability to mount r/w the /system partition though, and that is noted many times.
[Moto X General] rocketsaucev2:
Use titanium backup or a similar app to freeze the Motorola ota.apk

-Nexus 10-
[Moto X General] akhenax:
It was stated how to do so, in the post before yours.

Settings --> Apps -- All Apps

Force stop MotorolaOTA

Remove check for notifications.
[Moto X General] akhenax:
I thought losing r/w to the system makes root useless?
[Moto X General] titanshadow:
So I tried to do some mfastboot trickery and flast only the system image from the update file. That didn't work, failed to boot. Gave an error message about the recovery partition and the system partition so... I went ahead and tried to flash the recovery and system images, that had a similar problem. It seems that one of the two (I think the system partition) does something odd to fastboot on the phone where it won't let the phone boot if there are any version mismatches present.

Anyway, I ended up manually flashing everything and completely lost root - though I was expecting it. However, odd thing, System Settings, an app for Tasker, the helper is still fully functional even without root. I'm pretty sure if I ever turn it off it'll never turn back on again so, yeah, not doing that. But the only things I lost the ability to do were Titanium Backup and change my hostname.

Not that bad, considering it is a lost smoother with 4.4.2. And since it is a nearly pure google experience I don't have to worry about flashing a custom ROM like CM. Win Win.
[Moto X General] syntrix:
I hope you aren't serious.

If so, I can wifi tether using the root wifi tether with my unlimited plan. Sure xposed won't work, but that's not the list of essentials to me... more of a nexus thing.