Related
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Bump, I'm having the same problem on my tmobile m8
mmmgosu said:
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Click to expand...
Click to collapse
raphi809 said:
Bump, I'm having the same problem on my tmobile m8
Click to expand...
Click to collapse
What versions of the M8 do you have?
EddyOS said:
What versions of the M8 do you have?
Click to expand...
Click to collapse
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
raphi809 said:
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
Click to expand...
Click to collapse
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
EddyOS said:
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
Click to expand...
Click to collapse
Yes, if you have already started a thread asking for help, don't jump around.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mmmgosu said:
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
Click to expand...
Click to collapse
What response do you get for:
fastboot devices
If it returns the device ID, than try:
fastboot erase cache
Then try to flash recovery again.
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
when i tried fastboot devices it returns an ID
but when i tried
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
i have at&t
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do i do that?
fastboot oem rebootRUU
fastboot flash zip name_of.zip
fastboot reboot-bootloader
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
redpoint73 said:
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
Click to expand...
Click to collapse
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
i tried
fastboot oem rebootRUU
but it says ...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.018s]
finished. total time: 0.018s
question, can i flash TWRP with 0p6bimg.zip?
If yes, can anyone provide the file?
Thanks
mmmgosu said:
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
Click to expand...
Click to collapse
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
This is great info to tuck away for future reference. How should the memory be formatted? FAT32 or exFAT?
Sent from my Nexus 10
bruce7373 said:
How should the memory be formatted? FAT32 or exFAT?
Click to expand...
Click to collapse
FAT32.
redpoint73 said:
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
Click to expand...
Click to collapse
How exactly does one format the phone's internal memory via Device Manager?
adriankeith said:
How exactly does one format the phone's internal memory via Device Manager?
Click to expand...
Click to collapse
Couldn't actually tell you "exactly" myself as I haven't personally had to do it. But I know its been given as advice many times, and reported to work (at least for some instances of corrupted internal memory or can't mount memory).
In brief, open Device Manager, browse to the device/internal memory, and try to find the option to format FAT32.
Ok, I'm in the same pickle as person above. Let me just post the state the phone was in before everything happened. Unlocked bootloader, s-on, Android revolution HD installed (4.4.3). Friend tried to get back to stock and now the phone is stuck in hboot. Things done to phone: bootloader relocked, tried to change tampered flag without success, flashed stock recovery and boot image. Fastboot devices returns Id, storage is not recognized, adb commands do not work. I think he also tried to do factory reset while in hboot. Just stumbled upon this format memory thing, will do it once I get home. What are the steps after, can I just flash the correct ROM.zip or some moded hboot? If you can just point me in right direction I would very much appreciate it, thanks. Also if you need any additional info just ask for it
Similar problem here also,
I could really use some help guys! The new GPE 6.0 images are out on XDA. http://forum.xda-developers.com/htc...uu-m8-google-play-edition-5-1-lmy470-t3226765
I did a full wipe then I put on the rom using the zip file first through TWRP and it did install but the radio drivers failed.
So I then downloaded the system img file ruu and renamed it to 0P6BIMG.zip and now it is just stuck in a loop and will not boot into the Operating system. It will just freeze at the White HTC logo.
I press the power button and the volume up button to reset the device then push the power button and volume down button to get into the bootloader the bootloader instantly selects Hboot and starts loading up the 0P6BIMG.zip. The phone then procedes to give me the highlighted HBoot option and the message "Press <POWER> to reboot." Which then reboots right into the White HTC loading screen.
The phone is unlocked and has s-on. I have tried using ADB commands but cannot get an ID with ADB devices command.
Can someone help a brotha out?
I flashed system.img and boot.img of Android 6 Factory Image manually and worked so far.After that i want a clean install,so i erased system,userdata and boot Partition and flashed the Factory Image with the included skript.But Android wasn't booting(i waited over 30-35 min.).So did the same again with no success.So i flashed TWRP and flashed CyanogenMod (that worked for me, but TRWP shows Mount Erros with data,cache etc.).But CyanogenMod also stucks in Bootanimation.
Have you tried re-downloading the files? It could be a bad download maybe.
theminikiller said:
Have you tried re-downloading the files? It could be a bad download maybe.
Click to expand...
Click to collapse
Yes.I also tried it with a Lollipop Factory Image.
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
+1
I have the same problem
Dirty flashed the android 6 flash-all.bat and now I am soft-bricked
Fastboot is activate but fails all actions
If you get an answer please let me know
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
Click to expand...
Click to collapse
Now short enough?
Nic2112 said:
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Click to expand...
Click to collapse
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Nic2112 said:
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Unfortunately the MultiROM version is not working,too.The normal version worked well for before(My device wasn't shipped with 5.0.1 or is from best buy or something like that).
david.mueller1013 said:
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Click to expand...
Click to collapse
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Nic2112 said:
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Click to expand...
Click to collapse
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
How bout editing the thread title adding [solved]...
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
david.mueller1013 said:
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
Click to expand...
Click to collapse
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
caolfin said:
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
Click to expand...
Click to collapse
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Hi
Yes, the N7 is stuck in bootloader
I have tried many times to lock and unlock the bootloader and currently the last few lines of the bootloader screen are
SIGNING = yes
SECURE BOOT = enabled
LOCK STATE = unlocked
I am assuming that LOCK STATE means bootloader lock state and therefore this should be ok ?!
This is really stumping me now
Nic2112 said:
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Click to expand...
Click to collapse
Hi, I tried to reset the bootloader and now I cant get it to unlock ggggrrrrr
Comes up with the questions Unlock Bootloader ? and I say yes
I get
C:\adb\razor-lmy47v>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.003s
I'm totally stumped now
can someone with LTE (razorg) please do the OTA using the bootloader method (wiping data and system first) and put TWRP back and then make a TWRP backup without booting into the fresh android install so that people who dont have working USB can possibly get the update. it would be much appreciated and theoretically should work.
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
i.snehal.kiran said:
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
Click to expand...
Click to collapse
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Your oneplus bricked itself?
are you sure there wasn't a human involved in the process?
As other people says, you're the first one with a " bricked" device, so please tell everyone what your device status is, and how it got bricked.
did you unlock bootloader, did you have root? as much info as possible..
anupritaisno1 said:
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
Click to expand...
Click to collapse
I already have the link for that file. Someone shared. But, what next ?
Sent from my OnePlus2 using XDA Labs
anupritaisno1 said:
Fastboot on op2 is already a mess...
Click to expand...
Click to collapse
Why a mess?
Fastboot itself is very simple.
fastboot flash <<partition you need to flash>> <<file patch>>.
Is it different from the "common" fastboot we can find on a Nexus?
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
CyberCROC said:
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
Click to expand...
Click to collapse
You did 'fastboot oem unlock' first, correct?
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
CyberCROC said:
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Click to expand...
Click to collapse
And have you enabled OEM Unlocking in Developer Options ?
BTW Please reply to my PM ASAP if possible.
Thanks.
Best Regards,
Naman.
I can't OEM unlock in developer options as I no longer have access to my device
PM answered
Experiencing the same problem here.
I had the same in other thread. OEM unock was disabled. Do You have working stock recovery or TWRP? If stock works You can flash stock rom by ADB sideload.
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
cepheid46e2 said:
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
Click to expand...
Click to collapse
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
I have the same problem too
sino84 said:
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
Click to expand...
Click to collapse
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
try this:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
you need the OnePlus3_Unbrick_Tool_Full.rar to unbrick your phone, i was also in your situation,
you need also the Qualcomm_Diag_QD_Loader_2016_driver.exe with this two tools you can flash to restore the OP3
me helped al lot this thread http://forum.xda-developers.com/onep...icked-t3405700
a had a success with this part How to Make the device show as Qualcomm 9008
it is important that you have the correct driver installed on your pc that the phone will be recognized as Qualcomm 9008
I did the exact same stupid thing... locked bootloader before flashing stock recovery.
This post saved me:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I used method 2 in the post which wiped everything but at least i got the phone back.
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Since im a new member I cannot post links so ill have to give you directions.
Search google for Hard Bricked OnePlus 3 and it will be the first one called Mega Unbrick guide.
Use method 2. Ive used it multiple times when flashing goes wrong on my oneplus 3.
Another step, download the latest stock recovery from OnePlus and name it recovery.img and replace the one in the folder. You should understand more when you have all of the files.
You can download the latest recovery from OP at the bottom of the page linked here:
Google OnePlus 3 beta download and it should be the first one saying community build.
Hi, Guys.
I am trying to install the recovery in my phone, but without success.
I already tried some versions of twrp for our moto z play and able not to flash the trwp.
My bootloader is unlocked.
When i typed , show me the message below.
C:\Users\myuser\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY [ 0.400s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.197s]
finished. total time: 0.601s
fastboot flash recovery ( here the name of your twrp recovery).img
f1fan said:
fastboot flash recovery ( here the name of your twrp recovery).img
Click to expand...
Click to collapse
I already tried severa times and not worked.
iago1966 said:
I already tried severa times and not worked.
Click to expand...
Click to collapse
Are you sure it didn't work? The message is just a warning. The second OKAY indicates that it has been flashed sucessfully.
tomparr said:
Are you sure it didn't work? The message is just a warning. The second OKAY indicates that it has been flashed sucessfully.
Click to expand...
Click to collapse
Hi,
I'm sure that, but when show me "writing 'recovery', i think that the hour what the recovery is instaling in the device, but don't write.
When i choose the option for to go recovery, show me " no comand" and the robo of android .
iago1966 said:
Hi,
I'm sure that, but when show me "writing 'recovery', i think that the hour what the recovery is instaling in the device, but don't write.
When i choose the option for to go recovery, show me " no comand" and the robo of android .
Click to expand...
Click to collapse
What recovery are you trying to flash?
If you are flashing stock recovery , the "no command" screen with the android robot is correct.
tomparr said:
What recovery are you trying to flash?
If you are flashing stock recovery , the "no command" screen with the android robot is correct.
Click to expand...
Click to collapse
I tried recovery of Alberto97(tree versions), tried also chinese recovery, both does not worked.
Did you test the recovery you want to flash by using
fastboot boot recovery
?
It is a bad idea to directly flash an untested recovery. You may get the wrong file. Your download may be broken. Just test it at least once using fastboot boot, and if it runs you may try to flash. I am sure I don't want to flash anything that does not run. Usually I do not flash, but run using the cable if I need it. Do you really need the recovery when you're away from your computer?
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.