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

!!!Stop SAMSUNG GALAXY S3 FREEZING Problems!!!

Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.

Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom

kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:

Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...

what?
i havent got this

Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.

jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?

Read the freezing thread sticky .
Delete this non working fix as well .

JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?

Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.

Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.

[Q] Advice Please - Mobile Odin - Could not detect device model - USB not recognizing

Hi all, hoping to get some advice in regards to a brick wall I've hit.
So background, my Galaxy S4 (i9505 running 4.2.2) has had ongoing USB recognition issues and thus I haven't been able to upgrade to a custom rom for a while. After following a couple of very detailed and useful guides on here, without success I had decided that it was likely one of two things:
A hardware problem (I have a third party charging port installed after the OEM stopped working)
Or when I was playing around with settings I derped and uninstalled the MTP application or some related core service.
So I left it for a while but today I decided to do something about it and discovered Mobile Odin (4.20), bought it and clean flashed SlimKat 4.4.4 (http%www%slimroms%net/index.php/downloads/dlsearch/viewcategory/1182-jflte). Took a while but the rom booted, really liked the look and I tried to install 3rd party apps and set up phone as usual but noticed that Google Play Store was missing. Manually installed V4.9 but it kept opening and closing so I uninstalled and the flashed the normal gapps and the AIO gapps through Mobile Odin (with and without clear cache), both processed OK but upon reboot none of apps ever installed.
So I decided to re-flash the SlimKat, I had to re download as I performed a factory restore in amongst things and had the original rom stored on internal. When I flashed inject root was checked as were all the other default options but upon reboot Mobile Odin is giving me "Could not detect device model" which after looking around basically means I lost root .
So my questions are: Without connecting via USB (because it's still not working) what are my options for flashing another rom or regaining root? Is there a way to get to stock 4.4.4 without USB?
Really appreciate any advice, currently the phone has network service and WiFi so in the mean time, without Google Play store it is just a significant inconvenience, but still operational.
Regards,
Marc
#Update
I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat 4.4.4 but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.

Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?

lichking21st said:
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
Click to expand...
Click to collapse
Hey @lichking21st. Mobile Odin is allegedly just odin without the need for USB. I have tried to fix the USB to no avail
Actually just about to update my original post, I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.

Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing

grinchenator said:
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
Click to expand...
Click to collapse
Glad to see your problem is fixed, I would still advise you to get a custom recovery so you have some options if you really get stuck without root for next time. I recommend using TWRP but CWM works too.

[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

RIL disapperaring sometimes

Hi guys, I have to clear my mind on a problem:
I have a XT1562 european mono-SIM Moto X Play, and I've upgraded it to Marshmallow (the indian dual-SIM firmware) after unlocking the bootloader and flashed Squid kernel some weeks ago (and then updated to the last build, of course).
Sometimes I'm experiencing an annoying thing: after a reboot RIL dies, and on the best, on the next reboot it reappears; on the worst, after multiple reboots with no luck, I have to do a wipe cache to see it again.
I have root and Xposed (and so, also busybox).
Is anyone experiencing something similar?
There's a way to fix it that maybe I didn't find here on XDA?

Nobody?

have u tried flashing the modem for ur rom?

anks095 said:
have u tried flashing the modem for ur rom?
Click to expand...
Click to collapse
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.

nplezka said:
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
Click to expand...
Click to collapse
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.

anks095 said:
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
Click to expand...
Click to collapse
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...

nplezka said:
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
Click to expand...
Click to collapse
I don't know if this is the same thing as you but I had "Emergency Calls Only" sporadically as well but it would come back either after a short period of time or after a reboot. I also had random reboots too (didn't matter which ROM I was on at the time).
I lived with this for a bit but then upgraded my SD card (it was old) and I haven't had either problem since.
My guess is that my SIM card might not've been seated properly in the little carrier and/or the SD card I had was mucking things up somehow. I wasn't using it as internal storage either.
Anyways, if you haven't tried this already, might be worth taking out your SIM card and re-seating it (and maybe give the contact part a careful wipe). If you still have the problem and you have an SD card remove it and see what happens. Good luck!

Hi guys! I'm here with news:
after several tests in these days, I discovered the problem was every module that can modify the systemUI.
I tried activating and disabling those modules one by one (I'm talking about GravityBox first, then little modules like Advanced Power Menu or a newer one called NeoPowerMenu), and I saw that without them, I had network at every reboot. The only exception in systemUI is SignalIconsAOSP (I really hate that big "4G" icon next to the signal indicator) and it works at every reboot I did. The other modules (like Xposed GEL Settings, Lolistat, YouTube AdAway) don't annoy the system.
So, I don't know, Moto seems dislike too much modifications on the UI or it's a strange bug. Maybe a bug.