Develop Bugs

[GUIDE][FIX]Cant unlock bootloader? Read here for a Fix

Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.

That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k

I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?

cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.

edit: nvm...

Both download links link to the same file. splashscreen.img

Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love

jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...

MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.

This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)

I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated

PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.

rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?

error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830

im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?

Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.

[Tool]Bootloader with extra commands for Nexus 6P

Hi all:
This is a test tool for nexus 6p. with this bootloader, you can do some test. but please do not flash it to your phone,it will brick your phone. only follow the steps below:
step 1: download file View attachment fastboot-boot.img
step2:unlock your phone
step3: enter your phone into fastboot mode
step4: run fastboot command from your pc:
Code:
fastboot boot fastboot-boot.img
step5: now your phone will boot into a customized fastboot mode with extra commands.
eg: you can use
Code:
fastboot oem reboot-dload
to enter edl mode
supported command list is below:
Code:
(bootloader) commands:
(bootloader) download:
(bootloader) getvar:
(bootloader) oem help
(bootloader) oem partition-dump
(bootloader) oem hardboot-set
(bootloader) oem jump-to-kernel
(bootloader) oem hardboot-copy
(bootloader) oem dump-ram
(bootloader) oem select-display-panel
(bootloader) oem off-mode-charge
(bootloader) oem disable-charger-screen
(bootloader) oem enable-charger-screen
(bootloader) oem dump-partitiontable
(bootloader) preflash
(bootloader) oem device-info
(bootloader) flashing get_unlock_ability
(bootloader) flashing unlock_critical
(bootloader) flashing lock_critical
(bootloader) flashing lock
(bootloader) flashing unlock
(bootloader) oem lock
(bootloader) oem unlock-go
(bootloader) oem unlock
(bootloader) oem reboot-dload
(bootloader) oem reboot-recovery
(bootloader) reboot-bootloader
(bootloader) reboot
(bootloader) continue
(bootloader) boot
(bootloader) erase:
(bootloader) flash:
OKAY [ 0.329s]
finished. total time: 0.330s
Credit: @zhouwei @github
@tenfar
source code:https://github.com/tenfar/bootloader_lk

This is awesome, I've always wondered what that line in bootloader saying "Download Mode=disabled" was all about. I wonder if there's a full bootloader out there that would allow all these commands without bricking the phone.

shag_on_e said:
This is awesome, I've always wondered what that line in bootloader saying "Download Mode=disabled" was all about. I wonder if there's a full bootloader out there that would allow all these commands without bricking the phone.
Click to expand...
Click to collapse
yes. there is a bootloader that is unlocked all the time. but it's for android 5.0 i don't know if it will work with 7.0

tenfar said:
yes. there is a bootloader that is unlocked all the time. but it's for android 5.0 i don't know if it will work with 7.0
Click to expand...
Click to collapse
Your know if there a thread with descriptions for all of those tools, I've always been curious with what we can do in fastboot mode

Can any one help me.
i tried to boot into this bootloader same way like mention in this post but i got this its failed.
.
PS F:\nexus 6p\adb> fastboot boot fastboot-boot.img
creating boot image...
creating boot image - 712704 bytes
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.148s
PS F:\nexus 6p\adb>
.
i really want to get into edl mode to fix my fon, its stucked into bootloop, and restarting again again could not pass google logo only thing i can acess is bootloader and its unlocked.. i flashed factory image but still its same,

