Database Develop

[Q] Unofficial CM11 Problem

Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East

EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
Are you on the correct bootloader 10.26.1.18 as is required?

EastPatel said:
Hi.
I have just flashed the unofficial CM11 rom on the Original Android Development Forum on my TF701T. The install appears to have been successful however the system keeps freezing anwhere from 1 minute to 5 minutes after boot. Before it freezes everything appears to be working as it should. Any ideas what I have done wrong and what I have to do to fix this? Apologies if the same issue has been raised elsewhere.
Many thanks
East
Click to expand...
Click to collapse
I've not heard of this ocurring (my own tab has been running for a while now; no issues of this sort).
Are you on the latest ROM build (01/29)? Have you flashed the appropriate gapps?
Are you on the latest boot loader?
Any apps installed which could cause issue?
If it happens when plugged in to USB, is isb OK on your PC/Mac?
Have you used titanium backup to restore system level stuff from a non compatible build?
Do this,
Go back to stock (latest release from asus) and observe for an hour or two. Any issues? If not then flash ROM + gapps and wipe. Don't sign in and don't restore apps. Any issues? Then sign in and restore. Any issues? And so on and so forth until.you find the break point.

Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Pershoot once the new CM11 was first flashed the TF701 would freeze during the setup steps well before any 3rd party apps could be installed. After a number of attempts I manage to get through set up and the system becomes a lttle more stable but then freezes after a few more minutes. I can conform that the correct gapps has been flashed using the link on the associated thread and no additional apps except the ones included on the ROM have been flashed. The system freezes without being plugged into the PC via USB and as mentioned before I am coming from sdbags stock rooted 4.3 ROM and have not used titanium back up at all.
A couple of additional point
1) I have tried to reflash sdbags ROM again but it now gets stuck on a bootloop.
2) I noticed that my install of CM11 is not able to access either an SD card placed in the dock or MicroSD placed in the tab despite the system recognising when they are inserted or removed on the task bar.
3) Because the system freezes so quickly it tabvery difficult to transfer a new ROM downloaded to my PC over to the TF701 because the moment it freezes the PC can't communicate with the tab.
Apologies if this reply is a little onerous - any help would be greatly appreciated and thank you both again for your prompt response to my.request for help.
Kind regards,
East

Hold down Volume Down and Power and read the bootloader version from the top left.

EastPatel said:
Thank you for your prompt responses as always and apologies for not replying sooner.
SDbags I am installing CM11 over your own excellent 4.3+ stock rooted v2 ROM which I believe involved updating my boot loader. I am unsure how to confirm the version I am on but booting into recovery shows the following
Android Macallan-user BL released by ww_epad-10.26.1.7-20131108.
Click to expand...
Click to collapse
That's the wrong BL to be on. I don't believe sdbags' ROM updates BL. You must do it via Asus's update.
Go back to stock recovery and follow asus's procedure to update yourself to their latest 10.26.1.18 (4.3) build.

Dear SD Bags & Pershoot,
Apologies for not responding to your feedback sooner - Its been a busy week at work.
I will follow your advise and update the bootloader via the ASUS website and try to reinstall the rom again over the weekend or early next week and I will update this thread with the results. Once again apologies for not following the instructions more carefully.
Many thanks & kind regards,
East

Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East

EastPatel said:
Hi felIas.
I have updated the bootloader as I should have done initially which appears to have sent me back to stock unrooted 4.3. Please could you confirm that all I need to do now is install the recovery image and then flash CM11 and GApps? Does the rom file work the same way as SDbags rom where it also roots the phone as part of the installation or do I need to somehow root first?
Having said all this I am considering leaving the system as stock until a work around for sky go on rooted 4.4.2 devices is found!
Many thanks again for your guidance and patience.
East
Click to expand...
Click to collapse
I have a work around for Sky Go on rooted devices You didn't ask.
PM Please.

Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?

Jrockstar867 said:
Hey there I was wondering if anyone else is experiencing my problem. I updated to CM11 on my TF701 and while the dock and keyboard works some of the keys are dead i.e. Settings button, toggle wifi, toggle bluetooth, screenshot, disable trackpad, and auto brightness. Is there any way to fix this? I have tried editing the qwerty files and installing the asus keyboard apk, but neither worked. The APK did not install and editing the qwerty.kl file quite literally did nothing. Also curious if there is a way to get an external mouse to behave the way it did on JB left click is a standard touch and right click is back?
Click to expand...
Click to collapse
Kernel needs recompiling with fixes in it - not a huge job but something I have on my todo list - won't be for a while though.

Is there a thread I can subscribe to to get the latest news??
Sent from my Transformer TF701

[Q&A] [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]

Q&A for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]
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 [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]. 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!

Can i flash zip or ftf via adb? i'm using cm12 rom.

