Develop Bugs

[Q] stuck on htc quietly brilliant screen

Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.

You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium

Thanks sir, I'll try.

sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.

thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card

sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too

dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.

See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA

Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.

"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command

sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA

Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!

Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.

Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!

I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?

All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot

i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.

mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?

When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s

Nobody can help me?!! ((

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] Fastboot isn't working, neither is recovery...

I want to return my at&t m8 back to stock (currently on stock rooted with one bad mod installed) so I can give the phone to my father. I dont have S-OFF and dont care about resetting the tamper flag. I have tried many methods to do so, the first being fastboot flashing the stock recovery, then fastboot oem lock, rebooting bootloader, then running the AT&T RUU. After i tried this several times, i noticed that the stock recovery never gets flashed even though it reports 'okay':
Code:
fastboot flash recovery recovery.img
target reported max download size of 1830723584 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.789s]
writing 'recovery'...
OKAY [ 0.896s]
Fastboot reboot-bootloader (both the cli command and if you go select reboot fastboot on the phone) also doesn't work, it reboots the phone normally.
Seems weird that the flash doesn't happen and that reboot-bootloader doesnt work, but nonetheless i try another method restoring a stock nandroid from http://forum.xda-developers.com/showthread.php?t=2701376 . I followed the steps, fastboot erase cache --> fastboot flash boot boot.emmc.win --> fastboot erase cache --> reboot to recovery and restore nandroid --> reboot phone. ANNDDD.... somehow I'm still on the same System/ROM as I was before all this. Also worth noting, any files I push with adb are gone after a reboot. Not sure what is going on but any help would be appreciated.

So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]

jball said:
So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]
Click to expand...
Click to collapse
Yes I have root.
Unfortunately anything that has to be done from the phone that isn't in the boot loader or recovery, is not an option at this point because it's in a boot loop (makes it to lock screen and then reboots). Sometimes it stops the loops and works for awhile, so if it does I'll give this a shot. However, is there any other method via adb/Fastboot over USB or TWRP?

Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.

redpoint73 said:
Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.
Click to expand...
Click to collapse
Device id shows when i run fastboot devices . I am Positive the fastboot connectivity is not the issue here. So i am attempting to use the bootalble RUU. Since I am S-On though, I have to relock the bootloader first. When I run fastboot oem lock I get this:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.126s
And then it reboots the phone normally, it goes into its loop, I go back to bootloader, and it still shows unlocked.
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?

cojomojo said:
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?
Click to expand...
Click to collapse
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.

redpoint73 said:
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.
Click to expand...
Click to collapse
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
Click to expand...
Click to collapse
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494

jball said:
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.

cojomojo said:
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.
Click to expand...
Click to collapse
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.

jball said:
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.
Click to expand...
Click to collapse
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.

cojomojo said:
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.
Click to expand...
Click to collapse
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome

jball said:
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome
Click to expand...
Click to collapse
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.

cojomojo said:
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.
Click to expand...
Click to collapse
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
---------- Post added at 10:19 AM ---------- Previous post was at 09:54 AM ----------
@cojomojo
If nothing else works maybe try what I have over in here
http://forum.xda-developers.com/showthread.php?t=2586472

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.
Click to expand...
Click to collapse
Strange, fastboot problems are most often a driver issue. But I agree, if you've tried it natively on Mac and PC, it would seem that drivers is not the cause.
Out of curiosity, what ROM is running on the phone currently?

jball said:
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
Click to expand...
Click to collapse
I am trying to check to see if maybe fast boot is on. I suppose it is a possibility, now I just need the phone to stay on long enough to check.
redpoint73 said:
Out of curiosity, what ROM is running on the phone currently?
Click to expand...
Click to collapse
Running stock rooted, with one mod installed (wifi tethering). It is the 50% of the problem because it is causing the reboot loop i mentioned earlier.
******* Update **********
"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick. Thanks to all sticking with helping me out here, even as we approach 3 pages

@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be

jball said:
@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be
Click to expand...
Click to collapse
Will do for sure. Thanks for your help! I'm thinking I might try and get the phone on long enough to try flashify or something. Maybe try and get s-off???

Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it, does it state so in the bootloader screen?
If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.

ashyx said:
Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it? If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.
Click to expand...
Click to collapse
Bootloader says unlocked... so I assume it is unlocked. I suppose I could go through the unlock process again, but it definitely says "unlocked". Also TWRP flashing/restoring/anything does absolutely nothing. And I have tried 3 cables and 2 computers.
*** CLARIFICATION ****
I can get into TWRP fine, and I can restore, flash ROMS, whatever... BUT even though they report okay with 0 errors, everything stays the same, i.e. nothing in TWRP actually works. Same with Fastboot.

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.

writing 'bootloader_b'... FAILED

I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot.
I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD.
----------------------------------------------
D:\Download\platform-tools-Flash>fastboot flash bootloader bootloader-taimen-tmz12a.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.097s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.107s
D:\Download\platform-tools-Flash>
------------------------------------------------
I can not use the new phone anymore, please help to check my problem. Thanks.

Have you performed in fastboot Mode, at any time, this command: "fastboot flashing unlock_critical" ? (Without " ")

You can't flash factory image in recovery, it has to be done in bootloader mode, also can you boot in bootloader? Is your bootloader locked or unlocked?

Beast38 said:
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot. I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD. I can not use the new phone anymore, please help to check my problem. Thanks.
Click to expand...
Click to collapse
Apparently you have not unlocked your bootloader (critical) correctly. There are two separate commands needed to fully unlock it. That and you can't flash images from Recovery mode, you flash while in Bootloader mode. Read and follow the directions found on the same page you downloaded the image from HERE.

Thanks all. I re-check all procedure and re-do all process. It finally works fine for now.
I can not sure which step went wrong. All I know is "unlock done" "root failed or not complete".