jaspreet singh mehmi said:
i tried to boot into this bootloader same way like mention in this post but i got this its failed.
.
PS F:\nexus 6p\adb> fastboot boot fastboot-boot.img
creating boot image...
creating boot image - 712704 bytes
downloading 'boot.img'...
OKAY [ 0.047s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.148s
PS F:\nexus 6p\adb>
.
i really want to get into edl mode to fix my fon, its stucked into bootloop, and restarting again again could not pass google logo only thing i can acess is bootloader and its unlocked.. i flashed factory image but still its same,
Click to expand...
Click to collapse
Sounds similar to the bootloop of death. If you can't get into recovery and nothing else works you may be sol.

Fe Mike said:
Sounds similar to the bootloop of death. If you can't get into recovery and nothing else works you may be sol.
Click to expand...
Click to collapse
.
means there is no solution for this?:crying:
or we can open the fon and find out two pins to short them by this we can get into edl..

jaspreet singh mehmi said:
.
means there is no solution for this?:crying:
or we can open the fon and find out two pins to short them by this we can get into edl..
Click to expand...
Click to collapse
I don't know your exact situation, but quite a few who have this issue either bootloop or can only get into bootloader. They no longer have a working OS or recovery and have had to rma they're device.

jaspreet singh mehmi said:
.
means there is no solution for this?:crying:
or we can open the fon and find out two pins to short them by this we can get into edl..
Click to expand...
Click to collapse
what is your device model? H1511 ?

Its H1512
---------- Post added at 03:56 AM ---------- Previous post was at 03:55 AM ----------
tenfar said:
what is your device model? H1511 ?
Click to expand...
Click to collapse
Its H1512

jaspreet singh mehmi said:
Its H1512
---------- Post added at 03:56 AM ---------- Previous post was at 03:55 AM ----------
Its H1512
Click to expand...
Click to collapse
try this . this is for angler-row-vn1 View attachment fastboot-boot_vn1.img

tenfar said:
try this . this is for angler-row-vn1 View attachment 4154572
Click to expand...
Click to collapse
PS F:\nexus 6p\adb> fastboot boot "F:\nexus 6p\adb\fastboot-boot
_vn1.img"
creating boot image...
creating boot image - 714752 bytes
downloading 'boot.img'...
OKAY [ 0.037s]
booting...
OKAY [ 0.184s]
finished. total time: 0.243s
PS F:\nexus 6p\adb>
all done but now it didnt restarted into bootloader its stuck on google logo,, it should reboot into new bootloader by it self,, system tried to reboot but stucked on google logo... i can still go into bootloader by long pressing button that is not modified bootloader its still old one... what its mean file not for my model or is there some serious problem with it,,,, like hardware problem,,,
---------- Post added at 05:49 AM ---------- Previous post was at 05:44 AM ----------
tenfar said:
try this . this is for angler-row-vn1 View attachment 4154572
Click to expand...
Click to collapse
BL: angler-03.64
Baseband: angler-03.78
Product/Variant: ANGLER-ROW-VN1
This is my bootloader details,,,,

jaspreet singh mehmi said:
PS F:\nexus 6p\adb> fastboot boot "F:\nexus 6p\adb\fastboot-boot
_vn1.img"
creating boot image...
creating boot image - 714752 bytes
downloading 'boot.img'...
OKAY [ 0.037s]
booting...
OKAY [ 0.184s]
finished. total time: 0.243s
PS F:\nexus 6p\adb>
all done but now it didnt restarted into bootloader its stuck on google logo,, it should reboot into new bootloader by it self,, system tried to reboot but stucked on google logo... i can still go into bootloader by long pressing button that is not modified bootloader its still old one... what its mean file not for my model or is there some serious problem with it,,,, like hardware problem,,,
---------- Post added at 05:49 AM ---------- Previous post was at 05:44 AM ----------
BL: angler-03.64
Baseband: angler-03.78
Product/Variant: ANGLER-ROW-VN1
This is my bootloader details,,,,
Click to expand...
Click to collapse
when it stuck in the google logo. it is in a customized fastboot mode . you can use
Code:
fastboot oem reboot-dload
to enter edl mode.
Code:
fastboot oem reboot-recovery
to enter recovery
if it dosent work. try with this. maybe it's because the fbcon driver is wrong .that it cannot enter customiezed fastboot mode. this image below have disable the fbcon driver.
View attachment fastboot-boot_vn1_nofbcon.img

tenfar said:
when it stuck in the google logo. it is in a customized fastboot mode . you can use
Code:
fastboot oem reboot-dload
to enter edl mode.
Code:
fastboot oem reboot-recovery
to enter recovery
Click to expand...
Click to collapse
PS F:\nexus 6p\adb> fastboot boot "F:\nexus 6p\adb\fastbo
ot-boot_vn1.img"
creating boot image...
creating boot image - 714752 bytes
downloading 'boot.img'...
OKAY [ 0.043s]
booting...
OKAY [ 0.181s]
finished. total time: 0.233s
PS F:\nexus 6p\adb> fastboot oem reboot-dload
...
OKAY [ 0.006s]
finished. total time: 0.008s
PS F:\nexus 6p\adb>
all done now what should do, like how i can check its in edl

jaspreet singh mehmi said:
PS F:\nexus 6p\adb> fastboot boot "F:\nexus 6p\adb\fastbo
ot-boot_vn1.img"
creating boot image...
creating boot image - 714752 bytes
downloading 'boot.img'...
OKAY [ 0.043s]
booting...
OKAY [ 0.181s]
finished. total time: 0.233s
PS F:\nexus 6p\adb> fastboot oem reboot-dload
...
OKAY [ 0.006s]
finished. total time: 0.008s
PS F:\nexus 6p\adb>
all done now what should do, like how i can check its in edl
Click to expand...
Click to collapse
it will show a new com port named qdloader 9008 in your pc's device manager. then you can follow the steps in other thread.

tenfar said:
it will show a new com port named qdloader 9008 in your pc's device manager. then you can follow the steps in other thread.
Click to expand...
Click to collapse
thank you m trying all things installing nessery things i will inform u if i will sucess, thnk you for ur hlp... if i will sucess i will donate, you some money bro,, u r legend,,, sorry for my english,,

@tenfar
My fon in edl mode all set but miflash giving error hello packet, what its mean ans how to solve...
---------- Post added at 09:47 AM ---------- Previous post was at 09:43 AM ----------
And i delete sbl1 to get into edl mode other things was not working, so in advance bootloader i deleted sbl1,, now its showing in device manager as Qualcomm HS-USB QDLoader 9008(COM6)

jaspreet singh mehmi said:
@tenfar
My fon in edl mode all set but miflash giving error hello packet, what its mean ans how to solve...
---------- Post added at 09:47 AM ---------- Previous post was at 09:43 AM ----------
And i delete sbl1 to get into edl mode other things was not working, so in advance bootloader i deleted sbl1,, now its showing in device manager as Qualcomm HS-USB QDLoader 9008(COM6)
Click to expand...
Click to collapse
press power key for 30s untill you see the com port in device manager refresh . then pree flash/ dowload in miflash.

What is pree/download in miflash? And where i can find this.. and which version of miflash i should use..
---------- Post added at 10:18 AM ---------- Previous post was at 10:04 AM ----------
Flashing start but after 170 second again hello packet error its try to change state but failed i think device is not in right edl mode...

Works for me, but only erase sbl1 helps reach edl mode

can't unlock bootloader

Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?

Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem

amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?

Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse

Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here

Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.

Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk

tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.

Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools

jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.

BND-L24 8.0 Root

Can my model be rooted, and if so, could someone link me a tutorial?

CitrusMei said:
Can my model be rooted, and if so, could someone link me a tutorial?
Click to expand...
Click to collapse
Is your bootloader unlocked? Private message me and I can explain how to root with magisk. I just did it today so I know exactly what to do.

allrockedout said:
Is your bootloader unlocked? Private message me and I can explain how to root with magisk. I just did it today so I know exactly what to do.
Click to expand...
Click to collapse
Could you help me as well, I have the mate se so I believe it should work as well. Thx.

MadGoogler78 said:
Could you help me as well, I have the mate se so I believe it should work as well. Thx.
Click to expand...
Click to collapse
Sure are you on oreo? Is your bootloader unlocked?

It is. Verified unlocked bootloader and 8.0

Just as a note using the twrp_p10 image files does not work... on my mate se
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24952 KB)...
OKAY [ 0.988s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.010s

madgoogler said:
Just as a note using the twrp_p10 image files does not work... on my mate se
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24952 KB)...
OKAY [ 0.988s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.010s
Click to expand...
Click to collapse
If your on oreo thats the wrong command you should do (fastboot flash recovery_ramdisk )

dcraffam said:
If your on oreo thats the wrong command you should do (fastboot flash recovery_ramdisk )
Click to expand...
Click to collapse
i was able to successful in flashing the ramdisk but still no twrp will show up.
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 0.979s]
writing 'recovery_ramdisk'...
OKAY [ 0.210s]
finished. total time: 1.194s
what am i missing here
---------- Post added at 08:49 PM ---------- Previous post was at 08:26 PM ----------
madgoogler said:
i was able to successful in flashing the ramdisk but still no twrp will show up.
C:\Users\Bryan\Desktop\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk twrp_p10_lite_0.3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 0.979s]
writing 'recovery_ramdisk'...
OKAY [ 0.210s]
finished. total time: 1.194s
what am i missing here
Click to expand...
Click to collapse
ok like an idiot i forgot to hold the volume up button on reboot. Now im in with twrp recovery
thanks guys. might want to make this a sticky?

