My Pixel 3 XL had a pending security update. When I restarted the phone to install, I could no longer use my pin to get into the phone. After several attempts (thinking I had forgotten the pin), I was forced to do a remote erase/reset of the phone. At this point my phone would no longer boot. When I tried to fastboot using the power+ volume down button, I get an "device state: error" similar to what Ofuroski mentioned on this thread (https://forum.xda-developers.com/pixel-3-xl/help/device-error-t3885161). The recovery mode does not work either. This issue is also mentioned by raeray2 on this reddit thread https://www.reddit.com/r/GooglePixe...el_3_xl_died_and_wont_turn_on_again_fastboot/ though the thread itself gets distracted into battery/cable issues and does not address this one.
The reason I am starting a new thread is because I could not find a official solution to this specific issue.
After several frantic attempts, I called Google support. They tried the same things with no luck. They think the update could have gotten interrupted causing this issue. They are sending me a replacement as I am still within warranty. I will also post on Google's forums to get feedback.
Related
OK so I recently switched this neat, cheap and decent entry phone, and of course wanted to root and unlock the bootloader.
Using the technique outlined in http://forum.xda-developers.com/showthread.php?t=2066887 "[ROOT][CWM] Huawei Ascend Y201 Pro U8666" I managed to happily root the device. Meaning I could install droidwall and adfree, and uninstall one or two of the annoying Huawei apps. (Surprisingly there are less Vendor apps on this than the previous Ideos U8150 I had.)
So happy that that worked, I thought I would go to the next stage and unlock the boot loader, in preparation for maybe installing clockworkmod recovery. And eventually a ROM if I could find one that looked "safe" and sound.
Cranking up the "UnlockBootloader.exe" as before and clicking the unlock BOOTLOADER initiated something on my phone... However when I switched off my phone preparatory to rebooting, I found what I guess to be a bricked/borked device.
There's no vibrate, no flash on screen, no logo, no pink screen that other people talk about in the few reports I have found around the web. Just that the lower backlit soft buttons flash ten times and then nothing else happens. I can't even find information about what this obviously low level failure message means...
As you can guess, I have tried all sorts of things to get it going: battery removal; powering from USB while botting; any and all of the key press holds for boot; all to the same effect. Have tried several times to find anything similar on the net and can't seem to find anything similar. Especially the ten flash indicator
So my question is "Is this an absolute sign that the device is bricked?" I guess I could try to play the innocent and send it back under warranty, but I guess someone will realise it was my fault. Unless a memory failure happened at the exact time I was flashing/unlocking...
And a warning that same device owners should be careful when following the guide. I'm pretty sure I had everything as outlined. I'm running XP, didn't have it mounted, had fastboot off, etc... Although now its hard to check on the device to see if that was the case
and also
I should also perhaps add that before using UnblockBootLoader with root success, I tried the ICS "adb restore" directory traversal vulnerability, which is part of Root_with_restore, and was unsuccessful.
And that there's no life reported at a low, USB device level to my linux kernel, when plugged in now. So I can't even try a firmware patch using adb etc.
Of course I can't post a relevant cautionary note into the above mentioned thread, as I have yet to reach the 10 post milestone mark, enabling me to post in that section...
Hi,
Sorry for opening an old thread, have the same issue and just wanted to know if you manged to resolve this or it you just took it back to the shop?
Regard
No solution
No - I never managed to work out or find a solution. I just got a new one, and only went as far as the root'ing stage.
I have never seen an applicable ROM for this device anyway, so I guess it wasn't too much of an issue. And root'ing to get those crucial management apps installed, and also being able to remove some Huawei "cruft" is the real thing you need.
Hello.
I have the ZTE axon A1R (not pro) and about a month ago I received a notification for a update to marshmallow 6.0 and so I went through the process, and it completely froze and would not boot.
Since then I did a factory reset however I cannot get passed the sign in screen where it asks you to sign in with the gmail that was previously associated with the phone. I have done this countless times and it simply does not accept the email even though it is correct. I have initially waited 3 days and since then tried many many times but it simply throws me back to the sign in screen.
I have tried the other option where google sends a code digit and this doesnt work wither.
I have been in contact with zte customer service but it is a complete joke. They have done absolutely nothing to help me and what I thought would take a couple of days at the most to fix, has now been over a month and is very frustrating. They keep sending me email to "wait and that they forwarded my concerns to the appropriate people to help" however this has not happened in over a month now.
what can I do? (I tried searching for this problem here on xda forums and google in general but cannot find the relevant information. Mostly what I find is stuff for the pro version of this phone)
Thank you
Hi !
Is this thread useful ?
Cheers !
xanthrax said:
Hi !
Is this thread useful ?
Cheers !
Click to expand...
Click to collapse
hi,
thanx for trying to help but sadly the above is for the Axon 7.
i am only able to find information (on xda) regarding Axon 7 and axon pro neither of which is my phone.
mine is the regular axon (A1R) http://www.gsmarena.com/zte_axon-7686.php
I should note that I am not so much interested in rooting it or anything like that.
I just want to be able to use it again under any circumstance but I simply cannot get passed the "sign in with email previously associated with this phone" because it keeps sending me back after I put in the correct information.
ZTE has been a complete failure in helping me even though it was their update that has cause me problems in the first place
Try to change the email password from another device, a pc maybe
Sent from my SHIELD Tablet using Tapatalk
xanthrax said:
Try to change the email password from another device, a pc maybe
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
I have done that.
no go.
and the weird thing is that, when i do type in the wrong password, it knows, and says so... but when I type in the correct one, it doesnt say anything, just jumps right back into the 'please sign in with the email associated with this password' screen.
I think it may be a issue with the update itself.
I cannot get passed the 'verify your account'
page. I tried everything, I keep putting in the
correct email and password, and even trying with the
code that google sends via text, and it always just
sends me back to the 'verify your account'.
THis is a problem with ZTE update. It fails to
recognize the previous email that was associated to
the phone.
When I power the phone while holding the 'up' button
and go into android recovery, it says:
ZTE/P897A10_ROGERS/billy
6.0.1/MMB29M/20160707.005703
So it seems that even though I have reset the phone
into factory reset, it has still applied the 6.01
update which is not what the phone came with when I
bought it (it came with 5.01)
Perhaps this is the problem and why it is not
recognizing the email associated with the phone.
I dont know why it says "ROGERS/billy"
Rogers is not the carrier that I am with and billy is
not my name.
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again. After it gets detected, it will work fine for about 12 - 15 hours before the issue comes back again. When the issue occurs, my mobile network option in the settings will get greyed out. (see attachment below)
Went to my carrier and get a new SIM. Still, the issue persists. Even tried an E-SIM and it still doesn't work
I have contacted Google support and they told me to send my device down for repair and inspection however, even after repairing my device, the issue still persists. Factory reset does not fix it as well. Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
I saw that there was the September security update patch yesterday and I went to update it, however, the issue is still there
I then proceeded to contact Google support again and they kept telling me to send it for repair even though I already have?
Does anyone have a clue what to do?
Felixxxxx said:
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again.
Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
Click to expand...
Click to collapse
If others are experiencing the same issue after the update, then that highly suggests the problem was caused by the update.
So, unfortunately, ONLY google can fix it with another patch and you will have to wait until google gets around to fixing it.
I have similar problem though I thought it's caused by android 12 beta so I outped out it and everything was fine for few days. I restated my phone after day or two and the problem of no serivce came back. This time even factory reset didn't help.
I can't manually change preffered network type to 2g/3g and everytime I try to make a phonecall it says i need to turn off aeroplane mode off.
Felixxxxx said:
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again. After it gets detected, it will work fine for about 12 - 15 hours before the issue comes back again. When the issue occurs, my mobile network option in the settings will get greyed out. (see attachment below)
Went to my carrier and get a new SIM. Still, the issue persists. Even tried an E-SIM and it still doesn't work
I have contacted Google support and they told me to send my device down for repair and inspection however, even after repairing my device, the issue still persists. Factory reset does not fix it as well. Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
I saw that there was the September security update patch yesterday and I went to update it, however, the issue is still there
I then proceeded to contact Google support again and they kept telling me to send it for repair even though I already have?
Does anyone have a clue what to do?
Click to expand...
Click to collapse
Wow, unfortunate for sure. Isn't it possible to roll back to just before the update? Of course google makes the entire firmware available and I believe I've read if you remove the '-w' at the end of the script it doesn't wipe data?
At least if this was possible it would certainly indicate if it was the update or not?
cheers
So my Pixel 4a updated to the October Security Patch this night, and from there on it says "SIM not detected".
But when I go in settings it shows the network name.
I tried switching the SIMs with my Pixel 2 and everything works there, but any SIM I put in my 4a shows "SIM not detected" even though it can detect the network.
Which it probably wouldn't do if the SIM slot were defective, right?
And the timing with the update is too much of a coincidence...
I have similar issue - Pixel 3A, after update with November Security Patch, "No simcard" error appears with mandatory reboot. Tried with different SIM, there was prompt for PIN, verified and then it seems no access to simcard data. Even "emergency call" is no allowed from now. Looks like additional privilidges needed for access SIM card. No clue, how to proceed...
Hello. Rather new here. I have newly purchased a Red Magic 7 Pro from their Official Website. It hasn't even been 10 minutes since I got it before it started having problems like random shut down and reboots.
I've reached out to their support page now where they've told me to try updating the version of the phone. I've done both online updates and local updates, but neither method worked. I've thought about sending the phone back for a replacement if this continues, but I'd rather see if I can resolve the issue first before resorting to that
Mine is the global version and I've been told the update to download in the US and Asia update 3.14. The current version it's running is 3.12
I've considered rooting the device to see if I can do a true factory reset since their method of resetting it via the phone's settings and getting in its debug menu has done nothing. But it's still under warranty so if they give me the option to return it for a new one I will. Hopefully, if this is busted, it's only this particular phone.
When you got the the phone new did you transfer the data of your old phone?
Yea I was trying to transfer files at the time to my other android.
Pokemonaces said:
Yea I was trying to transfer files at the time to my other android.
Click to expand...
Click to collapse
There was a bug in the beginning i've you transfer files the Cellar data will never connect and turn off on with cause the phone to overheat. But you got a different bug i see. you can only try to update the phone to 3.14 or factory reset without transfer the apps first and update then. Btw ask on Reddit there are more active people.
Reddit link: https://www.reddit.com/r/RedMagic/
Update link: https://help.redmagic.gg/hc/en-us/articles/6360319907865-REDMAGIC-7-Pro\
I've tried updating first before transferring, but I get the same errors on the images above.
Depending on how often it reboots, in some cases it gets stuck on gaming mode and I have to wipe the data via holding down the volume down and power button method.
Some other causes include missing apps as it keeps resetting. The common factors is that certain games fail to download and random reboots.
The reboots happen pretty frequently when I try to update using Wifi. Even if it does go through, I get the update package error or poor signals error even though I have a solid internet connection.
And thanks I'll check out the Reddit page for more solutions there
Pokemonaces said:
I've tried updating first before transferring, but I get the same errors on the images above.
Depending on how often it reboots, in some cases it gets stuck on gaming mode and I have to wipe the data via holding down the volume down and power button method.
Some other causes include missing apps as it keeps resetting. The common factors is that certain games fail to download and random reboots.
The reboots happen pretty frequently when I try to update using Wifi. Even if it does go through, I get the update package error or poor signals error even though I have a solid internet connection.
And thanks I'll check out the Reddit page for more solutions there
Click to expand...
Click to collapse
Hmm can you check your google play system update. There is a bug that hasn't been fixed it can't update so the phone will reboot twice.
The only options is to reflash the software or send it back for a replacement.
I have reset my Oneplus 7 device, yesterday. On setting up the device it gets stuck after the agreement page for Co-Creation lab setup. I have seen many people on reddit having similar issue starting from yesterday. What could possibly be the problem and is there any workaround?
UPDATE:
Apparently we can move forward from this screen after going back and press agree/disagree and keep doing this multiple times (until it hopefully works). No idea why the issue exist in the first place, and why doing it multiple times helps. Ideas if any is appreciated...
Similar issue:
https://www.reddit.com/r/oneplus/comments/w22zqw
,
https://www.reddit.com/r/oneplus/comments/w2k16w
Me too facing the same issue .. any solution .. it's a Nord 12 + 256