Hi,
My phone pop up messages saying some services stopped. So I turned it off and then it stuck in a boot loop circle. (same problem in this thread, http://forum.xda-developers.com/nexus-4/help/help-im-stuck-bootloop-4-circles-t2864835)
First, I tried to enter recovery mode, failed.
then, I tried to fix my recovery ...
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.351s]
finished. total time: 0.355s
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-mako.img
sending 'recovery' (8838 KB)...
OKAY [ 0.492s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.512s
also tried the latest "openrecovery-twrp-2.7.1.0-mako.img" downloaded from http://techerrata.com/browse/twrp2/mako
same error
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.454s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.473s
here's the fact about my phone:
- CWM (recovery-clockwork-touch-6.0.4.7-mako.img)
- SuperSU (UPDATE-SuperSU-v1.93.zip)
- rooted before the 4.4.4 update, didn't fix the root after ATO update
- Standard Kernel, no custom ROM.
I did suffer the "randomly turning off" problem before (http://forum.xda-developers.com/nexus-4/help/nexus-4-randomly-off-intermittently-t2077148).
What could be the problem for the flash write failure? Is there any other way to recovery the data?
Many Thanks.
Related
When I try to flash my system it says:
C:\Program Files\Android\Android\tools>fastboot flash system system.img
sending 'system' (151459 KB)... OKAY [ 28.545s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 28.551s
Click to expand...
Click to collapse
did you ever get this fixed? I'm having same issue
try to restore the phone
I have a xt907 and after playing around with rooting, I goofed bigtime and now I can only boot to the fastboot menu.
Im trying to flash the default images back on,. but I keep getting errors. I've tried the firmware versions found at the sbf-droid page.
All the Versions except for the last one give me the same error on the system.img
Code:
sending 'system' (262144 KB)... OKAY [ 19.976s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
The last one Android 4.4.2 Blur_Version.183.46.10.XT907.Verizon.en.US - gives me the error
Code:
~/droid/VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml$ ./moto-fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 19.986s]
writing 'system'... INFOProtocol error (multiflash unexpected)
Any help?
Have you tried with rsd lite?
Edit: and you said you rooted did you unlock the bootloader?
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
https://www.androidfilehost.com/?fid=24671318762849134 you need to flash this fisrt before flash custom rom
Same Problem XDA devs Pl Help
Kabeesh said:
Hey guys, i wanted to unlock bootloader, and so i UNLOCKED BOOTLOADER, FLAHSED TWRP, TRIED TO FLASH CUSTOM ROM.
the twrp compared tz version and ended up in an error, so i searched online to know that, we need to update the system.
so i flashed recovery.img on top of twrp and rebooted where the fastboot got lost and ended up in a dead boot.
no vibrations, no led, no charging, no fast boot.
then i flashed using qfil using qualcom husb and got back the fastboot.
but this time, in fastboot, when i try to flash boot, system or recovery, it says, ::ARTITION TABLE DOES NOT EXIST.
so i tried to flash the gpt_both0.bin file as partition, and gave an error message of::: CANNOT FLASH THIS PARTITION IN LOCKED STATE.
i tried to fastboot boot twrp.img and ended up::: UNLOCK DEVICE TO USE THIS COMMAND.
so im pretty much got my bootloader locked and im unable to unlock it so i can flash stuffs.
the question is, how to flash the bootloader using fastboot so i can flash the rest and continue/??
Code:
C:\adb>fastboot devices
5072e4de fastboot
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24869 KB)...
OKAY [ 0.784s]
writing 'boot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.799s
C:\adb>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.016s
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (29968 KB)...
OKAY [ 0.944s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.952s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.950s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.950s
Click to expand...
Click to collapse
:fingers-crossed:
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
dladz said:
This should be asked in the relevant thread.
That being said.
1. Install a fresh OOS build, you have to have disabled any magisk modules before this.
2. Follow the instructions in the CRDroid thread.
*Note: you have to be using Windows 10 not 7
Make sure it's the 11 version not the 10 version of the ROM.
Make sure it's in the installer bat format.
You have to factory reset in the PE recovery after the installer has finished.
If you're still having issues then MSM format to 2.2 and then start at point 2
Bare in mind if you're on Verizon AFAIK it will not show your SIM, this is prevalent on all custom ROMs.
Click to expand...
Click to collapse
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
reppinrengar said:
Thanks for the reply
I can not flash anything to "critical partitions"
when I issue the command: fastboot flashing unlock_critical
it tells me that the device is already unlocked
when I try to flash the rom using fastboot it tells me it failed because flashing is not allowed to critical partitions
the phone is now soft bricked where it boots to the logo and then shuts off and i need to hold the power buttons
btw holding vol up + down + power brings up fastboot but holding vol down + power never brings up recovery
EDIT: the output of fastboot oem device-info shows
verity mode = true
device unlocked = true
device critical unlock = false
charget screen enabled = true
Click to expand...
Click to collapse
You don't flash using fastboot just stick with the installer.bat file, it's in the ROM zip
If that doesn't work then your system is borked, in which case like I said just use the MSM tool.
You're done in several steps.
You should never need to unlock critical
reppinrengar said:
The phone is the 5G unlocked US version model IN2025
I am running windows 10 with adb and fastboot set in my path variables
I installed the oneplus drivers that came with the phone
I ran the installer and this is the output:
Code:
Do you want to install ROM ( Reccomended )[Y/N]?y
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.403s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 2.913s
Sending 'boot_a' (98304 KB) OKAY [ 2.400s]
Writing 'boot_a' OKAY [ 0.286s]
Finished. Total time: 2.871s
Sending 'dtbo' (24576 KB) OKAY [ 0.612s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.774s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/2 (720896 KB) OKAY [ 17.547s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (211392 KB) OKAY [ 5.403s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'product' 1/2 (720896 KB) OKAY [ 17.475s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.035s
CLICK ENTER RECOVERY FACTORY RESET AND REBOOT
UPGRADING FROM SAME ROM, JUST REBOOT
#########################################
# ONEPLUS LOVE! #
#########################################
Press any key to continue . . .
Can anyone help me on what needs to be done in order to have a successful install? Thanks
Click to expand...
Click to collapse
Use the original OnePlus cable.
This phone have probably softbrick or hardbrick and bootloop and intro to recovery (no erecovery) gets a rescue mode screen
I have tried with the "potatonv" tool and trying to flash a stock rom and a custom recovery but none work and I have the bootloader unlocked but I get these following results:
>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 471859200 bytes
sending 'RECOVERY' (36118 KB)...
OKAY [ 0.986s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 1.012s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (36118 KB)...
OKAY [ 1.000s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.468s