Develop Bugs

[Q] Help: Can't relock, can't flash via fastboot

UPDATE: Still no solution found - new Ideas very welcome.
Hi there,
I'm at the end of my wits with my HOX which is with a german o2 branding. After getting stuck in bootscreen after athe OTA-Update from 1.26.207.2 to 1.28.207.9 - which failed for some reasons. I tried to install different Custom-Roms, none of which would boot beyond the first HTC-Screen.
The latest one I tried was Cyanogenmod, that did boot fully but I got constant "andoidupi crashed" messages, so I tried to reflash it.
After that things got weird, because right now I can't really do anything anymore. If I try to relock it via "Fastboot oem lock" it just reboots and it boots straight into CWM 5.8.3.1 but when I get back to bootloader its still "**** UNLOCKED ****"
I can flash boot.imgs via fastboot flash... but even so its says at the command prompt that it was successful flashed, it really isnt. No matter what - at reboot I will boot into CWM.
It is like working on a virtual machine - the HOX gives all the right responses, but noting I try to flash is permanent.
I can't relock, I can't flash new recoverys, can't flash new boot.img and everything I push onto the SDCARD via adb is gone after reboot. If I delete a file that is actually on the SDCARD it will be back after reboot, like it was never really deleted.
I already checked my drivers, switched off Antivir, tried it on a different PC, reinstalled the drivers etc etc.
My HOX is from German o2
I've got HBOOT 0.94.0000 and Radio 1.1204.90.13
If anyone has any suggestions besides "You have to fastboot flash recovery/boot..." and "Don't forget to erase cache after every flash" I'd be very thankfull
Best regards,
Thad

did you try to re-download your fastboot ?
and did you navigate on CMD to the right place where your fastboot folder is stored ?

You need to flash the stock recovery before you relock your bootloader.
Flash stock recovery
Relock bootloader
Install ruu
Hope this helped
EDIT: Just read your post again and you said you've tried flashing recoveries, sorry, its late here
Sent from my HTC One X using xda premium

i made a compilation of threads about this matter, it might help you. check it out..
http://forum.xda-developers.com/show....php?t=1692681

Thanks for all suggestions on the topic
@muamers
I redownloaded fastboot multiple times, but its all the same, sadly The problem is: It seems to work. I get all the right replies on the command prompt, but after rebooting nothing is flashed.
@mikey0105
The link goes to a 404 page - could you post it again?
Thank you

tadeausz said:
Thanks for all suggestions on the topic
@mikey0105
The link goes to a 404 page - could you post it again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1692681

Thank you Gibeon & mikey0105
I retried all the steps there, but still no change.
The problem still is the same. This is what I get in response:
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.044s]
finished. total time: 0.045s
>fastboot flash boot boot.img
sending 'boot' (4156 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.470s]
finished. total time: 1.008s
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.034s
>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
sending 'recovery' (5760 KB)...
OKAY [ 0.829s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.548s]
finished. total time: 1.377s
So everything should've worked out great. But not so, because in reality he really hasn't flashed anything to the HOX permanently. When I reboot to recovery I still have the OLD CWM without fixes. The boot.img isn't flashed either.
As I said: It's like working on a virtual machine, where nothing really has any effects, it's a if all the fastboot commands only affect the RAM but are not really flashed to Memory.
And I still can't relock, still can't reboot-bootloader from Bootloader.
Any other ideas are welcome...
Greetings,
Thad

Bump.
Nobody any more ideas?

Bump. Still no solution after many month

try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager

robchongke said:
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery

tadeausz said:
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
Click to expand...
Click to collapse
are you doing
fastboot flash recovery recovery.img
Or
fastboot boot recovery.img
I'm not sure the second one works, but if it did, it would do what you describe. So do the first.

help
I'm running ICJ ROM AOKP. last time I flashed this rom and flashed the gapps too,
Now I want to install a new package of gapps, SO, do I need to wipe data, cache, dalvic cache to install the gapps ???
Note that I'm going to install ONLY the gapps...
THANKS

aimen7 said:
i'm running icj rom aokp. Last time i flashed this rom and flashed the gapps too,
now i want to install a new package of gapps, so, do i need to wipe data, cache, dalvic cache to install the gapps ???
Note that i'm going to install only the gapps...
Thanks
Click to expand...
Click to collapse
That's the third time I've read this question from you.
STOP POSTING IT NOW!