please share the file to works in honor 7x BND-L24 8.0
when entering with vol + and power the green android comes out and says recovery error

gusta2322 said:
please share the file to works in honor 7x BND-L24 8.0
when entering with vol + and power the green android comes out and says recovery error
Click to expand...
Click to collapse
Flash in fastboot. It's stock recovery
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
Fastboot flash recovery_ramdisk recovery_ramdis.img
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
allrockedout said:
Flash in fastboot. It's stock recovery
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
If you rooted also need kernel.
https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=drivesdk
Fastboot flash kernel kernel.img

allrockedout said:
Flash in fastboot. It's stock recovery
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
Fastboot flash recovery_ramdisk recovery_ramdis.img
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
If you rooted also need kernel.
https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=drivesdk
Fastboot flash kernel kernel.img
Click to expand...
Click to collapse
thx men but a need twrp recovery please share

gusta2322 said:
thx men but a need twrp recovery please share
Click to expand...
Click to collapse
Fastboot flash ramdisk_recovery complete_twrp_ramdisk.img make backups in twrp you will need micro SD card because internal storage is not accessible.
https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Than in twrp click install image and install p 10 lite twrp. Everything's working in there better.
https://drive.google.com/file/d/1-dx_fQltWmIMcAFrJsuWtgHnhqVM22n4/view?usp=drivesdk
This is instructions if your coming from stock to twrp for first time.

