• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Flashing Boot.img???

flboy91

Android Enthusiast
what command prompt do i use to flash a boot image??? because every time i try to flash one... the rom won't boot and at the "quietly brilliant" screen the "this is for developement purposes" prompt pops up... so what am i doing wrong????
 
what command prompt do i use to flash a boot image??? because every time i try to flash one... the rom won't boot and at the "quietly brilliant" screen the "this is for developement purposes" prompt pops up... so what am i doing wrong????

From cmd prompt in windows type "fastboot flash boot boot.img . But you have to be in hboot on phone and ofcoarse plunged in.
Also, the boot.img has to be in the same folder as your "fastboot (sdk)
 
From cmd prompt in windows type "fastboot flash boot boot.img . But you have to be in hboot on phone and ofcoarse plunged in.
Also, the boot.img has to be in the same folder as your "fastboot (sdk)

O OK... do I have to click FASTBOOT???
 
O OK... do I have to click FASTBOOT???

Yes, when you enter hboot select fastboot then connect phone to pc(if you aren't already) then go to where your fastboot and boot.IMG is using command prompt,then type fastboot flash boot boot.img. that should do it
 
Yes, when you enter hboot select fastboot then connect phone to pc(if you aren't already) then go to where your fastboot and boot.IMG is using command prompt,then type fastboot flash boot boot.img. that should do it

O OK thanx bro that confirms I was doing it correct... . But every time I do that my rom won't boot it only boots when I don't flash the boot.img... I'm primo c
 
When you type fastboot flash boot boot.img and hit enter do you see "writing boot...(or something like that) under where you typed the above command?
 
And at the "quietly brilliant screen" the red lettered warning pops up at the bottom as if I'm going into recovery and the rom won't boot...
 
I assume your giving it enough time to fully boot. As far as the redletter screen that happens to me too, however, my phone does boot into the rom. If the rom won't boot I would start over from the beginning. Flash rom,gapps,
Oh, are you using the boot img that jmz posted. I don't think your suppose to use the one in the rom.

edit What rom are you trying to flash?
 
I assume your giving it enough time to fully boot. As far as the redletter screen that happens to me too, however, my phone does boot into the rom. If the rom won't boot I would start over from the beginning. Flash rom,gapps,
Oh, are you using the boot img that jmz posted. I don't think your suppose to use the one in the rom.

edit What rom are you trying to flash?

Miui.. but no I used the one from the cm9 thread that is posted separate
 
I'm going to try again n give it sometime to boot... how long does it take you to boot after the flash???

Mine took about 3 to 5 minutes. If that doesn't work I would try to post this problem in the miui thread ,maybe it will get jmz's attention. I'm at the end of my knowledge. Sorry I could not have been more help.:confused:
 
Mine took about 3 to 5 minutes. If that doesn't work I would try to post this problem in the miui thread ,maybe it will get jmz's attention. I'm at the end of my knowledge. Sorry I could not have been more help.:confused:

Its cool bro thanx for the input... cause you didn't HAVE to help.. than bro
 
I am having a ton of issues flashing the boot.img for the CM9 rom. For whatever reason I cannot figure it out.

I used that root tool to root my phone. My question is, can I rename the boot.img to recovery.img and put it in the recovery folder of the tool kit and flash it that way?
 
Jacob, I've merged your post into a thread on the same topic with the same title.

The only legitimate way to flash the boot image manually is:
1. Start the phone in bootloader
2. Connect the USB cable and select FASTBOOT on the phone (changes to FASTBOOT USB)
3. Open a command prompt and navigate to the folder where you installed ADB and downloaded the boot.img.
4. Open a command prompt in Windows (Start > Run > CMD) and type the command:
Code:
fastboot flash boot boot.img
If that doesn't work, either you have a problem with ADB/fasboot or it's the wrong boot.img.
 
Ok thank you! If people are still having problems here what I realized I was doing wrong.
when you click on run, "cmd", take note of what populates first on the command. Then type that into an empty internet explorer and then make sure you take the boot.img and the fastboot files and put them directly on the IE page that opens up.
 
Jacob, I've merged your post into a thread on the same topic with the same title.

The only legitimate way to flash the boot image manually is:
1. Start the phone in bootloader
2. Connect the USB cable and select FASTBOOT on the phone (changes to FASTBOOT USB)
3. Open a command prompt and navigate to the folder where you installed ADB and downloaded the boot.img.
4. Open a command prompt in Windows (Start > Run > CMD) and type the command:
Code:
fastboot flash boot boot.img
If that doesn't work, either you have a problem with ADB/fasboot or it's the wrong boot.img.

I did all of this and got <waiting for device>
And suggestions on what to do?
 
Try using the Jellyboot5 Boot.img. I couldn't get out of my bootloop until I used that image. I've used that same img for multiple roms too.

What version of the radio does your phone have? I've found that the radio in the OTA upgrade (version 1.00.00.0928) caused every custom kernel I tried to flash to boot loop. Is that still the case, or does Jellyboot5 work with the updated radio?

The original "stock" version (and in the RUU) of the radio is 1.00.00.0521_2, and that one worked with pretty much every custom rom/kernel I threw at it...
 
Back
Top Bottom