Database Users

Fastboot error

I have tried to install twrp recovery via fastboot and I get this error
1.C:\fastboot>fastboot flash recovery recovery.img
2.target reported max download size of 1526722560 bytes
3.error: cannot load 'recovery.img': No error
All other commands work to erase, reboot etc, but cannot flash recovery twrp on to my LGG2 D803 , any help will be appreciated.

Got it to work but flashed 3 different twrp and cm mod img and will not boot into recovery

Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014 in the command mode, by holding the volume up mode and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.

Well if you ever Brick your phone to the point that the only thing that works is Fastboot, I was able to recover my phone using this procedure, It was a lifesaver. The phone works perfectly now, follow the Youtube instructions, I also typed the procedure out too. Always type fastboot flash then the command
https://www.youtube.com/watch?v=hQVTc2m6U-I
Use above link to completely redoo your LGG2 from fastboot, re loading all the partitions.
fastboot flash boot boot.img
aboot aboot.img
recovery recovery.img
laf laf.img
dbi dbi.img
modem modem.img
persist persist.img
PrimaryGPT PrimaryGPT.img
rpm rpm.img
stli stli.img
tz tz.img
fastboot flash reboot
after flashing all the partitions it should load so you can flash the tot/kdz file via flash utility 2014, in the command mode, by holding the volume up button and plugging in the usb into the phone. then reload the original firmware and install twrp and if you want wipe it and reload one of the custom roms.

How to flash stock images - brick recovery

I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.

I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster

I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!

I got blinking brick. I can not go into fastboot

@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power

95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.

aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.

miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.

miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse

ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse

ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse

ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse

ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse

miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?

Rooted, TWRPed G5plus - updating to NPNS25.137-35-5

Phone : TYPE: M266C MODEL:XT1687. (G5 Plus, 4GB, from AMAZON, unlocked).
Currently on NPN25-137-33.
I'm fed up with the upgrade notifications to NPNS25.137-35-5 (not to mention It really interferes with day to day use). So it's time to upgrade.
But, as it's TWRPed, I cant just use the OTA update.
So, If I download POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from here anroidfilehost , will running the following fastboots (the undeleted ones) solve this issue and leav me with an updated, working TWRPed phome?
Code:
[STRIKE]$ fastboot flash partition gpt.bin[/STRIKE]
[STRIKE]$ fastboot flash motoboot motoboot.img[/STRIKE]
[STRIKE]$ fastboot reboot-bootloader[/STRIKE]
[STRIKE]$ fastboot flash logo logo.bin[/STRIKE]
[STRIKE]$ fastboot flash boot boot.img[/STRIKE]
[STRIKE]$ fastboot flash recovery recovery.img[/STRIKE]
$ fastboot flash system system.img
[STRIKE]$ fastboot flash modem NON-HLOS.bin[/STRIKE]
$[STRIKE] fastboot erase modemst1[/STRIKE]
[STRIKE]$ fastboot erase modemst2[/STRIKE]
[STRIKE]$ fastboot flash fsg fsg.mbn[/STRIKE]
$ fastboot reboot
I see no reason to repartition (first striked out command) - am I right ?
DO I need to flash motoboot or any other boot/bootloader image ?
$ fastboot flash system system.img should be run for each of the 5 img_sparsechunk.[0-4]?
And of course - have a current backup ready
Any advice will be appreciated.
Ben

No ideas anyone ?
Ben

I updated to 137-33-5.
Phone was TWRP'ed and rooted with Magisk.
I flashed all the items except "erase user data", if I remember correctly.
flashed TWRP, boot image, and rooted again.
All is well

Thank you !
Will try it in a few days (need my phone working now )

So, in the end, and after realizing that with each update I will have to fastboot again, decided to custom ROM my phone.
Installed RR yesterday.

I need help! BRICKED

Hello,
I was playing around with the Mi A1 magisk and i was flashing it. But then i by accident pressed lock bootloader (and confirming because i did not payed attention to what it was saying) and now the phone is BRICKED :crying: Only thing i get is the connect sound when connected to PC, but the phone shows NOTHING , just black and vibrates when i hold power and any other button. (no fastboot or recovery)
I think it is done for :crying: which hurts me to say cuz i got it as gift.
I think it will be expensive to fix in service center..
PLEASE HELP IF YOU CAN AS FAST AS POSSIBLE
Thanks in advance.

Same happened to me. Did you change anything with tools? did you erase partitions? what exactly thing were you doing to brick it? only press the lock cant brickt it. Normally you can just re-unlock it and flash with the stockrom. Just give us more information about the process you were doing

Actually i booted TWRP by mohacm flashed Magisk then i powered off the phone and than it happend. When it locked i turned it on and showed the colorfull bar and Mi logo for split second and turned off every single time. After re-unlocking it was in bootloop so i tried to restore with Mi Flash tool and it showed error at the end (something wrong with partition b flash) So i tried again and it froze so i turned the tool off and it put it the state it is now.
Also the response of the phone happens only when plugged to PC

