Help my fastboot -w error - Realme C12 Questions & Answers

It shows this error
I unlock bootloader
Boot to fastboot
Fastboot -w
Shows error
Fastboot erase userdata
works
Fastboot --disable-verification flash vbmeta vbmeta.img
this works fine
Fastboot flash recover recovery.img
Works fine
Fastboot reboot bootloader
Works fine
Fastboot reboot recovery
shows error

Necrazer said:
It shows this error
I unlock bootloader
Boot to fastboot
Fastboot -w
Shows error
Fastboot erase userdata
works
Fastboot --disable-verification flash vbmeta vbmeta.img
this works fine
Fastboot flash recover recovery.img
Works fine
Fastboot reboot bootloader
Works fine
Fastboot reboot recovery
shows error
Click to expand...
Click to collapse
I mean " fastboot flash recovery
Recovery.img "

Related

[Q] [Urgent Help] - Almost bricked

Please help.:crying:
I did the below fastboot commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
All gave me success.
But I am not able to do any of the below commands
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-crespo.img
fastboot -w update image-soju-jzo54k.zip
all i get is "error: cannot load 'bootloader-crespo-i9020xxkl1.img': Unknown error"
Wheareas in the mobile, i get an error:
FASTBOOT STATUS - FAILInvalid Argument
Try to use correct radio
Sent from my Nexus S using xda premium

Help me please i bricked my razr xt 925

Hello guys
i bricked my razr xt 925 during an flash of a custom rom on twrp and the recovery is gone but i can acess the boot menu and the android recovery
my phone is boot loader unlocked
i tried to flash it via rsd lite but it failed at step 2/22 help me please !!
Edit: it worked finally i just dowloaded the same file and used rsd lite and whent take a shower and when i look its done and the android was on thank you man
Growdii said:
Hello guys
i bricked my razr xt 925 during an flash of a custom rom on twrp and the recovery is gone but i can acess the boot menu and the android recovery
my phone is boot loader unlocked
i tried to flash it via rsd lite but it failed at step 2/22 help me please !!
Click to expand...
Click to collapse
I just managed getting out of trouble from these flash errors.
I personnaly used that kind of script to get rid of these XML errors :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen bcomes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot oem fb_mode_clear
fastboot reboot
Ask me if you need more details.
Edit : You should find a script in your rom folder allowing you to directly launch the flash from a command line (you just have to launch it and see what goes wrong if any goes wrong). If it says fastboot unknown command or something like that, place these files in the script folder :
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
adb.exe
Click to expand...
Click to collapse
Hybris95 said:
I just managed getting out of trouble from these flash errors.
I personnaly used that kind of script to get rid of these XML errors :
Code:
@echo off
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot reboot-bootloader
echo. When the screen bcomes back on, press any key to continue!
pause
fastboot flash partition partition_signed
fastboot flash sbl1 sbl1_signed
fastboot flash sbl2 sbl2_signed
fastboot flash sbl3 sbl3_signed
fastboot flash rpm rpm_signed
fastboot flash tz tz_signed
fastboot flash aboot aboot_signed
fastboot flash boot boot_signed
fastboot erase cache
fastboot flash system system_signed
fastboot flash recovery recovery_signed
fastboot flash modem modem_signed
fastboot flash devtree devtree_signed
fastboot flash logo logo
fastboot flash cdrom cdrom_signed
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg_signed
fastboot erase cache
fastboot erase tombstones
echo. Press a key to reboot the phone
pause
fastboot oem fb_mode_clear
fastboot reboot
Ask me if you need more details.
Edit : You should find a script in your rom folder allowing you to directly launch the flash from a command line (you just have to launch it and see what goes wrong if any goes wrong). If it says fastboot unknown command or something like that, place these files in the script folder :
Click to expand...
Click to collapse
IM tring to flash the rom via lsd lite but it got an error and i found on internet how to fix it but when i fix it its stops a 1/21 on rsd lite
Edit: can you do a tutorial for me please ? my razr is the gsm version and i use the brazilian firmware if thats helps
please help me im almost cryiing(sry for the bad english im brazilian)because this phone i just got him ,i have experience on the rsd lite but no much because i used it 4 times and in 2 it was when my razr xt910 bricked
Growdii said:
it worked finally i just dowloaded the same file and used rsd lite and whent take a shower and when i look its done and the android was on thank you man
Click to expand...
Click to collapse
Glad to hear it worked for you
Its always a pleasure to have a fully functionnal smartphone especially when it's some days old

How to prevent Auto-Reboot after flashing Factory Image?

How can I prevent Auto-Reboot of my Nexus 5 after flashing an Official Factory Image?
I've tried to add
Code:
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
after
Code:
fastboot -w update image-hammerhead-xxxxxx.zip
on
flash-all.bat​but the Nexus reboot anyway.
There is another command or option that could help me, or any other way for that?
Flash the files individually
Sent from my Nexus 5 using Tapatalk
alessio89g said:
How can I prevent Auto-Reboot of my Nexus 5 after flashing an Official Factory Image?
I've tried to add
Code:
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
after
Code:
fastboot -w update image-hammerhead-xxxxxx.zip
on
flash-all.bat​but the Nexus reboot anyway.
There is another command or option that could help me, or any other way for that?
Click to expand...
Click to collapse
Flash the files individually with fastboot, u can just do
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash system system.img
You don't need to flash userdata if u don't want to that will erase all ur data, just flash the above images, u will need to extract the zip file that contains the images tho as well as the original tgz file
Sent from my Nexus 6 using Tapatalk
So, is this the sequence?
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
When I use
Code:
fastboot flash recovery recovery.img
I suppose that I can flash directly the TWRP, right?
And this command
Code:
fastboot flash userdata userdata.img
equals
-w​in
Code:
fastboot [B]-w[/B] update image-hammerhead-xxxxxx.zip
right?
no need to fastboot reboot-bootloader after every line, i use the following and never had an issue:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
metpage said:
no need to fastboot reboot-bootloader after every line, i use the following and never had an issue:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
Don't you flash cache.img?
And could you talk me about this?
alessio89g said:
And this command
Code:
fastboot flash userdata userdata.img
equals
-w​in
Code:
fastboot [B]-w[/B] update image-hammerhead-xxxxxx.zip
right?
Click to expand...
Click to collapse
alessio89g said:
So, is this the sequence?
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
When I use
Code:
fastboot flash recovery recovery.img
I suppose that I can flash directly the TWRP, right?
And this command
Code:
fastboot flash userdata userdata.img
equals
-w​in
Code:
fastboot [B]-w[/B] update image-hammerhead-xxxxxx.zip
right?
Click to expand...
Click to collapse
alessio89g said:
Don't you flash cache.img?
And could you talk me about this?
Click to expand...
Click to collapse
i don't flash cache because afterwards you need to go into recovery and format cache otherwise you will bootloop (in my experience).
metpage said:
i don't flash cache because afterwards you need to go into recovery and format cache otherwise you will bootloop (in my experience).
Click to expand...
Click to collapse
And about userdata.img? Do you know if it's like the option "-w" in the line
fastboot -w update image-hammerhead-xxxxxx.zip
on flash-all.bat?
yes if you flash userdata.img you lose your data on your phone because you are replace you data with a clean version. SO if you want to keep your data, DON'T flash userdata.img

How To Guide How to downgrade back to 11 from 12

This guide is for anyones like me that wants to go back to Android 11 from 12.
Prerequisites:
unlocked bootloader
Your phone's Android 11 firmware
Ability to get into fastboot and type commands one at a time hitting ENTER after each line
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
flash bluetooth BTFM.bin
flash dsp dspso.bin
flash logo logo.bin
flash boot boot img
flash vendor_boot vendor_boot.img
flash dtbo dtbo.img
flash super super.img_sparsechunk.0
(This flash took almost 15 seconds to finish. Continue flashing sparsechunk.1 thru sparsechunk.11 one at a time.
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
I had to flash both a & b slots to get this to stick. Disable updates to avoid problems.

Question Flashed into TWRP = Qualcomm Crashdump Mode

I accidentally flashed twrp-3.7.0_11-0-lemonadep.img onto my OP9 and is not met by Qualcomm Crashdump Mode constantly when trying to boot. wanted to boot it temporarily, but did this instead.
I tried temparirely booting after but it did not work sadly.
I read that I have to boot into Oxygen again, but I am pretty stuck on what's to do next, since I booting into fastbootd with no luck, which led me to not be able boot Oxygen.
Do any of you guys have any idea of what I can do to get out of this state and booted into LineageOS.
dimitrysulah6211 said:
I accidentally flashed twrp-3.7.0_11-0-lemonadep.img onto my OP9 and is not met by Qualcomm Crashdump Mode constantly when trying to boot. wanted to boot it temporarily, but did this instead.
I tried temparirely booting after but it did not work sadly.
I read that I have to boot into Oxygen again, but I am pretty stuck on what's to do next, since I booting into fastbootd with no luck, which led me to not be able boot Oxygen.
Do any of you guys have any idea of what I can do to get out of this state and booted into LineageOS.
Click to expand...
Click to collapse
reflash to stock and try again
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
dimitrysulah6211 said:
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
Click to expand...
Click to collapse
use these commands
fastboot reboot bootloader
after flash press space drag and drop the img file and wait for it to flash
fastboot flash
dimitrysulah6211 said:
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
Click to expand...
Click to collapse
Never mind
bloxycola said:
use these commands
fastboot reboot bootloader
after flash press space drag and drop the img file and wait for it to flash
fastboot flash
Click to expand...
Click to collapse
try this
download the fastboot folder and driver from here ---> https://highonandroid.com/fastboot-zip-android-usb-drivers/
extract the fastboot folder
drag and drop the .imgs onto the fastboot folder then where the directory is (if your on windows) press on it and type in cmd the command promt will apear now connect your phone and turn it on and type
fastboot reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot reboot bootloader
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.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 multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.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 product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot reboot
if fastboot reboot bootloader not allowing you to flash try fastboot reboot fastboot
bloxycola said:
try this
download the fastboot folder and driver from here ---> https://highonandroid.com/fastboot-zip-android-usb-drivers/
extract the fastboot folder
drag and drop the .imgs onto the fastboot folder then where the directory is (if your on windows) press on it and type in cmd the command promt will apear now connect your phone and turn it on and type
fastboot reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot reboot bootloader
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.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 multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.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 product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot reboot
if fastboot reboot bootloader not allowing you to flash try fastboot reboot fastboot
Click to expand...
Click to collapse
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
dimitrysulah6211 said:
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
Click to expand...
Click to collapse
Yes
dimitrysulah6211 said:
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
Click to expand...
Click to collapse
Your trying to flash LineageOS right?
bloxycola said:
Your trying to flash LineageOS right?
Click to expand...
Click to collapse
Boot intro TWRP flash LineageOS then flash TWRP and try to se eif it boots
I believe that the right procedure is to update all the way up to OOS 13 F.20 firmware, then flash the Lineage Rec and from there flash LOS

Categories

Resources