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....
Related
I think I successfully installed the new update last night.
But everytime I reboot the phone, this same message keeps popping up.
----------------------------------------------
Congratualtions!
New software is update for phone is installed.
Phone is ready for use.
----------------------------------------------
*When I click Software Update again, it says "No Firmware"
*My phone also tries to connect to DM server right after every single boot
*My phone was never rooted, never tempered with.
There is something wrong with the update. Will this message go away in time?
tommae said:
I think I successfully installed the new update last night.
But everytime I reboot the phone, this same message keeps popping up and it seems the boot-time got slower than before.
Congratualtions!
New software is update for phone is installed.
Phone is ready for use.
Will this message go away in time? do I need to disable it from somewhere?
Click to expand...
Click to collapse
Mine did it maybe the first 5 times, but it seems to have gone away now
I am seeing the same thing. I think I've seen it 4 or 5 times by now. Will try a few times, to see how many times more it does that.
btw, mine's rooted, with stock firmware.
I rebooted at least 20 more times but the msg still pops up . Mine has never been rooted btw.
The problem isn't just the message.the update is being downloaded and installed everytime I reboot. In one instance, I was in the basement with bad signal, and it took about 30mins before it finished the update - and all that time, it wouldn't let me go past the password screen (my corporate acct requires me to have a password on the device).
So, is it just the 3 or 4 of us with this problem?
Sent from my SAMSUNG-SGH-I897
Try maybe rebooting through recovery (using the 3 button trick?)
Brynne85,
Could you explain the 3-button trick?
Thnx.
Sent from my SAMSUNG-SGH-I897 using XDA App
If u are getting the message that.....your update was installed successfully.... after ever reboot of the phone. In order to get rid of this message you need to dial this code from your phone. Code is *2767*3855# (be aware that code will factory format you phone so what this means is that u will loose every thing on the phone. For example: downloaded apps etc. I got this advise from samsung level 3 tech support. I did this on my brothers stock samsung captivate not rooted or anything, just stock. Also i am not responsible for anything that happens to u phone due to being rooted or whatever when preforming factory format. Backup u stuff like contacts or whatever.
hkk said:
Brynne85,
Could you explain the 3-button trick?
Thnx.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Turn your phone off, then press both the up & down volume buttons (hold them in) then press and hold in the power button as well. Continue holding all 3 until the ATT logo shows up, then let go of the power button, and a few seconds later, let go of the volume buttons. Your phone should boot up into a recovery console with blue letters. You'll use the up/down volume & power buttons to navigate this. But to do a reboot, I believe it's the first option and it will tell you to press the power button to "select" it...
May wanna try that before doing a whole format of your phone, but can't promise it'll work :-/ I just know mine quit doing after about 5 times and I'm pretty sure at some point between those times, I did this recovery thing just to see if my buttons worked (as some reported they couldn't get this to happen for them)
Yes you read it right I want to know how I can brick my phone or make it stop working completely. Now let me explain the reason why. I had installed an app called "Launcher Pro". Later I uninstalled it and that is when all hell broke lose. Basically when ever I would swipe my screen to unlock the phone, I would get constant error messages that would reappear the moment I would close them, and to make matters worse it would lock out the rest of the screen so I can not click any thing else (just like in windows vista and windows 7 when a UAC message pops up). This is further complicated by the fact that I have a Bell Canada Samsung Galaxy Phone, which does not have the 3 button recovery ability but that is not the end of my problems. I got this phone at a store called Best Buy and got their warranty. Now one of the things that voids the warranty is unlocking the phone, guess what?? My phone is unlocked. So since my phone is not dead, it boots up, the lock screen loads up, the top bar shows u the battery life and the fact it is getting service and can receive calls (but which I can not answer since when it comes to that screen, the screen freezes up with the error messages). So if I take the phone to Best Buy, they are going to pop in a different sim other then bell and when they see that it works, will hand me back my phone and void my warranty. So I need to have the phone in such a condition that they can not check that and yes there can be no physical or water damage either. How do I accomplish this?
Is it rooted ? Did u happen to enable usb debugging ?
If so a mere "adb reboot recovery" followed by a wipe data would solve ur issues
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Zink6 said:
Ya it is rooted, but usb debugging is not activated and I can not activate it the normal way through the settings screen, if you would know a way to do it some other way, that would be great. Just to let every one reading this know, I do not want to change my phone if I can help it, if there is a way for me to fix this with out bricking the phone and getting a new one, I will be more then happy to keep my current phone. Thanks
Click to expand...
Click to collapse
Have you tried booting into safe mode. Usually booting into safe mode will disable any 3rd party apps from loading. This might give you the chance to uninstall LauncherPro or even enable USB debugging. The method to get into safe mode for the Bell Vibrant seems tricky though:
Menu + Home + Power On right when you see the Samsung logo (specifically: http://forum.xda-developers.com/showpost.php?p=8583886&postcount=17) probably hold the keys. I know in the other Android phones (HTC Ion) you have to hold Menu from beginning til it boots.
http://forum.xda-developers.com/showthread.php?t=758678
Seems to work sometimes...
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Why unlocking it with code would void the warranty? if you flash, yes, maybe. but you enter the unlock code... isn't the official way? Don't bother how i got the code, I bought it, it's mine, i can unlock it. period. i dont understand how they would consider to void the warranty because you unlock with code. btw, Bell does give unlock code for 75$. so, my phone is not eligible for warranty?
MadWhips said:
Why dont you just re-lock your phone?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Guys c'mon.. At least read his post. He can't gain access to the phone at all right now. How do you expect him to relock?
Honestly with no adb you can't do much if u dont have 3button working
Try all those 3button tricks posted for those who can't get to recovery/download mode.
One if i recall is :
Turn off phone
Press n hold Home + Vol Down (or Vol up, up 2 u) + power
Keep holding, your phone will restart once, then twice, then let go off power button.
Its worth a shot
I work at best buy. They will not stick another sim card into the phone. Is it within the 30 day return policy? If its within 30 days go return it and show them the phone dont work and they will exchange it for you.. If its not within the 30 days they will most likely have to send the phone out to Samsung.
What i would do :
1. Take the phone back to the store.
2. Tell them the thing dont work...they wont know if its unlocked or rooted.
3. Ask them to exchange it under the manufactures warranty (if its not within the 30 days) and hopefully they will exchange it and not have to send it out to samsung.
WIN.
PM me if anything.
Asked the rep at best buy (by the way this is best buy Canada), and he said warranty is void if unlocked.
like eduard said, just take it do them. don't even ask or mention unlocking coz that will make them think that you have unlocked it.
take it there, say it doesn't work. done. don't ask, don't tell.
lol thats why you dont tell him you unlocked it! wow man.
its not about you telling them that u unlocked it, their procedure is to insert a different sim into the phone before sending it out for repair and/or exchange. And that is when I will be caught. So aside from giving best buy the phone, does any one else have any other ideas?
Did you try this?
http://forum.xda-developers.com/showthread.php?t=813580
I also have a Bell SGS. I got it from Wireless Wave and fortunately I have 3b recovery. You've tried both (up+home+power) as well as (down+home+power) right? You let go as soon as you see the boot screen that says i9000.
Drop it in the water?
zorxd said:
Drop it in the water?
Click to expand...
Click to collapse
Water damage is not covered by warranty.
From what i read, i can't imagine this is a hardware problem (though i could be wrong), so probably the worst that can be is that your phone needs a reflash. How much would that cost in CA if you can't talk it into a warrantee case?
Ya its not a hardware issue, its a software one. Let me give u more information. The phone boots and goes to the lock screen. Shows the correct time and date and shows on the top that it was connected to my phone service but the moment I swipe the screen to unlock, I get repeating messages, one of them reads "The process android.process.acore has stopped unexpectedly. please try again." and the other reads "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again". Both messages have a "force close" button on the bottom that takes the message away just for it to reappear a second later.
Also from what I have been reading in the forums, if I can only get my phone into usb debugging mode in any other way then the typical MENU > Settings > Applications > Development > USB debugging, it would solve all my problems. If any one knows how to do that, please share your knowledge.
There is a post on here for making a USB dongle that powers the phone straight into download mode.
You need a USB plug and a resistor.
You can then re flash.
Sent from my GT-I9000 using Tapatalk
Here's what you can do:
When you've started the phone (and the error messages come up) you connect your device to your PC with the USB cable.
At that point you'll see a new menu on the background (behind the error messages) for the selection of your connection (Samsung Kies, Mass Storage, etc...)
Click away the error messages very quickly and press the button Samsung Kies (you may have to try several times before you can do this but it's possible)
Then you open Samsung Kies and you use the procedure that is mentioned in the post below to reflash your device with a test firmware:
http://forum.xda-developers.com/showthread.php?t=766589
Make sure to read through that tread to know what codes you have to use in the registry. You should be able to flash your device in Kies with a (test/official) firmware this way.
In the end you my not even have to return it at all...
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
Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?
It may be formatting and encrypting your data partition.
Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.
Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???
frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.