Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Yes,No problem in Germany...
jonnyhh said:
Yes,No problem in Germany...
Click to expand...
Click to collapse
Were you affected by the Oct update?
Received in India. Didn't face any problem with October or November update.
iluvatrix said:
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Click to expand...
Click to collapse
Any improvements or fixes??
iluvatrix said:
Were you affected by the Oct update?
Click to expand...
Click to collapse
No,never had problems until now.
Anyone who couldn't update from September to October can report if it's possible to go from September straight to November, and if it works without bootloop or resetting data?
Thanks.
iluvatrix said:
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Click to expand...
Click to collapse
I had the boot loop last time and factory reset. This one I had no issues.
danannnn said:
Anyone who couldn't update from September to October can report if it's possible to go from September straight to November, and if it works without bootloop or resetting data?
Thanks.
Click to expand...
Click to collapse
Yes, my wife's phone. I had boot looped on October's update and reseted. My wife decided to skip Oct. Now she has received the Nov update and tried to update and got the boot loop. She has unlocked bootloader and critical partition. Restarted 7 or 8 times and managed to boot back to Sept. She is stuck now.
xrayA4T said:
I had the boot loop last time and factory reset. This one I had no issues.
Click to expand...
Click to collapse
Same here. Looks like everyone has to get boot looped either on Oct or Nov update.
No problem with update October to November updater, always using charger and battery 100%.
iluvatrix said:
Yes, my wife's phone. I had boot looped on October's update and reseted. My wife decided to skip Oct. Now she has received the Nov update and tried to update and got the boot loop. She has unlocked bootloader and critical partition. Restarted 7 or 8 times and managed to boot back to Sept. She is stuck now.
Click to expand...
Click to collapse
/shrugs
Thanks for the heads-up.
iluvatrix said:
Same here. Looks like everyone has to get boot looped either on Oct or Nov update.
Click to expand...
Click to collapse
If only my phone would boot with >October version at all, wiping or not.
Not even EDL flashing made it boot into October. I'll give November a try on the weekend, but I'm not hopeful.
Hopefully BF or CM has great deals on pixel 4a. Can't wait to ditch this dumpster fire of a phone.
danannnn said:
/shrugs
Thanks for the heads-up.
If only my phone would boot with >October version at all, wiping or not.
Not even EDL flashing made it boot into October. I'll give November a try on the weekend, but I'm not hopeful.
Click to expand...
Click to collapse
I will wait for your update. Also because i´m in the same boot.
I am with september update. In October update i get boot loop a manage to get the phone working witout reset, after 7-8 restarts.
Now i want to know if i get again bootloop if i try to get November Update. I have bootloader unloack because of gcam, but don´t have root.
Bootlooped in Oct update and Bootlooped with Nov update... Thanks xiaomi
ki69 said:
I will wait for your update. Also because i´m in the same boot.
I am with september update. In October update i get boot loop a manage to get the phone working witout reset, after 7-8 restarts.
Now i want to know if i get again bootloop if i try to get November Update. I have bootloader unloack because of gcam, but don´t have root.
Click to expand...
Click to collapse
I just tried September -> November and no dice.
Got the "Try again / Reset" screen. After choosing Try Again 6 or 7 times it switched back to other slot and booted into September after one more Try Again.
At least it looks like it'll work when I choose to reset, which is better than I had before, but I didn't want to do it now.
Im fully stock, not even gcam mod, but keep bootloader unlocked due to how this phone is prone to bootlooping between updates.
iluvatrix said:
Received this in Singapore.
Very hesitant to restart now in view of the Oct update that boot looped my phone causing me to factory reset.
Anyone else received this and successfully updated?
Thanks.
Click to expand...
Click to collapse
Noooo the dreaded bootloop is back?!
I thought they fixed the bootloop (caused by wrong update being offered) a long time ago! I am on November update and haven't had any issues for the past 9 months...
I think the problem is really in bootloader unlock. Maybe october update had a relock of bootloader ant that why we get bootloop.
I updated to november no boot loop this time, my phone has bootloader unlocked but still stock, with October it had the boot loop and I chose to full reset, I'm disappointed too, waiting a pixel 4a to replace it first and last xiaomi for me.
Wifi had become very unstable since October update. Battery last 1-2 h less, it had an issue with the charging port so I bought a Chinese replacement which only is useful for charging not for data, as soon I get a new original one (very expensive) I'll switch this to lineageOS and keep for experiments
I bought a Chinese replacement which only is useful for charging not for data, as soon I get a new original one (very expensive)
Click to expand...
Click to collapse
Simeone had stolen my orignal data cable so I too bought a cheaper data cable as I was traveling and later come to know it wasn't working for data. Later bought Portronics Konnect L cable from Amazon.in around ₹109 or $1.50 and it's fast and has data transfer capabilities.
Related
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.
That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.
Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.
update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app
I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk
Got two brand new OnePlus two's a day apart probably from the same batch.
On first launch it always got stuck on the checking connection
Tried both with
Vodafone lte
EE lte
bt hotspot
Vodafone hotspot
Multiple restarts did nothing
My guess was that some initialisation step happened at the factory and something funky was in the cache or data so I factory reset both devices (one day apart) and that solved it for me.
. After the reset and booting up it ran the updating android process which it did not before and then it worked flawlessly connecting to the networks
Hope this helps anyone and hope OnePlus fix this!
Got that as well when I received my Oneplus Two yesterday. I solved it by skipping that step, after that Internet worked flawlessly. After I updated to Oxygen OS 2.0.2 and unlocking the bootloader, the problem was gone completely.
Yep
dansou901 said:
Got that as well when I received my Oneplus Two yesterday. I solved it by skipping that step, after that Internet worked flawlessly. After I updated to Oxygen OS 2.0.2 and unlocking the bootloader, the problem was gone completely.
Click to expand...
Click to collapse
Same.
Sent from my OnePlus 2 using Tapatalk
Theshawty said:
Same.
Sent from my OnePlus 2 using Tapatalk
Click to expand...
Click to collapse
My guess is that unlocking the bootloader ran the factory reset. Maybe the problem was on 2.0.1 builds
Let's see when people get the next batch with 2.0.2 preinstalled
It's annoying because for non tech people like my fiance it would have been a straight send back to factory if I wasn't around lol
LOGMD said:
My guess is that unlocking the bootloader ran the factory reset. Maybe the problem was on 2.0.1 builds
Let's see when people get the next batch with 2.0.2 preinstalled
It's annoying because for non tech people like my fiance it would have been a straight send back to factory if I wasn't around lol
Click to expand...
Click to collapse
Unlocking the bootloader wipes the entire data partition.
Yeah, I'm willing to bet .02 fixed it.
Sent from my OnePlus 2 using Tapatalk
My OP2 is from de 4th of september batch, i´m from Portugal and had the same problem! Resolved after the bootloader unlock.
I had this problem, skipped that step, updated to 2.0.2 and did a factory reset.
It was virgin again and ran flawlessly without this error.
So this was a 2.0.1 bug.
Same for me, skipped and everything went smooth.
Hi, I was a beta-tester and recieved B330 one week ago, since this time I've observed 2 restart of my phones, phone restarted and I have to start with pin code.
I've my phone 6 months and never seen such a situation, only after update to B330, could someone confirm this issue ?
Maybe the time is too short because a lot of users get update now, but anyhow if you have same issue please write, thanks.
grzesoliwka said:
Hi, I was a beta-tester and recieved B330 one week ago, since this time I've observed 2 restart of my phones, phone restarted and I have to start with pin code.
I've my phone 6 months and never seen such a situation, only after update to B330, could someone confirm this issue ?
Maybe the time is too short because a lot of users get update now, but anyhow if you have same issue please write, thanks.
Click to expand...
Click to collapse
Have you factory resetted after the update? If not try once but do not forget to back up your data.
rspn69 said:
Have you factory resetted after the update? If not try once but do not forget to back up your data.
Click to expand...
Click to collapse
No, I've only wipe cache partition made, I will try with factory reset......
Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
You're not alone buddy. I'm in the same boat. Have sent mine for repair yesterday.
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
I think I may have the same problem. My phone wont boot past the logo at all. IDK what to do at all.
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
KLit75 said:
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
Click to expand...
Click to collapse
7 months...
Sent from my Nexus 4 using Tapatalk
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
hgil said:
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
Click to expand...
Click to collapse
Check if you can boot twrp. If you're not successful send the phone for repair. No option available to recover from this king of hard brick yet.
Weird thing is anything and everything is doable in fastboot. Moment you try to boot OS or recovery, gets stuck indefinitely in Google logo and reboot.
Sent from my Nexus 4 using Tapatalk
this exact thing literally just happened to me on Thursday. I was fully stock never unlocked the bootloader or anything. phone suddenly started looping, tried wiping cache, doing factory reset, finally went nuclear and unlocked the bootloader and flashed system images. nothing worked. warranty replacement is enroute.
I bought it on release day.
Old issue with Nexus devices. Has been going on since Nexus 5
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
sunseb said:
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
Click to expand...
Click to collapse
Did they give a new/refurb or was it they changed motherboard/memory chip?
Sent from my Nexus 4 using Tapatalk
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
sunseb said:
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
Click to expand...
Click to collapse
Thanks. Just was curious on what I could expect.
Sent from my Nexus 4 using Tapatalk
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
That really sucks, but doesn't sound like a hardware failure from my understanding... I lost ALL my data when I had to send it in, since my failure resulted in no access to the internal memory... Lost a few pictures which was a real bummer, but lesson learned and now I'll be backing up my memory more frequently and also setting up cloud backup for photos
bagarwa said:
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
Click to expand...
Click to collapse
It's likely a software failure. When you flash via fastboot, do you reboot back to bootloader after flashing radio and bootloader? If not then that's likely what's causing the fast boot method to fail for you. The first time after I did a complete fastboot flash of the software I fell asleep and woke up in the morning to my 6p still at the boot screen. When I re-traced my steps I found out that my mistake was not properly rebooting after flashing radio image, then doing another reboot after flashing bootloader.
Got my device back. Same exterior. Was told that motherboard was changed. I could notice that from fastboot.
eMMC changed from Samsung to Toshiba
DRAM changed from Hynix to Samsung.
My device joins this list. Gonna send it for repair tomorrow and hoping it is covered under warranty.
Additional update. I know I missed the bigger scheme that changed. My IMEI.
Just curious what happens if I restore my previous efs partition backup after backing up current.
Sent from my Nexus 6P using Tapatalk
update: My phone came back in 5 days. Mainboard failure. Replaced in Warranty!! New IMEI!!
Sent from my AO5510 using Tapatalk
sunseb said:
Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
Click to expand...
Click to collapse
my phone randomly locked up, then rebooted today. But when it rebooted it was stuck with the white google logo flashing. I can get into the bootloader mode, but from there, choosing recovery or anything else gets back into the white google bootloop. I called service and they're sending me a replacement. Phone was stock with a locked bootloader.
I made the mistake of accepting the April 2018 update (VS9951BA) for my non-rooted Verizon VS995 and the update has been installing for over an hour now. Think I should let it continue or power off/remove battery?
Ideas?
In case anyone else runs into the same issue, I waited two hours just in case and finally pulled the battery. So far, the phone seems ok and the update seems to have installed successfully.
JCDinPGH said:
I made the mistake of accepting the April 2018 update (VS9951BA) for my non-rooted Verizon VS995 and the update has been installing for over an hour now. Think I should let it continue or power off/remove battery?
Ideas?
Click to expand...
Click to collapse
This had happened to me with the last update!
I removed the battery, waited for 5 minutes and put it back in. Everything worked fine.