Hi folks,
Here is a resumé of what i've tried so far
Actual symptoms : Cyanogenmod logo with animation looping (no bootloop)
I've access to fastboot and philz recovery (but errors are shown, see below)
I've got the phone as it is, no idea of what the previous owner has done.
Can someone help me ?
I tried to unbrick using various methods :
ColosOS : device is displayed as FORGE HS-USB QDLOader 9008 or Qualcomm HS-USB QDLOader 9008
OPO recovery tool 1.1 : connected to com5, 8974_msimage.mbn: OK
that's the only thing shown, then the OPO vibrates and nothing happen
Flash zip bacon 33R and 44S via OTG => error status 7
Code:
Installing : /storage/usbdisk/cm-11.0-XNPH44S-bacon-signed-fastboot.zip
E: Can't mount /cache/recovery/last_install
E: faile to open last_install : File exists
Finding update package
Opening update Package
Installation update
Installation aborted
Code:
[U]Errors when booting Philz Recovery :[/U]
E: could not mount /data to setup /data/media path!
E: Can 't mount /cache/recovery/command
E: Can 't mount /cache/recovery/log
E: Can 't open /cache/recovery/log
E: Cannon mount path for settings file :/data/philz-touch/phils-touch6.ini
E: Can 't mount /cache/recovery/last_log
E: Can 't open /cache/recovery/log
E: Can 't mount /cache/recovery/last_install
E: Can 't open /cache/recovery/last_install
[U]Logs :[/U]
W; failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 (File exists)
mount : mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed : Invalid argument
Code:
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
finished. total time: 0.008s
OnePlus One ZIP with 3 bats and fastboot :
Code:
######### This patch is Created by ONEPLUS Technical Support. #######
###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ####
#
...
OKAY [ 0.003s]
finished. total time: 0.003s
erasing 'persist'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.138s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.221s
erasing 'reserve4'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.167s]
writing 'reserve4'...
FAILED (remote: flash write failure)
finished. total time: 5.251s
target reported max download size of 536870912 bytes
sending 'boot' (5578 KB)...
OKAY [ 0.181s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.232s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'recovery' (7510 KB)...
OKAY [ 0.243s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.295s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.800s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.851s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.056s
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.062s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.308s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.361s
rebooting...
finished. total time: 0.005s
It is done Now :)
Appuyez sur une touche pour continuer...
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
Click to expand...
Click to collapse
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
Click to expand...
Click to collapse
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Seems the guy you buy the phone has relock bootloader
In kitkat that was problem ....
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Status 7 message is due to improper twrp recovery..... flash the latest.... and unlock the bootloader once again.... may be that will help.
Really want to help u.... because, once i had bricked my device and lost efs also, and I know how bad it feels .... but thanks to my backups, i was saved...
#HappyFlashing#
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Qiou said:
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Click to expand...
Click to collapse
im having this exact problem... anyone managed to find a fix? Even putting it back to stock doesn't work!
Related
SOLVED: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851/post57916281#post57916281
The story goes, I was trying to flash CM11S after trying out the Oneplus One Lollipop Alpha. Part way through the process the command line was waiting for the device to reboot into fastboot and it never did.
Command Prompt Log:
Code:
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.770s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.613s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.004s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.016s
sending 'dbi' (11 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
sending 'aboot' (376 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 3.521s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.028s]
finished. total time: 0.037s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.012s]
writing 'tz'...
OKAY [ 0.015s]
finished. total time: 0.028s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
OKAY [ 0.162s]
finished. total time: 0.468s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
Now the device is entirely unresponsive aside from a vibration when I hold down the volume and power keys. Screen stays black too and my computer will not detect my device. The Device is recognized by MSM8974 Downloader as well, but every time I select it to repair it it fails. The device also happens to be recognized by QPST Configuration software.
MSM8974 Downloader Log
Code:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
More Information:
Storage Capacity: 64GB
PC OS: Windows 8.1
Windows Driver Signature Verification Status: OFF
Device Drivers: PDANet Android Drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers.
Hello.
Same problem here. I just tried to reflash another roll since i was trying to rollback from Lollipop alpha. I did some changes in TWRP and after reboot my device did not start at all. There is only a vibration when I try to turn it on. Charging is also disabled. Screen is blank and unresponsive. Both recovery and bootloader dont work. I tried to turn my opo while connected to PC and I can hear that system found a new device. But there is no popup window, just the sound. Even after unplugging the sound can be heard.
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
TheManDroid said:
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
Click to expand...
Click to collapse
Been there done that. Nothing came of it, hence my logs posted above. Also I wouldn't be posting about it if I had found a solution
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
I have the same problem. I suspect it's due to the differences in the partition tables between the ROMs. For example, the logo.bin for the CM11S image is around 9MB, whereas it is 512KB in the OnePlus ROM.
Hope we can get this fixed.
TheManDroid said:
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
Click to expand...
Click to collapse
Sorry if I came off harsh in my previous post. That was not my intention. As for senior member, it means nothing other than I have been here a while (around the block so to speak), and I am very glad your willing to offer assistance (we need more people like you in fact), I just was noting that the thread had stated logs from the source you had mentioned. Now to answer your questions (I'll post this in the OP as well):
- You can see in the logs posted above what is missing in my partitions and what partitions are missing in general.
- 64GB
- I have tried using the PDANet drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers. I will also note that I am on Windows 8.1 (Driver Signature Verification turned off).
Hello!
Mi Blu Pure XL is dead, No OS installed.
I tried to install the system image with fastboot, but I have the following errors.
The recovery and Boot was installed OK.
[[email protected] BLU]# fastboot flash recovery BLU_RECOVERY_0.img
target reported max download size of 134217728 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.933s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.573s
Errors:
[[email protected] BLU]# fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected] BLU]# fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected] BLU]# fastboot flash system BLU_SYSTEM_0.img
target reported max download size of 134217728 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
Please Help me!!! :crying:
Any Help!????
Any Help!????
This phone has a semi unlocked bootloader. You can only flash BOOT and RECOVERY. For the rest the need to use SP Flash Tool.
Error
Error with SP Flash Tool:
BROM Exception! ( BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)
I see that I need flash preloader firts. But i dont have preloader.bin
Someone could share ?
Thanks to all!!
I found everything needed in the following message
http://forum.xda-developers.com/pure-xl/general/blu-development-t3213354/post65349290#post65349290
Thanks to all! Today I am the happiest man in the world .
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
IK1981 said:
Dear all,
I own a XT1541 and updated to Marhsmallow via OTA few weeks ago. I encountered some troubles with the performance. I also had the issue that a single app was attempted to be optimized on every boot. Therefore, I decided to reset it to factory settings. However, it seemed that this process failed (waited nearly for an hour to complete but nothing happened).
After rebooting then manually, I am stuck in a fastboot message
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from charger boot mode
CID Read Failure
Invalid CID status 0x69
I can access the device via my Linux using fastboot command. What do you propose to recover from my problem.
Thanks
Click to expand...
Click to collapse
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
bobby0724 said:
Try flashing the factory image here are the instructions
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Already tried this. Already fails at first command... When doing this for the first time, it takes up to one minute to get a response. When retrying, it fails immediately
Code:
~/Downloads/XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml# fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 55.425
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
therealduff1 said:
Try usuing my Motorola downgrade tool , or Motorola utility , created by me , to try and fix problems like this. Links can be found in the general section of Moto g 3 forums , or in Moto g 3 devdb. Therealduff1 is the username you are looking for . I am happy to try and help you with this !
Click to expand...
Click to collapse
Thanks for your help. Tried it with your tool but as far as I could see I land in the same troubles.
Code:
OSPREY_RETEU_6.0_MPI24.65-33_cid7_subsidy
please move all of the firmware files into the moto toolkit directory (the same folder containing toolkit.py)
Please make sure usb debugging is turned on in developer settings, then type 'done' into this promptdone
error: device '(null)' not found
Has your device successfully loaded bootloader mode ? please type 'yes' if it has successfully loadedyes
Press enter to confirm you would like to upgrade to android marshmallow ;)
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 55.795s
Partition table has been flashed
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.438s
Bootloader has been flashed
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.172s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.530s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.093s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.094s
Stock marshmallow recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (238438 KB)...
OKAY [ 7.500s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 15.891s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (238552 KB)...
OKAY [ 7.492s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.608s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (256695 KB)...
One thing that confuses me is the fact that the tool tells me that I shall turn on the USB debug mode. However, since Android does not boot any longer, I have no chance to do this in the Settings. Is there any way to enable this debug mode in another way?
OK I HAVE A MOTO G3 , SKU=XT1541 , VER=P2B , BUILD MP.124.107.55 , SYS VERS=24.61.55OSPREY
It is an unlocked euro version with 1gb ram , i.e not locked to any carrier or ever has been.
I was able to unlock the bootloader , I then followed very carefully the instructions on this site to get the image , usb drivers and everthing required.
However once ono entering the commands at the dos window to start flashing a new rom it comes back with an error , I think I have the incorrect image or there is not one on this site.
I am a complete nuubie can anyone help me please.
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
some progress
robin red said:
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
Click to expand...
Click to collapse
ok I managed to get to the part when I load the sparse files 0-5 , it send them all but reports failure on them all every other command on the list executes correctly.
After this it locked for a while a rebooted in version 6 marshmellow.!!!!! well I guess I am learning.
Anyone any ideas , guess I am lucky I did not brick the thing.
here is what I am getting after entering the third command
C:\Users\Robin L\Desktop\roby>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.470s
Hi all,
Long story short, I did wanna install Snapchat, but my phone was rooted with magisk, so I did wanna do an reinstall of the latest OP6 10 andr. version.
But now I get in a bootloop the issue I see now when I try with ADB on Windows laptop is the following: "FAILED (remote: Failed to load/authenticate boot image: Load Error)".
My commands I tried:
PS C:\adb> fastboot flash recovery_a C:\adb\twrp-3.4.0-1-enchilada.img
target reported max download size of 805306368 bytes
sending 'recovery_a' (31072 KB)...
OKAY [ 0.792s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 0.819s
PS C:\adb> fastboot flash recovery_b C:\adb\twrp-3.4.0-1-enchilada.img
target reported max download size of 805306368 bytes
sending 'recovery_b' (31072 KB)...
OKAY [ 0.793s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 0.834s
PS C:\adb> fastboot boot C:\adb\twrp-3.4.0-1-enchilada.img
downloading 'boot.img'...
OKAY [ 0.794s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.833s
PS C:\adb>
Help... I know how to unbrick this device, but I can't lose the WhatsApp data etc, I didn't back up.
Thanks!
Hey! I've run over a similar issue on op6t.
I'd recommend you doing what I've mentioned in this reply: https://forum.xda-developers.com/showpost.php?p=82995393&postcount=2