I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Godders11 said:
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Click to expand...
Click to collapse
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Many thanks, I'll give that a try.
sfhub said:
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Click to expand...
Click to collapse
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
doggie123 said:
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
Click to expand...
Click to collapse
Hmm, I wasn't expecting that to happen, just expecting some file corruption to be overwritten, but it looks like you potentially had some bad sectors in the eMMC as well that got blocked out automatically by the erase.
This reminds me of the eMMC problem we had on Samsung where they changed wipe data to do a secure erase and that triggered an eMMC bug that left people with megabytes of unusable sectors.
If I were you, I would only run my system using a JSS15Q kernel because that has the fixes for the type of issue your unit seems susceptible to.
http://forum.xda-developers.com/showthread.php?p=44954087#post44954087
Related
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
open /cache/recovery/last_log on your tablet use root explorer
ypu will know whats wrong
I'm in Melb too, and that particular update has failed to download about 5 times now, and when it finally downloaded, it came up with a message saying "update invalid" or something along those lines. I'm gonna wait til I get home to try and update again.
altering WPA_Supplicant file is something you would've done so your tab would connect to ad hoc networks. Must be something else.. did you alter any other files? I'm working on this same issue. frustrating as f*#%
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
acorsino said:
I was running stock rooted 3.01 and was failing updates over and over until I flashed back to the stock recovery using the Acer recovery apk. As soon as I did that and tried the ota update again it worked right away... once 3.1 was installed I rerooted using iconia root 2.1 and flashed cwrecovery back to tablet... let me know if this helped
Click to expand...
Click to collapse
Same for me. Had to go back to stock recovery for the OTA update to work.
Mine failed the first time. I rebooted and it worked the second time.
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
mashilu said:
I tried using Acer Recovery Installer 1.5, checking Stock USA 1.141.07_COM_GEN1 and touched "install recovery image", rebooted, and nothing happened?
My build number remains 1.139.04_COM_GEN1
I am sure I have missed something...
Tried downloading and installing the 5th time, still failed and stuck at the same progress bar of 1/4 followed by that annoying honeycomb with exclamation mark logo.
Click to expand...
Click to collapse
If you see the little bee fail screen, it is not the stock recovery, but still CWM.
mashilu said:
Received the update notification this morning, happily started downloading and installation.
Like some out there, the tablet rebooted and it seemed to install but up to about 1/4 progress it froze with a central honeycomb logo with exclamation mark. Thought it was part of the process, left alone for an hour but nothing happened, hence rebooted with a notification of 'update failed'.
Searching through google and xda forum the last 2 hours -- have tried the unrooting the device, plugging in to power, removing sd card to no avail.
Someone has also suggested to restore wpa_supplicant file under system/bin. I don't remember altering the file at all, and when I check the file it is dated 29/3/2010... i bought my device in April, hence assuming it has not been altered either by myself or from any app. Like wise for the telephony files as well, as I haven't changed anything to try to stop the cell standby issue to improve battery life.
I am left with no options unless someone has a better idea. I have not uninstalled any pre-loaded apps. Rooted with Gingerbread (and as I said tried unrooted and re-rooted without success in updating).
Thoughts?
Current build:
Android version 3.0.1
Kernel 2.6.36.3
Build no. Acer_A500_1.139.04_COM_GEN1
Failed system update to 4.010.24
I am located in Melbourne, Australia.
(Last thing would be to download the actual rom and update via CWM.)
Click to expand...
Click to collapse
Hi .. try to do that...
the uploaded file helped and solved my issue..i'm now running Honeycomb 3.1
Solution posted by Bob here: (correct the link below "www")
w w w.androidtablets.net/forum/acer-iconia-tab-a500-forum/18444-update-failed-help.html
Here's the WPA_Supplicant from my A500, after the 3.1 update. Hope this works for you guys.
I'm not sure what the extension is for the A500, but I had to add .zip to be able to upload it. Try removing the .zip before using it. Also, remove the 'original'. I added that to keep it straight on my tablet.
Good Luck.
Bob
p.s: sorry i'm a newbie here and can't post link outside the forum at the moment..
just follow the steps described by Bob!
I did see that different logo, which I subsequently rebooted as I thought it's frozen again.
Interestingly, I tried to push for another system update, attempt no. 7, and now, it progresses and complete update!!! Woo hoo!
Thanks for all the help. I still don't know which one sorts what out though... Cheers!
Hello all.
I have an issue that I can't find on the forums...I'm totally confused.
My brand new (3 day old from Target) Iconia Tab 500 keeps saying there is a system update ready. A dialog box pops up saying it's ready & do I want to download now or wait.
If I click "now" it looks like it's downloading. There is a little status bar on the bottom right of the screen that says it's downloading & the yellow bar moves along at a decent pace.
I think it finishes downloading....because that status bar disappears.
Then nothing happens. I expected a "run update" type of window to appear, but it never does.
So if I click through to the "about" area & click "check for system updates"....and for about 1/2 of a second I see the spinning wheel icon that looks like it's contacting the Acer servers to check for any updates...but that disappears & it says "no updates currently available".
So I go on about my business.
Then seemingly at some random interval I get another "system update ready - do you want to download now or later". Of course if I click "now" the same thing happens....nothing.
I thought maybe i had downloaded it & now i have to install manually, but I can't see any file named "update" anywhere...particularly not in the "downloads" folder.
This has happened maybe 5 or 6 times over the past 3 days.
I'm totally confused. Can somebody help me please?
In the About Info it says:
Android: 3.01
Kernal Version: 2.6.36.3-00001-G9B3CE2B
Build: Acer_A500_1.104.02_COM_GEN1
FYI - I have not rooted this because #1 I have never done that before & am hesitant to screw it up & #2 I have 87 days left on my 90 day Target return policy & I don't want to do anything that's gonna screw that up in case I decide this tablet isn't really for me.
Thanks all !!
GMP
Same thing for me
I'm also having the same problem.
I've tried downloading the OTA update. The progress bar fills all the way up, gets to the end... then nothing. No button for "install now".
I've tried downloading 4 times, both with and without the sd card installed. I've even let it sit in this state for 15-20 minutes. It just hangs...and hangs....and hangs.
Android Version: 3.0.1
Kernel Version: 2.6.36.3
Build #: Acer_A500_1.141.07_COM_GEN1
Also, unrooted.
more info
Hmmmm - ok...additional info for me. I do NOT have any SD card inserted. I just decided to not buy one with the unit because I thought i had a few extra at home, but I didn't - & I haven't been back to the store to get one yet.
I wonder if that makes a difference for my situation?
I will get a card & try again asap & post a reply.
Thanks,
GMP
sparky999 said:
I'm also having the same problem.
I've tried downloading the OTA update. The progress bas fill all the way up, gets to the end... then nothing. No button for "install now".
I've tried downloading 4 times, both with and without the sd card installed. I've even let it sit in this state for 15-20 minutes. It just hangs...
Android Version: 3.0.1
Kernel Version: 2.6.36.3
Build #: Acer_A500_1.141.07_COM_GEN1
Also, unrooted.
Click to expand...
Click to collapse
I can't imagine having an SD card installed would be a requirement for the update. The card is a piece of optional equipment.
The only reason I tried with and without was that I saw some people were having some install issues that were solve by removing the card. But I think this was more an issue with rooted devices.
Trying anything at this point.
thanks
Makes sense.
Hopefully somebody will help us.
Thanks.
sparky999 said:
I can't imagine having an SD card installed would be a requirement for the update. The card is a piece of optional equipment.
The only reason I tried with and without was that I saw some people were having some install issues that were solve by removing the card. But I think this was more an issue with rooted devices.
Trying anything at this point.
Click to expand...
Click to collapse
I've got a few days left of "returnability" on this tablet. If I can't get this solved in a reasonable amount of time...buh-bye. May ditch in favor of the Toshiba.
Working! (i think)
I think I've got it working. I reset my device first (paperclip, pinhole...reboot).
Re-downloaded the update. Hurray - got a "install now" message. It's unzipping and installing right now.
Stand by for an update....
Success!!!
That worked. So, try resetting your tab with a paperclip.
Android Version: 3.1
Kernel Version: 2.6.36.3
Build #: Acer_A500_4.010.11_COM_GEN2
yay / boo
Yay for you!!
Boo for me....please don't tell me I have to factory reset just to do an update?
There must be another way??
sparky999 said:
I think I've got it working. I reset my device first (paperclip, pinhole...reboot).
Re-downloaded the update. Hurray - got a "install now" message. It's unzipping and installing right now.
Stand by for an update....
Click to expand...
Click to collapse
I didn't do a factory reset. It's just a "regular" reset. Not sure what the difference is between with sort of reset and simply running a power-cycle (except that the reset worked and power cycling didn't).
When I paper-clipped my Iconia (from power on), it simply shut down. When it booted back up, it was stil my machine with all my data and software.
ok - thanks!
Oh...ok - that makes sense - I'll try that.
Thanks!
GMP
sparky999 said:
I didn't do a factory reset. It's just a "regular" reset. Not sure what the difference is between with sort of reset and simply running a power-cycle (except that the reset worked and power cycling didn't).
When I paper-clipped my Iconia (from power on), it simply shut down. When it booted back up, it was stil my machine with all my data and software.
Click to expand...
Click to collapse
it worked for me too
Ok - I tried it last night & it worked for me too!
Thanks for the help!
GMP!
matildaleon said:
Oh...ok - that makes sense - I'll try that.
Thanks!
GMP
Click to expand...
Click to collapse
Cool. In retrospect, I think there may have been something waiting in the install queue that I couldn't see. The reset may have cleared it out.
Cheers.
in fatc what might have happend to you is that the paperclip thing looked if there is an update.zip in the cache, and if it finds one, it does the update.
you can also check in doing volume- power.
if you don't have cwm or any kernel installed.
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
sucinimad said:
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Click to expand...
Click to collapse
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
deusfaux said:
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
Click to expand...
Click to collapse
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
deusfaux said:
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
Click to expand...
Click to collapse
In the end, I went through almost the exact experience (including red LED). Running on stock 4.3 image now. Thanks.
my phone is reboot today.
there might be problem with rooted stock kernel?
there are someone has same problem?
Acuity said:
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
Click to expand...
Click to collapse
i got the same issue, look here: http://forum.xda-developers.com/showthread.php?t=2380546
Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.
Yeah I have the latest OTA also, but I am still having the same issue!!
StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.
Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!