Related
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Do a hard reset / wipe. That's my suggestion.
Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .
I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.
Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?
I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it
So what happens when you power on?
Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.
After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))
All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App
Can't enable USB debugging when phone can't be turned on at all.
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse
distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....
Hi there!
I'm wondering if you guys can help me brainstorm, or at least get to the root of the problem. Alright, so to preface... I'm using an ATT Galaxy S Captivate [i897]
I was updating my version of MIUI from the miui.us version 2.3 to version 4.0 [ICS.] This worked fine, and I had backed up my data with TitaniumBackup. However, I made a mistake: I chose one of the backup all options, where it backed up all my system data and app data. Little did I know, restoring the system data would completely own my phone. So I did a restore, rebooted, and my Captivate sits at the boot animation indefinitely. It won't get past it.
Somewhere along the line, my download mode and recovery mode 3-button combo got borked. They no longer work [trust me, I've tried every one.] When I try to enter recovery by pressing and holding a number of volume and power button combinations, it goes straight to the boot animation after the AT&T screen. When I try to enter download mode by pressing and holding volume/power, battery in, cable in, and every other possible combination [including switching the cable to different ports on my computer,] I simply get a "stuck" circular loading icon which flickers every few seconds. When I let go, it shows me a grey battery icon with that stuck loading circle overlaid.
So, moving on, I decided to disassemble my phone and try to reset it by shorting the TP contact in the back against the SD card slot. I wish I could find the thread; it's supposed to reset the device. It definitely causes my captivate to reboot [while it was stuck in the boot animation] but it didn't fix the problem. So I decided to make my own jig.
I built it out of three 100k ohm resistors, was super careful not to contact the metal parts of them while I plugged it into my phone. I tried plugging the micro B cable in first, then touching the resistor leads to pins 4 and 5 on the back end of the USB jig, but to no avail. I tried slightly different resistances, but no go. I tried connecting every pin to every other pin just for the hell of it, and no luck there either.
I don't have a soldering gun, so J-tagging is not an option [before I just buy a new phone, anyway,] and I'd rather not buy a USB jig because I'm not convinced it'll work. I know there are a lot of factors, and everyone says to try it 400 times, but I tried it more than I have patience for already. There's got to be something else wrong.
I'm wondering if TitaniumBackup has the capability to mess up the boot loader? If I accidentally overwrote system files with older ones, why would that cause it to get stuck in a bootloop? And where did my download mode go?
If anyone has any ideas, please let me know! I've done a massive amount of research on this. And I found some pretty brilliant ideas along the way, but none of them seemed to work for me. I'm to the point where I literally can't find any more references to problems similar to mine, so I figured I'd ask you guys!
TL;DR: I think by [accidentally] restoring system files with TitaniumBackup from MIUI 2.3 to 4.0, I may have completely owned the boot loader. Can this happen? And is there any fix? I can't get into download or recovery with button combination, jigs, or short-circuiting my phone in fun new ways.
Thanks
The phone by itself is not capable of writing to the bootloader. I am at a loss for why it doesn't work. All I can say is keep trying.
Sent from a jelly bean
korockinout13 said:
The phone by itself is not capable of writing to the bootloader. I am at a loss for why it doesn't work. All I can say is keep trying.
Sent from a jelly bean
Click to expand...
Click to collapse
Well. It might just be the way you wrote it, but you said "I try to enter download mode by pressing and holding volume/power, battery in, cable in...".
The correct method is exactly this.
1. Pull your battery.
2. Hold down volume button.
3. Insert battery.
4. Plug in USB.
5. You should be in DL mode.
Give it a try even if you think you have done it before....
What's with Kies asking for model and S/N and not proceeding?
Why doesn't odin see my phone while in download mode?
How to unbrick my phone?
I've got a problem: client requested a factory reset, so I thought why not?
The phone is now at "battery charging" screen, while not plugged in.
When I power it up, it's stuck at the screen with model name. When I turn it off then, it turns itself back on.
In download mode I had no success with Kies (says that model number and S/N won't accept firmware), so I can't even go past that. Odin said "Done (0 success / 0 failed)" when I tried to flash stock firmware.
I need your help. I am an aspiring technician at new job and took the "simple factory reset" job being confident in my Android abilities. I am afraid I bricked it by running Factory Reset.
TIA
Edit: Oh well, I'm going to have to reimburse the client with value of the device if I don't do it in few days. I see no interest in the question. Probably due to low interest in this model after all these years. Oh, well. There goes quarter of my monthly pay.
Just looking for opinions. I have a stock note 5, no jail breaking or weird loads. Just a run of the mill Note with way too many candy crush saga apps. We weren't even using it a couple days ago when it turned itself off. Reboot just got it stuck in an endless boot cycle. Loading normal or safe mode gets you the android 'no command' blue screen of death.
I figured maybe bad update...possibly load new firmware. Samsung's smart link application doesn't work, as apparently I don't have a S/N, it doesn't exist and you need that for smart link. (It's not the IMEI.) Anyway, Samsung over the phone told me to try a best buy samsung rep, they'd flash it for free. I thought that sounds safe. But they couldn't get it to recognize my phone....Verizon won't help me, I'm past the year warranty. But still owe too much money to pay it off and get a new one through them...That leaves flashing it myself with Odin. So I did. It went ok, it said it PASSED, the phone rebooted....It started a little config in what looks to be a factory reset type screen...it got to 'erasing', refresh arrow spinning to show me it was going, then it just stops. The world stops and no amount of letting it sit every gets it to go again. Rebooting still has 'no command' and no signs of life.
Any thoughts on what might be going on? Anything else to load or try? The phone's no good to me ****ed, so I'm open to suggestions. Likewise, does it sound like any hardware related things? Is there any hope? would love to hear a first impression from someone more experienced with phones and Android.
Try flashing the latest stock firmware in Odin using "Nand erase all" ticked under options..
Let us know how it goes..
CompuTechnoPro™ said:
Try flashing the latest stock firmware in Odin using "Nand erase all" ticked under options..
Let us know how it goes..
Click to expand...
Click to collapse
Same Problem it looks like. Odin does it's thing for about 3 minutes. Says 'PASS'. Phone restarts, does some initializing bar moving stuff for 10 seconeds, it switches to 'Erasing' then the phone just stops
That's unfortunate dude.
I'm really sick of Samsung phones. They're just terrible. As someone who's had to replace their screen twice and battery three times, it shouldn't be difficult to replace the motherboard.
This happened to my NOTE 5 (SM-N920V) as well
YOUR NOT ALONE! THIS SAME THING HAPPENED TO MY NOTE 5
I was fishing, this morning at about 7am when my phone rebooted all on its own to the same Samsung Boot Logo screen then stuck as well. NO RYHME NO REASON, I have never, ever cracked, hacked or smacked this phone either,:highfive:
"The only updating that has been done has come via Verizon/Samsung..." But none recently ...that I recall as in, the last week or so.
While I will admit doing "it" (hacking,cracking,modding,) to other android phones (Obviously or I wouldn't have a membership here). But this Note 5? No... Maybe perhaps that's why its broken now? LOL...
It does always seem that my continued membership here is not in vain though, ......
For now, I will do whatever it takes to get it back... .......next to buying a new phone or it not coming back on ever.
I will share here what I did to resolve the issue. And I will without a doubt utilize "EVERY" resources here at XDA-DEVELOPERS to do it, and happily without the help of Verizon or Samsung.
So far I have determined that my Note 5 version is not commonly referenced here which is: the SM-N920V (Verizon U.S)
Thank you XDA-Developers this is why we need informational communities like this in our lives! :victory:
Even though I may still go nutz during this repair... if it happens.... Wish us luck!
chroniclogic said:
YOUR NOT ALONE! THIS SAME THING HAPPENED TO MY NOTE 5
I was fishing, this morning at about 7am when my phone rebooted all on its own to the same Samsung Boot Logo screen then stuck as well. NO RYHME NO REASON, I have never, ever cracked, hacked or smacked this phone either,:highfive:
"The only updating that has been done has come via Verizon/Samsung..." But none recently ...that I recall as in, the last week or so.
While I will admit doing "it" (hacking,cracking,modding,) to other android phones (Obviously or I wouldn't have a membership here). But this Note 5? No... Maybe perhaps that's why its broken now? LOL...
It does always seem that my continued my membership here is not in vain, ......as for now, I will do whatever it takes to get it back... .......next to buying a new phone or it not coming back on ever.
I will share here what I did to resolve the issue. And I will without a doubt utilize "EVERY" resources here at XDA-DEVELOPERS to do it, and happily without the help of Verizon or Samsung.
So far I have determined that my Note 5 version is not commonly referenced here which is: the SM-N920V (Verizon U.S)
Thank you XDA-Developers this is why we need informational communities like this in our lives! :victory: Even though I may still go nutz during this repair... if it happens.... Wish us luck!
Click to expand...
Click to collapse
might be bad emmc look into booting from sd card not possible on all devices but may be a start,I had a note 4 do the same thing and most def was bad emmc
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
chroniclogic said:
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
Click to expand...
Click to collapse
Oh yea and i owned one of these most def not conventional I had mine apart many times.
Mine just shut off one day and wouldn't do anything plugged in or not ended up being the battery
chroniclogic said:
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
Click to expand...
Click to collapse
Is there any good way guides on how to find/test eemc or battery or whatever? I can't find many resources at all on how to help me troubleshoot.
Resplendentowl said:
Just looking for opinions. I have a stock note 5, no jail breaking or weird loads. Just a run of the mill Note with way too many candy crush saga apps. We weren't even using it a couple days ago when it turned itself off. Reboot just got it stuck in an endless boot cycle. Loading normal or safe mode gets you the android 'no command' blue screen of death.
I figured maybe bad update...possibly load new firmware. Samsung's smart link application doesn't work, as apparently I don't have a S/N, it doesn't exist and you need that for smart link. (It's not the IMEI.) Anyway, Samsung over the phone told me to try a best buy samsung rep, they'd flash it for free. I thought that sounds safe. But they couldn't get it to recognize my phone....Verizon won't help me, I'm past the year warranty. But still owe too much money to pay it off and get a new one through them...That leaves flashing it myself with Odin. So I did. It went ok, it said it PASSED, the phone rebooted....It started a little config in what looks to be a factory reset type screen...it got to 'erasing', refresh arrow spinning to show me it was going, then it just stops. The world stops and no amount of letting it sit every gets it to go again. Rebooting still has 'no command' and no signs of life.
Any thoughts on what might be going on? Anything else to load or try? The phone's no good to me ****ed, so I'm open to suggestions. Likewise, does it sound like any hardware related things? Is there any hope? would love to hear a first impression from someone more experienced with phones and Android.
Click to expand...
Click to collapse
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
---------- Post added at 01:55 AM ---------- Previous post was at 01:35 AM ----------
Resplendentowl said:
Is there any good way guides on how to find/test eemc or battery or whatever? I can't find many resources at all on how to help me troubleshoot.
Click to expand...
Click to collapse
The newer Samsung's do not use eMMc they use the newer UFS 2.0 which is why the note 5 and S6 never got micro sd slots. I could be wrong here but I don't think so.
MrMike2182 said:
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
______________________________________________________________________
Worth a shot.
Where the hell can I find pit files at? why is this **** so obscure on google search. I can't find **** all. It took me forever to find a fireware that appears to work. I'm having no luck finding .pit files
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
______________________________________________________________________
Worth a shot.
Where the hell can I find pit files at? why is this **** so obscure on google search. I can't find **** all. It took me forever to find a fireware that appears to work. I'm having no luck finding .pit files
Click to expand...
Click to collapse
What service provider do you have?
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
What service provider do you have?
Click to expand...
Click to collapse
the Note 5 in question is a version phone. So n920V. I've honestly googled and opened about 30 ****ty websites, cant find a single one with actual pit files. Just copy pasted generic guides and broken links
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
the Note 5 in question is a version phone. So n920V. I've honestly googled and opened about 30 ****ty websites, cant find a single one with actual pit files. Just copy pasted generic guides and broken links
Click to expand...
Click to collapse
Download it from my android file host
.PIT Verizon Galaxy Note 5
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
Download it from my android file host
.PIT Verizon Galaxy Note 5
Click to expand...
Click to collapse
Well ****, we're worse off than when we were before. I don't know if this in indicative of a hardware problem, but now that the battery has had time to drain, I plugged it in and left if for a day, but any time the cord is plugged in the phone is stuck in an infinite no command/reboot loop, and I can't get to download mode with up arrow + home + power like I could before. With the phone unplugged it has no life whatsoever.
Could this be a battery issue the whole time?
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
Well ****, we're worse off than when we were before. I don't know if this in indicative of a hardware problem, but now that the battery has had time to drain, I plugged it in and left if for a day, but any time the cord is plugged in the phone is stuck in an infinite no command/reboot loop, and I can't get to download mode with up arrow + home + power like I could before. With the phone unplugged it has no life whatsoever.
Could this be a battery issue the whole time?
Click to expand...
Click to collapse
Yes and it sounds like a hardware issue by draining that fast.. Did you try holding the volume down button and power button until it reboots?
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
Yes and it sounds like a hardware issue by draining that fast.. Did you try holding the volume down button and power button until it reboots?
Click to expand...
Click to collapse
So When it was plugged in to my comp it would not go into download mode...If I unplugged the cord, it would not turn on.
I got a wall outlet charger instead, with that plugged in I could get to download mode, and when I tried to turn the phone on without the wall charger it gave a 'battery 0%' warning...
Anyway, I got it to down load mode, unplugged the wall charger, moved it to the comp and did the flash with the pit file...Odin said it passed. I restarted the phone, picked factory reset. It installs a few quick things, goes to 'erasing' and after about 20 seconds, freezes, same as last time. Now it's back to no command
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
So When it was plugged in to my comp it would not go into download mode...If I unplugged the cord, it would not turn on.
I got a wall outlet charger instead, with that plugged in I could get to download mode, and when I tried to turn the phone on without the wall charger it gave a 'battery 0%' warning...
Anyway, I got it to down load mode, unplugged the wall charger, moved it to the comp and did the flash with the pit file...Odin said it passed. I restarted the phone, picked factory reset. It installs a few quick things, goes to 'erasing' and after about 20 seconds, freezes, same as last time. Now it's back to no command
Click to expand...
Click to collapse
How long did you let it sit there? Do the factory reset again and let it sit there for a little bit and see if it eventually goes. If not boot into recovery again and read to see what version firmware is listed.
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
How long did you let it sit there? Do the factory reset again and let it sit there for a little bit and see if it eventually goes. If not boot into recovery again and read to see what version firmware is listed.
Click to expand...
Click to collapse
It kicks itself off and goes to a 'no command' after the erasing screen gets stuck and quits 'twirling' for awhile. I don't know how to see a firmware listing. I can't get to a recovery mode(using that terminology to google some screenshots, I don't have that). The phone boots to maintenance mode only...any option I pick there goes to no command. I can use the vol down + home + power to get into download mode so it will be seen by the pc. That's about it
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
It kicks itself off and goes to a 'no command' after the erasing screen gets stuck and quits 'twirling' for awhile. I don't know how to see a firmware listing. I can't get to a recovery mode(using that terminology to google some screenshots, I don't have that). The phone boots to maintenance mode only...any option I pick there goes to no command. I can use the vol down + home + power to get into download mode so it will be seen by the pc. That's about it
Click to expand...
Click to collapse
That means that it didn't flash fully.. What firmware version did you flash in odin? And you can see the phone version again by going into download mode too it should be right at the top after pressing the volume up.
Click to expand...
Click to collapse
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!