Database Users

[Q&A] Fixes and Questions

I have created this thread to clean up the forums a bit and to fix one confusion that most people in the forums which are saying which can mislead people to think that user means that when they don't mean that.
Q: What is the different between brick and soft-brick?
A: This is the issue I was talking about above.
A soft-brick is where you cannot access the kernel or/and rom and a brick is where you cannot access the bootloader so you cannot turn on your device unless you JTag it.
Q: Since I flashed a kernel I got stuck on the splash screen (Google logo bootloader screen), I attempted to reflash but it did not help.
A: Make sure the kernel is supported by the Rom's build number and Android version, to fix this you have to flash a supported kernel, remember that not all kernels are supported.
Q: Since I upgraded to Android 4.3 via OTA I noticed a large battery drain, WHAT IS GOING ON?!?!
A: On day 1 after the upgrade Google Backup will be using your battery for restoring your data so you will have to wait until it is done BUT then it will backup your settings such has brightness and app data but you can switch off "App Data" from the sync settings to stop Google Backup.
Q: A while/day later the issue is gone but Google Services is draining my battery.
A: That is actually Google Maps doing the draining, it is using the internet to locate you, to stop the battery drain go to Settings, Location settings, and disable WiFi & Mobile network location.
Q: Titanium Backup is not restoring my backups, what can I do?
A: Flash SuperSU v1.51 via recovery, this will fix the root issues and the Titanium Backup restore issues.
Q: Root is not working on Android 4.3, I'm panicking!!!!!!!!!!!!
A: Don't worry, flash SuperSU v1.51 has mentioned above to fix root since it now uses the SU Deamon due to the new security.
Q: The stock recovery says "No command.", what can I do?
A: Either keep pressing or hold volume up and power to unlock the menu.
This does not always work for certain users so I would try volume down and power so see if that does anything.
Q: How do I disable the OTA updater?
A: You will need root and an application, thanks to @joshuab227 for the information, the following is from joshuab227's post:
Here's how to disable the auto OTA download on any ROM
Install Autorun Manager from the Play store.
Then enter its recommended advanced mode.
Go into the settings and enable the following : system entries and system app disable.
Disable com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Click to expand...
Click to collapse
Q: The Play Store app and web store will not recognise my device!
A: @ColdEmbrace has got this issue and found the solution so that should explain why the start of the post starts how it starts:
After trying all of the above options my device was still not showing in the store. I went to this link.
play.google.com/settings
I clicked on one of my devices and clicked the update option this loaded my Nexus 4 onto the list it is now available on the web store.
Thanks everyone for the advice and I hope this helps people who are still having issues.
Click to expand...
Click to collapse
Q: My device says that I have no internet connection with a empty signal bar with or without a sim card.
A: The user @matt0401 was one of the victims with this issue and managed to fix this issue with a interesting solution:
Wow, I'm up and running! Weird fix though...
I installed the toolkit and downloaded the ROM, and was attempting to get into fast boot manually because trying to do it during the unlocking process in the toolkit wouldn't work. I thought I remembered the buttons for getting into fast boot from my old Gnex as being "hold power and volume up at same time". I tried this, and the phone went to the white "Google" logo and then vibrated, and then screen went black and the LED notifier at the bottom of the phone glowed red for about 2 seconds. The phone then rebooted, about 10x faster than before might I add, and when I was booted up I saw "No SIM detected... emergency calls only". This would infer my SIM slot was finally being detected, whereas before even with no SIM inserted I just got "No Internet Connection".
I popped my SIM in, rebooted, and the network is connected. Time to review 5 days of missed texts. Thanks for the hand!
tl;dr --> Anybody having this problem, try turning it off, and then turning it back on with the SIM inserted, holding POWER + VOL UP til it does this hard reset type fucntion. When rebooted, the problem should be resolved.
Click to expand...
Click to collapse
Q: I have to reenter my pin code for my sim every time, what do I do?
A: @lucker#1 you guessed it has the same issue has well but he wasn't the OP of the thread that the issue was discussed in but he did sure find a fix, the following is a quote from his post:
i've also had that issue the second day after receiving the phone. I removed the sim, put it back in but that didn't help - i looked at my sim card tray and i realized that a one side of the sim card chip was close to one metal side of the tray and i figured that could be the issue - so what i did is i took a stripe of adhesive tape and made sure they wouldn't touch - I haven't had the issue again and it's been more than 2 weeks.
Click to expand...
Click to collapse
Q: Since I installed Android 4.3 a few of my apps are force closing, what should I do?
A: You have to reinstall that application to fix the issue.
Q: I am getting screen flickering.
A: Flash the correct kernel which supports your Android build and version.
Q: Got a kernel panic, HALP!!!
A: That is pretty rare for the kernel to panic but you can actually easily trigger it, to fix it you must reflash the kernel (make sure it is the correct one!).
Q: Since Android 4.3 on YouTube using Slimport there is a blue graphical glitch, why is it doing that and how to fix it?
A: Since Android 4.3 there is some major bugs, improvements and fixes and the graphical glitch (I got this myself) is due to the new Software Encoder, there is no fix yet but you can go around it by using VPlayer as it apparently supports YouTube videos and it has Hardware Encoding.
If you have any questions and answers please post them here.

