Related
Hi, I have a friend who has just smashed their Desire S whilst out on Sat.
Unfortunately, as the title says, they have no screen (touch doesnt appear to work either but no real way of telling!), not root, no USB debug and I have already checked and they didnt have their contacts set to sync with their google account but with the phone! :-/
Can anyone give any suggestions other than a screen replacement? They have already got an S3 on the way today so just want to be able to restore their contacts.
Cheers and thanks in advance!
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Aquous said:
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Click to expand...
Click to collapse
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
It is unlikely indeed that you will be able to recover the data as the phone is. If you're in the UK (possible as the phone is on Orange) and fancy posting it then I can stick my LCD and touch panel on it for you so I can recover the data.
Also if u r in the uk, try a phone repair shop that has jtag, they should be able to pull any data off the phone.
radeonorama said:
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
Click to expand...
Click to collapse
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Aquous said:
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Click to expand...
Click to collapse
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
radeonorama said:
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
Click to expand...
Click to collapse
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Aquous said:
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Click to expand...
Click to collapse
Yup, everything i needed off it worked.
I left it for a while as a last resort because of the risk of total data loss and bought a replacement screen which was DOA!
So you plan came into play and it really worked. It wasnt so hard as the steps you gave just helped me get the order right in my head rather than trying something and mucking it up even more!
Thanks again good sir! She was very pleased!
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data
same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Currently I am not able to switch on my phone !!!
AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!
Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.
The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.
hey there,
(new account since i can't access or recover my old one right now )
first of all, i'm on stock android 10, C3 update i think (the latest before yesterday's nov. update), neither rooted nor bootloader unlocked. here's my issue:
Final edit (smaller edits below):
No attempt worked, device had to be factory reset. Now Google can deal with the original issue of the screen behaving weirdly. (Seriously though, the display issues weren't even consistently present. Imagine a slightly greenish tint across the whole system, affecting and muddying the darker tones the most. Black was okay, because it's off on OLEDs anyway, but the launcher adds a brighter gradient with low color depth on top of black, ridiculing the desire of the pixels to be off. Weirdest thing ever, because it's not even visible on screenshots, but is following screen orientation. Now imagine not realizing that and sending a non-existing issue on a screenshot to Google support chat, then making a photo of it with another phone.)
edit: tldr version, because lots of text below: (edit: this didn't age well)
- stock android 10 (latest before nov.), bootloader locked
- sudden systemui crash loop (after changing wallpaper, green tint days before) on lock screen even in safe mode
- adb probably not enabled; fastboot lists device, no luck with adb (edit: adb sideload in recovery works)
- no backups; wanting to rescue my data;
additional attempts:
- safe mode also ended in sysui loop
- can get the loop at least stuck with its dialog box in emergency call ui, as well as with work profile switcher pattern prompt
- google's "find my device" inconsistently connects, seemingly by getting system stuck like above. could make it ring though, locking function reports success sometimes, but no further feedback
- adb sideloading . same version ota in recovery (is always enabled? system adb seemed disabled, so i wonder) didn't seem to change anything, sideloading nov. update processed at the G logo loading for a while, but systemui looped again afterwards.
edit: maybe incomplete? terminal ended both times at 94% and recovery at "...completed with status 0, so I thought is was normal (edit: it looks like it is, my Redmi reports even less percentage and status 0 with a successful flash)
Final edit:
- "fastboot continue", as well as parameters to switch boot slots didn't help in this case, both slots were affected and these commands aren't allowed on this locked bootloader
- "fastboot boot recovery.img" isn't either
- recovering data after a wipe is also a no; device is encrypted and therefore wipes the key to decrypt
- ADB sideloading already switches boot slots, no point in forcing it afterwards
- Getting the crash loop stuck by enabling the work profile seemingly provides enough time to input the pattern, but the system still prompted me to put it in before re-enabling fingerprints. Strangely enough, the profile successfully triggers, but that particular pattern has no effect on the regular lock screen (which essentially seem to trigger the exact same function. For God's sake if they had accepted that pattern to also unlock my fingerprints, I would have been able to recover all data.)
----
a couple of days ago i noticed my 3a was suddenly having a slight green display tint, which i was planning to fix or get fixed (haven't factory reset yet since i couldn't backup yet).
i recently started using cf lumen again to further dim the screen at night, so i assumed it was fixable misbehavior. i always disabled it in the morning.
occasionally i switched to a solid black wallpaper, because of the shadows/tints systemui uses to easily verify it is still there (the gradient shadow at the top of the launcher, which expands/darkens when you swipe the apps up, showed harsh steps, kinda like an image when lowering color depth).
Edit: Screenshots don't capture it, but it's following screen orientation and isn't present on settings in dark mode, maybe higher software layer that screenshots don't capture (looked silly, telling Google about it and sending a screenshot with no visible problem, 7/10 comedy).
Anyway, second troubleshooting with Google concluded with repair under warranty.
fast forward to today, i changed the wallpaper again (using an old quickpic version for an accurate portrait ratio, which has worked fine for months, and even longer on my phone before) and right after successfully applying it, systemui started its crash loop.
i could still temporarily unlock with my fingerprint, but it obviously locked again after crashing.
what made things worse, i rebooted and now i can't even temporarily unlock, because it asks for my pattern (which is default behavior), but i have barely a second to swipe up and enter it.
leaving the screen on and letting it loop now also reboots it into recovery mode after a while, prompting me with a notification that android couldn't boot and if i wanted to factory reset or try again, however, the booted ui looks functional and even quickly toggling the quick settings does work. i guess the failsafe triggers early, only because of systemui crashing.
----
so, i am now asking you helpful folks, what are my options to recover from this state?
i can't really afford deleting all of my files by factory resetting.
i don't have a google drive backup or a backup of my media. and correct me if i'm wrong, but i can only access the storage via usb by unlocking lock screen first, right?
i think i haven't used adb on it yet, if there's something i need to have enabled.
fwiw, i can also confirm that it shouldn't have any mechanical damage, since i used a spigen tough armor almost since i have my 3a and never did it drop with or without.
edit: i also booted into safe mode already, but the crash loop persists.
----
as of now, i'm gathering my options, so i apologize for not trying anything yet. i'm in the process of catching up to todays standards (e.g. a/b devices and stuff) and my time as a power user came to a stop late into the lifespan of my beloved nexus 5.
i'll probably update this post in case i have anything to report or forgot to add any details.
anyway, thank you for reading and for hopefully providing some directions in advance.
The simplest solution would be to just reflash the stock OTA. You can try dirty or do a factory reset first which should for sure work but is obviously more extreme.
Download the OTA here and move it to your PC
Reboot to bootloader
Reboot to stock recovery
Select ADB sideload
Open a terminal and adb sideload sargo-ota-qp1a.191105.003-a8fe1786.zip
Alternatively you can simply try reflashing the stock boot.img from the Nov update but if the SystemUI is corrupted that wont fix it.
ctfrommn said:
The simplest solution would be to just reflash the stock OTA. You can try dirty or do a factory reset first which should for sure work but is obviously more extreme.
Download the OTA here and move it to your PC
Reboot to bootloader
Reboot to stock recovery
Select ADB sideload
Open a terminal and adb sideload sargo-ota-qp1a.191105.003-a8fe1786.zip
Alternatively you can simply try reflashing the stock boot.img from the Nov update but if the SystemUI is corrupted that wont fix it.
Click to expand...
Click to collapse
thanks for your suggestions and the steps you provided. flashing the boot.img reflashes the kernel, doesn't it?
like you said, systemui seems corrupted, or was fed something invalid and is now struggling, so i would try to reflash the whole update via sideload.
i already had something similar in mind, but since i had adb disabled, i thought that wouldn't work. so i just booted into recovery, selected the sideload option and (little did i know) it showed my device in "adb devices".
since i was on the october update (c3? the latest before november's), would you recommend grabbing the same version and dirty flashing it, or go right to the november one?
and because i'm dirty flashing, i guess i would to keep my internal storage intact, maybe even app data?
i've seemingly got nothing to lose anyway, an extensive chat with google support also ended in resetting as the only option.
flashing the boot.img reflashes the kernel, doesn't it?
Yes
since i was on the october update (c3? the latest before november's), would you recommend grabbing the same version and dirty flashing it, or go right to the november one?
You could start with Octobers. That will have the smallest risk.
and because i'm dirty flashing, i guess i would to keep my internal storage intact, maybe even app data?
Yes, all will remain in tact
ctfrommn said:
flashing the boot.img reflashes the kernel, doesn't it?
Yes
since i was on the october update (c3? the latest before november's), would you recommend grabbing the same version and dirty flashing it, or go right to the november one?
You could start with Octobers. That will have the smallest risk.
and because i'm dirty flashing, i guess i would to keep my internal storage intact, maybe even app data?
Yes, all will remain in tact
Click to expand...
Click to collapse
unfortunately, flashing the existing version didn't change anything, still was force closing systemui...
after that, i sideloaded the november update, which was processing at the G logo loading screen for a while, but in the end, it resulted in the same systemui crash loop.
what i did try in addition, was visiting google's "find my device", successfully making it ring after getting the fc loop stuck with the emergency call ui as well as by switching to the work profile and triggering a pattern prompt. however, only the locking command acted like it was working, but didn't help. installing anything remotely from the play store also didn't give any feedback whatsoever.
right now, i'm out of options... it seems the only obstacle is the lockscreen (which i can almost unlock in those 2 seconds to re-enable my fingerprint) and adb not being enabled. the quick settings toggle properly though, and the ui including the wallpaper render correctly.
----
again, if it's of any use, i can get the loop stuck without being able to interact with anything afterwards by opening the emergency call interface or the work profile switcher. it displayed the fc window at least, which got the loop stuck, but going nowhere.
sysuicrash0511 said:
unfortunately, flashing the existing version didn't change anything, still was force closing systemui...
after that, i sideloaded the november update, which was processing at the G logo loading screen for a while, but in the end, it resulted in the same systemui crash loop.
what i did try in addition, was visiting google's "find my device", successfully making it ring after getting the fc loop stuck with the emergency call ui as well as by switching to the work profile and triggering a pattern prompt. however, only the locking command acted like it was working, but didn't help. installing anything remotely from the play store also didn't give any feedback whatsoever.
right now, i'm out of options... it seems the only obstacle is the lockscreen (which i can almost unlock in those 2 seconds to re-enable my fingerprint) and adb not being enabled. the quick settings toggle properly though, and the ui including the wallpaper render correctly.
----
again, if it's of any use, i can get the loop stuck without being able to interact with anything afterwards by opening the emergency call interface or the work profile switcher. it displayed the fc window at least, which got the loop stuck, but going nowhere.
Click to expand...
Click to collapse
Time to clean flash it sounds like.
ctfrommn said:
Time to clean flash it sounds like.
Click to expand...
Click to collapse
i'm afraid you're right... i'll probably get a spare phone soon and let the 3a sleep for a couple of days, in case a miracle happens.
another question, and sorry to bother you barely on topic, but do you think i could recover some data from the internal storage after factory resetting or even clean flashing? (partitions/mounts don't use reserved memory sectors, i guess?) i mean, a wipe does only delete and doesn't overwrite for the most part, right? i'd look for a recovery solution another day, if deemed viable.
You should be able to backup everything. When you plug it in the internal storage mounts, yes? If not, you may have to try adb pull. And a clean flash these days with the way Google backs up and restores everything isnt near as big of a deal as it once was.
Alternatively, you could try just wiping the system partition(s) and leave internal storage alone. Not sure if thats an option anymore with the way this phone is partitioned though.
ctfrommn said:
You should be able to backup everything. When you plug it in the internal storage mounts, yes? If not, you may have to try adb pull. And a clean flash these days with the way Google backs up and restores everything isnt near as big of a deal as it once was.
Alternatively, you could try just wiping the system partition(s) and leave internal storage alone. Not sure if thats an option anymore with the way this phone is partitioned though.
Click to expand...
Click to collapse
basically coming from a nexus 5 as my main device, everything was straightforward, or it was because i had it for that long.
in case i miss something or lack the knowledge, mounting it over usb requires the screen to be unlocked once, right?
since adb sideloading worked, this doesn't imply i had usb debugging enabled, does it?
at this point, i only care about my internal storage, my app data isn't as important and i didn't back it up in drive anyway. and before posting the thread, a google search seemed to confirm, that a reset would indeed affect the internal storage partition, which is why i've been hesitant.
i would reset the device in a heartbeat if i could pull my media before. :/
anyway, thank you for your help so far, really appreciated.
I also came from Hammerhead and Shamu so this device is still a learning curve for me as well. I think youve exceeded my ability to help as Ive never dealt with this. Reflashing the OTA should fix this so the fact it didnt is very odd. The combination of this device and Android 10 has introduced a lot of oddities which is why development is so slow right now.
Still haven't reset my device, really wanting to keep the internal storage (app data not as important), so I apologize for bumping.
Quick summary (full story and attempts above), if there's still anyone wanting to help me salvage my data:
- stuck in infinite SystemUI crash, thus retriggering screen lock
- bootloader locked, adb probably disabled (sideloading in recovery works)
- completely unmodified stock 10, crashing started after checking for update (didn't initiate on mobile data) and upon changing wallpaper a couple of minutes later
- wiping would include storage afaik
- sideloading update didn't recover (see below)
- was on October version, can't confirm successfully sideloading November's (terminal always finished at 94% and recovery told "completed with status 0"
- can't mount via USB because can't bypass lockscreen
Yet to try (need to use a friend's laptop)
- remotely booting TWRP (on 10 though, so not fully compatible afaik)
What's seemingly holding me back, or "entry points"
- remotely enabling adb (hopeless I guess?)
- disabling screen lock (although crashing, toggling quick settings persists)
- mounting internal storage from wherever
- wiping app data from SystemUI, or factory resetting without wiping storage
- any exploits, since it's my very own phone (I can provide proof, if needed)
Any further help appreciated, thank you for reading.
Have you tried flashing full factory image?
Edit the flash-all.bat file and remove the -w to keep your data also make sure you have latest platform tools (adb,fastboot).
kc6wke said:
Have you tried flashing full factory image?
Edit the flash-all.bat file and remove the -w to keep your data also make sure you have latest platform tools (adb,fastboot).
Click to expand...
Click to collapse
I haven't yet, no, thanks for the suggestion. I'll try it when I get my hands on that laptop again.
It's running Xubuntu (so probably a flash-all.sh), updating adb/fastboot should be child's play.
To be clear, by "keeping [my] data", do you mean the internal storage, app data, or possibly both?
I assume -w is the parameter for wiping, but not sure how that affects partitions on our Pixel.
(Also sorry for not responding sooner, didn't see the notification :/ )
sysuicrash0511 said:
I haven't yet, no, thanks for the suggestion. I'll try it when I get my hands on that laptop again.
It's running Xubuntu (so probably a flash-all.sh), updating adb/fastboot should be child's play.
To be clear, by "keeping [my] data", do you mean the internal storage, app data, or possibly both?
I assume -w is the parameter for wiping, but not sure how that affects partitions on our Pixel.
(Also sorry for not responding sooner, didn't see the notification :/ )
Click to expand...
Click to collapse
The -w is for wiping the internal storage. if you remove it you don't lose anything (apps and data, pics, etc..)
if you don't remove it, it wipes internal (as if it was new).
kc6wke said:
Have you tried flashing full factory image?
Edit the flash-all.bat file and remove the -w to keep your data also make sure you have latest platform tools (adb,fastboot).
Click to expand...
Click to collapse
hey, quick update:
i wasn't able to flash the factory image unfortunately. it fails the flash command because of the locked bootloader...
----
additional question to anyone regarding sideloading:
the process always seems to run fine in my terminal window, however, it always ends at
Code:
serving: '/home/myname/Downloads/sargo-ota-qp1a.191105.003-a8fe1786.zip' (~93%
serving: '/home/myname/Downloads/sargo-ota-qp1a.191105.003-a8fe1786.zip' (~94%
Total xfer: 2.00x
while the recovery log on my phone says
Code:
install from adb completed with status 0
after something going through something like "step 1/2" and "step 2/2" (cant remember exactly, but there wasn't much more).
anyone got a clue?
As you found out, the only option available to you with a locked bootloader is the "side load" option - which you have already tired. Just to be sure, you did flash the correct factory image - the Google page lists every Pixel device and you have to make sure you download the correct one.
Outside of that very small possibility that you flashed the incorrect version, I think you will have to contact Google support for help/repair.
sic0048 said:
As you found out, the only option available to you with a locked bootloader is the "side load" option - which you have already tired. Just to be sure, you did flash the correct factory image - the Google page lists every Pixel device and you have to make sure you download the correct one.
Outside of that very small possibility that you flashed the incorrect version, I think you will have to contact Google support for help/repair.
Click to expand...
Click to collapse
I'm pretty sure I flashed/sideloaded the correct one, I think I even verified the November update version in my quick settings (during the one or two seconds the UI takes to crash)...
I've thought the 94%/status 0 messages were normal, something like finishing the remaining 6% in an instant (for checks or so).
I have yet to try factory resetting, and I'm sure that'll fix it (which the Google support chat concluded as well), but I don't want to wipe my internal storage just yet.
Ironically, I rebooted the first time it crashed, hoping it would fix it. But all that did was forcing the pattern lock. Before, I was able to fingerprint unlock it instantly and even interact with the system for a second (probably to enable ADB, USB, ...).
But now, I have to swipe up and put in a complex 9 point pattern in 1-2 seconds, which I can physically get to 8...
It seems, the remaining single point of my pattern could rescue every single bit of my data.
I had forgotten that you haven't tried to factory reset the phone. Unfortunately I think that is your best/only option at this point. I do think that will work, but if not then it's going to have to be escalated to Google for more assistance.
If anyone cares, I updated the mess of my OP to be even more of a mess.
TL;DR: No idea worked, was forced to factory reset.
Now it's Google's turn to repair my display issue, which I almost forgot about.
Thanks to anyone who read and tried to help. Probably not a useful post for anybody, maybe the collection of ideas are, though.
Have a great day.
have you given any thought to unlocking the bootloader now that you have to start over?
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
If you can enter recovery mode try to sideload the same exact ota package of the rom she's running, maybe that can help. Good luck!
andyysk said:
Hi all,
Im in a desperate and urgent need of help.
My Mrs pixel 7 pro is stuck in a boot loop that restarts 5 seconds after the google writing appears when starting. I wasn't home when it happened but she doesnt really make sure her phone has some battery before turning it on, as soon as she sees 2% she starts it, so im guessing maybe she bricked it while the phone was trying to apply an update when turning it on as she said that the external battery didnt have any juice left inside.
Anyway,
I know i can wipe the phone from recovery mode and make it into a factory reset phone. The issue here is we have over 6000 photos and videos of our son in that phone that she hasnt copied to the external hard drive i gave her for months due to her not liking that her little laptop is slow.
I tried recovery mode Reboot, i tried going into safe mode (no luck as it will go straight into fastboot mode). She doesnt care about a lot of things and obviously she never unlocked the developer setting or bootloader so device state is also locked.
I am begging you, anything any info or advice on how i can get those pictures out of the phone. Is there any way i can flash the stock firmware just to make the phone start and copy them after?
Any possibility or chance or retrieval?
I am willing to pay anyone that can guide me in the right direction as there are over 6 months worth of photos and memories.
Thanks in advance and may the luck be on my side.
Click to expand...
Click to collapse
As @acuicultor said;
Here's Googles official OTA updates and instructions etc.
From what i've read briefly and as far as i can gather (still running a stock pixel 7 pro - for the first phone in god knows how long, so i'm not well read on this device but...) if you can sideload the latest OTA update via sideload then you should in theory be able to save the data and boot again. But if you flash full firmware then your device will be wiped in the process (if that's even possible with a locked bootloader).
Very best of luck
EDIT: hmm thinking about it, you won't have enabled USB debugging in dev options, hang on, i'll reboot direct to recovery to see if i can get the device recognised without USB debugging enabled. Sorry to be vague (hopefully someone more experienced with this device will chime in with more advice), like i say, i'm not rooted, flashed with custom rom - nothing, just plain old stock so i've not read up much on proceedures for this device. Bare with me!!
Had another thought, do you or have you been using Google photos to view your images on the device. If so, did you enable backup photos online when you first set the app up? If so, they could be backed up automatically...
Edit: my bad..
Try this link
If that fails just Google 'Google photos sign in'
Just tried from recovery to run some adb cmd's, no joy without enabling debugging 1st
There may be hope... If your photos aren't backed online already from above link...
EDIT:
1. From power off state (make sure the device is charged before apply any ota update) Press vol down and power together. As soon as it boots to google logo, let go of vol down, then power. That will put you in fastboot mode where you use the vol up/down to navigate to Recovery mode and power button to select.
2. Then when you have the screen that says 'no command', press power button and CLICK vol up (releasing vol up straight away but keeping power pressed). That'll take you a blue menu at top of screen.
3. Use vol buttons to navigate to 'apply update from adb'. I have checked using 'adb devices' and 'adb reboot sideload' cmd's on PC and the device is now recognised...
Will write further instructions shortly. (no guarantees this will work tho without losing data...or even if it'll work at all - i suspect the OTA update with just fail to transfer)
OR there is another option, using the same instructions above (1) in fastboot mode use the volume buttons to navigate the menu, power button to select Rescue mode. Then contact your service center for support who will advise/offer support - hopefully, which may end up having to send the device in and still offers no guarantee of preserved data
reg66 said:
@acuicultor said;
Here's Googles official OTA updates and instructions etc.
Click to expand...
Click to collapse
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
WoKoschekk said:
Following the link it's all explained there:
- no USB-Debugging needed
- booting recovery by key combo
- no loss of any data when using the OTA files
Also turning on USB-Debugging in developer options is not necessary for the recovery. It's enabled by default and moreover the recovery doesn't consider any system settings like disabled/enabled USB-Debugging.
Click to expand...
Click to collapse
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
reg66 said:
Ahh cool. I obviously didn't read much of it! Dunno what's happened to the chap, maybe his wife has killed him lol
Click to expand...
Click to collapse
yes, maybe...
FYI: Stock recovery only uses a minimal adbd with a very limited set of commands. That's why some known ADB commands won't work.
minadbd