BenPope said:
That's the third time I've read this question from you.
STOP POSTING IT NOW!
Click to expand...
Click to collapse
sorry, I'm CONFUSED about that

Aimen7 said:
sorry, I'm CONFUSED about that
Click to expand...
Click to collapse
Make 1 new thread or search....don't go posting it in every Q&A thread !
That is confusing ! :thumbdown:

JB OTA for HTC_044 not working // manual firmware also not working (SOLVED)

I've been trying to update my HOX to JB since yesterday but to no avail:
Im on everything stock (ROM, Recovery etc) and phone is un-rooted. I relocked the bootloader too. but when the update downloads and the phone restarts after a few while, a red triangle with exclamation marks appear and phone restarts.
I've tried to do this 3 times now with no avail.
alternately i've been trying to follow this and when i reach the flashing firmware part, it fails after 2 tries and after the 3rd it just stucks:
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
OKAY [ 1.683s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.886s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12875 KB)...
after 3rd attempt it just stays in sending 'zip' state
anyone got a clue how i can solve either problem?! :/
note my camera app is a modified version. rest all ROM is stock. could this be the issue?! if so, then any way to resolve this other than RUU method?

The last method you tried will not work if the bootloader is still locked !

The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.

Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!

MarcelHofs said:
Ah like that ! Thanks clyde :thumbup:
I did not read carefully... was kinda busy with my mac & cheese !!!
Click to expand...
Click to collapse

ClydeB1 said:
Click to expand...
Click to collapse
LOL !

ClydeB1 said:
The red triangle is normally an indication that you do not have the stock recovery. Try to reflash recovery and then fastboot erase cache before trying again, You would need to unlock bootloader in order to fastboot flash recovery. As pointed out in my other reply to you, you would probably need to revert to the stock camera app as well.
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
thanks, will try the OTA method 1st by installing the RUU. if that works then brilliant! otherwise try the 2nd

ClydeB1 said:
Using the fastboot flash zip method, you need to have a locked bootloader and then enter command fastboot oem rebootRUU before running the fastboot flash zip command.
Click to expand...
Click to collapse
worked like a charm, thnx mate! :good:

Didnt work for me
Asad_612 said:
worked like a charm, thnx mate! :good:
Click to expand...
Click to collapse
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?

mewazhere said:
I get to the rebootRUU step and that works, but when I try to flash the firmware.zip it always comes up with "error: cannot load "fastboot.zip" : Unknown error" do you know what the problem might be?
Click to expand...
Click to collapse
Fastboot.zip ..... Yeah that's wrong
Fastboot flash zip firmware.zip
And the firmware file need to be named firmware.zip !

[Q] galaxy nexus stuck on boot loop screen animation.

I update, my ROM from cyanogenmod ROM 10.1 m1 to 10.1 m2 ROM and know my galaxy nexus is stuck on boot loop animation! I tried, tacking out the battery and then turning it back on no luck in also tried the ( volume button and power button method) and still no luck with that. Is,there a way I could fix it?

wipe data and reflash rom.

Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse

Never, mind i got it working know!

mrcoleminer said:
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse

Zepius said:
mrcoleminer said:
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse

Chamaeleon said:
Zepius said:
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse

