Stock boot.img - T-Mobile HTC One (M8)

Could some one share the stock boot.img
for the latest tmo ota?
Can't seem to find it on here. Ruu's, nandroids and radios. But no boot. Img

Related

Extracting Boot.img

anyone know how to extract a boot.img from a nandroid, i rooted my stock cspire play and unlocked the bootloader, im still on stock but i want to have the cspire boot.img just incase i may need it, i made a nandroid of my stock rom
You can try this
third post

Galaxy nexus 4.2.2

Hello, I'm on 4.2.1, but the phone keeps offering 4.2.2, it downloads it, but I can't install it since i'm on custom kernel and phone is rooted.
My question is that if I install the stock kernel, will I be able to install the update OTA?
If yes, then where can I get a 4.2.1 Maguro stock kernel?
Use this app to unlock your bootloader if you haven done so, then extract boot.img from the stock google image(which can be obtained here for older versions). Then flash the boot.img in fastboot.
Code:
fastboot flash boot boot.img
Anyway, I don't think you will download the whole stock image just to get a 4mb kernel, luckily i have the stock image lying around, so download it here.

Does anyone have the flashable 1.10.605.10 update?

Trying to update firmware to 1.10.605.10 after S-OFF.
Changing recovery to stock, then taking OTA errors out for me using the stock ROM.
Thanks!
Yeah ...its been posted here
http://forum.xda-developers.com/showthread.php?t=2465774
Sent from my Nexus 7 using Tapatalk 4
I tried flashing the modified zip, as well as the original, with twrp recovery and both received an error.
The modified zip gave this error -
"Error flashing zip '/sdcard/modified_OTAPkg.zip' Updating partition details..."
The rom I am using is the VZW Stock Rooted deodex, should I be using something different?
Wozzie said:
The rom I am using is the VZW Stock Rooted deodex, should I be using something different?
Click to expand...
Click to collapse
The update doesn't work with a deodexed ROM. It also likely doesn't work if you've removed some of Verizon's bloat software on the stock odexed ROM.
@CNexus wants to make an updated flashable zip for rooted users, as well as a fully flashable ROM (if I am reading that right), but needs the right framework files.
Both the modified zips, and the modified recovery won't work for me for some reason.
The modified zip just errors out in TWRP.
If I try the stock recovery method -
Fastboot signed stock recovery
Take the OTA w stock ROM
Errors out
or
Flash Andy's odex stock ROM
Fastboot signed stock recovery
Take OTA
Updates firmware to .10
Fastboot TWRP, flash SU
Restore stock ROM from TWRP backup
Firmware is back to .08 now
Does restoring the stock ROM in TWRP downgrades my firmware to .08 again?
Confused :/
gzbrambila said:
Both the modified zips, and the modified recovery won't work for me for some reason.
The modified zip just errors out in TWRP.
If I try the stock recovery method -
Fastboot signed stock recovery
Take the OTA w stock ROM
Errors out
or
Flash Andy's odex stock ROM
Fastboot signed stock recovery
Take OTA
Updates firmware to .10
Fastboot TWRP, flash SU
Restore stock ROM from TWRP backup
Firmware is back to .08 now
Does restoring the stock ROM in TWRP downgrades my firmware to .08 again?
Confused :/
Click to expand...
Click to collapse
Restoring a backup generally completely wipes out the current software in place. If you flashed the odexed ROM, took the OTA with the stock recovery, then restored a backup of .08, then you lost the .10 update because it was on that installed ROM. You overwrote it.
If you want the update, which was so small and negligible that it's not really even important enough to take, then you have to flash the odexed ROM, take the update with the stock recovery, and stay on that ROM. That's the only way that works presently. No one has released a working odexed or deodexed ROM with the update included, nor is there a working flashable zip that doesn't require you to be on and stay on the stock odexed ROM.
IceDragon59 said:
Restoring a backup generally completely wipes out the current software in place. If you flashed the odexed ROM, took the OTA with the stock recovery, then restored a backup of .08, then you lost the .10 update because it was on that installed ROM. You overwrote it.
If you want the update, which was so small and negligible that it's not really even important enough to take, then you have to flash the odexed ROM, take the update with the stock recovery, and stay on that ROM. That's the only way that works presently. No one has released a working odexed or deodexed ROM with the update included, nor is there a working flashable zip that doesn't require you to be on and stay on the stock odexed ROM.
Click to expand...
Click to collapse
Thank you. That makes perfect sense now.
gzbrambila said:
Thank you. That makes perfect sense now.
Click to expand...
Click to collapse
Actually if you took the update while on stock recovery...the actual firmware portion did update and will stay updated regardless of what rom software version you are running. The update was both a software (.10) AND firmware update.
Sent from my Nexus 7 using Tapatalk 4
gzbrambila said:
Trying to update firmware to 1.10.605.10 after S-OFF.
Changing recovery to stock, then taking OTA errors out for me using the stock ROM.
Thanks!
Click to expand...
Click to collapse
As stated earlier the OTA doesn't play well with deodex ROMs. I figured out how to do this with no issue. Be warned as this will wipe your device. Download the decrypted RUU and boot into RUU mode and follow Zarboz's instuctions for installation. That will get you back to stock. What I did was:
relock bootloader for RUU flash
flash the RUU
OTA (don't set up your phone bc bootloader unlock will wipe it again )
unlocked bootloader again
installed custom recovery via fastboot
made unrooted stock nandroid
flash SuperSU
Also, once you have custom recovery installed you can pull the recovery_signed.img from the decrypted RUU zip and copy/paste it into fastboot directory and flash stock recovery at will for updates for your stock ROM. Tested that method and it works. I did it this way bc I was having the same issues with failed updates so I said screw it and went full on RUU

How to flash 10c bootloader and modem

I downloaded the stock untouched 10c firmware zip, and the 10c partitions zip and extracted them. I got bin files and I renamed the modem from bin to IMG and bootloader I'm not quite sure which file is it. IIRC its the aboot.bin which I'd rename to IMG.
In twtp I tried flashing just the modem and its asking which partition boot or recovery to flash it. I chose neither cause modem obviously doesn't belong there.
Can I use flashify for the modem IMG and bootloader one? Once I know which one is bootloader?
Or what's the best way? I'm downgrading both since I've heard res-remix 5.4.1 (android 5.1) will let data work with them
Why are you trying to downgrade? 10m had best battery life, 10r was most stable. 20b is both

Flashing updated pre-rooted firmware

I know there are threads with instructions about how to do this all over, but they all seem to vary slightly in their instructions and most of the update posts seem to refer to unrooting and flashing stock OTA, then re-rooting, but would this work as it seems like it would be faster and easier. I have soft-bricked my phone more than once and it has been months since I have done this as you can tell by how old my firmware is, so I just want to confirm this will work.
Right now my Zenphone 551ML is on Z00A_WW_2.19.40.22. I would like to update it to Z00A_WW_2.20.40.90. Originally I used fastboot to flash boot.img, droidboot.img, recovery.img, and system.img from (Z00A_WW_2.19.40.22_system_w_root.zip) downloaded from mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw.
Can I just perform the same process to update to new firmware by using "fastboot flash...." command to flash all four .img files to my phone, which I downloaded from mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw but using the pre-rooted boot.img, droidboot.img, recovery.img, and system.img files from the Z00A_WW_2.20.40.90 folder?
Thanks!

Categories

Resources