Database Develop

[Root] [Recovery] [Wipe-optional] 4.4.4 KitKat SGP311/312 10.5.1.A.0.283 VMo US, EU1

Xperia Tablet Z 4.4.4 KitKat Rom - Pre-rooted - Includes Recovery
For SGP311 and SGP312 - Wiping is optional​
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
Requirements:
Flashtool 0.9.15.0 or higher
Rooted SGP31X (on any other previous Android version) with custom recovery (i.e. XZDualRecovery) installed.
Previous firmwares up to 4.4.2 can be rooted with towelroot.
If your current Rom doesn't have recovery, follow step 10 of this post: http://forum.xda-developers.com/showpost.php?p=53063218&postcount=14 with tablet in USB debugging mode (step 4 of the same post).
This works on locked or unlocked bootloaders and any customization.
This ROM is pre-rooted and comes with recovery. Other than that it is identical to stock rom.
Download links:
SGP311 US_CA_PR https://mega.co.nz/#F!dhMBkRpC!qAsRR7WXJlKwsUwBuv1vig
SGP311 EU1 https://mega.co.nz/#F!p4FzQaqQ!o88OJPX4SyAYOUM3PMb5_A
SGP312 US_CA_PR https://mega.co.nz/#F!El8QnQxC!BlkadNT5FWGF3dLfCbD4mA
Use the link that matches your tablet model. You only need the zip and ftf files. The txt file is just the checksum if you want to verify that your download is error-free.
Instructions:
0- Backup before you start messing with your tablet!
1- Put system.flashable.zip in /sdcard of your tablet.
2- Keep SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf on your PC.
3- Disconnect any USB cable that may be attached to your tablet.
4- Reboot to recovery. Preferably to TWRP, but you can make CWM work too.
5- Do not wipe anything.
6- Once in recovery, flash system.flashable.zip.
7- It is important to TURN OFF the tablet after this step.
8- Find and use the Power Off option in the recovery and turn your tablet off. In CWM based PhilZ Touch it is under "Power Options" -> "Power Off". In TWRP it is under "Reboot" -> "Power Off". If you see your tablet rebooting, force it to turn off by pushing the power and volume up keys simultaneously (or however else you can!)
9- Open Flashtool 0.9.15.0 (or higher) and click on the flash icon. Choose flash mode.
10- Navigate to where you have saved SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf
11- If you do not want your any of your current data to be wiped uncheck all the items under the "wipe" section. My recommendation however is to wipe.
12- Now flash this ftf with your tablet in flash mode. To put your tablet in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
13- Reboot. You are now on rooted 4.4.4.
Credits:
I only put the files together. All the credit should go to XDA's [NUT] and DooMLoRD and many others...

Can I flash this on SGP312?

Kindly request if you could make also a flashable zip with any European rom

FiDra said:
Can I flash this on SGP312?
Click to expand...
Click to collapse
You can and it is not going to break your tablet but there are small differences between the two fimwares. I added a link for SPG312 too.

nick2crete said:
Kindly request if you could make also a flashable zip with any European rom
Click to expand...
Click to collapse
I can try when I have time. PM to me your model and your customization code.

Flashed and works good on SGP312
Thanks!

It worked perfect !
Thank you very much !

I wasn't going to update to 4.4.4 until you offered this solution. Swapping kernels,etc., re-rooting, reinstalling recovery was just more work than it was worth and had the potential to brick the device. Your approach is brilliant! Thank you very much.
However, I am not able to boot into recovery.

Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.

Working on 311

najoor said:
OP!!
Click to expand...
Click to collapse
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?

Shanliang- said:
Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.
Click to expand...
Click to collapse
How is it performing for you compared to omni rom?

cantenna said:
How is it performing for you compared to omni rom?
Click to expand...
Click to collapse
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.

Shanliang- said:
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.
Click to expand...
Click to collapse
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us now

cantenna said:
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us know
Click to expand...
Click to collapse
yep! it's possble with BackupTA.

I'm surprised to hear there is occasional static sound with a stock ROM from Sony. Can you pleas elaborate as to the problem?
Also, if I follow this tutorial will it automatically relock my boot loader? I'd prefer to keep an unlocked boot loader until I have had opportunity to test drive.
I'm very pleased with my Omnirom ATM. Am curious to try though.
Thanks

Destroyedbeauty said:
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?
Click to expand...
Click to collapse
I've make one for 311/312, you can grab it here :
http://forum.xda-developers.com/xpe...ent/stock-rom-xperia-tablet-z-sgp312-t2876245

Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?

tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
Sorry, I do not and I have not tried this ROM yet

tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
I got my stock 4.4.4 rooted, but unfortunately not with this ROM. Below are my thoughts on what the problem may be.
system.flashable.zip only includes TWRP 2.6.*, which apparently has issues mounting encrypted partitions. These issues are solved in TWRP 2.7; can the OP update system.flashable.zip to include 2.7?
For those who still want to use this ROM, after flashing system.flashable.zip, I'd immediately install dual recovery before rebooting. I've not tested it myself but it's my theory for what will work.

[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac

[Q&A] [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Pac
Q&A for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][I9295][4.4.2] Super WizCyan - S5 Style [debloated & deodexed + Addon Package]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,

lamhcmute said:
Hi everyone,
This ROM is great. every things are working well.
But I don't know how to change the "Right hard key's function. I don't want it show the "recent apps" when we press.
It should be a menu key when we using App.
Please support!
Thanks,
Click to expand...
Click to collapse
In post# 1 under the downloads section, below version 03 you will find revert longpress to recents & menu. You can download and flash this zip through recovery and menu key will be as before.

no root after flashign WizCyan
After flashing WizCyan 4 with update 1 I don't have root access. I've tried reinstalling several times and I've also tried to install superSU on it's own using CWM, both the latest version and older versions, with no success. I've also tried to install just v4 but the problem persists. Does anybody have any clue on what could be wrong? I've had root on the phone using other ROMs. I use the latest CWM.
And yes, I chose no when promted to fix superuser in CWM. Although I have also tried to pres yes during one installation.

What version of cwm are you having? Also when you click on the supersu app what message do you get?

I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.

Gudiol said:
I used version 6.0.3.5. Today I installed 6.0.5 and redid the flashing of the update and also of superSU 2.16 by it self from CWM. No difference
When i press the superSU app I dont get any message really. Looking at the log it's as if though the app denies all apps access without asking. I tried changing the settings in superSU to allow all requests and then the phone passed the check with root checker and root apps also seem to work. No app is added to the SuperSu applist.
Click to expand...
Click to collapse
I would suggest that you do a clean install of the ROM, now that your recovery has been updated

Excessive consumption of battery
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.

srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Will suggest to do a clean install and check and if not then report back. Anyone else facing this issue.. kindly report

srDosaps said:
Sorry, but this was translated by google.
I found a big problem in version 4 and is the battery, prior to this version, the battery works well, the battery lasted the whole day, but now the battery hopefully enduring three hours.
Please, give solution to this problem or any suggestions, as I really like this ROM and do not want to change the other.
Thanks in advance.
Click to expand...
Click to collapse
Ok, did some testing and found that some of the init.d scripts were eating battery therefore have posted an update in the OP removing these and battery consumption should be better after flashing this update.

can i install
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?

s4active user said:
i have 4.4.2 NE5 but DBT not PHN,can i install this rom on my firmware and do i need install first version 4 and then flash version 4 update 02?and how much memory i have after flashing this rom is ih still around 12 gb or less?
Click to expand...
Click to collapse
Sure, you can install on any firmware, but if you have wifi issues then you may need to flash modem or some other workaround. Just wipe data/factory reset and install version 04 followed by update 02. I am not sure on what you mean by memory but presume that you are referring to internal sd card. This will depend on what apps/features you install from the addon package and playstore. The ROM will not affect your internal sdcard space as it will be installed on the reserved system space.

Problem with Rom Super Wizcyan - S5 Style
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.

Kaitenx said:
Hello, first sorry by my english, its sucks, but ill try to explain my problem, i install the rom wizcyan - s5 style in my I9295 (of course), and follow all the instruction, like de developer says, starts normaly, but for example, when i push the screen mirroring button, the phone freeze an restart, and occasionally shows a message like "android core process stoped". do all the wipes, and install the 6.0.5 rom manager, all the proces finish ok, install the update, and occurs the same problem, i like this rom its cool , faster and light, without all the samsung crap, someone can help me please, thanks in advance.
Click to expand...
Click to collapse
In case you want to use screen mirroring then you would need to install allshare from the addon package

I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Still can't get my Wifi to enable. The flash was successful, as I can see the correct baseband on the "about" screen, but it refuses to enable. I'm in Australia, but I believe this phone came from UAE -- would that make a difference to the way the modem interacts with the Wifi hardware? I pulled this info from logcat:
Code:
I/WifiManager( 1084): setWifiEnabled : true
I/WifiService( 882): setWifiEnabled: true pid=1084, uid=10008
E/WifiHW ( 882): ##################### set firmware type 0 #####################
E/WifiHW ( 882): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 882): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 882): return of insmod : ret = -1, Exec format error
E/WifiStateMachine( 882): Failed to load driver
E/WifiStateMachine( 882): sendErrorBroadcast code:10
E/WifiController( 882): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
In the mean time, I'm going to try to source either a local radio, or one from the original region, to see if that helps.

