[COLLECTION][FIRMWARE][RUU][BACKUPS] T-Mobile US - Release Builds (Update 5/16)

cdfosburg · May 24, 2014

Behold_this said:
Normal

So the software version should stay at 1.12.531.19?

Please forgive me. I had coffee now and learned how to read every post. I see the differences and where I was going wrong.

Behold_this · May 24, 2014

cdfosburg said:
So the software version should stay at 1.12.531.19?

Please forgive me. I had coffee now and learned how to read every post. I see the differences and where I was going wrong.

No problem. Glad you found what you needed. Enjoy your first thank you.

donciclon · May 26, 2014

Are there any disadvantages or consequences to ROM-firmware version mismatch? Or is it just a stability concern?

pman24101 · May 26, 2014

Will the RUU return my converted htc from Gpe to Sense 6?

ggeralds · May 27, 2014

Just an FYI - and OP, this would be great to put in the "sdcard install" area.

Once the update has flashed successfully, remove the file (0P6BIMG.zip) from the root of the SD card or you will never be able to boot just into bootloader mode (it will always try to update), UNLESS you remove the SD card.

Learned this the hard way in panic mode......Trust me on this one.

---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------

BTW - I'm one of the lucky ones on T-Mo to get s-off...

Thank you guys soooooo much for making the firmware update process work so well. Worked like a charm the first time using one of the customs.

twoeleven99 · May 27, 2014

i updated to the latest tmo firmware ...i was on a custom rom arhd and got the update successfully and i am still rooted on arhd. for some reason i thought i would have to reroot my device after applying the update after having s- off...just want to make sure i did it right

Behold_this · May 27, 2014

ggeralds said:
Just an FYI - and OP, this would be great to put in the "sdcard install" area.

Once the update has flashed successfully, remove the file (0P6BIMG.zip) from the root of the SD card or you will never be able to boot just into bootloader mode (it will always try to update), UNLESS you remove the SD card.

Haha, yeah it does auto initiate flash prompt in bootloader if you don't rename the file, erase it, or remove your sdcard. You don't have to accept the flash though. I'll add that note to OP.

Behold_this · May 27, 2014

twoeleven99 said:
i updated to the latest tmo firmware ...i was on a custom rom arhd and got the update successfully and i am still rooted on arhd. for some reason i thought i would have to reroot my device after applying the update after having s- off...just want to make sure i did it right

yes you did it right this firmware does not touch root whatsoever. Root is superuser permission within the system. System.img is not included in or modified by firmware. System.img is considered software. Firmware is device-specific and controlling data and code.

twoeleven99 · May 27, 2014

Behold_this said:
yes you did it right this firmware does not touch root whatsoever. Root is superuser permission within the system. System.img is not included in or modified by firmware. That is considered software. Firmware is device-specific and controlling data and code.

Thank you for the info

ARHD M8

uoY_redruM · May 27, 2014

What exactly does this do? Update everything that you would normally only be able to update via the RUU file?

Say for instance the new T-Mobile update. Updated via the flashable zip someone provided. Already have root and custom recovery. That doesn't provide updated radio, hboot, etc (if I understand correctly) and that's what this does?

Sent from my HTC One_M8 using XDA Free mobile app

Sent from my HTC One_M8 using XDA Free mobile app

donciclon · May 27, 2014

Does the ext_sdcard method work for any firmware package, or is it specific to this one?

EDIT: Decided to be brave and test it myself. Flashed 1.54.401.10 successfully via the MicroSD card. I also removed the recovery.img from the firmware zip so as not to lose TWRP. Did need to re-install elemental kernel though because I forgot to also remove the boot.img, but no big deal.

uoY_redruM · May 27, 2014

uoY_redruM said:
What exactly does this do? Update everything that you would normally only be able to update via the RUU file?

Say for instance the new T-Mobile update. Updated via the flashable zip someone provided. Already have root and custom recovery. That doesn't provide updated radio, hboot, etc (if I understand correctly) and that's what this does?

Sent from my HTC One_M8 using XDA Free mobile app

Sent from my HTC One_M8 using XDA Free mobile app

Anyone?

Sent from my HTC One_M8 using XDA Free mobile app

Behold_this · May 27, 2014

donciclon said:
Does the ext_sdcard method work for any firmware package, or is it specific to this one?