Brick after trying to revert to stock

Okay so I was on Lineage OS and I tried to revert to stock with the Huru updater which went wrong because I forgot to rename the files. So now I'm stuck, my phone won't turn on, I can't flash TWRP >> writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.530s
Tried flashing back the stock system.img but it didn't work. Anyone know what to do? Cuz i'm clueless

Jetze243 said:
Okay so I was on Lineage OS and I tried to revert to stock with the Huru updater which went wrong because I forgot to rename the files. So now I'm stuck, my phone won't turn on, I can't flash TWRP >> writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.530s
Tried flashing back the stock system.img but it didn't work. Anyone know what to do? Cuz i'm clueless
Click to expand...
Click to collapse
BIG HOLES in the story. Not enough information to even begin to help.
Start with say what ota files did you feed into hurupdater?

mrmazak said:
BIG HOLES in the story. Not enough information to even begin to help.
Start with say what ota files did you feed into hurupdater?
Click to expand...
Click to collapse
You're right, i'll tell you everything I remember. I used the latest files I could find for bnd-l21, then when I tried flashing it it gave me an error because I forgot to rename the files. After that I tried a bunch of things like reflashing TWRP which gave me that error. Then i tried reflashing stock recovery to see if that'd error too and it did.

Jetze243 said:
You're right, i'll tell you everything I remember. I used the latest files I could find for bnd-l21, then when I tried flashing it it gave me an error because I forgot to rename the files. After that I tried a bunch of things like reflashing TWRP which gave me that error. Then i tried reflashing stock recovery to see if that'd error too and it did.
Click to expand...
Click to collapse
well let me look at some of my notes, and when i find them i give you some commands for fastboot to see the partition information

mrmazak said:
well let me look at some of my notes, and when i find them i give you some commands for fastboot to see the partition information
Click to expand...
Click to collapse
Alright, thank you

Jetze243 said:
Alright, thank you
Click to expand...
Click to collapse
i have one that will hopefully verify the version of partiton table, maybe.
fastboot oem get-build-number
and one to verify lock status
fastboot oem get-bootinfo

