My phone screen is broken and it remains black while the phone is on. I can't enable adb debugging because of this or unlock oem.
Is there a way I can odin an unlocked oem bootloader or something similar that would work so i can install a custom recovery and use adb through it?
Related
hello,
my nephew forgot pattern and when i enter recovery mode says (no command).
device has official kitkat firmware and locked bootloader and usb debugging disabled.
any ideas ??
You should be able to use the gmail account to unlock it after a few attempts. It would be fairly easy to unlock the bootloader and flash cwm if the stock recovery isn't working for a factory reset. In fact now I think about it unlocking the bootloader wipes the device anyway so if you are stuck boot into fastboot mode power and vol down then use adb ( you will have to set this up first) to input the command "fastboot OEM unlock" hit OK on the tablet and when the tablet reboots the bootloader will be unlocked it will also be reset which is the point of the exercise
Sent from my C5303 using xda app-developers app
So my Nexus6p randomly restarted once (I had been on 7.0 since release date with no issues) and since then is stuck in bootloop on the Google Logo.
Holding the Power+Volume Down boots into bootloader. From there I can't get to recovery or even tried the factory reset from there and it always gets stuck on the Google Logo.
I have downloaded the SDK and while fastboot works, adb doesn't.
I can't flash anything through fastboot because boot loader is locked. I can't unlock the booatloader because remote oem unlock is disabled. I have never had the need to root or unlock bootloader, so never had USB debugging or allowing unlock checked under debugging tools.
Can't sideload OTAs since adb doesn't work.
Do I have any options to recover the device and make it work again?
kumarshah said:
So my Nexus6p randomly restarted once (I had been on 7.0 since release date with no issues) and since then is stuck in bootloop on the Google Logo.
Holding the Power+Volume Down boots into bootloader. From there I can't get to recovery or even tried the factory reset from there and it always gets stuck on the Google Logo.
I have downloaded the SDK and while fastboot works, adb doesn't.
I can't flash anything through fastboot because boot loader is locked. I can't unlock the booatloader because remote oem unlock is disabled. I have never had the need to root or unlock bootloader, so never had USB debugging or allowing unlock checked under debugging tools.
Can't sideload OTAs since adb doesn't work.
Do I have any options to recover the device and make it work again?
Click to expand...
Click to collapse
Do you just have stock recovery? If so, can you boot directly into it with power + vol up. If so, maybe try hitting stock recovery menu to side load ADB or factory reset? Otherwise, sounds pretty borked unfortunately.
Sent from my Nexus 6P using Tapatalk
Hi, I need help, I'm new to this and I want you to answer me: I just installed the twrp recovery on my j500m and I have flashed magisk and the non-verity-opt-encrypt file started normal but I realized that I have unlocked oem disabled, I read somewhere else that if it is not damaged it should be disable the oem unlock option but when I'm going to activate it can not be activated for more than the button to activate, I think it's because of the non-verity-opt-encript file, I do not know if this could cause a brick when I turn off the phone and turn it on again, I need help, please.
you should before flashing twrp 3.1.1.1 or other files by odin
You must open the oem lock from the developers options
and active usb debugging
TL;DR: Do I need to unlock OEM bootloader to boot into TWRP on the SM-J530f?
A friend of mine own a Samsung J5 (J530F), and she broke her screen (of course, USB debugging is not enabled), and she really would like to recover some files & contacts. I tried to blindly unlock the screen with an OTG keyboard, but for now, I'm not very successful (it's even harder when you never used a phone to blindly unlock it ), so I also tried to flash this TWRP recovery. (my hope is to get access to ADB shell after booting TWRP) Using heimdall, I didn't see error that looks fatal, just a minor (?) error during the session ending:
HTML:
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
However, after rebooting with Power+Volume up+Home, nothing special happens (at least given that I can't see the broken screen). And "adb shell" can't find the device.
So do you think I just did something wrong, or do I really need to unlock the bootloader to boot TWRP on the SM-J530f? If I do need to unlock the OEM, is there some signed image that could let me boot something with ADB access? If not, any other idea?
Thanks!
Odin
Hey !
I don't really understand but I could advise you to use Odin for Samsung instead ADB shell (if you use it, think to uncheck auto reboot). If you don't use it maybe try to install samsung usb drivers.
For the OEM unlock, It depend of your android version. I am not sure but you can unlock it in the dev options in the settings in Android Oreo or Nougat but not in Pie or Ten.
In theory, you can access to the device storage in recovery mode by using a computer.
I think it is all,
Cheers.
Thanks for your answer, but unfortunately I can't access the dev settings because the screen is broken. If I could go in dev settings, I'd just enable usb debugging directly.
Hi. I have an LG v20 H990ds. I used a non-genuine usb-c cable which messed up its usb-c port. Ever since then, phone started bootlooping. Despite replacing the usb-c cable, phone is on bootloop. I think the firmware flashing can resolve the issue.
But the phone doesnt stay in download mode for more than 3-4 seconds as it keeps bootlooping. When it is in download mode, my computer doesn't detect it or get a trigger that the phone is connected in device manager.
But when I enter into fastboot, I can install fastboot drivers just fine and able to use fastboot commands. I would have flashed boot.img and system.img using fastboot but it shows the device is 'locked'. Since I cant use 'fastboot oem unlock' as the developer options of the phone software was not enabled, I have come here for seeking help.
Can I bypass the developer options and unlock in fastboot? Can I use EDL mode? Or Qualcomm tools? What are my options? I am really not sure why its bootlooping despite getting usb c port fixed. I will really appreciate if someone can help please. The only way the device can work is if it bypasses the 'lock' checks in fastboot. So a patch or something that can bypass the fastboot can help. Or if I can unlock bootloader n fastboot without using android OS.