Related
EDIT: Here's a verbose log that was being recorded before the device rebooted as explained below. It happened 2 seconds after I locked the screen with the lock key...
http://www.fast-files.com/getfile.aspx?file=74248
I know it's a big file, and it's long but it does open in regular Notepad, just wait 40 seconds. Hopefully you can find the cause at the bottom of the log. I can't make sense of it.
---------------------------------------------------------------------------------------------------------------
Hey guys, any idea how to find out why my S4 seems to be rebooting every few hours, mostly after being woken up?
Some tech info:
Baseband: I9505XXUGNE5
Stock Kernel
SE For Android: Enforcing
Build Number: KOT49H.I9505XXUGNE5
Phone is rooted & Xposed installed
Quick bit of info:
It seems to happen 90% of the time when the screen goes off. By this I mean, the screen can go off no problem and then I can turn it back on without an issue. However if the phone does reboot, it seems to be when the phone is woken up after being locked/asleep. However it does happen sometimes whilst I am using the phone. Though very rarely.
It's also important to note that the phone does a 'fast reboot', not a regular one. Like it skips the 'Samsung Galaxy S4' screen and just goes straight to the spinning logo. It does reboot very fast, but it is really annoying.
However I don't have to put my SIM PIn in again, it just asks for my phone PIN and then starts to load apps as normally.
Is there some sort of App I can install that will log all errors right up to the point where it crashes. Then I could view the log and work out what caused the crash? I have the Donate of aLogcat but it doesn't seem to allow me to do this...
Any ideas guys? Any info would be absolutely awesome.
I really don't mean to bump guys but I've flashed 3 times now and still get reboots...
Could I need to flash a new boatloader or something?
The download is to slow. Just post your log in pastebin and post the link here.
What I would do in your case is to fully wipe (also wipe your sd card) and return to a clean rom. Don't install any apps, dont restore backups and see if the problem persists.
If even with a fress install you have to issues, then it's a hardware issue.
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I updated the post HERE if somebody is interested. More KNOX remains to freeze or delete
leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I would suggest performing a factory reset before freezing the Knox stuff. That way you have a clean start.
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
wild wadi said:
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
Click to expand...
Click to collapse
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Lennyz1988 said:
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Click to expand...
Click to collapse
Chainfire asked in another post people who are experiencing these reboots to list their installed root apps which I sent to him.
http://forum.xda-developers.com/showthread.php?t=1538053&highlight=random+reboot&page=551
Maybe it is SdFix. I will check that out but, I would like to know if others who are experiencing reboots here have SdFix installed or maybe to list their installed root apps (like Chainfire suggested) so we can compare notes as to who is and who is not experiencing random reboots.
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
You have to uninstall every Knox app, that will stop the reboots
Sent from my Galaxy S4 using Tapatalk
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Remove all Knox related apps via "Titanium Backup" and you are good to go. :good:
there is also an xposed module that deals with these random reboots, but personally i think the best way is to revert to an earlier firmware. fnb8 is rock solid.
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Yes
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to xxufnb9 ?
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
nm8 said:
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Click to expand...
Click to collapse
wuwinso said:
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to UGNF ?
Click to expand...
Click to collapse
juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
yup same here after reading this thread and removing all knox crap.... phone has not had a self reboot reboot for the day...
Revert
Had to reflash the old XXUFNB9, it was useless with all those restarts. Downgrade went okey, however need to delete the Media Storage `s cache because it will keep crashing. Testing now if it solved the problem.
Update 1: after 2 hours later no restart so far..
I recommend this solution who doesn`t want to loose everything and risking if a factory reset will solve this issue. There is a problem with the KNOX 2.0 update (XXUGNG8) ...
Update 2: Link for the firmware, for whoever choose to do this way: http://www.sammobile.com/firmwares/3/?download=31852
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
nm8 said:
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
Click to expand...
Click to collapse
Stabil for 3 hours or 2 days - well that's for sure great ....
You both must be joking - take older NB8 and you can have an uptime of > 1 month without any problem,
All newer version are worse -
As s.o. mentioned, there is an Xposed Modul made by Thomas Hofmann that tries to solve this. This is not a Knox problem but seems to be in AOSP itself - although might mainly be triggered by Knox 2.0 (NB8 is still Knox 1.0). In general situation goes worse the more processes are started, i.e. with heavy load. It is said to happen not only with S4 but e.g. also with N3.
As Thomas Hofmann stated: "I figured out that actually the system server process crashed due to an ArrayIndexOutOfBoundsException"
If you want to know details plz have a look at Thomas's blog. With his modul he mainly catches a faulty parameter value that would otherwise cause a certain method to crash. As a result he manages to avoid the reboot but of course the real problem goes deeper, so to fix this for real Google / Samsung are needed.
=> I want a 4.4.4 rom with towelroot fixed, without those ArrayIndexOutOfBoundsExceptions and as solid as NB8 - but I doubt Samsung is able or willing to do this.
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
nm8 said:
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Click to expand...
Click to collapse
no random rebooting anymore xugng8 firmware
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
i have sorted my i9505 to the xugng8 firmware by re-installing with latest odin...download fresh stock firmware xugng8 firmware and i re-installed 2 weeks now no reboot ,but make sure before you do these steps usb debuging mode is selected ,rest you all know
nm8 said:
I don't use towelroot because I don't have to.
Click to expand...
Click to collapse
Yes, many think this to be a nice 'feature' to get root, but that rediculous. Towelroot (plus the older Exynos bug - but that was Samsung specific) is the biggest bug in Android since many years. Using a kernel that is not hardened against this (this unfortunately includes the otherwise almost perfect NB8 rom) could mean you couldn't be save anymore from someone taking over your phone unnoticed using root authorization.
---------- Post added at 02:20 PM ---------- Previous post was at 02:08 PM ----------
juzzy16 said:
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
Click to expand...
Click to collapse
As said those reboots most certaintly are caused by a bug in AOSP code itself - but in fact they seem to be mainly triggered by Knox 2.0. Otherwise a lot more phones other than S4 or N3 should be involved.
As we will never know fpr sure if and when Google/Samsung will solve the real reason of this problem and "removing" Knox 2.0 seems to help, it would be very nice of you (juzzy16, nm8, sneazy) to perhaps add another comment in 2-3 weeks about reboot behaviour again including the rom version you are using and what exactly of Knox you had removed.:good:
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
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.
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others
Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.
This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps