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!
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 .
So H2OS boots up just fine. Fastboot mode works. When I boot into recovery mode the oneplus logo shows up, but it is as nothing happens afterwards. I left the device there for more than an hour and still nothing. Flashing from the OS twrp 2.8.7.0 or 3.0.0-2 has no change on this. Flashing from fastboot the same. When I try to boot from fastboot,I get the following error:
[email protected] ~/Downloads $ fastboot boot twrp-3.0.0-2-oneplus2.img
downloading 'boot.img'...
OKAY [ 0.807s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.873s
[email protected] ~/Downloads $ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.815s]
writing 'recovery'...
OKAY [ 0.534s]
finished. total time: 1.349s
Any ideas?
I have official android 11 without root or anything but it does not let me flash anything or boot and it tells me the fastboot of the mobile that is in the slot: B
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 2.548s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.862s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> Fastboot flash recovery TWRP.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.621s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 2.773s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009>
vickmen said:
I have official android 11 without root or anything but it does not let me flash anything or boot and it tells me the fastboot of the mobile that is in the slot: B
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 2.548s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.862s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> Fastboot flash recovery TWRP.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.621s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 2.773s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009>
Click to expand...
Click to collapse
TWRP has not worked on Pixel 3 since Android 9. There is a test build for Android 10 at https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622/page29, but the only response to that post was it did not work. There is nothing for Android 11.
dcarvil said:
TWRP has not worked on Pixel 3 since Android 9. There is a test build for Android 10 at https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622/page29, but the only response to that post was it did not work. There is nothing for Android 11.
Click to expand...
Click to collapse
Thank you, he enters me and everything but he asks me for a password, I put it on him and nothing but at least I know that my mobile is in good condition, I had been scared hahaha
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.