You've bricked nothing at all, just chill. I suppose you've installed all the drivers for the A1 while installing the Mi Flash if yes then install minimal adb and fastboot tool, paste all the files from the images folder from the firmware file to the directory of the minimal adb and fastboot tool, open cmdhere.exe located in minimal adb and fastboot tool folder, boot you phone into fastboot mode(press and hold volume down and power buttons at the same time till fastboot bot appears), plug the phone to the pc, enter the following commands:
- fastboot devices (You should see your device's serial tex next to fastboot text if you see nothing, install fastboot drivers properly)
- fastboot flash modem_a modem.img
- fastboot flash modem_b modem.img
- fastboot flash sbl1 sbl1.img
- fastboot flash sbl1back sbl1.img
- fastboot flash rpm rpm.img
- fastboot flash rpmbak rpm.img
- fastboot flash tz tz.img
- fastboot flash tzback tz.img
- fastboot flash devcfg devcfg.img
- fastboot flash devcfgback devcfg.img
- fastboot flash dsp adspso.bin
- fastboot flash sec sec.dat
- fastboot flash splash splash.img
- fastboot flash misc misc.img
- fastboot flash aboot emmc_appsboot.mbn
- fastboot flash abootbak emmc_appsboot.mbn
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
- fastboot flash system_a system.img
- fastboot flash system_b system.img
- fastboot flash lksecapp lksecapp.img
- fastboot flash lksecappbak lksecapp.img
- fastboot flash cmnlib cmnlib.img
- fastboot flash cmnlibbak cmnlib.img
- fastboot flash cmnlib64 cmnlib64.img
- fastboot flash cmnlib64bak cmnlib64.img
- fastboot flash keymaster keymaster.img
- fastboot flash keymasterbak keymaster.img
- fastboot flash userdata userdata.img
- fastboot reboot
Done!

But the problem is that i cannot boot into fastboot. The phone doesent respond to any actions. I was writing it on the top of the thread. If could boot into fastboot then i would use Mi tool again.

Also when the phone is connected to the PC and i hold the Power and volume buttons (up or down doesent matter) nothng happens just the PC does the dis and connect sounds

try hold volume and and down and then connect to pc after that hold power button volume +,- in the same time then wait 6sec . check if ur phone detect on devie manager port

The PC CAN detect the phone. The problem is not in PC but in the phone cuz it wont boot or show NOTHING on the screen whatsoever.

The PC recognizes it as Qualcomm HS-USB Diagnostics 900E (COM3)

AND you're dumb enough to not mention that. If so buy a cheap type-c cable that works on your phone, make it a deep flash cable(search on youtube how to make it) and flash the stock rom using it, that's my best bet.

dont get how someone can mess up the bootloader. i think in 10 years of my phonelife the bootloader menu never bugged.

Ok guys,
Thanks to everyone who helped my phone Is Back alive thx to Xiaomi Service center.

Can't get hard bricked OP8P to EDL mode

Hello Everyone
My Oneplus 8 Pro won't turn on at all , not to recovery mode , not to fastboot mode , not to EDL mode , not even to charge... nothing
And I'm pretty sure everything is set up correctly , the msm tool , the qualcomm drivers , the cable and the port because i have an old oneplus 3t which i'm using for now and it got recognized in the msm tool as soon as i connected it
Here is some context of what happened before my Oneplus 8 Pro died :
I never flashed any custom roms on it , i've been using the stock firmware with root the whole time
I had a custom kernel installed on Android 11 before updating to Android 12 , when i updated to Android 12 (OTA update) the kernel went back to the stock one
after updating to Android 12 there was another OTA update that always fails to install (I believe it was 11.c.16), i got tired of it so i decided to manually updating to the latest firmware including that 11.c.16 incremental update and be done with it
I couldn't sideload it using TWRP becuase i couldn't install TWRP , everytime i tried to flash it using fastboot it seems like it succeeded but when i boot to recovery it boots to fastboot mode
so i googled how to install a firmware using fastboot commands , i found a method to flash the files one by one after extracting them using payload dumper and i tried it , when i was done flashing the files , as soon as i hit enter on the last command to reboot the phone it went to a black screen and has been dead ever since
Here are the fastboot commands i used to flash the firmware :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot -w
fastboot reboot
Sorry for taking so long , I'm desperate
Any kind of help , suggestions or ideas are much appreciated

I haven't been keeping up on that thread since since it doesn't affect me, but I think you fell into the known "OOS Deathtrap" that's been explained here.
Like I said - no idea if it has a solution, or even if there is one now, but it couldn't hurt to read it.

Well... at least now i know what caused the issue , unfortunately i don't think there is a solution other than replacing the motherboard (which was the the solution i wanted to avoid)
I think it's time to say goodbye to oneplus
I wish i had read that article before flashing , Oneplus should put a disclaimer or a warning or something