Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
When the bootloader is unlocked, "allow oem unlocking" is greyed out.
You use fastboot commands when flashing firmware and locking the bootloader
Code:
fastboot devices
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
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
wehramausi said:
Hi everyone,
I just bought a Google Pixel 5 with Android 11 that was declared "new" and when I got it, from the first time powering it on, I got the security alert that the bootloader is unlocked, see photo attached. For several personal reasons I cannot easily send it back, so I tried to understand what this means but I am no developer. I tried an entire day to install ADB, put the phone in developer mode and download the firmware image from the official source, I got to the point where the ADB devices command showed the phone as connected but then nothing else worked. In every video or guide online, the steps varied from what I had in front of me, or did not yield the same results, or how the files looked was different (I downloaded the same firmware version that is installed on the phone from the official Google page but never had an image file, just various other very non-descript files in it). As I am pretty clueless, I tried googling my way around the error codes I got but everything I tried didn't work. I either got more error codes, answers like the ADB server is already killed, or that flashing command that just returned something like "waiting for available device" and got stuck on it, or nothing happened at all. Then I figured out that the option in the developer menu "Allow OEM unlocking" is greyed out and I read then that there are phones where you simply cannot lock or unlock the bootloader. However, all online guides I see are from people who have a locked bootloader and want to unlock it, and in my case it's exactly the other way around, it came unlocked and I want to lock it. I also tried a normal reset of the phone from the settings menu, deleting all data, and it didn't work. When I got into fastboot mode, I only could choose between Recovery Mode, Rescue Mode and Restart Bootloader, I tried all of them and none worked, and often the last thing that happened was that the screen turned into a small Android with an open chest, and a line "No command" and the only way to get the phone out of this was by pressing the power button for more than 10 seconds. Every time it restarts, the bootloader unlocked safety advice is showing.
After reading all day long about this, I suspect that the phone was probably refurbished. I wondered whether they maybe accidentally forgot to lock it or whether it was intentional, and in case it was intentional, if there is any way someone would have digital access to the phone. I want to understand if it would be possible for me to keep it without having security issues. I read that the unlocked bootloader is a physical problem, if your phone gets stolen or you physically lose it, someone might hack your PIN easier, or get easier access to your data. However, the PIN code and the standard data encryption also seem to protect my data enough. And tbh, as soon as my phone would be lost or stolen, I would delete all data via Find My Device. So I wondered... if it's impossible for me to lock the bootloader, can I still safely keep the phone and use it, with all standard security apps installed like an anti virus app, Google Play Protect and standard security features like PIN and fingerprint unlock and encryption and be safe, or is there any danger I am not aware of? Or is there any way to enable OEM lock or fix this somehow that I would be able to get done as a non-developer? As mentioned before, sending it back is too difficult at the moment so I am just trying to understand what this bootloader unlocked means for me and if it poses a threat to my security as a normal user? (Watching videos, online banking, emails, sending work-related but not highly data sensitive documents, paying with NFC..)
Thanks in advance! I really appreciate any insights to help me understand what this is, if there is any solution to it or if it actually poses no danger if I secure my data another way.
Click to expand...
Click to collapse
Trade you for a locked 4a 5g...
sipotek said:
Hey Bro can you share a method that how can I root Google Pixel 5, I tried a lot but i can't update the recovery mode? can you share some simple method like with the help of any Apk, or recovery file.
Click to expand...
Click to collapse
Lots of threads and guides online that show how to root
Related
The "black screen of death" is an error that's been occurring in X1095 devices after the 5.1 update. Google "moto x 5.1 black screen" and you'll see numerous complaints of the same:
http://forum.xda-developers.com/moto-x-2014/help/help-t3176829
https://forums.motorola.com/posts/c3be8d6f29
https://forums.motorola.com/posts/fe6a7fc56e
https://forums.motorola.com/posts/bbac67c0ef
I encountered this problem while on vacation so I stand to lose all of my vacation photos if I do a factory reset. I would sooner send my phone to a forensics lab and have them de-solder the memory and destructively recover my files, than perform a factory reset.
BUT I would much rather create a fix that everyone can benefit from, if possible.
The symptoms are:
- Phone at lock screen is an unresponsive black screen
- Active display works, but trying to open any apps through notifications brings me to the black screen.
- Camera opens by shaking, but can't interact with the screen. Volume button doesn't take picture. I CAN take pictures by using the camera timer on my Moto 360 watch.
- Voice commands work, Google Now opens normally, but can't interact with it. It invariably brings me to the "Unlock your phone to continue/say cancel to stop" but there's nowhere for me to apply my pattern lock. I am able to tap the blue word "cancel."
- Status bar and software buttons (back, home, recent apps) do not appear in any screens. The only way to determine battery level is through ambient display.
- I CAN launch Navigation through my Moto 360 watch without the "unlock your phone" dialog. Navigation functions normally except rotation is stuck in portrait, and I cannot interact with it except via the watch.
- I CAN send SMS etc through my Moto 360 watch. All of android wear seems to be functioning normally, except after wiping my phone's cache partition through stock recovery I no longer see notifications via watch.
- Phone is continually warm, can barely maintain charge even when plugged in.
- Holding the power button brings up the "Power off" popup which is clickable. Restarting in Safe Mode results in the same but with the words Safe Mode strewn across the lower left.
The culprit appears to be that com.android.systemui is broken, perhaps amongst other things. I believe this because:
- Apps all work fine
- No status bar or nav buttons display
Path #1:
Since the Pure Edition supports ADB Sideload with stock recovery and locked bootloader, my ideal solution would be to create an "OTA" zip package someone could sideload. It would basically spoof an update to replace com.android.systemui and clear all its (presumably corrupt) data. Is this possible? I've spent a lot of time researching, but I can't for the life of me figure out how ota zips are actually formulated. Is it like adb push where I can sideload the .apk I want from the stock ROM, or does it require something more elaborate such as building a version of the OS? This would be perfect because anyone with the Pure Edition could un-brick their phone, at least long enough to recover their files.
Path #2:
Since my Moto 360 seems to have access to my phone, I could conceivably connect it to my computer through adb and create a rescue app that uses the watch to retrieve my files off my phone. This would sadly only work for people who have smartwatches.
Path #3:
Wait for the next official OTA update and hope and pray that it fixes the issue when I sideload it. I have the luxury of setting my phone aside and being patient, but that doesn't work for most people. There is also the chance that the OTA does nothing.
Any advice how to get started on the sideload front? I'm willing to do the leg work, I just need help going the right direction.
bken said:
The "black screen of death" is an error that's been occurring in X1095 devices after the 5.1 update. Google "moto x 5.1 black screen" and you'll see numerous complaints of the same:
http://forum.xda-developers.com/moto-x-2014/help/help-t3176829
https://forums.motorola.com/posts/c3be8d6f29
https://forums.motorola.com/posts/fe6a7fc56e
https://forums.motorola.com/posts/bbac67c0ef
I encountered this problem while on vacation so I stand to lose all of my vacation photos if I do a factory reset. I would sooner send my phone to a forensics lab and have them de-solder the memory and destructively recover my files, than perform a factory reset.
BUT I would much rather create a fix that everyone can benefit from, if possible.
The symptoms are:
- Phone at lock screen is an unresponsive black screen
- Active display works, but trying to open any apps through notifications brings me to the black screen.
- Camera opens by shaking, but can't interact with the screen. Volume button doesn't take picture. I CAN take pictures by using the camera timer on my Moto 360 watch.
- Voice commands work, Google Now opens normally, but can't interact with it. It invariably brings me to the "Unlock your phone to continue/say cancel to stop" but there's nowhere for me to apply my pattern lock. I am able to tap the blue word "cancel."
- Status bar and software buttons (back, home, recent apps) do not appear in any screens. The only way to determine battery level is through ambient display.
- I CAN launch Navigation through my Moto 360 watch without the "unlock your phone" dialog. Navigation functions normally except rotation is stuck in portrait, and I cannot interact with it except via the watch.
- I CAN send SMS etc through my Moto 360 watch. All of android wear seems to be functioning normally, except after wiping my phone's cache partition through stock recovery I no longer see notifications via watch.
- Phone is continually warm, can barely maintain charge even when plugged in.
- Holding the power button brings up the "Power off" popup which is clickable. Restarting in Safe Mode results in the same but with the words Safe Mode strewn across the lower left.
The culprit appears to be that com.android.systemui is broken, perhaps amongst other things. I believe this because:
- Apps all work fine
- No status bar or nav buttons display
Path #1:
Since the Pure Edition supports ADB Sideload with stock recovery and locked bootloader, my ideal solution would be to create an "OTA" zip package someone could sideload. It would basically spoof an update to replace com.android.systemui and clear all its (presumably corrupt) data. Is this possible? I've spent a lot of time researching, but I can't for the life of me figure out how ota zips are actually formulated. Is it like adb push where I can sideload the .apk I want from the stock ROM, or does it require something more elaborate such as building a version of the OS? This would be perfect because anyone with the Pure Edition could un-brick their phone, at least long enough to recover their files.
Path #2:
Since my Moto 360 seems to have access to my phone, I could conceivably connect it to my computer through adb and create a rescue app that uses the watch to retrieve my files off my phone. This would sadly only work for people who have smartwatches.
Path #3:
Wait for the next official OTA update and hope and pray that it fixes the issue when I sideload it. I have the luxury of setting my phone aside and being patient, but that doesn't work for most people. There is also the chance that the OTA does nothing.
Any advice how to get started on the sideload front? I'm willing to do the leg work, I just need help going the right direction.
Click to expand...
Click to collapse
Path #1:
Won't work for 2 reasons. One, the OTA zips have to be digitally signed by motorola on the stock recovery. To flash another recovery which can use unsigned OTA zips means you would have to unlock the bootloader. Unlocking the bootloader erases the phone. Second, flashing stock firmware is confirmed to NOT fix it. The only known fix is format the data partition. Which means the problem is in the data partition somewhere, not in the system partition.
Path #2:
Would not work without root access on the phone. Since you have no root access, again no go.
Path #3:
Maybe in the next update OTA it could be fixed maybe not. This issue also exists in 5.0 as well, but it is much more rare. I had it happen to me on 5.0.
My suggestion:
If you don't wait on an OTA to see if there is a fix, bite the bullet and factory reset, unlock your bootloader. If you have an unlocked bootloader there will be options available to recover your files if this ever happens again via custom recovery like TWRP.
Sent from my XT1095 using Tapatalk
AGISCI said:
Path #1:
Won't work for 2 reasons. One, the OTA zips have to be digitally signed by motorola on the stock recovery. To flash another recovery which can use unsigned OTA zips means you would have to unlock the bootloader. Unlocking the bootloader erases the phone. Second, flashing stock firmware is confirmed to NOT fix it. The only known fix is format the data partition. Which means the problem is in the data partition somewhere, not in the system partition.
Path #2:
Would not work without root access on the phone. Since you have no root access, again no go.
Path #3:
Maybe in the next update OTA it could be fixed maybe not. This issue also exists in 5.0 as well, but it is much more rare. I had it happen to me on 5.0.
My suggestion:
If you don't wait on an OTA to see if there is a fix, bite the bullet and factory reset, unlock your bootloader. If you have an unlocked bootloader there will be options available to recover your files if this ever happens again via custom recovery like TWRP.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Would Path #2 stand a chance if I only wanted photos? I don't care about all my settings etc that would require root to access - I feel like Wear has at least that much permission on the phone? I really just wish I had a way to launch AirDroid...
It's a shame, I worry about hardware failure so I keep the bootloader locked to preserve my warranty. Then I suffer a software failure that I could easily recover from if I had voided my warranty, but because I didn't, I'm screwed. It always feels like a no-win situation, a gamble between whether software or hardware will fail first.
Maybe if there is an app for your watch that can see and backup your photos. Yes that is possible. But fixing it remotely via the watch is what would need root since it would need to modify files that it doesn't have permission to touch.
Sent from my XT1095 using Tapatalk
AGISCI said:
Maybe if there is an app for your watch that can see and backup your photos. Yes that is possible. But fixing it remotely via the watch is what would need root since it would need to modify files that it doesn't have permission to touch.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I didn't realize that AirDroid 3 allows access to the phone without any inputs from the phone, and luckily I had it installed! I recovered just about everything I wanted. PSA to everyone with a Moto X - Airdroid will save your butt if you get the black screen of death. I'm so happy right now haha
I don't care about fixing my phone, I only wanted my files. I only suggested to fix it via sideload so it would work long enough to recover my data.
adb backup command is your friend.
Only problem is I read somewhere that adb does not work either when you get the blackscreen problem.
Sent from my XT1095 using Tapatalk
Correct! There is no way to enable ADB debugging for those of us who don't leave it on 24/7. Also, IIRC people haven't had luck connecting to ADB regardless, presumably because I don't think you can connect with ADB until you unlock your phone and accept the computer's fingerprint? Neither of which you can do with a black screen. The only ADB you can access is sideload from recovery. If I had a custom recovery I could adb pull from within recovery, but with stock I cannot...
AirDroid has saved everything I wanted except my SMS, which is funny because it can read my SMS's, so worst case I can copy and paste into a text file... It's a minor thing to lose though. In any case, I'm switching back to my Nexus 4 until this gets sorted - don't want to risk the problem recurring with the Moto X. Maybe when that gets sorted I'll have a chance to offload them. Otherwise, no big loss, I got 99% of what I wanted.
Sorry for bumping an ancient thread BUT I just wanted to update that I fixed my phone and recovered ALL my data. Sideloading the next OTA through stock recovery fixed everything.
Didn't try it until recently; left the phone in a drawer while I went back to my Nexus 4 and then Nexus 5X. Finally gave it a go and it worked! Maybe someone else is in the same boat, and has a soft-bricked Moto X they can finally rescue their data off?
Hi,
I'm in need of help urgently!
Last week I had updated my Note 5 to MarshMallow and it was working fine. I remember the phone had never been off or restarted after the update until today when the battery ran out. Connected to charger and when I turned on the mobile it showed this message :
"Enter PIN instead of using fingerprint recognition after restarting device to protect fingerprints"
Now I've been unlocking screen using fingerprints from the time I got this phone. Unfortunately, I forgot the PIN and now I can't use fingerprints to unlock the screen. After a few failed attempts the wait time keeps increasing and now it has reached 30 minutes.
Is there anyway I can unlock my phone?
Please help ASAP!
Login into this website using your Samsung account
findmymobile.samsung.com/mindex.jsp
Find "Unlock my device" section
And make sure your device is connected to the internet then unlock you device
GreenXSI said:
Hi,
I'm in need of help urgently!
Last week I had updated my Note 5 to MarshMallow and it was working fine. I remember the phone had never been off or restarted after the update until today when the battery ran out. Connected to charger and when I turned on the mobile it showed this message :
"Enter PIN instead of using fingerprint recognition after restarting device to protect fingerprints"
Now I've been unlocking screen using fingerprints from the time I got this phone. Unfortunately, I forgot the PIN and now I can't use fingerprints to unlock the screen. After a few failed attempts the wait time keeps increasing and now it has reached 30 minutes.
Is there anyway I can unlock my phone?
Please help ASAP!
Click to expand...
Click to collapse
On the MM build, after a reboot you have to use the pin but subsequent times will be fingerprint, I have no idea why they did this. Sorry that happened to you, I have no idea how to get around that other than to keep searching, someone else had had that happen I'm sure.
Yep, I'm screwed, too...
I even kept a list of every iteration of PIN numbers I would ever use (they are generated by an algorithm). I have tried every one - and I am still locked out - with 60 minutes in between tries!
I have very, very important legal documents, notes, and recordings on my phone that I didn't get to backup yet. Unfortunately, most backups do not "dig" well enough under App directories to get all files generated by all Apps. So sad...
And "No", I can't access any sdcard or SIM bc it's an S6 edge+, and they are all locked into the case! The supposed Samsung "unlock" feature does not work, though it says it does.
Dying here! HELP...
Douglas333 said:
Yep, I'm screwed, too...
I even kept a list of every iteration of PIN numbers I would ever use (they are generated by an algorithm). I have tried every one - and I am still locked out - with 60 minutes in between tries!
I have very, very important legal documents, notes, and recordings on my phone that I didn't get to backup yet. Unfortunately, most backups do not "dig" well enough under App directories to get all files generated by all Apps. So sad...
And "No", I can't access any sdcard or SIM bc it's an S6 edge+, and they are all locked into the case! The supposed Samsung "unlock" feature does not work, though it says it does.
Dying here! HELP...
Click to expand...
Click to collapse
You're screwed really and this is why a lot of devs on here say to make backups! Your only option at this point is a firmware reinstall..
Rats! Catch 22...
MrMike2182 said:
You're screwed really and this is why a lot of devs on here say to make backups! Your only option at this point is a firmware reinstall..
Click to expand...
Click to collapse
But without root, I can't find a backup that will catch all the files well nested under App directories. With root, there are too many "gotchas" nowadays.
Besides, I know I have tried every PIN I would have ever set - so this MM "PIN" is a joke! There should have been a warning, as this is a serious disruption of service.
Wiping is just not an option - I have files created Friday, before the Upgrade, which would not have gotten backed up anyway. Besides, No update should block data access. One of you Gurus can't think of a workaround or push Samsung or Google for a fix? I'm thinking more like "Class Action Lawsuit" for disrupting normal access to my data and my lawsuit...
Anyone else that pissed?
Douglas333 said:
But without root, I can't find a backup that will catch all the files well nested under App directories. With root, there are too many "gotchas" nowadays.
Besides, I know I have tried every PIN I would have ever set - so this MM "PIN" is a joke! There should have been a warning, as this is a serious disruption of service.
Wiping is just not an option - I have files created Friday, before the Upgrade, which would not have gotten backed up anyway. Besides, No update should block data access. One of you Gurus can't think of a workaround or push Samsung or Google for a fix? I'm thinking more like "Class Action Lawsuit" for disrupting normal access to my data and my lawsuit...
Anyone else that pissed?
Click to expand...
Click to collapse
You need to learn to "manually" back your stuff up yourself and don't rely on any programs/apps to do it...
There's seriously nothing the dev community could do because for 1 it's not the right way to go about this because if someone's phone is stolen or whatever basically they'd be able to come to XDA-Developers and find a way around the phone being locked for 2 that's definitely not what devs do, we don't look for ways to break into a phone or circumvent the security. You should have backed up anything you knew was important, simple as that .. You need to factory reset at this point. Sorry.
I bought a Moto X (2014) with a broken/damaged screen for super cheap. When I bought it, it vibrated and made sounds so I knew it was functional. The next day, the alarm woke me up so I turned it off. The day after it happened again, so I just let it ring under a pillow until the phone died. Yesterday, the screen replacement finally arrived and I performed the switch myself.
When I tested the screen before closing it back up, the phone wouldn't boot, but the screen itself appeared to be functional so I closed it back up. The infamous green light issue was occurring, no doubt due to the fact that I let the battery drain completely then left it in a drawer for about a month, in addition to God knows what the previous owner had done to it.
After several hours of hooking it up to various chargers and cables and computers and performing a seemingly infinite number and duration of button combinations, it finally booted up, and started to charge normally.
Only then I realized it was still protected by the pattern code from the previous owner. Due to fear of FRP, I kept trying to crack the pattern code to no avail. Eventually I said frick it and went into bootloader mode to try and unlock the bootloader, but it turns out that adb is not enabled, and neither is the "allow bootloader unlock". So I said frick it and hit factory to reset the phone, but the phone simply rebooted. Odd. Alright, so I hooked it up to a computer in bootloader mode and performed fastboot erase userdata. Upon reboot, FRP had kicked in.
Hours of searching yielded various methods of bypassing this, none of which worked. However due to the blessing/curse (more on that later) that it's on Marshmallow, I was able to use a Google Assistant loophole to access pretty much the entire device (minus Google apps, including the play store). This included the settings app. To my dismay, I'm unable to activate dev options and the reset button is greyed out, no doubt due to a group policy preventing these functions until the owner's Google account is entered.
I came across a method that showed a lot of promise. Through the use of an app called Quick Shortcut Manager, it allows you to log into any Google account and once you reboot afterwards, FRP is no longer an issue. However in my case, since I seem to be exceptionally lucky, during the sign in process, the phone reboots unexpectedly. How very odd. Retried several times under various conditions, including Force Stopping all Google apps (which returns the navbar buttons, without function, and also the notification tray but not quick settings).
Alright. I installed Telegram via apk and logged in. As soon as I logged in, the phone reboots unexpectedly again, which leads me to believe that this random reboot occurs whenever ANY account is added to the device (because Telegram accounts are saved under Settings > Accounts).
Knowing I'm stuck with a locked bootloader and no way of unlocking it without accessing dev options which I'm unable to do, I decided to try flashing an earlier build. I downloaded 4.4.4 and 5.0.1 factory images and proceeded to try flashing 4.4.4, to no avail, since apparently downgrading is also impossible with a locked bootloader. Most commands returned a "remote failure" response. I continued anyway and upon reboot I discover that nothing has changed. I've tried this with both system images.
I tried RSD Lite as well but it won't even detect the phone in fastboot/bootloader mode (on Windows 10 Insider Preview). Tried with admin privileges. The "fastboot flash" option in the Config menu was greyed out for some reason.
I've hit a roadblock. I'm so ready to just toss this phone out the window but I decided to come here and ask for help first. Please, XDA. Do not fail me.
P.S. I've lost contact with the owner because I bought the phone on a local equivalent of Craigslist so neither the ad nor my communication with him still exists. And even if by some miracle I managed to find one, it would do me no favors if he would remove the account via Google Device Manager because I've already reset it. The only thing he can do for me is log into the phone using his email and password and then reset it, which would require going somewhere with WiFi that is also public all the while making sure he doesn't try to steal the phone back now that it's fixed.
Edit 2: Ever since I added the Telegram account, the phone is no longer usable, since it reboots unexpectedly as soon as it connects to WiFi and discovers that an account has been added to the device. I'm going to reset it again so I can continue using it with these limitations.
I remember once on a Samsung device I found a pre-rooted IMAGE file and flashed it via fastboot and that fixed everything. I can't seem to find anything of the sort for this phone though.
I've found instructions on how to convert a ZIP ROM into a system image, but those instructions are only for Linux.
Hello.
It's me again, and I have another problem. Damn machines like to play it hard (or maybe I'm just clicking wrong choices all the time).
Before unlocking my device via MiUnlock I got myself a finger scanned for quick unlocking the phone. It didn't work all the time but was a nice addition to pattern unlock. After unlocking my phone via fastboot mode I was on tour, and during driving, I was in need of screen being on. I turned off pattern/fingerprint unlock in order to get my beloved girl as a guide.
However, when I wanted to turn it on again today, after setting pattern, pin code or passlock, retyping (redrawing) it again and clicking "confirm"...nothing happens.
Is this the "feature" Xiaomi warned about before I was unlocking my phone on MiUnlock?
Can I somehow turn it on again? It seems like a bad joke, that your device can be secure ONLY when totally locked. And when You like to get root access - sorry mate, you are on your own.
Just to clarify - my MIUI is unchanged from the beginning 7.0 with latest possible update via OTA (all the way to 9.2.1.0 NCFMIEK version). I'm looking forward to swapping it for the new one someday, but I would like to know if there's another way around than just reflashing whole phone and reconfiguration process, that always took me much time. I'll get rid of preinstalled vanilla someday anyway, tbh, but I'm just curious. Also – will this be a thing and will it still occur, when I install some custom?
INB4 – buy yourself a car holder, lazy bastard.
INB5 – You could have changed screen awake time option anytime dude, wtf.
INB6 – You dunno anything about unlocking, get back into your cave and keep smashing stones.
INB7 - better try custom ROM... Time for a Change.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.