hi guys,
I bought a Z3C and I just checked the bootloader is not locked .
pen the dialler and enter #*#7378423#*# to access the service menu.
Tap Service info > Configuration > Rooting Status. Bootloader unlock allowed says Yes
I wanted to know if I could flash via Flashtool software directly ?

OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.

savudin said:
OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.
Click to expand...
Click to collapse
If you didn´t wipe data in recovery, then no data should be wiped. That´s normal.

Yes, that's it. But, did I had to wipe data? I've read that clean install is recommended. I've noticed no problems in the last couple of hours of usage.

Dirty Flash from 23.0.1.A.5.77
I dirty flashed 23.1.A.0.690 from Greatslon MIUI v5 23.0.1.A.5.77 and still have root.
The phone froze and bootlooped a couple of times when i installed and restarted it, but patience was rewarded, as it finally booted.
I can still mount /system as rw both via adb shell, "onboard" terminal and through Root Browser.
Can i be of some help with a logcat, and in case how?
I am a software developer myself, but in a different branch than android. I just can't see through how i should get started with android development.
Great work guys
I guess i should add, that i still have my bootloader locked.
So to summarize:
>Bootloader locked (never unlocked)
>Firmware 23.1.A.0.690 from this thread
>Full root
>System R/W

Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets

Interesting, I did exactly the same but only have partial root, meaning that my system indicates root but I don't have writing permissions. Tried the ADB fix but did not work. Any other suggestions for getting full root again?

FYI: Nut has mentioned that he fixed recovery in his main development thread and will be working on releasing it to everyone soon.

Tnx for ur great work... but i have problem to download from mega site.. and specialy from the folder...
can anyone give me the direct link of [5.0.2] Firmware 23.1.A.0.690 Generic and A.5.77... not the folder link...
and can anyone tell me where exactly save the file we download from mega site ?
i cant find it anywhere...
Tnx alot.. :xX

How to delete recovery when it not working, thanks

Can't try new xposed for lollipop because it require install from recovery. And recovery not working in 5.0.2

air32 said:
Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets
Click to expand...
Click to collapse
edit the build.prop

what if I restore the TA Backup after that?

AndreDNA said:
what if I restore the TA Backup after that?
Click to expand...
Click to collapse
You would only need to restore the TA backup if you've unlocked your bootloader in the past.

I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app

AndreDNA said:
I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.

2mal16 said:
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.
Click to expand...
Click to collapse
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD

AndreDNA said:
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD
Click to expand...
Click to collapse
Go to the thread of NUT dual recovery and (assuming your on a windows pc) download the installer for nut dual recovery. it will let you install the recovery on locked bootloader by running the install.bat file. with this recovery you can then flash a prerooted lollipop zip (you can do it yourself with prf creator, include the newest SuperSU zip and the newest dual recovery zip together with stock lollipop rom) after wiping your phone. people also just flashed over KK but i prefer to do it clean and set up my phone newly again. you will then end up with a phone which has system rw and root on lollipop but the recovery will be gone until NUT fixes it. That is what everybody is waiting for.
So unlocking BL wont really gain you anything except sonys DRM keys not working. it will just introduce an additional step to relock them.
Here is the thread: http://forum.xda-developers.com/showthread.php?t=2261606
to get into recovery just spam the volume up button(or down since it has two recoveries ) when your phone boots and lights up the led.

CM Recovery for Nexus Player (fugu)

This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img

Dude, quit being so amazing. It's getting ridiculous.

Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.

Yes!!! Glad to see you!

@WugFresh

@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]

GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.

I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.

bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.

Can confirm a working flash. Everything looks great! Thanks for all the hard work

no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?

How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!

Edit

Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse

OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)

OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.

WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.

dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks

Yes it seems Google decided to remove the backup confirmation dialog from TcSettings

So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2

How to root my Sony Xperia Z3 compact?

Dear XDA-developers,
Today I spend numerous hours in trying to root my xperia z3 compact.
I currently have MM 6.0.1 D5803 installed on it with 23.5.A.0.575 the netherlands T-Mobile version. I have tried the following: Kingroot, iroot, kingoroot etc but it is all not working. I also used adroid sdk and changed the fastboot driver. I am able to fast boot etc.
Could anybody help me out with rooting this device? Love to hear from you guys.
Kay

It is described here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343/page149
Basically you must downgrade to kitkat, run the rooting script and install recovery, and then install a prerooted marshmallow rom.

