Hello, what could be the cause of the black screen? I can manage to boot it up to recovery mode(TWRP) but after a few seconds it goes into black screen. Same goes after seeing the samsung logo. I can't seem to boot into odin mode as I tried multiple times it only shows the samsung logo and then boots into samsung logo again. I also tried connecting it into the computer but the device won't show up even though I unlocked the oem. When charging it shows the battery indicator fine. It shows error on the upper left: Custom Binary blocked by frp lock. what can I possibly do to make it work again? Thanks! It's on custom rom: onkiller-os v2.0 final and custom recovery: twrp 3.4.0.
The oem Unlocking gets enabled sometimes if your battery runs out.
try flashing the stock rom again, it can help sometimes. it happened once to me as well. My phone died once bcuz the battery ran out and somehow oem unlocking got reenabled
Ahmed9193 said:
The oem Unlocking gets enabled sometimes if your battery runs out.
try flashing the stock rom again, it can help sometimes. it happened once to me as well. My phone died once bcuz the battery ran out and somehow oem unlocking got reenabled
Click to expand...
Click to collapse
Thanks for the reply. ah, But the oem is enabled and can I flash the stock rom without accessing odin mode? I can't seem to boot into it.
Boot into download mode, by pressing power, home and volume down button
Try that
Related
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.
Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait
Samsung Galaxy S6 SM-G920I
Version Lollipop 5.1.1
Long story - My S6 suddenly died. When I tried to turn it on, it would turn on with the logo screen " Samsung Galaxy S6" and freeze right there and then after probably 30 seconds it goes black and then the logo again; forever and ever until the battery goes flat. Doing the physical button combinations did not work. FLASHING STOCK ROM DOES NOT WORK EITHER(and yes I did check that it is the right ROM) I'm able to go into download mode but the thing is:
Since my phone died SUDDENLY:
- DEVELOPER OPTIONS IS NOT TURNED ON
USB Debugging shouldn't have been on.
-I don't know but something to do with turning off OEM unlocking? and/or any other knox or something that blocks rooting, installing recovery etc.
Because of this, when I tried installing TWRP recovery or SpaceX kernel, it says "Custom Binary(RECOVERY) Blocked By R/L"
Tried searching up Google but only came with one English post and did not get much info out of it. The rest were about FRP etc and the way they had it was different from mine.
So now my phone is stuck. Any help? I don't mind voiding my warranty so go ahead with crazy methods that might work.
TL;DR
S6 suddenly dies, frozen at logo screen. Developer options is not enabled> USB DEBUGGING not enabled. Flashing STOCK ROM doesn't work. No recovery. Installing TWRP or SPACEX KERNEL is "Custom Binary(RECOVERY) Blocked By R/L"
Any help?
***EDIT***
DOWNLOAD MODE DOES WORK***
bump
bumpppp
bumpittybump
Seriously... No one is helping...
My phone began lagging last night so I gave it a restart. The shut-down animations were normal but when the phone turned back on, it gave me the dreaded FRP LOCK curse. I went through many forums and videos and I was able to take the lock off via FRP Hijacker, but now I am stuck at the download mode. If I try booting the phone on with the stock recovery, the Samsung Note5 splash screen stays indefinetly (soft brick). If I try booting the phone with a custom recovery, I get a message in purple text saying "Recovery image signature check fail. Reboot to avoid Warranty bit set" and it will keep bootlooping. Currently, I am not sure how to continue if I cannot get to the recovery mode and flash a ROM. So basically, I am stuck at not being able to flash a rom, nor being able to get into recovery mode successfully without a brick or bootloop. Any help is greatly appreciated.
Edit 1: USB Debugging is turned on as well as OEM Unlock
you need to use odin and downgrade to a stock 6.0 tar file..or use a conversion tar file taking you from n920p to n920f..or n920c ...ill upload the files everyone needs after work today...
My father-in-law's S6 was rebooting right after the menu screen came up. After trying numerous things which wouldn't work (still had varying boot loops) like getting into the recovery mode and doing a factory wipe, I decided to use Odin and flash the base stock Android nougat on this (it had the one verizon security patch after that, so should be no issue doing this).
That went okay and it rebooted and got all the way to "Android is starting" which you see after a firmware upgrade. But I didn't realize the battery had run down through all this so it died at this stage. So it was taking a charge now, so let it charge overnight and give it another run.
Got up today, tried to start it...back to the boot loop. So I figured I'd flash stock again with Odin (can always get back to that mode).
It completes successfully and then after the reboot at about 32% jumps to "erasing" and then the boot loop again.
Got into recovery mode once and wiped cache (pointless at this point, but whatever) and did factory reset there, then boot to bootloader. Got all the way to the verizon screen...and then boot loop again.
Is this phone just done? The only thing I can consistently get to is Odin mode. I tried the stock reflash a couple more times and keep ending up in a boot loop and it doesn't even get past the "custom" screen now. And I can't even actually get it to shutdown for that matter. I can get to the battery pull mode but if I try to power off from there, I just get the black screen with the blue light.
And, to make matters even worse, now on restart, it brings up the blue system update screen for a second, then jumps over to the no command screen, sits there for a second, then reboots again. I think I've somehow managed to even blow the recovery menu but this has all been stock and never had any custom firmware or root.
Any help/suggestions would be greatly appreciated!
Pixel stuck on "google" screen after screen & battery replacement (initial boot ok..)
Hi -
Pretty sure phone is bricked as I've tried most stuff I can think of. I replaced the battery & screen on my pixel, everything worked ok once glued back together, phone booted into android and I got as far as unlocking at the lock screen. Then the phone froze, rebooted and is now stuck on the google screen (before the G screen).
I cant get into recovery mode and device appears to be locked - I can see it in fastboot but most fastboot commands fail due to lock (and it wont unlock).
Anyone got any ideas of anything else I could try?
Thanks
marcus-w said:
Hi -
Pretty sure phone is bricked as I've tried most stuff I can think of. I replaced the battery & screen on my pixel, everything worked ok once glued back together, phone booted into android and I got as far as unlocking at the lock screen. Then the phone froze, rebooted and is now stuck on the google screen (before the G screen).
I cant get into recovery mode and device appears to be locked - I can see it in fastboot but most fastboot commands fail due to lock (and it wont unlock).
Anyone got any ideas of anything else I could try?
Thanks
Click to expand...
Click to collapse
Any luck? I'm in the same situation. Bought a used pixel on ebay and it powered on and booted in to Android successfully the first time, but then frozen, and I try to reboot it
then it just won't pass the "Google" screen, can choose recovery in fastboot but will also stuck at "Google" screen forever. Only thing seems to work in the fastboot is the bar code mode.