Huawei Nexus 6P :: Unable To Update Android After Editing
Jan 15, 2016
I flashed the recovery, rooted the device. Updated the build.prop. Then unrooted it, put back stock recovery and locked the bootloader. I was getting "Your device is corrupt" message on boot, however, it was able to boot. I have received the January security updates, but I am not able to install it. It proceeds through installation and during the restart it shows "Error". I have already tried clearing cache.
Is there anything I can do ? Is there any way to update build.prop without getting "Your device is corrput" message ?
Not wanting to wait for the OTA update to appear on it's own, I downloaded the 5.0.1 OTA update directly and tried to do a adb sideload from my Mac but sadly I get a "device not found" after doing the adb reboot bootloader command. I do adb devices and indeed no devices are attached. So I entered recovery mode and still no device found and so I just start the Nexus 6 back up as normal. At that point, adb devices shows the Nexus 6 and so rinse and repeat - the device is not found while in bootloader. Must be doing something wrong since I was able to install 5.0 without any issue and it's already unlocked.
I've tried a few methods of getting recovery back but so far have failed. I always end up with that droid and a red warning triangle, which if left long enough it will boot into android on its own..
Recently, a friend lost a phone. Apparently, it was turned off after being found. When going to Android Device Manager, it only indicated that it couldn't locate the phone. I thought that it would show its last known location, but it did not. Shouldn't it?
Android Marshmallow. I noticed that on my Moto X Pure (Style) before and also now on my Nexus 6P that whenever I charged it to 100% it won't say "Full" but instead "Charging on AC" still. On my Moto X before, the "Full" message will be displayed after 30 mins or so. However on my Nexus 6P now, it will take more than an hour for it to say "Full".
I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
So I was running screwd ROM with elementalX kernel. Everything was working great but I'm a long time DU user. Went to their G+ page flashed ROM. I had issues with it so I wiped and restored my backup of screwd ROM through TWRP. The first go around I selected to restore all partitions. It got stuck on the boot logo. Booted back into recovery and restored android again. This time I unchecked the vendor image box and restored the rest of the partitions. Worked like a charm.
on my previous phone (Xperia Z2) I can plug in to my computer via USB and copy files to/from the internal storage or SD card. When I plug my Nexus 6P in to the computer the same way, I just get an empty folder. I can't see all the files on the internal Android file system. Is this normal?
I am having issues with calling and receiving calls, I am able to send SMS and go on the web, but not able to call or receive calls, I've done a factory reset , cleared the phone cache...
I am having the problem of writing to my internal storage. Ever since upgrading to 6.0.1 I have not been able to download anything successfully. I am currently on the current android version, do I need to have the phone encrypted for storage to read/write?
Did a swap from a 64 GB 6P to a 128 GB and tried just doing a nandroid. That would've worked but the fingerprint reader wouldn't work without a factory reset. I also accidentally restores the old EFS in TWRP without knowing I shouldn't, but used the original EFS (did a backup on new device before transfer) and restored it back to what came the device.. So I did that and re-did everything and it seemed to have no problems at first. I downloaded some Google Music playlists, Viper4A + busybox, and at some point my phone stopped letting me modify the files.
Camera can't take pictures. Chrome can't download files. I can't add/remove files via PC. I can't modify files via file managers. I tried chmod 777 sdcard but it doesn't fix the problem. I tried reflashing the ROM and all, and did a complete wipe but restored the data (only) from TWRP - so the problem might be somewhere in there. I haven't changed anything from the setup I had on the 64 GB - it was working fine and then just stopped letting me do stuff.
I'll probably try a complete factory firmware restore then flash the ROM all over again, but wanted to see if there was a simple fix first.
I recently unlocked the bootloader and rooted my Nexus 6P and just this evening received an update for the November Security Update. This downloads fine but when the phone reboots to install, it just goes to TWRP and doesn't install.
This is most likely incredibly simple and stupid for me even to ask, but is it possible to install one I've unlocked/rooted?
Since the latest Jan security patch, my apps will not update over wifi at home. It keeps saying downloading for ever. The moment I turn wifi off, apps download just fine on 4g.
Nexus 6p all stock and on Jan security patch. I have reset my router twice and still nothing.
I am not rooted. I can access my phone through Windows 10. But I cannot see all my folders. The 2 that I am having problems with are my Camera and Music folders. Some of the files are there. When I use ES File Explorer I can see and access them fine. Right now I cannot pull off any of the photos or videos I take. This all happened after upgrading to 6.0.1. I have tried 2 different cables and 2 different computers with the same results. I have made sure that USB Debugging is enabled. I also made sure that I had PTP and MTP enabled. Also upgraded to the latest 6P drivers for Windows 10.
I've had my Nexus 6p for 1 week and I have not received any OTA update notifications. I'm still running MDA89D (latest is MDB08M??)I'm on Verizon (with a sim from my Note 4) and have not done any modifications to the phone yet (bootloader, root, etc)According to the factory images page, URL...
how do I flash the OTA update on my phone? When I try to do it via the phone (notification tray), it gives me an error after the attempted flash.I assume I need to download the OTA somewhere and sideload it. Where can I get it? My current build number is MMB29M..I assume I just flash the system.img from the latest factory image?
Day one powering up the phone there was a system update that that never installed. Since then I have not received any OTA updates. I have had it since October 29th.
I am on Verizon and used my sim from another phone. Concerned that because the first update borked during set up that I am not going to receive OTAs. Seen other listing the same scenario. Factory reset and removing sim in order?
I just received a notification on my 6P saying that the january security update is available. The thing is that I'm rooted with systemless root, xposed, EX Kernel and TWRP.
I am on stock rom, using SuperSU 2.66. I have tried using texdroider_dpi and one other app but they cannot change my dpi. It says it sets but then I reboot and I'm stuck on 560 dpi. I changed dpi in adb but some elements don't work such as my Swiftkey, the little blue diamonds for top devs in play store.
I assume this is a SuperSU issue but these DPI apps have worked since I first rooted this phone back in November. Only the current update has broken this.
I was rooted on 6.0 and wanted to keep my user data, so I downloaded the 6.0.1 factory image and individually flashed the different pieces with Fast boot.
I also updated to the latest TWRP.
My phone now boots to 6.0.1 and works normally, but when I go into recovery TWRP can't access the internal SD card and just shows 0 bytes, so I can't reflash SuperSU.
Is their a way to update while being rooted, and keep the data. I am thinking that after I lock the phone and update it, and re root it, that my phone will be wiped completely
A new update is out for the 6p with monthly security updates. I have two questions:
1. I'm assuming Google is going to break systemless root. Does this update do that or does it still work? 2. Now that we're seeing monthly updates, keeping root is going to be difficult.