Similar issue in Switzerland
M1chiel said:
It is described here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343/page149
Basically you must downgrade to kitkat, run the rooting script and install recovery, and then install a prerooted marshmallow rom.
Click to expand...
Click to collapse
Hi, I actually have the same problem rooting my new Z3C in Switzerland. I know that I have to downgrade but when I flash the rom it just boot in the welcome page and the it crashes and go in bootloop.
I've tried with both:
"D5803_23.0.1.A.5.77 Android 4.4.4_Customized CE1 1288-7915.ftf"
"D5803_23.4.A.0.546 Android 5.1.1_Customized CH 1288-9528.ftf" (I know that is not the KK but I just wanted to try if it works, but no success at all even flashing a lollipop from CH)
Any ideas guys?

jassi0709 said:
Hi, I actually have the same problem rooting my new Z3C in Switzerland. I know that I have to downgrade but when I flash the rom it just boot in the welcome page and the it crashes and go in bootloop.
I've tried with both:
"D5803_23.0.1.A.5.77 Android 4.4.4_Customized CE1 1288-7915.ftf"
"D5803_23.4.A.0.546 Android 5.1.1_Customized CH 1288-9528.ftf" (I know that is not the KK but I just wanted to try if it works, but no success at all even flashing a lollipop from CH)
Any ideas guys?
Click to expand...
Click to collapse
You need to follow this guide here
To answer your question you need build 23.0.A.2.93 or older, to be able to use griefroot

Didgesteve said:
You need to follow this guide here
To answer your question you need build 23.0.A.2.93 or older, to be able to use griefroot
Click to expand...
Click to collapse
Thank you for you answer. I've actually just tried with this but I get stuck in the welcome screen and then it simply continues to reboots.
I've installed this: D5803_23.0.A.2.93_Generic GLOBAL.ftf
After having a look to the firmware that I had on the phone (original and working was the 6.0.1 GLOBAL version).
All my previous phone was rooted and now I feel like in prison without a rooted xperia! ahahah

jassi0709 said:
Thank you for you answer. I've actually just tried with this but I get stuck in the welcome screen and then it simply continues to reboots.
I've installed this: D5803_23.0.A.2.93_Generic GLOBAL.ftf
After having a look to the firmware that I had on the phone (original and working was the 6.0.1 GLOBAL version).
All my previous phone was rooted and now I feel like in prison without a rooted xperia! ahahah
Click to expand...
Click to collapse
Then you are doing something wrong with flashtool, I used that build yesterday, then used geifroot and dual recovery, before flashing Slim 2.
you need to tick all of the wipe boxes, and none of the exlcude, or it won't work. You can't keep your data flashing to a different firmware.

Didgesteve said:
Then you are doing something wrong with flashtool, I used that build yesterday, then used geifroot and dual recovery, before flashing Slim 2.
you need to tick all of the wipe boxes, and none of the exlcude, or it won't work. You can't keep your data flashing to a different firmware.
Click to expand...
Click to collapse
Ohhh nice, it was not mentioned that you have to check all the tick boxes! Thank you so much!
It seems to work now.
I think it would be better to emphasize this in the guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
I'm downloading the rom, what would you suggest me if I do really care about the battery life? Maybe the lollipop instead of Marsh-mellow because of the presence of Stamina mode in lollipop?
I guess I will just try to find the best...

jassi0709 said:
Ohhh nice, it was not mentioned that you have to check all the tick boxes! Thank you so much!
It seems to work now.
I think it would be better to emphasize this in the guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
I'm downloading the rom, what would you suggest me if I do really care about the battery life? Maybe the lollipop instead of Marsh-mellow because of the presence of Stamina mode in lollipop?
I guess I will just try to find the best...
Click to expand...
Click to collapse
There are only two good builds for the Z3c at the moment.
The Slim 5 which is lollipop
or the Slim 2 MM. I was sceptical about MM battery life and held back 5.1 for a long time, but now the latest roms is out, the doze function works as well or better than stamina mode. I am getting 4 days between charges now, something I could never do before

Didgesteve said:
There are only two good builds for the Z3c at the moment.
The Slim 5 which is lollipop
or the Slim 2 MM. I was sceptical about MM battery life and held back 5.1 for a long time, but now the latest roms is out, the doze function works as well or better than stamina mode. I am getting 4 days between charges now, something I could never do before
Click to expand...
Click to collapse
Thank you for your answer. Really useful! I've finally managed to room and install that I wanted!
If you have such permission, I would suggest to edit the guide in: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
by adding the following:
7. Just select the name of the fw you downloaded and click on "Flash". Note: select both wipes in case you are coming from different android version.
43. Open Flashtool and select the non-pre-rooted fw (this is 23.1.A.0.690), but DESELECT system: in "EXCLUDE" make sure you check the checkbox next to "SYSTEM", flash it.
I will put this comment on the relative guide too!
I don't want to abuse of you kindness but I am currently searching for some CPU+GPU clock and voltage changer. Is there any efficient application that you can suggest me?

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?