Bump!, Not much people are reading this...
Sent from my Nexus 4 using xda app-developers app

Bump once again and the last time.
Sent from my Nexus 4 using Tapatalk 4

[STOCK] [FTF][LOLLIPOP][C6616] 10.6.A.0.454_R1E USA compatible with C6606 T-mobile

Downloaded by Xperifirm
Repackaged by Flashtool & PRF
C6616_10.6.A.0.454_R1E_USA.ftf
MD5 : 21B83601302DA66596238F711BEAF219
Flash it with Flashtool
Flashable Zip Rooted (TWRP or CWM)
Rooted-C6616_10.6.A.0.454_R1E_USA.zip
Fully compatible with C6606 Sony Xperia Z T-Mobile.
If you flash this on Tmobile C6606
1. LTE works
2. Google Wallet Tap & Pay works
3 NO WIFI calling

So I've been using this C6616 rom on my C6606 for a few weeks or so now and everything has been working great except for low signal reception. I've read about adding the correct APN in order to use the proper T-Mobile bands, however, after trying a few different sets of settings, I"m still getting much poorer signal than when I was using the latest, official C6606 rom. Are you having any signal issues?

@hoodred
Can we Flash this over Locked Bootloader of Xperia Z T-mobile????

anumeric1122 said:
So I've been using this C6616 rom on my C6606 for a few weeks or so now and everything has been working great except for low signal reception. I've read about adding the correct APN in order to use the proper T-Mobile bands, however, after trying a few different sets of settings, I"m still getting much poorer signal than when I was using the latest, official C6606 rom. Are you having any signal issues?
Click to expand...
Click to collapse
No Signal issue
I did have problem yesterday, but after calling T-Mo, it was them repairing the tower.
I get all LTE, i did input the APN manually .
You do have to realize if you are living in T-Mo high traffic/customer area, their tower prioritize for T-Mo stock ROM phone as first priority.
C6616 is identical to C6606 all the bands are also identical.
Its basically overstock C6606 re-branded as C6616 and sold as unlocked.

TechLife said:
@hoodred
Can we Flash this over Locked Bootloader of Xperia Z T-mobile????
Click to expand...
Click to collapse
All Sony t-mobile phone bootloader are locked.
so Yes. i flashed this on my own locked bootloader T-Mo Xperia Z

hoodred said:
All Sony t-mobile phone bootloader are locked.
so Yes. i flashed this on my own locked bootloader T-Mo Xperia Z
Click to expand...
Click to collapse
Thanks.....
Please inform this is Lollipop ? 5.1 or 5.0.1....& Both ftf & zip are pre rooted ?

Tried installing. Kept getting stuck at flashing system.sin so it bricked my phone. I just reinstalled 4.4.2

MoseIlla said:
Tried installing. Kept getting stuck at flashing system.sin so it bricked my phone. I just reinstalled 4.4.2
Click to expand...
Click to collapse
That happened to me as well when I tried to flash it with the older flashtool
Flash it with the latest flashtool version 0.9.18.6

Random Reboots
Anyone else having a problem with random reboots with this ROM on the TMobile C6606. Mine will reboot out of the blue with no rhyme or reason. Tried uninstalling various apps to see if one may be the culprit but nothing so far.

