Could someone please help me with the proper commands to flash these 3 files in Fastboot mode with ADB
ADB FASTBOOT commands to flash
boot.img
recovery.img
recovery2.img
https://openkirin.net/user_guide/how-to-flash-extracted-partition-images/
MadGoogler78 said:
Could someone please help me with the proper commands to flash these 3 files in Fastboot mode with ADB
ADB FASTBOOT commands to flash
boot.img
recovery.img
recovery2.img
Click to expand...
Click to collapse
This must be nougat.
Let's say the images are in same folder you are running the cmd window from. If they are not then you need to adjust the command to include the full path to them.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
Now of you are getting error messages , like , partition length over, or , partition does not exist, then you must not have nougat rom on device.
In that case you will need different commands, and different files. Lol
Related
i have a error on ascend P6 its stuck on android logo and in recovery its shows the error i attached a pic. i tried the dload option for software but it doesnt work , please help . i got this phone like this condition only . i dont know history .
missime said:
i have a error on ascend P6 its stuck on android logo and in recovery its shows the error i attached a pic. i tried the dload option for software but it doesnt work , please help . i got this phone like this condition only . i dont know history .
Click to expand...
Click to collapse
Does it have an SDcard in it with a rom in /dload? It sounds like it may be looking for this. Get a card in it and do a force reset (volume up/down pressed and power button pressed .
stuartggray said:
Does it have an SDcard in it with a rom in /dload? It sounds like it may be looking for this. Get a card in it and do a force reset (volume up/down pressed and power button pressed .
Click to expand...
Click to collapse
yeah its loaded in . it just goes to recovery .
P6_firmware(P6-U06,Android_4.2,Emtion_UI,V100R001C00B107,Normal,05011RJP)
this is the zip i have extracted it dload/update.app
is there any other way to load it ?
any adb command to psh the update.app file atleast . coz in recovery its taking adb drivers .
missime said:
any adb command to psh the update.app file atleast . coz in recovery its taking adb drivers .
Click to expand...
Click to collapse
any solution for this error?
in fast boot mode, using adb to flash every *.img file to phone.
Code:
adb wait-for-device
adb.exe reboot bootloader
fastboot.exe flash fastboot fastboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash batt batt.img
fastboot.exe flash cache cache.img
fastboot.exe flash crc crc.img
fastboot.exe flash curver curver.img
fastboot.exe flash efi efi.img
fastboot.exe flash md5rsa md5rsa.img
fastboot.exe flash modemimage modemimage.img
fastboot.exe flash userdata userdata.img
fastboot.exe flash verlist verlist.img
fastboot.exe flash system system.img
fastboot.exe flash cust cust.img
fastboot reboot
vagraxy said:
in fast boot mode, using adb to flash every *.img file to phone.
Code:
adb wait-for-device
adb.exe reboot bootloader
fastboot.exe flash fastboot fastboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash batt batt.img
fastboot.exe flash cache cache.img
fastboot.exe flash crc crc.img
fastboot.exe flash curver curver.img
fastboot.exe flash efi efi.img
fastboot.exe flash md5rsa md5rsa.img
fastboot.exe flash modemimage modemimage.img
fastboot.exe flash userdata userdata.img
fastboot.exe flash verlist verlist.img
fastboot.exe flash system system.img
fastboot.exe flash cust cust.img
fastboot reboot
Click to expand...
Click to collapse
how did u flash the system img...it say its too big..any suggestion please
If you are NOT able to boot into 12S, and ONLY fastboot mode is available. This CM12S recovery file will help. Just unzip and run following command in fastboot mode.
fastboot -i 0x1ebf flash recovery recovery.img
Thanks for this, mate.
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---
My phone Redmi note 8 error The system has been destroyed
errors program miflashtool can not foud file flash_all.bat
krampusxxx said:
My phone Redmi note 8 error The system has been destroyed
errors program miflashtool can not foud file flash_all.bat
Click to expand...
Click to collapse
Did you extract your fastboot rom twice? you need to extract the fastboot rom[can be found here] twice to flash via mi flash.If that doesn't work follow this:
Assuming your bootloader is unlocked then boot device in fastboot mode and connect to PC. Make sure you have minimal ADB and fastboot installed in PC. Move vbmeta.img file from the fastboot file you have(it's inside the images folder) to the adb and fastboot folder. Then flash using this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
if that does not work then type:
Code:
fastboot flash vbmeta vbmeta.img
after flashing vbmeta flash recovery.
However if your bootloader is not unlocked you need to visit service center.
Does anyone have the full fastboot flashing steps from the Bootloader to everyfile in the image file.zip?
I'm not sure exactly what you're asking. To be rooted? To merely flash full stock firmware? If the latter, just extract the full firmware zip and the latest Platform Tools into the same folder. If you don't want to wipe your phone, edit the Flash-All.bat with Notepad (assuming you're running Windows) and remove the "-w ", and save the file. Then open a command prompt in that folder, type Flash-All.bat and press enter. That's it.
If you're asking what are the steps the Flash-All.bat takes to flash everything that's in the inner zip file that's unextracted, just open the Flash-All.bat with Notepad and take a look.
If you're wanting to be rooted, [GUIDE] Root Pixel 6 Pro with Magisk.
If none of my guesses are correct, please be more specific of what exactly you're asking.
Wouldn't it be just fastboot flash filename "file location" for each file?
spart0n said:
Wouldn't it be just fastboot flash filename "file location" for each file?
Click to expand...
Click to collapse
Every device is different, with Motorola we started with :
fastboot gat-var
and flashed each image seperately.
The "flash-all.bat" only does a "fastboot update <update.zip>" - so no individual flashing of image files.....
s3axel said:
The "flash-all.bat" only does a "fastboot update <update.zip>" - so no individual flashing of image files.....
Click to expand...
Click to collapse
Yea, but i cannot tell where the image.zip is getting hung up at if i run that.
AndroidAddict420 said:
Yea, but i cannot tell where the image.zip is getting hung up at if i run that.
Click to expand...
Click to collapse
You could open a command shell and run the flash-all.bat from there - then you at least see the output of the command.
Or you can enter the commands from the flash-all.bat manually in a commandline window (everything starting with "fastboot..." )....
s3axel said:
You could open a command shell and run the flash-all.bat from there - then you at least see the output of the command.
Or you can enter the commands from the flash-all.bat manually in a commandline window (everything starting with "fastboot..." )....
Click to expand...
Click to collapse
I am using LIX
AndroidAddict420 said:
I am using LIX
Click to expand...
Click to collapse
OK, I don't know LIX - is that some kind of Linux ?
I would still assume you can execute the dividual fastboot commands from the flash-all.bat (flash-all.sh) manually ?!
s3axel said:
OK, I don't know LIX - is that some kind of Linux ?
I would still assume you can execute the dividual fastboot commands from the flash-all.bat (flash-all.sh) manually ?!
Click to expand...
Click to collapse
LIX is short for Linux
I'm not sure if fastboot would work in a Linux terminal window as I've always used Windows... Best of luck finding a solution!
Oh, and by the way, you can use fastboot in CMD and flash individual partitions with it. An example command of flashing the bootloader file would be:
"fastboot flash bootloader bootloaderfilename.img"
You essentially just have to change the last word before the filename to flash different partitions (aside from when you're flashing the update image, as it's a little bit different then).
Also note that the bootloader.img file would have to be in the exact same location as your adb and fastboot files. But again, I'm not at all sure how it would work on Linux...
NippleSauce said:
I'm not sure if fastboot would work in a Linux terminal window as I've always used Windows... Best of luck finding a solution!
Oh, and by the way, you can use fastboot in CMD and flash individual partitions with it. An example command of flashing the bootloader file would be:
"fastboot flash bootloader bootloaderfilename.img"
You essentially just have to change the last word before the filename to flash different partitions (aside from when you're flashing the update image, as it's a little bit different then).
Also note that the bootloader.img file would have to be in the exact same location as your adb and fastboot files. But again, I'm not at all sure how it would work on Linux...
Click to expand...
Click to collapse
Why would anyone ever change their bootloader?
spart0n said:
Why would anyone ever change their bootloader?
Click to expand...
Click to collapse
To update it.
If you want to flash each image separately, you can follow these steps (for some images, sequence is important, so I suggest following the sequence below to avoid issues)
Code:
################################################
### Files from the root of the factory image zip
################################################
# bootloader (replace <version> with the bootloader file version)
fastboot flash bootloader bootloader-raven-slider-<version>.img
# reboot to bootloader
fastboot reboot bootloader
# radio (replace <version> with the radio file version)
fastboot flash radio radio-raven-<version>.img
# reboot to bootloader
fastboot reboot bootloader
#####################################################
### Files from the image zip in the factory image zip
#####################################################
# boot
fastboot flash boot boot.img
# dtbo
fastboot flash dtbo dtbo.img
# vbmeta
fastboot flash vbmeta vbmeta.img
# vbmeta_system
fastboot flash vbmeta_system vbmeta_system.img
# vbmeta_vendor
fastboot flash vbmeta_vendor vbmeta_vendor.img
# vendor_boot
fastboot flash vendor_boot vendor_boot.img
# reboot to fastboot
fastboot reboot fastboot
# super
fastboot flash super super_empty.img
# product
fastboot flash product product.img
# system
fastboot flash system system.img
# system_ext
fastboot flash system_ext system_ext.img
# system_other (replace <other> with the inactive slot)
fastboot flash system_<other> system_other.img
# vendor
fastboot flash vendor vendor.img
# vendor_dlkm
fastboot flash vendor_dlkm vendor_dlkm.img
# reboot
fastboot reboot