What are the commands for flashing a rom in fastboot?
Ive tried
Code:
fastboot flash ----.zip
?
Am doing this cause JOKERDROID4.2BUZZ.zip wont flash in clockwork mod 3.2.0.0 or 4.0.0.2. It flashes in 2.5.1.7 but boot loops. I am coming from cm7 what do you think?
You can only flash a particular partition with Fastboot, like /system /data, Recovery, boot etc. AFAIK, You cant flash a Zip ROM as is the case with CWM.
You can check the list of Fastboot Commands here:
http://android-dls.com/wiki/index.php?title=Fastboot
Also, you got 2.5.1.7? Where? AFAIK Wildfire only has 2.5.0.7. Anyway, you can use Fastboot to replace your CWM 3.x or 4.x with 2.5.0.7, then try flashing Jokerdroid. Also, make sure you are performing a wipe (Factory Reset / Wipe data in Clockworkmod)
Where can i get 2.5.0.7?
Cant remember where i got 2.5.1.7 the file name was 2.5.0.7 but cwm said 2.5.1.7?
It's there under Custom Recoveries:
http://forum.xda-developers.com/showthread.php?t=1029318
jokerdroid just bootloops!?
i have wiped and wiped cache and delvik!
Try Redownloading the ROM. Or, if you search the thread, there is one version which is clocked at 648MHz. Try that. Probably the high CPU clocks are not suiting your device.
EDIT: Scratch that. Its clocked at 710, so shouldn't cause an issue.
Well after boot looping 5 or so times it rebooted cwm then rebooted system and bootlooped once but the powered up? Wierd!
if you want to flash a .zip package:
fastboot update filename.zip
if you want to flash an img. file:
depending whether you want to flash a new recovery:
fastboot flash recovery filename.img
or a new ROM:
fastboot flash system filename.img
I do however strongly recommend erasing you current recovery before flashing a new one:
fastboot erase recovery
and do a full wipe (this will erase your data, recovery and system partitions)
fastboot erase system -w
Hi,
I updated my kernel for install CM10.1.
now I want to flash HDR 18.2 And I know it works best with the stock kernel.
how do I install the stock kernel?
Thanks!
Flash the boot.img that you have in zip of rom or from OP of thread of your rom
you have to make an "erase cache" (with command: "fastboot erase cache") before and after flash the new boot.img
Guich said:
Flash the boot.img that you have in zip of rom or from OP of thread of your rom
you have to make an "erase cache" (with command: "fastboot erase cache") before and after flash the new boot.img
Click to expand...
Click to collapse
oh, so its that easy? i thought i need to do something complicated for changing the kernel.
but u say to do it just like i flash a normal rom?
thanks! :silly:
For change the kernel, you have to flash the boot.img from fastboot and making an erase cache.
After, you have to flash the modules (if you are flashing a custom kernel).
If you need change the rom, you have to do:
- A backup of your currently rom
- Reboot in fastboot and making a "fastboot erase cache"
- Flash the boot.img (fastboot flash boot boot.img)
- Another erase cache
- Reboot in recovery
- Full wipe
- Flash new rom
- Reboot & Enjoy
Hi all,
I'm on RENOVATE ROM at the moment. Is it possible to switch to aokp or aosp roms with just flashing boot.img using fastboot and installing the ROM from recovery??
Yes!
1. Flash the boot.img from ROM.zip via fastboot and then fastboot erase cache
2. Go to recovery and flash this script : http://d-h.st/kG0 (it wipes data/cache/dalvic/system)
3. Flash the rom.zip and gapps.
4. Reboot!
After moving my Mi6 from EU ROM to Global Stable 8.2.2.0, I realised that MIUI has now programmed either the boot.img or system.img to overwrite recovery partition on every "normal"/system boot.
So much for unlocking the bootloader...
Although the source system.img has a recovery-from-boot.p file, but it appears to be different from the stock recovery.img file. Attempting to replace it with the TWRP image or removing it entirely (and flashing the rebuilt system.img) results in boot failure (see below for more information).
Does anyone know:
where the "protected" recovery image may be found? and/or
how to repack/rebuild a system.img which will not cause a boot hang?
Note that I have rebuilt it "correctly" (as "correct" as I know) using the properly extracted file_contexts (as extracted from the file_contexts.bin) from the initrd.img from inside the boot.img using the command:
Code:
make_ext4fs -s -T -1 -S file_contents -L system -l <size of partition> -a system system.img <mount point>
I have tried both a blind fastboot flash system system.img, and also a standard "clean" flash using the MiFlash tool (after ensuring that the correct MD5, CRC and sparse CRC strings are edited in the various files, of course).
Thanks!
fastboot flash recovery TWRP.img
That's the solution.
And if you flash a MIUI rom with TWRP simply flash twrp.img without Reboot under TWRP, after rom.zip flash. That's all
reb00tz said:
After moving my Mi6 from EU ROM to Global Stable 8.2.2.0, I realised that MIUI has now programmed either the boot.img or system.img to overwrite recovery partition on every "normal"/system boot.
Click to expand...
Click to collapse
dennis46419 said:
fastboot flash recovery TWRP.img
That's the solution.
And if you flash a MIUI rom with TWRP simply flash twrp.img without Reboot under TWRP, after rom.zip flash. That's all
Click to expand...
Click to collapse
Hi @dennis46419,
Thanks for replying. I have always done that upon forced reboot by the MiFlash tool (i.e. the moment it powers off for a reboot, I put it right back into fastboot mode to flash TWRP again, then directly boot with the TWRP.img).
As mentioned, I believe the new global stable ROM actually overwrites recovery on every boot.
Have you experienced this (i.e. when using the global stable ROM)?
OK, seems I missed the solution as already provided by @TheStrix:
https://forum.xda-developers.com/showpost.php?p=72620133&postcount=2
But the instruction (which I missed because I downloaded directly from the TWRP site) was already here: https://forum.xda-developers.com/showpost.php?p=72620133&postcount=2
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Flash stock
finish setup
before doing anything else
MichaelDrakeMS said:
Hey guys! Need some help.
I've been trying to flash a Android Pie ROM on my device and I have no success.
The problem is, after flashing the rom and TWRP Zip the device reboots twice then boots back into TWRP.
Then all the files on the device has random letters and numbers (i.e. ckjrdh574o0hmdu749y7nv)
Why can't I flash a Android Pie rom successfully?
I am on the latest Android Pie update. (Flashed on both slots)
Here is my steps:
Flash stock rom on both slots
Boot up in stock rom. (no set up, no password, no pin, nothing totally skipped setup)
Place files on device (Rom and twrp.zip)
Reboot into Bootloader
Boot into latest TWRP using fastboot
Once in Twrp, slide slider to allow modification to system parition
Factory reset/wipe data (and all that)
Flash rom (I tried Carbon Rom 7 and lineage os 16)
Flashed twrp zip
reboot
After the system reboots twice I am back in twrp and all the files and folder have numbers and letters as files names.
Any idea as to why this keeps happening?
How can I fix this?
Click to expand...
Click to collapse
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
parakleet said:
Flash stock
finish setup
before doing anything else
Click to expand...
Click to collapse
Yup I did. I just didn't sign in my account or do the security pin/pixel imprint. I skipped everything untill I was at the home/launcher.
Az Biker said:
Not sure if Carbon / Lineage has special install instructions or not, but you can follow the initial 9x setup in the link in my sig, then follow cust Rom installation process.
Click to expand...
Click to collapse
Nothing to special from the norm. I didn't everything the forums told me to do.
Okay definitely, I'll check that out and try those steps.
Also do you think I have a phone that twrp can't decrypt? I remember a while back doing one of the twrp updates that some phones won't decrypt because it used the older encryption method or something like that and TWRP was only able to decrypt then phones using the new method or something like that.
Oh and another question, do you guys think I should root the stock image with magisk then boot into twrp using fastboot and install the room then the twrp.zip?
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
Now that's all the steps j took to flash the roms.
I do not install twrp app I skip that.
My first methond to flash stock on both slots is set slot to a then flash stock using the flash all bat file in from the stock images (google directions to flashing images)
Then it would reboot. Then I would set to slot b and flash the stock images the same way using the bat file.
Then I found out that wasn't really the best way to do it so I used deuces (I believe that was the users name) bat file to flash the stock images on both slots the correct way and that's what I've been doing since.
But your steps have a different step then what I do. It seems it does the same as deuces bat file however once it's done I just boot straight into stock rom. I dont boot into stock recovery and factory wipe. But I will definitely try that as well.
Finally fixed it!
I flash both slots and followed everyone's directions.
The problem was I wasn't wiping all the things I needed too.
I read in another roms steps to not only do the factory reset thin in TWRP, but to also manually wipe system, data, dalvik/art cache. Then flashed the room and TWRP.zip.
I did this and BOOM, I booted up into the room! Thanks again for everyone's help!
amartolos said:
My question would be do you have other details you might have overlooked? For example, at the end of flashing, TWRP would usually ask whether you want to install their app. Did you install it or did you skip it?
Also, what was your exact procedure in flashing stock rom to both slots? I have also messed around with custom roms and reverted back to stock using the following:
Return to Stock:
Source of this knowledge is Method 2 of this video.
#flashing bootloader to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash bootloader_a bootloader[...].img
fastboot reboot-bootloader
fastboot flash bootloader_b bootloader[...].img
#flashing radio to slot A and slot B
Code:
fastboot reboot-bootloader
fastboot flash radio_a radio[...].img
fastboot reboot-bootloader
fastboot flash radio_b radio[...].img
#set active slot to B, flash system image
Code:
fastboot --set-active=b
fastboot reboot-bootloader
fastboot --skip-reboot --skip-secondary update image[...].zip
#set active slot to A, flash system image [different command!!!]
Code:
fastboot --set-active=a
fastboot reboot-bootloader
fastboot --skip-reboot update image[...].zip
Now straight from the bootloader, boot into recovery.
Wipe data/factory reset.
Let it reboot back into android.
Then, I followed the install instructions in the twrp thread to get custom recovery back onto my device. (If you want rooted stock android, flash it from twrp and then install the latest magisk manager apk.)
Now just find another custom rom and follow the install directions from that thread.
Click to expand...
Click to collapse
I stumbled across this post after having several issues trying to get my Pixel 2 XL flashed with a custom ROM (constantly resulting in boot-loops), and the steps worked perfectly.
I've ended up running these steps several times today, but I like keeping all of my stock images in sub-folders by release date. I'm not the greatest Powershell guru, but I've written a script that will search sub-directories in a folder for dates, and select the latest date and automatically flash the radio, bootloader, and image from that directory using your steps.
Code:
clear;
# Execution Policy must be adjusted in order to obtain the current executing directory of the script. This is a one-time command that must be run separately.
# Set-ExecutionPolicy RemoteSigned
# To reverse the command set the execution policy to restricted:
# Set-ExecutionPolicy Restricted
# The root directory which contains date sub-folders in the format yyyy-MM-dd representing an extracted OTA zip.
$startingDirectory = split-path -parent $MyInvocation.MyCommand.Definition;
# Alternatively, hard code a starting directory.
# [System.String]$startingDirectory = 'D:\Flashing\Roms\Taimen\Stock\';
[System.String]$targetFolder = (Get-ChildItem $startingDirectory | Select-Object -Property @{Name='Date';Expression = { Get-Date $_.Name -Format 'yyyy-MM-dd' }}, @{Name='FullName';Expression= {$_.FullName}} | Sort Date -Descending | Select -First 1).FullName;
if (-not $targetFolder) {
throw 'No folders are located in directory ''' + $startingDirectory + ''' with the date format yyyy-MM-dd.';
}
[System.String]$bootloader = Get-ChildItem $targetFolder -Name 'bootloader-*.img';
[System.String]$radio = Get-ChildItem $targetFolder -Name 'radio-*.img';
[System.String]$image = Get-ChildItem $targetFolder -Name 'image-*.zip';
# Validate all files have been successfully located.
[System.Collections.Generic.List[System.String]]$messages = [System.Collections.Generic.List[System.String]]::new();
if (-not $bootloader) {
$messages.Add('The bootloader file was not located.');
}
if (-not $radio) {
$messages.Add('The radio file was not located.');
}
if (-not $image) {
$messages.Add('The image file was not located.');
}
if ($messages.Length -gt 0) {
throw 'Unable to locate files in path ''' + $targetFolder + ''':' + [Environment]::NewLine + [System.String]::Join([Environment]::NewLine, $messages);
}
$bootloader = [System.IO.Path]::Combine($targetFolder, $bootloader);
$bootloader;
$radio = [System.IO.Path]::Combine($targetFolder, $radio);
$radio;
$image = [System.IO.Path]::Combine($targetFolder, $image);
$image;
#adb reboot bootloader;
function Reboot-Bootloader {
fastboot reboot-bootloader;
sleep 5;
}
#flashing bootloader to slot A and slot B
'Flashing bootloader to slot A.'
Reboot-Bootloader;
fastboot flash bootloader_a $bootloader;
'Flashing bootloader to slot B.'
Reboot-Bootloader;
fastboot flash bootloader_b $bootloader;
#flashing radio to slot A and slot B
'Flashing radio to slot A.'
Reboot-Bootloader;
fastboot flash radio_a $radio;
'Flashing radio to slot B.'
Reboot-Bootloader;
fastboot flash radio_b $radio;
#set active slot to B, flash system image
'Flashing system image to slot B.'
fastboot --set-active=b;
Reboot-Bootloader;
fastboot --skip-reboot --skip-secondary update $image;
#set active slot to A, flash system image [different command!!!]
'Flashing system image to slot A.'
fastboot --set-active=a;
Reboot-Bootloader;
fastboot --skip-reboot update $image;