Hey guys
I noticed that many people are having problems to flash using fastboot. They report that fastboot says the bootloader would be locked, even if it's definitely unlocked.
so my question, who of you is able to flash (kernels for example) using
Code:
adb reboot bootloader
fastboot flash boot boot.img
and who can flash using
Code:
adb reboot oem-unlock
fastboot flash boot boot.img
I've been talking to LG about this problem, but all they said was to change a driver config for ADB. But due to the fact that I'm using Linux, it is impossible that it is a driver problem. I also tried their "solution", but guess what... it didn't work.
first one don't work by me
please use the poll, so that we've got all informations bundled
Hi
I've already voted.
So for me it does not work.Always comes back PERMISSION DENIED.
232.10 3At Austria.
I have rooted and bootloader unlocked.CWM recovery installed.CM 10.1 RC2 installed.
I can flash everything,rom,kernel...
Everything works just Reboot bootloader is not working.
Has an idea? Thanks
I can't really test adb due to idiot computer asking for disk to be inserted. But when I reboot to bootloader it says "now ready" which didn't happen when it was locked. Used the hacked method too, my odm_reserved reads:
0x000000000000000000000000000000000000fdffffffcafffffffdfffefeffed
As @laufersteppenwolf probably knows I am UK 234-000 user, unlocked with the original terminal hacked that blew all our fuses :thumbup:
Sent from my rooted P880
@non4 said:
I can't really test adb due to idiot computer asking for disk to be inserted. But when I reboot to bootloader it says "now ready" which didn't happen when it was locked. Used the hacked method too, my odm_reserved reads:
0x000000000000000000000000000000000000fdffffffcafffffffdfffefeffed
As @laufersteppenwolf probably knows I am UK 234-000 user, unlocked with the original terminal hacked that blew all our fuses :thumbup:
Sent from my rooted P880
Click to expand...
Click to collapse
it's not about the bootloader being locked, it's about the ability to use fastboot for flashing something (kernel for example)
laufersteppenwolf said:
it's not about the bootloader being locked, it's about the ability to use fastboot for flashing something (kernel for example)
Click to expand...
Click to collapse
I know, but does yours say "now ready"? If so then LG really did screw up, idiots
Also if I type "reboot oem-unlock" in terminal I get "welcome to fastboot mode "
Sent from my rooted P880
@non4 said:
I know, but does yours say "now ready"? If so then LG really did screw up, idiots
Also if I type "reboot oem-unlock" I get "welcome to fastboot mode "
Sent from my rooted P880
Click to expand...
Click to collapse
yeah, it says now ready, but fastboot says my bootloader is locked -.-
EDIT: @@non4 already knows LG's answer to this problem, but i think i can tell it y'all:
We are very sorry to say that there is no way to solve the problem you mentioned.
Click to expand...
Click to collapse
nice work LG -.-
laufersteppenwolf said:
yeah, it says now ready, but fastboot says my bootloader is locked -.-
Click to expand...
Click to collapse
You tried typing OEM unlock command? A few people have to do this to get to correct working fastboot mode. In fact I think the guy that got my BL unlocked with his echo odm method had this issue
Sent from my rooted P880
no, i can't ATM...
laufersteppenwolf said:
no, i can't ATM...
Click to expand...
Click to collapse
Reboot oem-unlock works in terminal emulator, that's the only way I can get into "welcome to fastboot" screen. When you can try it, if you can flash stuff through here then we have a solution for you unlucky fellows
Sent from my rooted P880
I'm sorry, but "reboot oem-unlock" does not work.
I just get black screen. :crying:
varadinum said:
I'm sorry, but "reboot oem-unlock" does not work.
I just get black screen. :crying:
Click to expand...
Click to collapse
Weird...
Sent from my rooted P880
Security error for reboot oem-unlock, but manual flash is possible. Normal fastboot says BL is locked, as usual.
Sent from my LG-P880 using Tapatalk 2
maybe you guys can contact LG, too. So they eventually can realize that they've f**ked up, regarding the bootloader...
varadinum said:
Hi
I've already voted.
So for me it does not work.Always comes back PERMISSION DENIED.
232.10 3At Austria.
I have rooted and bootloader unlocked.CWM recovery installed.CM 10.1 RC2 installed.
I can flash everything,rom,kernel...
Everything works just Reboot bootloader is not working.
Has an idea? Thanks
Click to expand...
Click to collapse
maybe my post here helps:
http://forum.xda-developers.com/showthread.php?t=2224020&page=46
adb reboot oem-unlock i got the fastboot welcome screen. i was hoping to see the unlock screen once more because i think something went wrong..
guys, I'm stuck at the CM10.1 boot animation, and after reading numerous posts I found some saying that I need to flash the boot.img through the fastboot. I've managed to go to the Welcome to LG Fastboot Mode though TWRP2.5.0.0 reboot -> bootloader. But when i try fastboot devices my device isn't listed... Any advice on what should I do? Is there any other way to solve the boot issue? I've waited like 15 mins with the phone not getting further than the CM10.1 Logo... :'(
PS: I'm using Minimalistic ADB and Fastboot from here
http://forum.xda-developers.com/showthread.php?p=42407269
both reboot commands "oem-unlock" and "bootloader" are defined in the kernel source code. "oem-unlock" sets an intern hardware flag for booting the unlocked mode and "bootloader" just sets the normal bootloader flag.
wondering why the reboot parameter "recovery" actually only does a normal reboot? (CM has an additional script they call before rebooting to recovery for setting the recovery boot flag)
right, no "recovery" command defined in the kernel source, but its only a few lines of code to add this
------
reboot
bootloader: locked fastboot
oem-unlock: unlocked fastboot
some time ago i messed around with these hardware flags and now oem-unlock doesnt work. it boots instead into recovery lol. no clue why
Gesendet von meinem LG-P880 mit Tapatalk 4 Beta
problem ( Please help quick )
Hi Every One
i have a question
i install new firmware to update hboot
first step to install was relocked bootloader and i did it
after installation i want to unlock my bootloader but my android does not up and freaze on htc one boot animation
how can i unlock my bootloader via fastboot ?? please help me quick
Related
I've got a nexus one with a broken power button and a corrupt OS. It rarely successfully manages to boot. Since this is the case, I'm not able to turn on USB debugging to follow some of the tutorials here..
My next try was fastboot.. I downloaded these two files:
recovery-clockwork-5.0.2.0-passion.img
update-cm-7.1.0-N1-signed.zip
But it seems like I wont be able to flash a recovery file if I have "s-on" displayed on my hboot or fastboot screen..
How do I gain "s-off"? And is it possible to flash a stock rom via fastboot?
And yes, my phone's got stock gingerbread 2.3.4 rom.
HBOOT 0.35.0017
MICROP 0b15
Touch panel SYNT0103
Radio 5.08.00.04
Please help me with this matter as I have been trying to accomplish this task for over three months now..
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
troby86 said:
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
My phone's power button is broken so I'm not able to select the recovery option
Jack_R1 said:
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Click to expand...
Click to collapse
It's already unlocked, as there is a small open lock displayed at the bottom of the boot screen.. and fastboot displayed it as already unlocked as well.. still.. i need a way to go to recovery without the power button
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Jack_R1 said:
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Click to expand...
Click to collapse
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
knaphih said:
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
Click to expand...
Click to collapse
Do you have the fastboot command on your computer?
troby86 said:
Do you have the fastboot command on your computer?
Click to expand...
Click to collapse
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
---------- Post added at 06:18 AM ---------- Previous post was at 06:11 AM ----------
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
And if none of that seems to work:
http://www.androidguys.com/2010/09/08/manage-nexus-broken-power-button/
OR
http://www.yamihoshi.nl/tech/tutorial-google-nexus-one-power-button-soft-fix
Both are the same, the second one is easier to follow.
OR
Put your recovery .img file into the same folder as your fastboot command, and run this: "fastboot boot recovery-clockwork-2.5.1.4-passion.img"
^^^^^USE YOUR RECOVERY NAME...NOT THE EXACT ONE ABOVE^^^^^
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
Click to expand...
Click to collapse
I've attached an image showing proof that I've tried your method but still kept on failing to reboot to recovery..
When i try the command "fastboot boot recovery-clockwork-5.0.2.0-passion.img", the phone simply restarts and goes back to the 'X' boot screen and gets stuck there.
Could anyone please find me an genuine unedited gingerbread 2.3.4 ROM so I can PASSIMG it? ... I've downloaded several rooted ones.. but all seem to need the "android-info" file
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
Click to expand...
Click to collapse
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
knaphih said:
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Click to expand...
Click to collapse
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/showthread.php?t=1312540
You guys are life savers troby86 and Jack_R1..
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
Click to expand...
Click to collapse
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/show....php?t=1312540
Click to expand...
Click to collapse
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
knaphih said:
You guys are life savers troby86 and Jack_R1..
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
Click to expand...
Click to collapse
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
troby86 said:
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
Click to expand...
Click to collapse
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
mally2 said:
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
Click to expand...
Click to collapse
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
bassmadrigal said:
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
Click to expand...
Click to collapse
well what do you know, he may just ask the OP to send him his nexus to get it fixed and you will never hear from him again.... just warning y'all thats all....
After a long search, I couldn't find anything related to this issue, that's why I've posted this here.
So I tried to root an LG 4X HD, I rooted it immediately without unlocking BL, now everytime I boot into bootloader, I get this:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: unable to start kernel
Unrecoverable bootloader error (0x0000002)
Android (ICS) boots just fine, has root access... but can't access recovery
I know I did something wrong here, little help?
Sent from my LG G2 using Tapatalk... Awesome
Unlock the boot loader
don't forget to hit thanks!
abhi08638 said:
Unlock the boot loader
don't forget to hit thanks!
Click to expand...
Click to collapse
Tried that, won't get into OEM BL unlock mode... it's just odd.
Sent from my LG G2 using Tapatalk... Awesome
hanisod said:
Tried that, won't get into OEM BL unlock mode... it's just odd.
Sent from my LG G2 using Tapatalk... Awesome
Click to expand...
Click to collapse
On ICS you can't unlock bootloader, try upgrading to JB.
Press thanks if it helps
hanisod said:
After a long search, I couldn't find anything related to this issue, that's why I've posted this here.
So I tried to root an LG 4X HD, I rooted it immediately without unlocking BL, now everytime I boot into bootloader, I get this:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: unable to start kernel
Unrecoverable bootloader error (0x0000002)
Android (ICS) boots just fine, has root access... but can't access recovery
I know I did something wrong here, little help?
Sent from my LG G2 using Tapatalk... Awesome
Click to expand...
Click to collapse
My problem is same as yours or nearly the same.
I unlocked bootloader on V20a with "adb reboot oem-unlock" and installed CWM + CM11. Everything was working fine, but GPS. From time to time loses signal, takes more minutes to get lock, etc...
I read somewhere on this forum that there is a problem with the V20x basebands and the solution is to roll back to V10x. So I flashed back to V10H with .dz file. When I type "adb reboot bootloader", "adb reboot-bootloader" or "adb reboot oem-unlock" the phone just restarts. (At this point I can boot into LG's recovery.) Rooted the system and flashed CWM recovery from shell. When I want to boot in to new recovery then appears this message. (I can boot into system.)
Again if I flash back the V20a, I can boot into bootloader and can install custom recovery (without re-unlocking).
I would like to know, how could I manage to work V10x+CWM+CM11 together
jeBACH said:
My problem is same as yours or nearly the same.
I unlocked bootloader on V20a with "adb reboot oem-unlock" and installed CWM + CM11. Everything was working fine, but GPS. From time to time loses signal, takes more minutes to get lock, etc...
I read somewhere on this forum that there is a problem with the V20x basebands and the solution is to roll back to V10x. So I flashed back to V10H with .dz file. When I type "adb reboot bootloader", "adb reboot-bootloader" or "adb reboot oem-unlock" the phone just restarts. (At this point I can boot into LG's recovery.) Rooted the system and flashed CWM recovery from shell. When I want to boot in to new recovery then appears this message. (I can boot into system.)
Again if I flash back the V20a, I can boot into bootloader and can install custom recovery (without re-unlocking).
I would like to know, how could I manage to work V10x+CWM+CM11 together
Click to expand...
Click to collapse
you need to mod 20x kdz with 10x baseband, and flash that. there's a tutorial somewhere around the forum, search and you'll find it.
The tutorial that Flying_Bear is talking about is:
[BASEBANDS][TUTORIAL] Freedom! Choose your baseband.
Hello All,
I have following issue and hope that - if possible - someone can help me. I also would like to mention that I am not an
Android expert but did read a lot of articles here in the forum to find out - or better - to get an idea how things are working.
My Z3C had a water damage. Now I only get fastboot mode. Display is broken and does not show anything. I installed Android-SDK
to get ADB and Fastboot. I installed also drivers.
When I connect the device while pushing the "volume down" button the device manager show me a somc flash device with the "volume up" button I see an Android ADB Interface device. However ADB is not working (no device found) only Fastboot does.
I flashed the "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" with Flashtool via fastboot in the hope that I can somehow access
to "sdcard" by blindly navigating to "mount storage" but nothing seem to work.
On my linux device I see that the usb device is recognized but that it is not an mtp device.
Before I continue to spent hours without really knowing what I am doing I thought that if there is a solution I would find it here.
So if there is any way to get access to my files / pics on the device I would be really glad if someone can let me know how or
at least bring me to the right direction.
Thanks a lot in advance!
Is your bootloader unlocked?
clouds5 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for your reply clouds5.
I followed the process to unlock the bootloader (got code from sony side and unlocked via fastboot with
"fastboot.exe -i 0x0fce oem unlock 0xKEY").
In Flashtool, when I click on the "BLU" Icon I get a window with with my IMEI and my Unlock Code and a
Relock Button. So I assume that the bootloader is unlocked.
If there is another way to verify please let me know and I will do.
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Galbasib said:
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Click to expand...
Click to collapse
hmm you better send it to repair.
evildog1 said:
hmm you better send it to repair.
Click to expand...
Click to collapse
That's unfortunately not an option as I had to disassemble the device
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
Should sdcard appear automatically when booting into recovery or are there any specific steps I would need to complete?
Hey people, first time in this section so I'm gonna go straight to the chase...
I've been having some troubles unlocking this phone's bootloader
http://www.gsmarena.com/asus_zenfone_go_zb452kg-8097.php
Here's the thing
I've already enabled "Enable OEM unlock" in Developer Options
I've already unlocked many devices and this is the first time i got this problem
When going in bootloader and doing
Code:
fastboot oem unlock
It's stuck in
Code:
...
waited for 5 mins... NONE, still stuck
Reboot and did nothing, bootloader still locked
So I'm gonna need some help in this freakin phone :fingers-crossed:
How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...
BallisticSmith said:
How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...
Click to expand...
Click to collapse
Downgrade to the very first firmware version
veez21 said:
Downgrade to the very first firmware version
Click to expand...
Click to collapse
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware
veez21 said:
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware
Click to expand...
Click to collapse
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english
Str1kman said:
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english
Click to expand...
Click to collapse
You can download it, then flash(needs root) the very first stock recovery and then you can flash the firmware?
this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.
yankee77 said:
this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.
Click to expand...
Click to collapse
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.
Mr.haikal
veez21 said:
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.
Click to expand...
Click to collapse
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D
Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_...s/download/master/twrp-3.2.1-0-ASUS_X014D.img
Source: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
Cool, I'll try it when I get the device on my hands. I don't have it anymore.
EDIT: It works wew ?
Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
+1 worked after i installed the drivers from Asus PCLink. Anyone has a custom kernel or ...
BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
I got root access with KingRoot and then flashed TWRP with Flashify.
Somehow that gave me access to bootloader without the necessity to downgrade the firmware.
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?