Related
So when I was trying to unlock my phone via my fingerprint, i didn't have my finger on there correctly 1 to many times and locked my phone. I couldn't remember my passcode and had to log into it via my google account. It then restarted and now won't boot. Gives me the "custom binary blocked by FRP lock" Tried flashing the root tar file and TWRP tar file with no luck. Don't know what to do as I have never came across this before. Any help is appreciated. Phone is rooted but stock.
They holding volume up, home and power when the phone is off. Should get you into recovery. Then do a factor reset. Not sure if this will work though.
Sent from my SM-N920P using Tapatalk
CBRRider said:
So when I was trying to unlock my phone via my fingerprint, i didn't have my finger on there correctly 1 to many times and locked my phone. I couldn't remember my passcode and had to log into it via my google account. It then restarted and now won't boot. Gives me the "custom binary blocked by FRP lock" Tried flashing the root tar file and TWRP tar file with no luck. Don't know what to do as I have never came across this before. Any help is appreciated. Phone is rooted but stock.
Click to expand...
Click to collapse
The phone is rooted so flashing the tar file for root or TWRP is useless because its already rooted. The problem is you locked the phone with your fingerprint. Did you make a backup? You can restore that and you should be good beause it resets the device completely. However, if you did not, then flash the stock tar file in Odin and you'll be good to go. You can find the stock tar file here...http://forum.xda-developers.com/showpost.php?p=62536311&postcount=1
I can confirm it works. You will just have to reroot because it returns the phone to stock out the box.
Due to FRP (Factory Reset Protection) by Google, You won't be able to flash any custom files to phone, it'll always fail, To be able to flash any custom files, You have to enable "allow OEM unlocking" from developer menu, which will disable the FRP lock, But this is not possible in your case since you can't access the menu, But since you're rooted, i assume that you enabled "USB Debugging", So now connect the phone to PC and run CMD and try the following commands one by one,
adb devices # this should list your device
adb shell
su
cd data/system
ls #this will list all files in that dorectory
rm *.key #to delete all .key files which contains the lock
and you're done.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
Due to FRP (Factory Reset Protection) by Google, You won't be able to flash any custom files to phone, it'll always fail, To be able to flash any custom files, You have to enable "allow OEM unlocking" from developer menu, which will disable the FRP lock, But this is not possible in your case since you can't access the menu, But since you're rooted, i assume that you enabled "USB Debugging", So now connect the phone to PC and run CMD and try the following commands one by one,
adb devices # this should list your device
adb shell
su
cd data/system
ls #this will list all files in that dorectory
rm *.key #to delete all .key files which contains the lock
and you're done.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
How does one use ADB when its stuck like this?
hshah said:
How does one use ADB when its stuck like this?
Click to expand...
Click to collapse
He just said his phone is rooted, And i assumed that USB Debugging is enabled, So if you have the same case, You can connect your phone to PC and start using ADB as normal, Then you can follow my guide to get rid of any kind of screen security there, Simple like that.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
He just said his phone is rooted, And i assumed that USB Debugging is enabled, So if you have the same case, You can connect your phone to PC and start using ADB as normal, Then you can follow my guide to get rid of any kind of screen security there, Simple like that.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
If your phone doesn't boot to system, Then you can't use my method, My method was all about saving the data on the phone, And if the data wasn't important to you, you can always flash the stock FW for your phone, Or even wipe the phone from recovery, And i can see you had no option since system doesn't boot up.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
If your phone doesn't boot to system, Then you can't use my method, My method was all about saving the data on the phone, And if the data wasn't important to you, you can always flash the stock FW for your phone, Or even wipe the phone from recovery, And i can see you had no option since system doesn't boot up.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
Interestingly I have just recovered it by flashing stock through ODIN and all I lost was root and Xposed. All my data etc is still there! :highfive:
hshah said:
Interestingly I have just recovered it by flashing stock through ODIN and all I lost was root and Xposed. All my data etc is still there! :highfive:
Click to expand...
Click to collapse
Good for you, And that's because you've flashed an One-Package FW (AP only) which is simillar or newer than the one you had, In that case all your of your settings and data will be still there, And that applicable also for the screen security, Which you'll notice it being there if you had one before your phone got stucked at boot screen, Now i see what your problem was, Before now i thought it was about security. :highfive:
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
Good for you, And that's because you've flashed an One-Package FW (AP only) which is simillar or newer than the one you had, In that case all your of your settings and data will be still there, And that applicable also for the screen security, Which you'll notice it being there if you had one before your phone got stucked at boot screen, Now i see what your problem was, Before now i thought it was about security. :hoghfive:
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
I actually didn't have any screen security. I know I had turned on OEM and USB Debugging, so not sure how OEM got turned off.
Anyways glad its sorted! Just finished re-rooting and I am back up and running!
odin flash fails
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
mevj said:
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
Click to expand...
Click to collapse
You need to flash stock ROM, not custom ROM.
hshah said:
You need to flash stock ROM, not custom ROM.
Click to expand...
Click to collapse
where can i find this stock rom
mevj said:
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
Click to expand...
Click to collapse
I have the exact same problem and tried flashing a stock rom but it fails as well.
did you have any luck??
mine is stuck too i turned off oem unlock and resarted phone now it wont boot i tried odin to stock oi6 but i did ota to oj6 which i see isnt released yet, so does anyone know if and when they are going to release OJ6 FW? and does anyone know how to fix this problem
How did you do it?
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
How do you get it to flash via odin? I keep trying and get a failure of the lock. Is there a specific method you did that i am not doing right?
Please help if you can. I don't want to have to go to warranty and pay a hefty fee.
I too am suck in FRP lock. I also can't get into TWRP or can't flash it on the phone.
I would really appreciate it.
psychokrod said:
How do you get it to flash via odin? I keep trying and get a failure of the lock. Is there a specific method you did that i am not doing right?
Please help if you can. I don't want to have to go to warranty and pay a hefty fee.
I too am suck in FRP lock. I also can't get into TWRP or can't flash it on the phone.
I would really appreciate it.
Click to expand...
Click to collapse
Try flashing this one in Odin http://forum.xda-developers.com/showthread.php?t=3273483
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
Did THE stock flash worked for you? cause i can only boot in download mode also. I didnt know about this lock.... Is it so i have to walt for 3 days to use my phone?
liobeir said:
Did THE stock flash worked for you? cause i can only boot in download mode also. I didnt know about this lock.... Is it so i have to walt for 3 days to use my phone?
Click to expand...
Click to collapse
Yes it did. Download the stock firmware from Sam Mobile and just flash it through ODIN whilst in Download mode. It kept all my apps and settings too.
After around 5-6 hours this morning/afternoon, I've officially given up on fixing this on my own, and I've all but accepted my device to be a $600 paperweight.
I decided to make one last attempt at saving it by posting for help.
Problem: My phone has a feature called "FRP" (Factory Restore Protection), which is tied to one's Google account. Basically, if you have a Google Account on the phone, it locks the phone to any custom binary/custom OS/whatever.
Once I realized this, in order to root my phone, I went in and removed my Google accounts. Sure enough, this disabled the FRP Lock, and I was able to root my device.
After rooting my device, I re-added my Google accounts and went about my business for the next couple of weeks or so.
Just this morning, my phone was having issues charging, so I decided it'd be a good idea to give my phone a reboot. Big problem. It turns out I simply haven't ever turned off my phone since I rooted it. On top of that, I didn't think the FRP Lock would apply to booting the phone, I thought it only affected flashing new firmware. I was wrong.
After my phone turned off, red text appears at the top of the screen: "Custom binary blocked by FRP Lock".
This is the problem. It simply cannot boot. Because it cannot boot, I cannot remove the Google accounts to disable the lock and resolve the problem. Because the lock can't be disabled, I can't flash the phone's original firmware, because FRP Lock will stop anything and everything I try to do.
---
Goodbye 1k+ photos on phone... And, well, goodbye *phone*.
Unless someone has any helpful thoughts! And that's why I'm here.
tl;dr: Soft bricked phone due to FRP Lock. Not able to restore original firmware, factory restore, or boot into phone's operating system.
Important: The phone turns on, and I have access to the recovery menu as well as "Download Mode"
---
What I have tried:
Factory restoring through the recovery menu, doesn't have any effect
Flashing stock firmware through Odin (Nand write failure)
Flashing a custom recovery environment (TWRP) through Odin (FRP Lock blocked this flash)
ADB and Fastboot cannot recognize the device
Tried to use Kies 3 and Smart Switch to "re-initialize" my OS or something. Both failed, saying that my phone wasn't compatible, and that my serial number was invalid (it was, in fact, correct)
---
And I probably did more things that I simply don't remember. The point here is that I've done everything, and literally everything has failed for one reason or another.
I feel like it is a possibility that if I attempted another stock ROM, then I might be able to avoid the Nand Write Failure. But again, I don't know, and I've almost accepted that I need to start looking for cheap alternative phones.
Thanks in advance, I really hope that this can be fixed one way or another. I'd be sad to see my photos disappear, but if it was the only way for my phone to work again, I could live with it.
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
I thought about doing that, but I have no way of wiping the phone. What do you suggest?
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Cosmic Blue said:
you can wipe the phone through recovery. it is under the advance section. you will need to delete each section manually.
Click to expand...
Click to collapse
I am not running a custom recovery OS, there is no Advanced section. :s
Yarraque said:
1. Go to download mode
2.Untick auto reboot,
3.Flash twrp
4.do not reboot to system, reboot to recovery.
5. Install super su and reboot system
Done.
Click to expand...
Click to collapse
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Purlek said:
When I try to flash TWRP (or anything for that matter), FRP Lock blocks the flash.
Click to expand...
Click to collapse
Go to the developer settings and unlock "oem unlock" thing. Try again.
Yarraque said:
Go to the developer settings and unlock "oem unlock" thing. Try again.
Click to expand...
Click to collapse
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Purlek said:
I was unable to boot into the phone.
However, I've more or less resolved the issue.
The issue was that when I was first trying to flash stock firmware, I was using an old version. I've read since then that that doesn't work. So I spent 15 hours+ downloading the latest firmware of 6.0.1, and sure enough, it flashed successfully.
Click to expand...
Click to collapse
Oh nice to hear ^^
Samsung FRP
Cosmic Blue said:
have you tried delete the operating system and then flashing a stock rom using odin
by deleting the OS you have a blank phone with google deleted, thus disabling FRP lock.
Click to expand...
Click to collapse
Would this work with the Samsung Account Factory Reset Protection?
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
You could try booting to TWRP with "fastboot boot <filename here>". Then copy the files from there. I'm not sure if this will work if she had the screen locked beforehand though. You could also try flashing the latest factory image but make sure your remove the "-w" from the flash-all.bat file before running the script so it will not wipe user data. Both of these options might not be possible though if you do not have the boot-loader unlocked.
cynnican said:
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
Click to expand...
Click to collapse
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
crixley said:
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
Click to expand...
Click to collapse
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
cynnican said:
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
Click to expand...
Click to collapse
Yep you can sideload without needing it toggled in developer mode
crixley said:
Yep you can sideload without needing it toggled in developer mode
Click to expand...
Click to collapse
This worked perfectly, thank you!
cynnican said:
This worked perfectly, thank you!
Click to expand...
Click to collapse
I'm glad to hear! Nothing worse than having to wipe and losing important things you can't get back. I've had that happen a few times. Happy to help.
I'm not very technical - please keep this in mind with my query below.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved.
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
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.