mrmazak said:
i have one that will hopefully verify the version of partiton table, maybe.
fastboot oem get-build-number
and one to verify lock status
fastboot oem get-bootinfo
Click to expand...
Click to collapse
Okay, here's the output:
C:\Users\Gebruiker>fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0BFR)
OKAY [ 0.000s]
finished. total time: 0.000s
&
C:\Users\Gebruiker>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Gebruiker>

Jetze243 said:
Okay, here's the output:
C:\Users\Gebruiker>fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(0BFR)
OKAY [ 0.000s]
finished. total time: 0.000s
&
C:\Users\Gebruiker>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Gebruiker>
Click to expand...
Click to collapse
then this should work.
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
download the recovery from
https://forum.xda-developers.com/devdb/project/dl/?id=28883
if it works and boots, follow that with hurupdater again, or my HWOTA guide.

mrmazak said:
then this should work.
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
download the recovery from
https://forum.xda-developers.com/devdb/project/dl/?id=28883
if it works and boots, follow that with hurupdater again, or my HWOTA guide.
Click to expand...
Click to collapse
Same result as last time:
C:\Users\Gebruiker> fastboot flash recovery_ramdisk C:\Users\Gebruiker\Desktop\complete_twrp_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (14672 KB)...
OKAY [ 0.526s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.526s

Jetze243 said:
Same result as last time:
C:\Users\Gebruiker> fastboot flash recovery_ramdisk C:\Users\Gebruiker\Desktop\complete_twrp_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (14672 KB)...
OKAY [ 0.526s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.526s
Click to expand...
Click to collapse
I suspect something now, but need to confirm something.
You said you used "latest files for L21"
not very specific.
On pro-teammt.ru site the newest full firmware in the list for L21 is (BND-L21C432B131CUSTC432D002)
this is nougat firmware.
That explains what is happening.
your partions are half oreo and half nougat.
lets hope you can flash nougat twrp .
then do the full ota Of OREO this time.

mrmazak said:
I suspect something now, but need to confirm something.
You said you used "latest files for L21"
not very specific.
On pro-teammt.ru site the newest full firmware in the list for L21 is (BND-L21C432B131CUSTC432D002)
this is nougat firmware.
That explains what is happening.
your partions are half oreo and half nougat.
lets hope you can flash nougat twrp .
then do the full ota Of OREO this time.
Click to expand...
Click to collapse
For Nougat it was "fastboot flash recovery recovery.img" right?
edit: Do you have a link for a nougat twrp?

Jetze243 said:
For Nougat it was "fastboot flash recovery recovery.img" right?
edit: Do you have a link for a nougat twrp?
Click to expand...
Click to collapse
try this bro
https://androidfilehost.com/?fid=962021903579497006

Jetze243 said:
For Nougat it was "fastboot flash recovery recovery.img" right?
edit: Do you have a link for a nougat twrp?
Click to expand...
Click to collapse
I don't know how well these files work, I have never had the need to use them:
https://forum.xda-developers.com/devdb/project/?id=23956#downloads

mrmazak said:
I suspect something now, but need to confirm something.
You said you used "latest files for L21"
not very specific.
On pro-teammt.ru site the newest full firmware in the list for L21 is (BND-L21C432B131CUSTC432D002)
this is nougat firmware.
That explains what is happening.
your partions are half oreo and half nougat.
lets hope you can flash nougat twrp .
then do the full ota Of OREO this time.
Click to expand...
Click to collapse
Okay I flashed the Nougat TWRP succesfully! How do I know which firmwares are Oreo and which aren't tho? On Teampro there are no versions next to the files

Jetze243 said:
Okay I flashed the Nougat TWRP succesfully! How do I know which firmwares are Oreo and which aren't tho? On Teampro there are no versions next to the files
Click to expand...
Click to collapse
It's not real easy. Sometimes it is in the change log. Click the build number and read through it, see if it says.
I have found that generally build numbers for the 7x that are b300 and higher are Oreo
And ones that are below are nougat.
Almost none of the devices have nougat full available.