andycore said:
I've been tinkering with trying to get WizCyan totally working on my device for a couple of days, but I can't for the life of me get Wifi working (at first it was root access, but that was fixed by upgrading CWM). Here is the exact process I've followed:
Updated CWM to 6.0.5 (PhilZ's version)
Did a factory reset from recovery (I didn't use the "Clean to install new ROM" function)
Installed WizCyan version 4, followed by update 2
Rebooted, attempted to configure WiFi -- failed.
Flashed the NE5 modem package from the links in the dev thread, using Odin 3.07 -- twice each, as instructed
Click to expand...
Click to collapse
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.

JASONRR said:
Can't get anything much from the logcat, it refers to a file that gets created on 1st boot you can try doing a factory reset from settings--> backup & restore--> factory data reset. Only backup your internal sd card before doing this as it will wipe your entire phone including internal sdcard and then reflash the modem.
Click to expand...
Click to collapse
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?

andycore said:
Well if I'm going to go that far, I may as well do it properly and completely restore the phone to stock and start again. When I bought it, the first thing I did was root, flash CWM and a CM based ROM -- it's probably worth starting fresh anyway, I'm only going to be using it for a couple more weeks until it's replacement arrives.
I'm currently downloading the latest firmware for my region (XSA), a 4.2.2 based MK3 build from the end of last year -- do you think I'd have better chances if I restored to a 4.4.2 build (like NE5), or should it not matter if I completely reset the phone to factory settings/software?
Click to expand...
Click to collapse
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.

JASONRR said:
Generally doing a factory reset from the phone resets the entire firmware and is helpfull to resolve such issues. if you want to install the entire firmware, I would recommend flashing the 4.4.2 PHN firmware you can get the download link in post# 13. But then there were wifi issues after flashing the PHN firmware for which a factory reset from the phone happened to be the solution.
Click to expand...
Click to collapse
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.

andycore said:
Thanks for that mention of the firmware, I had the radio from that link but forgot you'd also linked the full package. Google Drive is much faster than the websites I'd been trying to get files from, it took 15 hours to download the XSA firmware I was originally going to use.
You were totally correct, resetting the phone was the solution. I got the PHN firmware, flashed it via ODIN only to find it still hadn't fixed the WiFi problem -- even after a factory reset -- however the process of flash/reset/re-flash fixed it for me -- it seems unnecessary to me, but I guess times have changed since I last tinkered with unlocked devices. I'm happy to say that I now have WiFi working under WizCyan now, just wanted to check back in just in case anybody else was facing similar issues. As painful as it is to have to back up and totally restore, sometimes starting completely fresh is the best solution.
Now I'm off to rebuild my SD Card, lol.
Click to expand...
Click to collapse
Glad to know that you managed to get the wifi working.
Personally, I did not face the wifi issue after flashing PHN firmware, but know that quite a few have faced this issue as reported in this thread
Normally my understanding and experience is that when you flash different modems / firmware some corruption occurs and factory reset from within the phone resets the partition & firmware. 1st time I experienced this was when I was using a MTK 6575 based device and had amended the EBR, MBR and scatter files to modify the partition sizes, even though these were flashed through mobiuncle tools (similar to odin), the revised partitions did not get changed until I did a factory reset from within the phone. I know that this is irrelevant here but thought that I would share this.

Android 7.0 Call Problem

Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie

I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it

Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie

aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.

Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie

I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.

none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me

I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.

stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well

Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!

Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie

Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie

aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.

Update OP3 from 3.1.2 to OOS 5.0.1 (process and files required)

Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.

AbhiM7 said:
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
Click to expand...
Click to collapse
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/

hellcat50 said:
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
Click to expand...
Click to collapse
Hi, I've already downloaded this very stable file and tried flashing using TWRP

AbhiM7 said:
Hi, I've already downloaded this very stable file and tried flashing using TWRP
Click to expand...
Click to collapse
I read something about wrong batteries causing this problem. Do you use the original battery?

hellcat50 said:
I read something about wrong batteries causing this problem. Do you use the original battery?
Click to expand...
Click to collapse
I though of running a diagnosis check by dialing *#808# and looked up Charger option, it shows the battery as "itech_3000mah"
is that original?
I had given the phone to repair for water damage to a professional service chain (Not OnePlus, some company here called Yaantra). I've heard from talking to an official repair person of OnePlus that fake batteries are not possible for OnePlus.
The battery works absolutely alright, charges up nicely and I get decent SOT. Can't complain at all.