Soulaysahmi said:
Chamaeleon said:
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
I was using the ClockworkMod (I don't remember exactly the version number but I updated recently and it was the touch screen one). I'll try to re-install also the recovery with the very last version (6.0.4.7). Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse

Chamaeleon said:
Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
have you tried adb sideload?

Soulaysahmi said:
have you tried adb sideload?
Click to expand...
Click to collapse
Just tried.
On the terminal after the command
adb sideload cm-11-20141115-SNAPSHOT-M12-maguro.zip
it tells me "error: closed"
I also tried to reinstall the Clockwork via bootloader but didn't change the situation (still not able to do a complete factory reset)

you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?

Soulaysahmi said:
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Click to expand...
Click to collapse
You are right, I didn't click "install zip from sideload" before. Now I tried in this way and, effectively, it worked: I managed to send and install the zip apparently without any problem but than after rebooting I'm still not able to turn on the phone completely. Again the same problem. I re-tried to do wipe data/factory reset both from the recovery and using adb but didn't managed to finish the process...
It seems I tried all the options since now.... but my nexus is still unusable...

did you try getting back to stock rom using any guide on this forum?

Soulaysahmi said:
did you try getting back to stock rom using any guide on this forum?
Click to expand...
Click to collapse
I tried but still with the same result. I'll try to follow the guide I found here

I mean through methods other than recovery, through fastboot mode or odin mode.

Soulaysahmi said:
I mean through methods other than recovery, through fastboot mode or odin mode.
Click to expand...
Click to collapse
I tried to Restore Galaxy Nexus to Stock (as described here) with the proper google image but in the last passage I get:
$ fastboot -w update image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMELC03
Baseband Version.....: xxx
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
FAILED
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'
I put all I need in one folder and I decided to update the bootloader at the PRIMEMD04 version but apparently I didn't managed because doing again the procedure I was getting the same error
ps: I'm using linux so I don't have odin

when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?

Soulaysahmi said:
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Click to expand...
Click to collapse
Yes I have BOOTLOADER VERSION - PRIMELC03
With fastboot I tried to install the PRIMELC04 bootloader
$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.969s]
finished. total time: 8.278s
$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But than, after the reboot, on the screen it's still written BOOTLOADER VERSION - PRIMELC03
I think this is the main problem now... if it's not updated the bootloader I can not reinstall the rom probably...

you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img

Soulaysahmi said:
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Tried as you suggested to install the PRIMELC04 bootloader flashing each image.
Apparently is not possible also in this way. After rebooting on the screen is still written BOOTLOADER VERSION - PRIMELC03.
So I tried to install a stable cyanogenmod 10.2.1 (which should work with the bootloader 03).
I used adb sideload and after the "installing updates" message, everything stopped with the message "fixing fs_size in crypto footer". After more than 30 min I rebooted and the situation was the same as before.

/sdcard not mounting

dear all
i am using GN 4.2.2 stock
at the moment i can go to fastboot and i flash clockwordmod recovery v6.0.1.9
i did this because my phone startted to reboot
at the GB logo
.
now problem is i cant flash ROM to sdcard.
here is the output
=================
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.435s
==========================
sending 'radio' (12288 KB)...
OKAY [ 1.353s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 2.060s
===================================
in recovery when i am trying to mount sdcard.
===============
Error mounting sdcard

Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app

1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?

Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????

amith007 said:
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!

zakisays said:
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
Click to expand...
Click to collapse
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.

zakisays said:
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
Click to expand...
Click to collapse
Perhaps you didnt read the post, so I will quote it here:
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse

Zepius said:
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance

zakisays said:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
Click to expand...
Click to collapse
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread

samersh72 said:
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
Click to expand...
Click to collapse
i gave the following command
H:\Galaxy Nexus (yakju)>adb -d push "H:\Galaxy Nexus (yakju)\Stock-Unroot Jelly
Bean GNex GSM.zip" /sdcard/
its almost 2 hours now the command hasnt finished executing, hope all is going ok
ok i cancelled the previous command .
rebooted to recovery , mounted /data and /system
then reran push command.
got the zip file into sdcard
then tried installing , error generated
finding update package
opening update package
installing update
Installation aborted
!!!!!
please help
thanks

just do this: http://forum.xda-developers.com/showthread.php?t=1626895

Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
well i followed the steps.
i got error as below
===================
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe flash bootloader bootloader-magu
ro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.507s
================================
i hope now its clear what i am facing.
i can boot to fastboot and to recovery , but cant do anything else
if i flash something then the "Too many links error" comes
thanks for the help , is there anything else i can try
========================
ok i found something interesting
when i flash something i get the error " Too many links"
then when i run fastboot.exe devices , i get
???????????? fastboot
and after reboot i get
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe devices
My IEMI number fastboot
y is this happening

*sigh* ...
Op, uninstall all drivers, reboot your system;
Connect device in fastboot to PC, manually update drivers, disconnect device, reboot PC
Connect device again, flash recovery, after it finishes, disconnect USB, use volume keys to "reboot recovery", reconnect USB, manually update drivers again
'adb devices' should return your SN
'adb push ROM.zip /sdcard/' or if that doesn't do it, 'adb push ROM.zip /data/media/'
Sent from my Nexus

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.