EDIT: Decided to be brave and test it myself. Flashed 1.54.401.10 successfully via the MicroSD card. I also removed the recovery.img from the firmware zip so as not to lose TWRP. Did need to re-install elemental kernel though because I forgot to also remove the boot.img, but no big deal.

Sorry, I didn't see your post before. Yes that flashing method works for any HTC One M8 firmware as you found out. [emoji106]

Behold_this · May 27, 2014

uoY_redruM said:
What exactly does this do? Update everything that you would normally only be able to update via the RUU file?

Say for instance the new T-Mobile update. Updated via the flashable zip someone provided. Already have root and custom recovery. That doesn't provide updated radio, hboot, etc (if I understand correctly) and that's what this does?

The answers to your questions can actually be found just doing a few searches within the thread, but I will answer it one more time. Firmware does not contain system image at all and does not touch system at all. Your Android system is considered software. Software is never included in firmware packages.

Firmware is device controlling and device specific code and data. It is what allows your hardware to run. It is generally speaking unrelated to software, with the exception of boot.img, which does specifically correspond to the software you are running.

Any of the custom firmware packages in this thread can be modified to your liking. If you want the stock recovery then keep the stock recovery. If you don't, then remove the recovery image from the package.

If all you're looking to do is update the firmware that was recently updated via the OTA simply flash the small custom firmware package. It contains every firmware image that was updated minus the recovery and boot.img.

You need to understand my advice to users to stay away from this thread until you have a solid understanding of what firmware is, is for users own safety. You can very easily hard brick your device (rendering it's completely dead and about as useful as a paper weight) incorrectly modifying or flashing firmware. You really cannot hard brick your device flashing an incorrect custom system (eg a custom ROM). That is a misconception an important point to make.

uoY_redruM · May 27, 2014

I know the difference between the two, I use to make custom roms and I created the very first custom rom for the SGS3. I'll apologize now and admit I was being lazy and didn't read though the thread.

Basically just take the stock one and remove the recovery and boot to updated everything else related to the upgrade that can't be accomplished without otherwise flashing the RUU .

Sent from my HTC One_M8 using XDA Free mobile app

donciclon · May 27, 2014

Behold_this said:
You really cannot hard brick your device flashing an incorrect custom system (eg a custom ROM). That is a misconception an important point to make.

You know, I always had that nagging question in the back of my mind anytime I read someone warn of hard bricking from flashing a ROM. I was pretty damn sure that a non-malicious ROM cannot brick your device. By non-malicious, I mean one that does not (intentionally) attempt to write to the partitions where HBOOT, Radio and related stuff live. I'm in these forums all the time and constantly see a brick warning from even some real veteran cooks (maybe just to cover their a$$). Thanks, I knew i wasn't crazy.

Behold_this · May 27, 2014

uoY_redruM said:
I know the difference between the two, I use to make custom roms and I created the very first custom rom for the SGS3. I'll apologize now and admit I was being lazy and didn't read though the thread.

Basically just take the stock one and remove the recovery and boot to updated everything else related to the upgrade that can't be accomplished without otherwise flashing the RUU .

Sent from my HTC One_M8 using XDA Free mobile app

You can do that, but you don't need to do any modifying if you don't want to. Just use the custom firmware package in the OP (the first custom package not the expanded one). It has all the updated firmware with only boot.img and recovery.img removed.

Behold_this · May 27, 2014

donciclon said:
You know, I always had that nagging question in the back of my mind anytime I read someone warn of hard bricking from flashing a ROM. I was pretty damn sure that a non-malicious ROM cannot brick your device. By non-malicious, I mean one that does not (intentionally) attempt to write to the partitions where HBOOT, Radio and related stuff live. I'm in these forums all the time and constantly see a brick warning from even some real veteran cooks (maybe just to cover their a$$). Thanks, I knew i wasn't crazy.

Yup that's right, you hit the nail right on the head with the non-malicious part. Even then there are some safety checks in place as most partitions cannot be written to by recovery, unless s-off. This does not mean a ROM can't leave you with a non-booting phone. That can easily happen but a non-booting phone does not equal a hard brick. Some people even come to call that a soft brick but whatever you choose to call them, they are recoverable.

Behold_this · May 27, 2014

I'm going to close the thread guys. please see @Garmig's thread for all your needs

http://xdaforums.com/showpost.php?p=51836232&postcount=1

[COLLECTION][FIRMWARE][RUU][BACKUPS] T-Mobile US - Release Builds (Update 5/16)

Senior Member

Senior Member

Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts