Database Info

[Q] boot loop cannot get PC to read device

Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?

sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?

sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:

tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?

sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.

tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks

sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard

tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere

sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.

tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111

sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img

tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip

sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.

Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:

[Q] Please Help Im having trouble flashing ROM

Hi Guys,
When trying to flash a ROM using TWRP v2.5.0 it keeps giving me this error: Unable to mount '/external_sdcard and then Unable to open zip file. I have tried to use multiple zip files and none of them work. I have also tried installing it from my microsd and no luck there either. I am a big noob so any help or advice would be greatly appreciated!
thanks in advance!

feedback
snoboardfrk said:
Hi Guys,
When trying to flash a ROM using TWRP v2.5.0 it keeps giving me this error: Unable to mount '/external_sdcard and then Unable to open zip file. I have tried to use multiple zip files and none of them work. I have also tried installing it from my microsd and no luck there either. I am a big noob so any help or advice would be greatly appreciated!
thanks in advance!
Click to expand...
Click to collapse
Just need a little more info....
What bootloader are you on??
What format is your ext sdcard??
What zips are you trying to flash??
How did you install twrp??
What is the OS of your PC??

lj50036 said:
Just need a little more info....
What bootloader are you on??
What format is your ext sdcard??
What zips are you trying to flash??
How did you install twrp??
What is the OS of your PC??
Click to expand...
Click to collapse
Well I have successfully flashed ROMS before and installed twrp through goo manager. I wanted to bring my tablet back to stock because I was going to sell it. When I went to wipe before installing back the stock rom i wiped the system and everything so I cant boot it up after since it doesnt have a rom on it atm. I also cant get it to connect to my computer through the recovery for some reason so I had to use an external sd card to put roms on but that isnt working. I forget what bootloader I'm on since its been a while since I have done anythign with this tablet but that latest ROM I had on it was a jellybean one so i probably updated the bootloader before installing the rom.
I am just trying to flash stock rom back on but I have tried others and no luck with a few different ones. I was trying to experiment with a what format the sd was to see if that would help but so far I have tried exFAT and FAT and neither has helped. My pc is windows 7 64 bit.

SKU
snoboardfrk said:
Well I have successfully flashed ROMS before and installed twrp through goo manager. I wanted to bring my tablet back to stock because I was going to sell it. When I went to wipe before installing back the stock rom i wiped the system and everything so I cant boot it up after since it doesnt have a rom on it atm. I also cant get it to connect to my computer through the recovery for some reason so I had to use an external sd card to put roms on but that isnt working. I forget what bootloader I'm on since its been a while since I have done anythign with this tablet but that latest ROM I had on it was a jellybean one so i probably updated the bootloader before installing the rom.
I am just trying to flash stock rom back on but I have tried others and no luck with a few different ones. I was trying to experiment with a what format the sd was to see if that would help but so far I have tried exFAT and FAT and neither has helped. My pc is windows 7 64 bit.
Click to expand...
Click to collapse
Ok we need the bootloader version so we make sure we flash the correct SKU.... We need your pc to recognize your tablet in fastboot mode...
So boot into the screen where you enter recovery, but don't enter recovery in the upper left corner there will be small white letters, that will tell us your tablets SKU we are interested in the letter like WW, or US... Than in that same screen plug it into your PC and see if it will recognize it as a fastboot devices in your files manager.. It may just go get the drivers for it or it may not.. Let me know... Thx lj

lj50036 said:
Ok we need the bootloader version so we make sure we flash the correct SKU.... We need your pc to recognize your tablet in fastboot mode...
So boot into the screen where you enter recovery, but don't enter recovery in the upper left corner there will be small white letters, that will tell us your tablets SKU we are interested in the letter like WW, or US... Than in that same screen plug it into your PC and see if it will recognize it as a fastboot devices in your files manager.. It may just go get the drivers for it or it may not.. Let me know... Thx lj
Click to expand...
Click to collapse
Ok so it says key driver not found... then its a US bootloader. So nothing pops up on my PC when i boot it up. Im gonna go look for the driver and see if I install it if it will recognize my device.

snoboardfrk said:
Ok so it says key driver not found... then its a US bootloader. So nothing pops up on my PC when i boot it up. Im gonna go look for the driver and see if I install it if it will recognize my device.
Click to expand...
Click to collapse
We need the boot loader version. It's really important to stop you hard bricking your device. Don't flash or do anything just yet, but my guess is you will need buster99's fix.

sbdags said:
We need the boot loader version. It's really important to stop you hard bricking your device. Don't flash or do anything just yet, but my guess is you will need buster99's fix.
Click to expand...
Click to collapse
Ok the version is US_epad-10.5.1.14.8-20130514. Does that sound right? Thanks!

fastboot/adb/drivers
snoboardfrk said:
Ok the version is US_epad-10.5.1.14.8-20130514. Does that sound right? Thanks!
Click to expand...
Click to collapse
Head over here and grab up on this for your PC. http://forum.xda-developers.com/showthread.php?t=2588979. Let me know when you have that done...the lj

lj50036 said:
Head over here and grab up on this for your PC. http://forum.xda-developers.com/showthread.php?t=2588979. Let me know when you have that done...the lj
Click to expand...
Click to collapse
Alright awesome, I just installed it. Should it recognize the device now?

Let try
snoboardfrk said:
Alright awesome, I just installed it. Should it recognize the device now?
Click to expand...
Click to collapse
Open your CMD window as admin boot your tablet into fastboot plug it into your PC... Than type
Code:
fastboot devices
copy and paste the outcome....

lj50036 said:
Open your CMD window as admin boot your tablet into fastboot plug it into your PC... Than type
Code:
fastboot devices
copy and paste the outcome....
Click to expand...
Click to collapse
C:\Windows\system32>fastboot device
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable

snoboardfrk said:
C:\Windows\system32>fastboot device
usage: fastboot [ <option> ] <command>
Click to expand...
Click to collapse
Maybe just copy and paste the commands I give you LOL......:silly:
Look again....

lj50036 said:
Maybe just copy and paste the commands I give you LOL......:silly:
Look again....
Click to expand...
Click to collapse
LOL wait im confused. Haha sorry Im bad at this. So you want me to type in on the cmd: fastboot device right? Then all these options pop up. Am I doing something wrong?

snoboardfrk said:
LOL wait im confused. Haha sorry Im bad at this. So you want me to type in on the cmd: fastboot device right? Then all these options pop up. Am I doing something wrong?
Click to expand...
Click to collapse
No worries....
Check your spelling of
Code:
devices
So if you can just copy and paste the command I give you than there will be no mistakes, I dont like mistakes....

lj50036 said:
No worries....
Check your spelling of
Code:
devices
So if you can just copy and paste the command I give you than there will be no mistakes, I dont like mistakes....
Click to expand...
Click to collapse
LOL makes sense my bad. Here is what pops up:
015d29955b37fc0c fastboot

snoboardfrk said:
LOL makes sense my bad. Here is what pops up:
015d29955b37fc0c fastboot
Click to expand...
Click to collapse
Thats what we need now go to here http://www.service.asus.com/#!downloads/c1wax
GET THE LATEST ONE YOU CAN FIND WITH A US SKU
This is most important that you get one with a US SKU....
Let me know when you have it.....
---------- Post added at 04:35 AM ---------- Previous post was at 04:32 AM ----------
At this point it is most important if you don't understand something you ask... No matter what it is, I will be here all night if thats what it takes.....
Your 700 will live again!!!!!:highfive:

lj50036 said:
Thats what we need now go to here http://www.service.asus.com/#!downloads/c1wax
GET THE LATEST ONE YOU CAN FIND WITH A US SKU
This is most important that you get one with a US SKU....
Let me know when you have it.....
---------- Post added at 04:35 AM ---------- Previous post was at 04:32 AM ----------
At this point it is most important if you don't understand something you ask... No matter what it is, I will be here all night if thats what it takes.....
Your 700 will live again!!!!!:highfive:
Click to expand...
Click to collapse
Ok am I just looking to download drivers? Whats the difference between the TF700KL vs TF700T? You have been very helpful, I really appreciate it!
Scratch that, I'm assuming we are talking about latest firmware?