Finally, an end to the madness!!!
Huge thanks to the OP, hoodred !!!
I've been looking for a solution to T-Mobile's willful negligence of us Xperia Z (C6606) customers.
Now I wanted to share my experience and I hope it helps others who bought this phone thinking T-MO would support us.
First off, I'm no expert so I'm not responsible if you brick your phone or something else goes wrong.
I'm just passing on what MY experience was and I hope you can benefit from it.
Second, I'm no expert, as I've stated, so don't expect any tech support from me. XDA is a vast resource, but it takes some work to get the results you want.
All I can tell you is to use the grey matter between your ears and research (a lot) before you proceed. Make sure you know what you're doing.
Watch some of those youtube vids that show you step by step how to flash a new ROM.
I can't (won't) guarantee that this will work, all I can tell you is that it worked for me.
*** PROCEED AT YOUR OWN RISK ***
I was able to successfully load this (the OP's) firmware onto my T-Mobile C6606 which has a locked bootloader.
Yes, I made all the checks ahead of time, I checked the service menu and it does indeed say "Bootloader unlock allowed - No"
So I thought I was boned... But I tried installing Nut's XZ Dual Recovery and that worked.
Please note that I had already rooted with Towelroot.
Once I was at this point, I backed up all my files from the internal storage and made sure everything was synced with google.
Now I was committed; I did a factory reset to clean house, then rebooted into CWM.
First off I performed a backup in CWM, it took about 8 minutes.
Then, in CWM, I cleaned cache, cleaned dalvic, then did the "prep for new ROM option."
Once that completed, I had CWM install from the zip file from the OP, not the FTF (although I suppose that's another way to go...)
Flashing the new ROM was pretty quick and I just rebooted after.
First boot with the new ROM took a little longer, but it wasn't extremely long, I don't think it took more than 5-10 minutes.
Once it got to the new phone setup, I knew I was home free.
I entered my WiFi settings and google account and it just finished updating everything else on its own.
SuperSU was pre-installed so I didn't have any problem with TiBackup or any other rooted apps.
I hope this helps some of you T-Mobile people with one of these phones. I was going nuts waiting for them to release an update but that's just crazy.
I can't tell you how happy I am to finally be on LP. It's on 5.0.1 right now and I've experienced no real issues.
The phone got moderately hot due to downloading so much data over the WiFi and all the processing and setup but otherwise, it's been excellent.
The phone now says that it's a C6616 everything seems to work correctly:
Mobile Bravia Engine, WiFi, Bluetooth, GPS, mobile data (I'll check APN's today just to verify settings...), camera, etc. I haven't come across any faults, but I'll update if I do.
Big thanks to Sony for keeping their word and supporting their customers, Great job, Sony!
Thanks again to hoodred !!! You Rock!

BeachBum68 said:
Thanks to the OP!!! I've been looking for a solution to T-Mobile's willful negligence of us Xperia Z (C6606) customers.
Now I wanted to share my experience and I hope it helps others who bought this phone thinking T-MO would suport us.
First off, I'm no expert so I'm not responsible if you brick your phone or something else goes wrong.
I'm just passing on what MY experience was and I hope you can benefit from it.
Second, I'm no expert, as I've stated, so don't expect any tech support from me. XDA is a vast resource but it takes some work to get the results you want.
All I can tell you is to use the grey matter between your ears and research (a lot) before you proceed. Make sure you know what you're doing.
Watch some of those youtube vids that show you step by step how to flash a new rom.
I can't (won't) guarantee that this will work, all I can tell you is that it worked for me.
*** PROCEED AT YOUR OWN RISK ***
I was able to successfully load this (the OP's) firmware onto my T-Mobile C6606 which has a locked bootloader.
Yes, I made all the checks ahead of time, I checked the service menu and it does indeed say "Bootloader unlock allowed - No"
So I thought I was boned... But I tried installing Nut's XZ Dual Recovery and that worked.
Please note that I had already rooted with Towelroot.
Once I was at this point, I backed up all my files from the internal storage and made sure everything was synced with google.
Now I was committed; I did a factory reset to clean house, then rebooted into CWM.
First off I performed a backup in CWM, it took about 8 minutes (.
Then, in CWM, I cleaned cache, cleaned dalvic, then did the "prep for new ROM option."
Once that completed, I had CWM install from the zip file form the OP, not the FTF (although I suppose that's another way to go...)
Flashing the new rom was pretty quick and I just rebooted after.
First boot with the new rom took a little longer, but it wasn't extremely long, I don't think it took more than 5-10 minutes.
Once it got to the new phone setup, I knew I was home free.
I entered my WiFi settings and google account and it just finished updating everything else on it's own.
SuperSU was pre-installed so I didn't have any problem with TiBackup or any other rooted apps.
I hope this helps some of you T-Mobile people with one of these phones. I was going nuts waiting for them to release an update but that's just crazy.
I can't tell you how happy I am to finally be on LP. It's on 5.0.1 right now and I've experienced no real issues.
The phone got moderatly hot due to downloading so much data over the wifi and all the processing and setup but otherwise, it's been excellent.
The phone now says that it's a C6616 everything seems to work correctly: Mobile Bravia Engine, WiFi, Bluetooth, GPS, mobile data (I'll check APN's today just to verify settings...), camera, etc. I haven't come across any faults but I'll update if I do.
Big thanks to Sony for keeping their word and supporting their customers, Great job, Sony!
Thanks again to the OP!!! Such a great help.
Click to expand...
Click to collapse
Check the APN settings. Had to adjust mine for LTE to work. Also try using STAMINA power saving mode after you're satisfied with your setup. As I posted above I have had a random reboot issue since flashing over to this ROM. After tinkering around I think I have found STAMINA to be the problem. I be interested to see if anyone else experiences this. Love the ROM anyhow, totally agree with you thanks Sony. :good:

rhodemaster said:
Anyone else having a problem with random reboots with this ROM on the TMobile C6606. Mine will reboot out of the blue with no rhyme or reason. Tried uninstalling various apps to see if one may be the culprit but nothing so far.
Click to expand...
Click to collapse
Its due memory leak bugs on lollipop affecting stamina mode among other things.
Especially if you have tons of apps running in the background.
Even though Stamina mode killing or hibernatimg the apps, due to the bugs the it didnt clear the memory fast enough.
Its Google fault not Sony
It will get fixed once its updated to 5.1.1
First it get sluggish than it will reboot to clear up the memory.
Use Greenify instead, it'll help to a point or xposed lollipop memory bugs fix

BeachBum68 said:
Huge thanks to the OP, hoodred !!!
I've been looking for a solution to T-Mobile's willful negligence of us Xperia Z (C6606) customers.
Now I wanted to share my experience and I hope it helps others who bought this phone thinking T-MO would support us.
First off, I'm no expert so I'm not responsible if you brick your phone or something else goes wrong.
I'm just passing on what MY experience was and I hope you can benefit from it.
Second, I'm no expert, as I've stated, so don't expect any tech support from me. XDA is a vast resource, but it takes some work to get the results you want.
All I can tell you is to use the grey matter between your ears and research (a lot) before you proceed. Make sure you know what you're doing.
Watch some of those youtube vids that show you step by step how to flash a new ROM.
I can't (won't) guarantee that this will work, all I can tell you is that it worked for me.
*** PROCEED AT YOUR OWN RISK ***
I was able to successfully load this (the OP's) firmware onto my T-Mobile C6606 which has a locked bootloader.
Yes, I made all the checks ahead of time, I checked the service menu and it does indeed say "Bootloader unlock allowed - No"
So I thought I was boned... But I tried installing Nut's XZ Dual Recovery and that worked.
Please note that I had already rooted with Towelroot.
Once I was at this point, I backed up all my files from the internal storage and made sure everything was synced with google.
Now I was committed; I did a factory reset to clean house, then rebooted into CWM.
First off I performed a backup in CWM, it took about 8 minutes.
Then, in CWM, I cleaned cache, cleaned dalvic, then did the "prep for new ROM option."
Once that completed, I had CWM install from the zip file from the OP, not the FTF (although I suppose that's another way to go...)
Flashing the new ROM was pretty quick and I just rebooted after.
First boot with the new ROM took a little longer, but it wasn't extremely long, I don't think it took more than 5-10 minutes.
Once it got to the new phone setup, I knew I was home free.
I entered my WiFi settings and google account and it just finished updating everything else on its own.
SuperSU was pre-installed so I didn't have any problem with TiBackup or any other rooted apps.
I hope this helps some of you T-Mobile people with one of these phones. I was going nuts waiting for them to release an update but that's just crazy.
I can't tell you how happy I am to finally be on LP. It's on 5.0.1 right now and I've experienced no real issues.
The phone got moderately hot due to downloading so much data over the WiFi and all the processing and setup but otherwise, it's been excellent.
The phone now says that it's a C6616 everything seems to work correctly:
Mobile Bravia Engine, WiFi, Bluetooth, GPS, mobile data (I'll check APN's today just to verify settings...), camera, etc. I haven't come across any faults, but I'll update if I do.
Big thanks to Sony for keeping their word and supporting their customers, Great job, Sony!
Thanks again to hoodred !!! You Rock!
Click to expand...
Click to collapse
Your Welcome
Since you flash the rooted version DO NOT UPDATE THE BUSYBOX
the busybox created specifically for SONY device.
All other busybox are not compatible with Sony xperia z line and you will lose RW on the system partition.

Busybox blunder
Didn't know that... What can I do to fix that if I did that? I literally just did that today... Can I undo this somehow?
Regards
---------- Post added at 01:50 AM ---------- Previous post was at 01:42 AM ----------
Almost a week update: Ok, I did experience some random reboots but a lot of that was caused because of two reasons: First, location by default sets that damn GPS on by default. That caused some major overheating until I turned that off.
Second, I had frozen quite a lot of apps with TiBackup. Lollipop didn't like that, got near constant reboots until I defrosted everything and was more... selective. It's been much better behaved, but it still happens occasionally. I'll need to investigate further.
These are relatively minor issues compared to the major goodness and improvements... I'll take that any day.
I did reinstall Nut's XZ Dual Recovery, that also installs and works flawlessly.
---------- Post added at 01:54 AM ---------- Previous post was at 01:50 AM ----------
Thanks, I tried Greenify as well and that did make a huge difference. Any thoughts on the 5.1.1 update?
Thanks.

BeachBum68 said:
Didn't know that... What can I do to fix that if I did that? I literally just did that today... Can I undo this somehow?
Regards
---------- Post added at 01:50 AM ---------- Previous post was at 01:42 AM ----------
Almost a week update: Ok, I did experience some random reboots but a lot of that was caused because of two reasons: First, location by default sets that damn GPS on by default. That caused some major overheating until I turned that off.
Second, I had frozen quite a lot of apps with TiBackup. Lollipop didn't like that, got near constant reboots until I defrosted everything and was more... selective. It's been much better behaved, but it still happens occasionally. I'll need to investigate further.
These are relatively minor issues compared to the major goodness and improvements... I'll take that any day.
I did reinstall Nut's XZ Dual Recovery, that also installs and works flawlessly.
---------- Post added at 01:54 AM ---------- Previous post was at 01:50 AM ----------
Thanks, I tried Greenify as well and that did make a huge difference. Any thoughts on the 5.1.1 update?
Thanks.
Click to expand...
Click to collapse
re-install the dual recovery and you will get the System RW (RIC killer script) and busybox back
http://nut.xperia-files.com/
look for XZ locked dual recovery latest version
You can either use the flashable zip or installer.
They just done updating Z2 andZ3 to 5.1.1 xperia z is next. probably by mid-end of august

Thanks!
Created an account just to say thank you to everyone that put in time to get this available to us and for the recommendation.
Flashed this onto my C6606 T-Mobile branded Sony Xperia Z. I'm using MetroPCS in the US.
Was a bit of trial and error with the Flashtool drivers [needed to disable the Windows 8 driver signature verification]. Also had trouble with the procedure [starting the Flash, turning off the phone, disconnecting it, reconnecting it with the volume down button pressed].
Everything seems ok though. The battery life is actually better when in standby mode. The responsiveness seems improved. Seems like a new phone.

rhodemaster said:
Anyone else having a problem with random reboots with this ROM on the TMobile C6606. Mine will reboot out of the blue with no rhyme or reason. Tried uninstalling various apps to see if one may be the culprit but nothing so far.
Click to expand...
Click to collapse
Yes...I am having the same random reboot issue since flashing the C1616 5.0.2 ftf on my C6606 with the newest 9.18 of flastool.

Schmidt2010 said:
Yes...I am having the same random reboot issue since flashing the C1616 5.0.2 ftf on my C6606 with the newest 9.18 of flastool.
Click to expand...
Click to collapse
If your phone unrooted, ROOT it and iinstall xposed memory leak fix module or use greenify it help to a point

Does the Xposed framework install on Lollipop? I thought there was a big problem with that.
Also, what the heck is up with the write permissions to the sdcard?
What a pain in the a**. Definitely has been causing problems for some apps...
Turn off stamina mode and use greenify, that's worked wonders for me. I also turn off auto sync until I leave work. That saves my battery a bit.
Sent from my C6616 using XDA Free mobile app

BeachBum68 said:
Does the Xposed framework install on Lollipop? I thought there was a big problem with that.
Also, what the heck is up with the write permissions to the sdcard?
What a pain in the a**. Definitely has been causing problems for some apps...
Turn off stamina mode and use greenify, that's worked wonders for me. I also turn off auto sync until I leave work. That saves my battery a bit.
Sent from my C6616 using XDA Free mobile app
Click to expand...
Click to collapse
Xposed
http://forum.xda-developers.com/showthread.php?t=3034811
memory leak module
https://play.google.com/store/apps/details?id=com.thetonyp.fixlollipopmemoryleak&hl=en
Sd card write permission
Use any root explorer eg.. ES file explorer
/system/etc/permissions/platform.xml
look for
name="android.permission.WRITE_EXTERNAL_STORAGE"
and add
<group gid="media_rw"/>
save and reboot

Service Provider Update after Root

I have followed the guide to flash the unlocked firmware and root my S7 Edge (http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145) and all has been working well this weekend. This morning my phone gives me a persistent popup notification about a service provider update and "my device will restart to configure features supported by new sim card." The only option is to press ok and allow it to reboot. I cannot use my phone while this notification is active, and I am unable to kill it in any way. When the phone reboots to recovery, the configuration fails with "dm-verity verification failed". I then reboot system or power off and the endless cycle continues.
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.

I wasn't getting any notifications however i did have some strange behavior going on and rebooted only to get the dm-verity verification failed and was no longer able to boot it would just sit at the Samsung splash screen I then had to factory reset re-post and re-setup everything, hopefully your experience won't need that since you are still able to boot!
Sent from my SM-G935U using Tapatalk

Thank you for the response, it's always nice to know someone has had similar problems. Looks like I will have to try reflashing the firmware. After your re-setup, did you do anything to prevent the issue from reoccurring?

Everything is again in working order. If anyone finds this and has the same problem, after flashing the Verizon fixes the phone is identified (in the about device setting) as the SM-G935V version again and is set to download updates automatically. I unchecked this option and I hope this should prevent it from happening again.

Not really wasn't sure exactly what happened the first time but thankfully (knock on wood) ??? it hasn't happened again.
Sent from my SM-G935V using Tapatalk

mine did it too. had to reinstall the whole thing.

drmatthews1 said:
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
Click to expand...
Click to collapse
shawnten said:
mine did it too. had to reinstall the whole thing.
Click to expand...
Click to collapse
I encountered this issue today and found a solution:
http://forum.xda-developers.com/galaxy-s7/help/whats-package-service-provider-update-t3425169

This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!

Dameon87 said:
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Click to expand...
Click to collapse
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?

thedrizzle said:
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
Click to expand...
Click to collapse
This has been my experience, as well as a few others. I'm not 100% sure it's that setting in particular, but I am 100% sure that it is caused by a setting in xTouchWiz. I had the issue once before, and it was a clean install save for xTouchwiz and me running through all the options. Since then, I've limited the choices in xTouchwiz and have not experienced the issue since. When I have some time I'll run through it and see if I can replicate the behavior again, since I'm working on a ROM.

There is a simple fix...
I agree, XtouchWiz drops a bomb when installed and it will cripple your phone. I never played with DVFS, I personally though it was the disable TIMA that set it off. An easy fix for anyone who stumbled on this. Power off your phone, remove the sim card, power up your phone, freeze a service called AutoPreconfig, power down and insert sim, good to go.
More info http://forum.xda-developers.com/gal...ge-service-provider-update-t3425169?nocache=1
Shout out to Wired4Fun for this easy fix.

[Rom] Mokee 7.1.2 for Lenovo Vibe Shot

https://download.mokeedev.com/?device=zoom

Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..

X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.

stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this

X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good

stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?

Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?

linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.

Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.

@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..

GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)

has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.

mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing

Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.

The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st

bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?

hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?

Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?

Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.

Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?

Jan 2020 update summary

Gang,
Just a recap about the Jan 2020 update for Pixel devices.
Functional updates: https://support.google.com/pixelphone/thread/24852169 (incl. some wi-fi stability fixes)
Security updates: https://source.android.com/security/bulletin/pixel/2020-01-01
Our Pixel 2 XL got a ~9.1MB update, which in my opinion (and my user experience) shows how stable it is nowadays.

arturiu said:
Gang,
Just a recap about the Jan 2020 update for Pixel devices.
Functional updates: https://support.google.com/pixelphone/thread/24852169 (incl. some wi-fi stability fixes)
Security updates: https://source.android.com/security/bulletin/pixel/2020-01-01
Our Pixel 2 XL got a ~9.1MB update, which in my opinion (and my user experience) shows how stable it is nowadays.
Click to expand...
Click to collapse
Yeah it is pretty stable barring few issues like lock screen sound is gone. WiFi still keeps dropping for me at times.

100rabh7791 said:
Yeah it is pretty stable barring few issues like lock screen sound is gone. WiFi still keeps dropping for me at times.
Click to expand...
Click to collapse
I never had noticeable wifi issues with my phone, both at 2.4 and 5 GHz networks, at home, work or traveling. I'm on stock ROM.
There could be a few toxic combinations of AP model, network and channel which may cause instability, but I never noticed that.

arturiu said:
I never had noticeable wifi issues with my phone, both at 2.4 and 5 GHz networks, at home, work or traveling. I'm on stock ROM.
There could be a few toxic combinations of AP model, network and channel which may cause instability, but I never noticed that.
Click to expand...
Click to collapse
Oh, and my lock/unlock sounds work as expected. I never had to reset the device, though, and that seems to be one of the root causes.

arturiu said:
I never had noticeable wifi issues with my phone, both at 2.4 and 5 GHz networks, at home, work or traveling. I'm on stock ROM.
There could be a few toxic combinations of AP model, network and channel which may cause instability, but I never noticed that.
Click to expand...
Click to collapse
i think it is more related to how i hold the phone. i think i disrupt the antenna signal. I m not sure however.

100rabh7791 said:
Yeah it is pretty stable barring few issues like lock screen sound is gone. WiFi still keeps dropping for me at times.
Click to expand...
Click to collapse
See this article and thread to get lock and other sounds back.
https://www.xda-developers.com/how-to-fix-charging-end-call-sounds-google-pixel-android-10-update/
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-fix-androidq-unlocking-sound-bug-t3989657

I passed on the December update due to the new Gestures crashing - and the inevitable factory reset.
Does anyone know whether I can update from November to January without having to factory reset?
Cheers!

Langduscher said:
I passed on the December update due to the new Gestures crashing - and the inevitable factory reset.
Does anyone know whether I can update from November to January without having to factory reset?
Cheers!
Click to expand...
Click to collapse
Sure you can. Just fastboot the January factory image with the -w removed from the flash-all.bat file. Make sure to disable all magisk modules and substratum themes first, set your screen lock to swipe, and update your platform-tools. And there ya go :good:

Badger50 said:
Sure you can. Just fastboot the January factory image with the -w removed from the flash-all.bat file. Make sure to disable all magisk modules and substratum themes first, set your screen lock to swipe, and update your platform-tools. And there ya go :good:
Click to expand...
Click to collapse
Cheers for your swift reply Badger!
What I really meant was: with Nov to Dec, new gestures were broken and required a factory reset to get to normal state.
What I'm looking for is if I flash -w, will it still break gestures to the point of a needed factory reset? Or can I update/ flash -w and not having to factory reset?
Cheers!

Langduscher said:
Cheers for your swift reply Badger!
What I really meant was: with Nov to Dec, new gestures were broken and required a factory reset to get to normal state.
What I'm looking for is if I flash -w, will it still break gestures to the point of a needed factory reset? Or can I update/ flash -w and not having to factory reset?
Cheers!
Click to expand...
Click to collapse
Hard to say my friend. Month to month builds are comprehensive and inclusive. I would first try fastbooting without the -w first so you don't wipe data. If the problem persists, then do a factory reset, which you would do anyway if you did a clean fastboot install. Here is a list of fixes for January if that helps at all. https://support.google.com/pixelphone/thread/24852169?hl=en :good:

Badger50 said:
Hard to say my friend. Month to month builds are comprehensive and inclusive. I would first try fastbooting without the -w first so you don't wipe data. If the problem persists, then do a factory reset, which you would do anyway if you did a clean fastboot install. Here is a list of fixes for January if that helps at all. https://support.google.com/pixelphone/thread/24852169?hl=en :good:
Click to expand...
Click to collapse
My gestures are really glitchy and i frequently get defaulted back to the pixel launcher from my action launcher which supports the Android 10 gestures. I also get a lot of freezes/delays. I was running stock with magisk and kirasukura kernel. So I backed up my entire SD to my PC and now Im about to do a full wipe (keeping the -w in the flashall.bat file) and start android 10 fresh. For me its been long overdue.

Langduscher said:
Cheers for your swift reply Badger!
What I really meant was: with Nov to Dec, new gestures were broken and required a factory reset to get to normal state.
What I'm looking for is if I flash -w, will it still break gestures to the point of a needed factory reset? Or can I update/ flash -w and not having to factory reset?
Cheers!
Click to expand...
Click to collapse
I did the Nov/Dec update and didn't notice any gestures issues. What specific issues did you found ?

I installed a clean flash (full factory Image) of the January update. There major takeaways:
1) Titanium Backup does not batch restore files....at least not for app+data. I had to choose either small batch clusters to restore or do them one by one or download from the play store and restore data using Tb. Super PITA. Not sure why this doesn't work anymore.
2). Doing the clean wipe fixed a feature I was having issues with. RCS was not working on my corporate WiFi but it does now.
3). Unfortunately now all my notifications (including the incoming call screen) now come thru as a heads-up/peek notification and if I turn that off I get no notifications at all!! I can't figure out how to get normal notifications back. It is really frustrating.
Anyone else notice these thing or now how to fix them?

bsg411 said:
I installed a clean flash (full factory Image) of the January update. There major takeaways:
1) Titanium Backup does not batch restore files....at least not for app+data. I had to choose either small batch clusters to restore or do them one by one or download from the play store and restore data using Tb. Super PITA. Not sure why this doesn't work anymore.
2). Doing the clean wipe fixed a feature I was having issues with. RCS was not working on my corporate WiFi but it does now.
3). Unfortunately now all my notifications (including the incoming call screen) now come thru as a heads-up/peek notification and if I turn that off I get no notifications at all!! I can't figure out how to get normal notifications back. It is really frustrating.
Anyone else notice these thing or now how to fix them?
Click to expand...
Click to collapse
I think 1) is a known problem; I've had this issue on both stock and custom roms. TiBU needs to update for Q; with respect to 3), when my screen is locked and i receive a phone call, it shows the incoming call screen. Check out your settings>apps & notifications and see if you don't have something toggled off.

Is anyone having trouble, with using Magisk, on the latest update?

jlokos said:
I think 1) is a known problem; I've had this issue on both stock and custom roms. TiBU needs to update for Q; with respect to 3), when my screen is locked and i receive a phone call, it shows the incoming call screen. Check out your settings>apps & notifications and see if you don't have something toggled off.
Click to expand...
Click to collapse
I've been tweaking the app&notification settings for 2 days now.....can't figure it out. Hopefully something will work.

Droid_Nut said:
Is anyone having trouble, with using Magisk, on the latest update?
Click to expand...
Click to collapse
Working fine for me on stock (Magisk 20.3; Magisk Manager 7.5.1).

Lughnasadh said:
Working fine for me on stock (Magisk 20.3).
Click to expand...
Click to collapse
Great thanks for the heads up. :highfive: