Related
1st comes 1st lg ls740 this is to backup the laf partition, i recomend yall bakup,recovery an boot as well just in case
Note: This assumes you've already rooted manually or with Towelroot and know what adb/fastboot is.
First, backup your LG Download mode (laf) with this code, so you can use LG Flash if necessary.(make sure phone is on and pluged in and android debuging is enabled
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
Run the following code to zero out laf:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(i did this and my volt told me the memory was full but this still got me into fastboot
adb reboot
For whatever reason, you won't be able to access fastboot via "reboot to bootloader" like most phones, so you've got to do a key combo:
Power Off
Unplug USB
Hold Volume Up
Plug in USB
step 2
fastboot oem device-info
should look something like this ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.013s
step 3, fastboot oem unlock
should look like this,
...
OKAY [ 0.004s]
finished. total time: 0.005s
DO NOT skip this step before shutting off or rebooting the phone
WHEN YOU ARE DONE IN FAST BOOT MAKE SURE TO RESTORE THE LAF.IMG
fastboot flash laf laf.img
p.s if you backup your laf.img make sure to move it off of the internal storage to the sd card or computer or you will not be able to acsess it
notreal456789 said:
1st comes 1st lg ls740 this is to backup the laf partition, i recomend yall bakup,recovery an boot as well just in case
Note: This assumes you've already rooted manually or with Towelroot and know what adb/fastboot is.
First, backup your LG Download mode (laf) with this code, so you can use LG Flash if necessary.(make sure phone is on and pluged in and android debuging is enabled
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
Run the following code to zero out laf:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(i did this and my volt told me the memory was full but this still got me into fastboot
adb reboot
For whatever reason, you won't be able to access fastboot via "reboot to bootloader" like most phones, so you've got to do a key combo:
Power Off
Unplug USB
Hold Volume Up
Plug in USB
step 2
fastboot oem device-info
should look something like this ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.012s]
finished. total time: 0.013s
step 3, fastboot oem unlock
should look like this,
...
OKAY [ 0.004s]
finished. total time: 0.005s
DO NOT skip this step before shutting off or rebooting the phone
WHEN YOU ARE DONE IN FAST BOOT MAKE SURE TO RESTORE THE LAF.IMG
fastboot flash laf laf.img
p.s if you backup your laf.img make sure to move it off of the internal storage to the sd card or computer or you will not be able to acsess it
Click to expand...
Click to collapse
One question is it to unlock the phone from a carrier?
Juniluis said:
One question is it to unlock the phone from a carrier?
Click to expand...
Click to collapse
What kind of unlock is this??? Does this allow sim unlock?
???
What??
I'm confused. Is this to unlock the phone to use it in any carrier?
Bootloader unlock sounds like.
Sent from my HUAWEI Y536A1 using XDA Free mobile app
So i have both the short story with some important explanation and the long story on what I've already tried.
Short story
So my dad bought a oneplus one 16GB from someone and the phone has a bootloop when you try the boot into the system.
I tried to unlock the bootloader, but it runned the command and it just reboots to recovery and the bootloader is still locked.
Also the tamperflag is true so that means that the bootloader has already been unlocked and is relocked.
I can't also boot from a custom recovery image because the bootloader is locked (I think it can with CM11S).
Rom: I guess it is CM12S (with the blinking Cyanogen logo at startup).
Recovery: probably the recovery from CM12S (Cyanogen recovery as text and it is a touch recovery).
Long story
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem device-info” and it told me that the bootloader was still locked but it was tampered.
I tried after that to boot from a TWRP recovery image but i wasn't able to because the bootloader was locked.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
ninjawulf98 said:
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem get-lockstate” and it told me that the bootloader was locked but it was tampered.
Sadly enough when I typed the command now it takes forever to answer, after more than 10 minutes it still displays that it is waiting.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
Click to expand...
Click to collapse
Are you able to enter fastboot mode now?
Bobbi lim said:
Are you able to enter fastboot mode now?
Click to expand...
Click to collapse
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
ninjawulf98 said:
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
Click to expand...
Click to collapse
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
ninjawulf98 said:
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
Click to expand...
Click to collapse
Which stock recovery is it? ColorOS? CM? Or OxygenOS?
I had a similar issue when I tried to unlock mine when I first got my OPO
Sent from my Nexus 7 using Tapatalk
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
ninjawulf98 said:
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
Click to expand...
Click to collapse
Maybe my previous post was a bit confusing but it is still locked, i meant that the previous owner locked it and then relocked it.
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
GirishSharma said:
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
Click to expand...
Click to collapse
I've got the following:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Windows\System32>
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
GirishSharma said:
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
Click to expand...
Click to collapse
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
And when i do the command: "fastboot oem device-info" again.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ninjawulf98 said:
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I don't know if this is an issue but i have both the adb and fastboot tools installed from here and the adb, fastboot and drivers here .
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
GirishSharma said:
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
Click to expand...
Click to collapse
I already founded that thread and did the solution that worked for him and another solution that a guy a few posts above him mentioned. Sadly enough without any results.
Anyway, thanks for the help and all the effort you did!
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
ninjawulf98 said:
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
Click to expand...
Click to collapse
Now actually i think that the partition bootloader doesn't exists but boot does (which I think containts the bootloader and the kernel).
After waiting very unpationtly -+ 24 hours I tried it.
Sadly enough again without success.
CMD copy:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot devices
866878f3 fastboot
C:\Windows\System32>fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.057s
C:\Windows\System32>
Fried emmc. Sell it for junk.
Sent from my SM-G920T
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Deep.G said:
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Click to expand...
Click to collapse
The command for unlocking the bootloader is "fastboot oem unlock" not "fastboot unlock oem".
Also sometimes when you type a commando that isn't recognised by the phone it can take forever.
So, I think that the commando "fastboot flashing unlock" doesn't exist.
Anyway I think I know now for sure that the previous owner erased and/or formatted the cache.
Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.
Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"
Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .
No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s
ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.
Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…
Please help me I screwed up! I tried flashing from Global Beta Back to Stable beta (ROM V10.4.1.0.PCAMIXM), I got bootloader unlocked and after a restart, I forgot to turn on USB Debugging, and when I flashed it I've got an error at the end (failed to check sparse crc). The thing is i thing I've chosen flash and lock and my bootloader might be locked again because every time I try to flash again I get echo Missmatching image and device and it's flashing forever. I tried to unlock it again but i get a fail verifying the device at 50%. So now I am stuck in fastboot, I can't get the phone to recovery mode. Is there any fix? Please help me I am not that not tech-savvy.
I guess bootloader is not locked!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
try
Code:
fastboot boot "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.3.1-2-sagit.img"
and install Universal DM-Verity, ForceEncrypt, Disk Quota Disablers
fastboot flashing get_unlock_ability
fastbootflashing unlock
fastboot flashing lock
fastboot flashing unlock_critical
fastboot flashing lock_critical
fastboot oem enable-charger-screen
fastboot oem disable-charger-screen
fastboot oem off-mode-charge
fastboot oem select-display-panel
fastboot oem device-info
fastboot reboot-fastboot
fastboot reboot-bootloader
fastboot oem gpt-info
fastboot oem adb_enable
fastboot oem shutdown
fastboot oem get-dtid
fastboot oem get-hwid
fastboot oem get-prjid
fastboot oem get-skuid
fastboot oem get-rfid
fastboot oem get-featureid
fastboot oem get-jtagid
fastboot oem get-bcid
fastboot oem get-secdispid
fastboot oem get-cpuidhash
fastboot oem get-toolid
fastboot oem isn-info
fastboot oem ssn-info
fastboot oem system-info
fastboot oem get_build_version
fastboot oem get-batcap
fastboot oem get-batvol
fastboot oem get-bootcount
fastboot oem factory-reset
fastboot oem factory-reset2
fastboot oem reboot-recovery
fastboot oem set-permissive
fastboot oem enter-dload
fastboot oem check-s3
fastboot oem EnterShippingMode
fastboot oem check-nrfuse
fastboot oem check-fuse
fastboot oem fuse-info
fastboot oem show-barcode
fastboot oem checksetupwizard
fastboot oem asus-csc_lk
fastboot oem rsa_test_
fastboot oem crc32_
fastboot oem hash_
fastboot oem gen-random
fastboot oem auth-hash
fastboot oem auth-hash_2
fastboot oem auth-hash_3
fastboot oem get-imeiauth
fastboot oem slot_b_enable
fastboot oem get-verify_vbmeta_ret
fastboot oem update-cmdline_
fastboot oem backup-fac
fastboot oem restore-fac
fastboot oem get-pmic-reg_
fastboot oem write-pmic-reg_
fastboot oem reset-boot_count
fastboot oem reset-lock_count
fastboot oem reset-a_retry_count
fastboot oem reset-a_unbootable_count
fastboot oem reset-b_retry_count
fastboot oem reset-b_unbootable_count
fastboot oem force-hwid_
fastboot oem reset-dev_info
fastboot oem reset-auth2
fastboot oem reset-auth3
fastboot oem disable-verity
fastboot oem enable-verity
fastboot oem enable-vbmeta
fastboot oem read-vbmeta
fastboot oem read-rollback
fastboot oem reset-rollback
hi, which one i can use to unlock my bootloader?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL: Post-CS3-30-ZS673KS-user
(bootloader) ABL: Post-CS3-25-WW-user
(bootloader) CID: ASUS
(bootloader) COUNTRY: WW
(bootloader) Project: ZS673KS
(bootloader) DT ID: 100
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 32
(bootloader) LOCK_COUNT: 1
(bootloader) Check_APDP: 0
(bootloader) rawdump_en: false
(bootloader) Current Slot: b
(bootloader) Slot_b bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) SNAPSHOT-UPDATE-STATUS: none
OKAY [ 0.080s]
finished. total time: 0.080s
Following the answer.
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Your phone is tencent edition or not?
HunterTik said:
Your phone is tencent edition or not?
Click to expand...
Click to collapse
No, its the ROG edition
zvrsd said:
No, its the ROG edition
Click to expand...
Click to collapse
Then use official unlock mathod hope it works for you.
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Click to expand...
Click to collapse
You're in userspace fastboot. Reboot to the bootloader
The one you get to by using volume up and power is bootloader
From bootloader `fastboot reboot fastboot` -> userspace fastboot
From userspace fastboot, select reboot bootloader -> bootloader
`adb reboot fastboot` -> userspace fastboot
`adb reboot bootloader` -> bootloader
The bootloader also needs to be unlocked for most commands to work.
Andrologic said:
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
Click to expand...
Click to collapse
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
zvrsd said:
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
Click to expand...
Click to collapse
Thanks. Found it - going to try..