So we could oem unlock if we had access to fastboot, well what if fastboot is hidden behind the recovery or download mode just like the LG volt?
Related
Hello.
Long story short:
I have a OnePlus2, I can boot in Fastboot mode and my PC does recignize the fastboot device.
fastboot oem device-info says that Bootloader is locked and when I try to unlock (fastboot oem unlock) it states "okay" but cannot boot into system because there is none installed. -> Bootloop
I cannot boot into recovery nor install a recovery due to the locked bootloader.
My Question:
Is there a way to unlock the bootloader in fastboot and/or install a boot.img?
I am happy for any help that I get.
Have a good day/night
SoulSnatcher
No, but why you don't have system?
You have stock recovery download official signed full zip and flash it. Recovery.
Also unbrick guide using the one you need Qualcomm drivers
Sent from my ONE A2005 using Tapatalk
I can't seem to get ADB or Fastboot working in Recovery or Download Mode.
In recovery if I select the option 'install update from adb sideload' then my device shows up is adb (not useful to me right now) but not in fastboot, which is what I need to execute the 'fastboot oem unlock' command (is that the right way? I've already enabled oem unlocking in settings). I can flash files via Odin, do I need to flash twrp or something?
Any help would be appreciated!
EDIT:
So it turns out that the toggle 'allow oem unlocking' unlocks the bootloader. The reason i thought it didn't was because when I flashed the cf-auto-root file I got stuck in a bootloop. Turns out I had to flash the file, then go into recovery, then reboot which solved my problems.
Samsung devices do not support fastboot mode.
The device is already OEM unlocked. You should be able to boot into Download or Odin mode and flash pretty much anything.
ODIN only
what i messed up?
i have installed custom official cynogen14.1 rom and twrp recovery. everything was working fine.
but i messed up with bootloader. I have locked oem from fastboot mode without enabling option for oem unlocking in developer settings.
Now as my phone have custom rom and twrp installed it went into bootloop and only shows zuk logo and again restart.
What i diid till now?
i have opened backcover so that i can turn of bootloop and phone by disconecting battery.
I can enter into fastboot mode by pressing vol.+ and vol- buttons sumultaneously and connecting usb cable.
But i cannot unlock bootloader as it says unlocking bootloader not allowed. I have tried device specific commads like "fastboot -i 0x2b4c oem unlock" and "fastboot -i 0x2b4c oem unlock-go" but nothing works.
i have stock recovery image but cannot flash while bootloader is locked.
i can enter into adb sideload by following method:
by loading stock recovery by typing "fastboot boot recovery.img" (this does not work with twrp as it says signature varification failed)
and then selecting apply update >> selecting apply fron adb
this much i can do does anyone knows how to recover from such a state.
please help me or my phone will be a waste.
is there any way to install stock recovery i think phone will boot properly if i managed to install stock recovery.
Hello,
I have a galaxsy s5 906k and I've been reading on how to unlock the bootloader as I'm trying to install Remix OS and it seems I've come across a lot of misinformation.... and if possible can someone tell me what exactly I need to unlock the bootloader, as I can't find a list of the appropriate tools? Do I need twrp for my specific device?? Some have said yes and some no.
My phone is already rooted.
Also post unlock bootloader question, can I use the 900k rom from remix to install on my 906k?
EDIT**
I can only boot into download mode, not fastboot mode. adb devices returns the device, but fastboot devices returns nothing. Tried adb reboot-bootloader`and it just shows waiting for any device.
These all boot into download/odin mode!!!!!!
adb reboot download
adb reboot bootloader / adb reboot-bootloader
fastboot oem unlock
fastboot flashing unlock
Only one that boots into recovery mode! Then I go to Reboot to bootloader and it comes back to recovery mode!!!!!!!!!!
adb reboot recovery
Hello. I have a lg v20 H990N. I flashed TWRP by dirty santa method and wanted to go back to stock. As per the instructions on the link https://forum.xda-developers.com/v20...-h990-t3624296, I used method 1a for going back to stock. I ran the code as mentioned in the method while using my backed up "abootbackup.img" but I accidently ran the code twice.
Code:
dd if=abootbackup.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
After booting to bootloader. this is what I see written on the boot loader screen.
___________________________________
Welcome to fastboot mode for bootloader unlock:
*Quick Guidnance
1) Read Device Id
fastboot oem device-id
2) Write unlock key
fastboot flash unlock unlock.bin
3) Check boiotloader is unlocked
Fastboot getvar unlocked
*How to exit fastboot mide
USe "Fastboot reboot' command if fastboot is available
________________________________________
This is the meassage that pops up in fastboot. I can use fastboot but can't use "fastboot flash recovery twrp-3.0.2-1-h990.img" as it exits with error that remote: device is locked. I can't flash kdz with lg Up as Lg up says " there is no haadset connected". TWRP recovery is also not boot neither is the nougat rom that was installed. More \over my device is shown as "Kedacom USB device " in device manager in fastboot mode. Not in Com ports.
It apperas that my bootloader has locked somehow after flashing abootbackup and I can't unlock it as h990N is not supported by LG to unlock bootloader. screenshot attached.
Please help!!!
Yeah flashing the stock bootloader relocks most v20 variants, (the dirty santa bootloader can't truely unlock them, it just ignores the lock)
I'm not sure what you expected? Your link is broken, but it sounds like you reflashed stock firmware and then the stock bootloader and expected to be in a different situation than a fresh unrooted device?
You should be able to boot normally to Android or boot I to download mode and reroot from scratch.
.