Firmware
snoboardfrk said:
Ok am I just looking to download drivers? Whats the difference between the TF700KL vs TF700T? You have been very helpful, I really appreciate it!
Click to expand...
Click to collapse
No your going to download the firmware... It is going to upgrade your bootloader but, since you were not able to mount anything in recovery.. We need to do it this way to start from scratch.... Im not sure the difference between the KL and the T but don't get the KL BAD...Thx for asking instead of just assuming you will be a pro by the time we get done...
---------- Post added at 04:47 AM ---------- Previous post was at 04:45 AM ----------
Yes get the US SKU V10.6.1.14.10
Most Important

lj50036 said:
No your going to download the firmware... It is going to upgrade your bootloader but, since you were not able to mount anything in recovery.. We need to do it this way to start from scratch.... Im not sure the difference between the KL and the T but don't get the KL BAD...Thx for asking instead of just assuming you will be a pro by the time we get done...
---------- Post added at 04:47 AM ---------- Previous post was at 04:45 AM ----------
Yes get the US SKU V10.6.1.14.10
Most Important
Click to expand...
Click to collapse
Ok I'm downloading the US sku version of the most recent firmware. A couple minutes left

snoboardfrk said:
Ok I'm downloading the US sku version of the most recent firmware. A couple minutes left
Click to expand...
Click to collapse
Ok once you get it unzip it, there will be another zip inside, unzip it, than there will be a blob file move it to the root of your C drive...Let me know when you have it there or if you have any questions alone the way....

Huawei P8 (L09) bricked TWRP no OS

I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.

icemann1908 said:
I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.
Click to expand...
Click to collapse
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Sent from my Nexus 6P using XDA-Developers mobile app

Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse

Rashad83 said:
ebbytay said:
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse

Rashad83 said:
ebbytay said:
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse
You're welcome. Good luck.
Click to expand...
Click to collapse

Fastboot FAILED (remote: failed to erase partition )

I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You

It seems that your partitions are corrupt.
I had the same issue and solved it by restoreing completley to stock Rom. There must be a thread for this anywhere out, if not download a fastboot image from cyanogen support site extract it and try to flash it.

That is what I was leaning towards, but in every solution to restore the stock ROM I have to use fastboot and fastboot just fails to write anything. I can't even get TWRP to stick, fails to write every time. I tried the OnePlusRestoreTool but the driver installs ok but the tool can't find the phone, tried 2 different PCs. I was hoping for another solution other than fastboot or the OnePlusRestoreTool, I searched but could not find another method, I was hoping someone could point me in the right direction.
Thanks

newpop1_android said:
I have OPO 64GB and unlocked via fastboot. Every fastboot command related to flash or erase or format gave same error, unable to erase or write the partition.
I was able to fastboot boot <custom_recovery.img> into TWRP 2.7 I believe but TWRP gives errors, unable to mount <partition>, etc. Any command in TWRP results into a failure to mount or write.
I tried ADB Sideload <zip> and at 12% it rebooted back into Cyanogen Mod ready logo.
TWRP only runs if I boot to it via fastboot, it can't write to the bootloader via fastboot. One strange thing under TWRP storage it shows Internal Storage 0MB and USB-OTG 0MB, the partitions also show 0MB excep for system, but can't format anything or resize.
I feels like there is no storage in this device, is this something that can be fixed or is this a DOA device? It was working fine and a Cyanogen update ran and bricked it!
When I try to fastboot flash I get this error, fail to write. I even tried the OnePlusRestoreTool and it fails to write to the phone.
fastboot flash recovery twrp3.img
target reported max download size of 1073741824 bytes
sending 'recovery' (13326 KB)...
OKAY [ 0.422s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.479s
Thoughts?
Thank You
Click to expand...
Click to collapse
Try this

geowolf1000 said:
Try this
Click to expand...
Click to collapse
So I tried the link but also their method uses FastBoot and FastBoot fails to write to the OPO every time no matter what, see below. I can put TWRP in memory but can't write to the SD I guess. Any tool that can reformat the storage and put it back together since FastBoot and ADB can't write to it?
Thx
target reported max download size of 1073741824 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.137s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.208s

Has a second method from terminal
Run command from twrp rerminal
Στάλθηκε από το A0001 μου χρησιμοποιώντας Tapatalk

Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work

Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
He tried that one, but as the PC doesn't detect his phone that ain't gonna work...
@newpop1_android could you sent me a PM, I'll try to resolve your issue in a teamviewer session.

Chinaroad said:
Try this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , it will rewrite all the partition and then change the rom and recovery you want, it should work
Click to expand...
Click to collapse
Hello, so I managed to get an older PC to do all this in as well and tried another PC anyway. I ran the color.zip install, drivers installed OK and phone is detected, I ran the Msm8974DownloadTool.exe and it found the phone in COM3, I see a progress bar in one file, the image file and then it reboots the phone but it comes back to the Cyanogen splash screen and it does not go anywhere, so I reboot it again manually power+VUp and the tool finds it again and tries to send the *same* file again, and then I tried this loop at least 10 times.
I conclude that it is unable to write the image to the cell, same symptom I encountered with Fastboot flash boot img. Does this mean that the cell is bricked since nothing can write to the SD?

Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
If only one image file is "flashed", check if your color.zip is downloaded correctly
Hope this helps

Flo9818 said:
Do the progressbars you see in Msm8974DownloadTool.exe become green?
Maybe see there:
http://www.technobuzz.net/guide-to-recover-from-hard-bricked-oneplus-one/
It is nearly the same like the one posted before, but has some screenshots.
After doing this color OS should boot up, not cyanogen os.
Hope this helps
Click to expand...
Click to collapse
Hello, not really, it does one file and then I see progress bar move on the first file, progress bar finished and then the phone boots to the cyanogen screen again, then i tried again, it still shows the same file again. It does not save the file, fails to write pretty much, same thing as fastboot.

There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Have you restarted your PC?

Flo9818 said:
There should be serveral progressbars. One for each image in color.zip. Try to reinstall the qualcomm 2012 drivers.
Click to expand...
Click to collapse
I actually did that and tried one plus one as well, I also tried the other unbrick toll as well with other drivers. The phone is recognized no problem, but nothing can write to it, just like fastbook flash , write denied every time.

Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked

Flo9818 said:
Restarted your PC after qualcomm driver install?
Maybe there be driver problems related to win10.
Also check
fastboot oem device-info if your bootloader is really unlocked
Click to expand...
Click to collapse
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?

MrPowerGamerBR said:
It won't work, his device is not recognized by adb or fastboot.
My device is in the same state, I rebooted it and it hard bricked, I tried using the ColorOS flash tool but, when I start it, it is stuck in a loop trying to flash "8974_msimage.mbn", any solution would be appreciated, because I hard bricked it in the first day after receiving my OPO (I bought an used one).
I already tried on two different computers, the same issue happens, I also tried to find a fix, but everyone that had this issue never replied, so I think this state is really THE hard brick, with no ways to go back to the original state.
@newpop1_android did you find a solution for your problem?
Click to expand...
Click to collapse
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?

Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Yes, I did.
I also tried that tool before, same issue.

Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.

MrPowerGamerBR said:
The problem is that the device gets disconnected when flashing for some reason. I tried two different drivers, both didn't work.
I'm willing to pay 5$ to someone who can fix this issue for me.
Click to expand...
Click to collapse
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/

Flo9818 said:
Did you run the programm as administrator?
Someone in the oneplus forum had the same problem with loop flashing the 8974_msiimage.mbn and solved it with
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe a try?
Click to expand...
Click to collapse
Flo9818 said:
Which Windows Version do you use? I would try with win7. With win 8.1 and 10 you have to disable driver verification.
Have you disabled your antivirus?
Have you disabled UAC?
Maybe another USB cable?
If all this does not work see here:
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
Click to expand...
Click to collapse
Windows 7, but Windows 7 also needs to disable driver verification.
I don't use any antivirus.
No, but I ran the tool as administrator.
I already tried that, I tried with the original cable that came with the device and my Moto G 2014 cable, same issue on both.
It isn't a missing driver issue tho, Qualcomm drivers are installed and working because the ColorOS flash tool detects the device.
Anyway, thanks for helping

Rooting Android 9 December Update With Magisk (No TWRP)(Global)

- Make sure usb debugging is enabled in your developer options menu, your bootloader is unlocked and your critical partitions are unlocked. For instructions, visit https://developer.razer.com/razer-phone-dev-tools/general-instructions/?_ga=2.111753092.1097369801.1578321896-2010083175.1573219083?_ga=2.111753092.1097369801.1578321896-2010083175.1573219083
- Download and extract platform-tools to your desktop (for adb and fastboot functions) here http://https://developer.android.com/studio/releases/platform-tools
- Download the current release on Razers website here http://https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip or for a list of releases https://developer.razer.com/razer-phone-dev-tools/factory-images/. Unzip, and copy the boot.img to your phones internal storage.
-Download and install Magisk Manager on your device. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
-open Magisk Manager, and select install, and when prompted, select "select and patch a file". Choose the boot.img you put in your internal storage.
-Once patching is finished (the patched image will be in the same location as the original image), move the patched boot.img from your phone to your platform-tools folder (will be labeled "magisk_patched.img").
-right-click within the platform-tools folder and select "open powershell window here" or "open cmd prompt here".
-IF USING CMD:
Code:
adb reboot bootloader
-IF USING POWERSHELL:
Code:
./adb reboot bootloader
. Your device should restart and boot into the bootloader.
-next, flash the patched boot image to BOTH slots,
-IF USING CMD:
Code:
fastboot flash boot_a magisk_patched.img
and then
Code:
fastboot flash boot_b magisk_patched.img
-IF USING POWERSHELL:
Code:
./fastboot flash boot_a magisk_patched.img
and then
Code:
./fastboot flash boot_b magisk_patched.img
-Finally, restart your device and verify Magisk is installed via the Magisk Manager app, and that WiFi is working.
NOTE Keep the original boot.img because it can be flashed the same way to revert to stock.

Thanks for this, I had been waiting on a method to root the latest update and this looks like it. Will try it when I get a chance.

Working 100%, thanks again.
Sent from my Phone using Tapatalk

patient81 said:
Working 100%, thanks again.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
You're welcome!

After I try flashing <waiting for any device> shows up and nothing happens help

plankton57 said:
After I try flashing <waiting for any device> shows up and nothing happens help
Click to expand...
Click to collapse
I PMed you, in case you still need help.

bdizthebiz said:
I PMed you, in case you still need help.
Click to expand...
Click to collapse
i faced the same issue send help

bdizthebiz said:
I PMed you, in case you still need help.
Click to expand...
Click to collapse
Im having the same issue, stuck on <waiting for any device> in powershell. is there a fix for this?

Anytime tried relocking bootloader after this method?

@bdizthebiz Can you explain what´s the trick please?
Edit: Nevermind. I´ve solved it changing usb driver to Android Bootloader Interface.

Lonewolf007ljp said:
Anytime tried relocking bootloader after this method?
Click to expand...
Click to collapse
no reason to relock your bootloader unless you're getting rid of your phone. Just keep it unlocked.

crombull said:
@bdizthebiz Can you explain what´s the trick please?
Edit: Nevermind. I´ve solved it changing usb driver to Android Bootloader Interface.
Click to expand...
Click to collapse
how to change to android bootloader interface?
---------- Post added at 07:48 AM ---------- Previous post was at 07:29 AM ----------
After I try flashing <waiting for any device> shows up and nothing happens. I tried so many methods and couple hours. please help

Fastboot issue
If you're having issues interacting with your device while its in fastboot, it could be because the appropriate drivers aren't installed. Please refer to this link;
https://s3.amazonaws.com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf

error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a Magisk_patched.img
error: cannot load 'Magisk_patched.img': No such file or directory

kevinc999 said:
how to change to android bootloader interface?
---------- Post added at 07:48 AM ---------- Previous post was at 07:29 AM ----------
After I try flashing <waiting for any device> shows up and nothing happens. I tried so many methods and couple hours. please help
Click to expand...
Click to collapse
I changed the properties of the android device in device manager as bdizthebiz user said.

crombull said:
I changed the properties of the android device in device manager as bdizthebiz user said.
Click to expand...
Click to collapse
did that already. still same results

Sorry. I cannot help you. Perhaps using another PC...

Hi, thanks for your guide but before I attempt I am on the November 2019 Security Patch (Android 9), does this matter or do you not know? Sorry if it's a silly question.

this method work for oreo or not?