Hello there i had problem with my oneplus one the support send me a
We prepared an Automated batch file which will fix your issue automatically, all you need to do is to download the zip file from the link below and extract it, after extracting please open the "README !!!!!.pdf" and follow the instructions.
PLEASE NOTE :- IT WILL DELETE ALL YOUR PHONE'S DATA> PLEASE BACK UP YOUR PHONE'S DATA
This should resolve your issue.
but i have try the setup as the support writ to me 10 times but i am getting all times errors
######### This patch is Created by ONEPLUS Technical Support. #######
###### This patch should only be used for ONEPLUS ONE 64GB Global Version. #####
#
...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
erasing 'persist'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 4.901s
error: cannot load 'persist.img'
erasing 'reserve4'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.010s
error: cannot load 'reserve4.img'
error: cannot load 'boot.img'
error: cannot load 'userdata_64g.img'
error: cannot load 'system.img'
error: cannot load 'recovery.img'
error: cannot load 'cache.img'
error: cannot load 'NON-HLOS.bin'
error: cannot load 'sbl1.mbn'
error: cannot load 'sdi.mbn'
error: cannot load 'emmc_appsboot.mbn'
error: cannot load 'rpm.mbn'
error: cannot load 'tz.mbn'
error: cannot load 'logo.bin'
ihop some of you can help me
i have mailed oneplus one support no answer
What was the problem you were having in the first place please?
Transmitted via Bacon
To run that all-in-one batch FIX file released by OnePlus you need to unlock your bootloader FIRST then run that batch file(s). Put your device in bootloader mode and run fastboot oem unlock (This wipes you device)
Now put it in bootloader mode again and run the 3 batch files contained within that .zip file.
Edit: I see the second file actually does unlock your bootloader, have you run the files in the correct sequence e.g. ONEPLUS ONE - 0.bat then ONEPLUS ONE - 1.bat then ONEPLUS ONE - 2.bat with your device in bootloader mode ?
Hey all, sorry I may be posting this in the wrong place, new here. Can someone help me with this please?
I'm trying to flash 5.0 to my Nexus 5. I have unzipped the right hammerhead zip (I'm 95% sure) into the platform-tools folder which contains my fastboot file in it. I put my phone into fast boot mode (its unlocked, I flashed to 4.4. 4 this way). When I run the flash-all.sh command in terminal (on mac) I get the following dialog:
error: cannot load 'bootloader-hammerhead-hhz12d.img'
rebooting into bootloader...
OKAY [ 0.055s]
finished. total time: 0.056s
error: cannot load 'radio-hammerhead-m8974a-2.0.50.2.21.img'
rebooting into bootloader...
OKAY [ 0.048s]
finished. total time: 0.048s
error: failed to load 'image-hammerhead-lrx21o.zip': No such file or directory
Any thoughts on what this could be? My phone flashes just before every error. Would love any help, thank you!
croikee said:
Hey all, sorry I may be posting this in the wrong place, new here. Can someone help me with this please?
I'm trying to flash 5.0 to my Nexus 5. I have unzipped the right hammerhead zip (I'm 95% sure) into the platform-tools folder which contains my fastboot file in it. I put my phone into fast boot mode (its unlocked, I flashed to 4.4. 4 this way). When I run the flash-all.sh command in terminal (on mac) I get the following dialog:
error: cannot load 'bootloader-hammerhead-hhz12d.img'
rebooting into bootloader...
OKAY [ 0.055s]
finished. total time: 0.056s
error: cannot load 'radio-hammerhead-m8974a-2.0.50.2.21.img'
rebooting into bootloader...
OKAY [ 0.048s]
finished. total time: 0.048s
error: failed to load 'image-hammerhead-lrx21o.zip': No such file or directory
Any thoughts on what this could be? My phone flashes just before every error. Would love any help, thank you!
Click to expand...
Click to collapse
I've had the same issue while flashing Nexus 4 from Ubuntu, it found out i should just change directory with "cd" command before i run the script, so the command should be "sudo sh flash-all.sh", not "sudo sh /home/username/Downloads/occam-lrx21t/flash-all.sh", i used.
Hope this will help someone.
Recently bought a pixel 128gb to replace a crappy nexus 5x which had died. I just finished flashing 8.1 factory image and unlocked with flashing critical flag. So now, trying to boot the latest twrp 3.2.0.0 gives me an error:
Code:
>fastboot boot twrp.zip
creating boot image...
creating boot image - 9166848 bytes
downloading 'boot.img'...
OKAY [ 0.281s]
booting...
[B]FAILED (status read failed (Too many links))[/B]
finished. total time: 0.415s
I've now tried this on 3 different computers (2x Win10 and again on Linux) with latest google USB drivers and latest platform tools and receive the same error.
Anyone else seeing similiar issue and/or can share some tips and advice?
wow, need some more coffee...figured it out.
I was trying to boot the twrp.zip rather than the .img tehehehe
I have the same error. Not flashing the zip. I'm lost
I'm no expert, but you have to fastboot boot twrp.img (AFAIK)
Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.
Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"
Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .
No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s
ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.
Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…
I've recently gotten an unknown-manufactured android pad and I want to flash my custom AOSP system into it. I'd just prefer to change the system image of the pad, from Android 9 to Android 10, and when I tried to flash the system image into it, the error pops out like this:
Code:
[email protected] /media/caesar/TLC_0/AOSP/out/target/product/generic fastboot -S 128M flash system system.img
Invalid sparse file format at header magic
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
And now I've got no idea how can I solve this problem, I would appreciate your help. THANKS!