Stupid question: Can the firmware be updated when running a custom ROM? - HTC 10 Questions & Answers

I've been reading on one of the other threads here that if you take an OTA while running stock + twrp, the firmware won't update, but you can then update it using fastboot.
Is it possible to update the firmware (not system) on a device using fastboot if it's running a custom ROM, or is it still required to restore to stock prior to taking the update?
Thank you.

Yes.
If you flash a firmware pulled straight from an OTA it will replace twrp with the stock recovery. Also flashing firmware may brake cell service on custom roms. If its a custom firmware zip that has boot, recovery, rcdata etc removed than you should be okay.
For example I'm using MaximusHD rom which is based on .401 (WWE/Europe) firmware. If i flash the US T-Mobile firmware I will loose cell service since the actual firmware files within /system are not made to work with that particular radio/firmware. I'll then have to flash the firmware/radio that was released for .401 or switch to a rom made with the T-mobile firmware.
BEWARE flashing firmware is a risky business. I've had HTC phones for years and the M9 i had kicked the bucket when i flashed a firmware package like i had done hundreds of times before. A random fluke bricked it.
So be careful what you do and accept possibly braking the phone before you even attempt something.

Related

[Q] OTA Update 4.3

I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it possible to flash or adb stock recovery back?
Yes, the stock recovery and files are posted here. I have reflashed the stock recovery and ota'd myself. As easy as flashing a custom recovery. You might want to read all the other ota threads here...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
flyinfool2 said:
Is it possible to flash or adb stock recovery back?
Click to expand...
Click to collapse
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Great info, Thanks!
flyinfool2 said:
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
Click to expand...
Click to collapse
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
andybones said:
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Click to expand...
Click to collapse
Well damn andy. Dropped the knowledge bomb on him
Yeah it's not worth OTA'ng, especially given the experience vzw S4 owners had with getting their root exploits and such closed...
Flashable OTA update question
So my One is unlocked and S-off. I manually updated to firmware version .15, however, my ROM is still version .10. (I could not download the version .15 ROM version as it was taking way too long) I keep getting the constant nag about the software update. I want to stay current, but dont want to lose ROOT or worse.
First, how do you use a flashable rom file to update your current rom? I dont what to have to backup and flash a new rom and restore all my settings everytime if I can avoid it. Is there a way to just update like what the OTA does?
Here was my thought. I would make a backup and clean install the current version (.15) of a custom, stock ROM. This would prevent future OTA's correct? Then, I would just update with flash-able files as they are released to keep my ROM up to date and ROOT privileges, etc safe?
Or would it be possible to update my current .10 ROM to .15, disable all OTA's and then flash updates as they are released?
BreakingVZW said:
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Click to expand...
Click to collapse
This is my wifes phone, so she is not concerned with having any custom operating ROM. For me however, I have always been a hacker at heart, and I love to run different ROMS on my own phone. For her phone, I just want the ability to run the most recent stock software, with root, so that I can make backups and freeze unnecessary apps to my liking. If a rooted stock zip is just around the corner, then I see no need to take the OTA update as you stated. Thanks for the insight. I just didn't realize that I could get the same result (an updated stock, rooted update) without taking the OTA. I appreciate the help! :good:
What can I do in the meantime to prevent my wife from accidentally accepting the OTA (it just began pushing on her phone)? I know the update wont take without stock recovery installed, but is there an easy way to prevent the repeated download and prompt for install?
EDIT: I found another thread with a flashable file to stop OTA...thanks all
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
wpsantennas said:
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
Click to expand...
Click to collapse
I have that. Haven't figured it out yet either. I did the stock recovery too. s-off and unlocked.
Had the same exact problem as WPSantennas and paganhobbit. Endded up using this thread http://forum.xda-developers.com/showthread.php?t=2475216 to return to S-On, Locked Bootloader at 1.10.605.8 (For mine to work right on this tutorial I had to skip the 2nd 'fastboot oem rebootRUU' after failing for it work.) I think the latest OTA doesn't really like if you have modified or deleted their stock bloat apps for some reason. IMO, The update is not impressive at all and I'd advise to stay at 4.2.2 but this is may be good to do if you want to bump to KitKat in the future. Hope this helps!
EDIT: Here's the link to the RUU I used since the link on the original was dead: http://www.android-edge.com/Login/uploads/PN017IMG_M7_1.10.605.8.zip
I ended up RUU-ing as well, going back to .10. Then it updated to .15 and the 4.3 update without a problem. I didn't re-lock or go S-On to do this. I had tried three different "official stock recovery" files I found, but 4.3 wouldn't update successfully with any of them.
A new problem is it doesn't seem to want to remember my WiFi connections for some reason now. If I go out of range and come back, I have to re-enter the WPA2 key all over again. I suspect it's Verizon's ploy to make me use more data

[Q] Is it safe to flash older rom on newer firmware?

I didn't make a nandroid backup before I flashed a custom rom (stupid, I know) and the only stock nandroid backup I can find is a version older than my current firmware. So now I want to flash a stock rom and recovery that is a version older (e.g. current FW: 2.11.708.2, nandroid backup and recovery is 1.60.708.2), is this safe to do?
edit: also would I be able to get official OTA updates this way as well?
Thanks!
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
redpoint73 said:
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
Click to expand...
Click to collapse
Thanks for the reply redpoint.
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
zentenk said:
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
Click to expand...
Click to collapse
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
redpoint73 said:
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
Click to expand...
Click to collapse
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
zentenk said:
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
Click to expand...
Click to collapse
Yes, I understand perfectly what you are asking, and why. I just don't have an answer for you.
Just a suggestion, I would try to restore nandroid and stock recovery, and see what happens.
I think the worst that will happen, is you have to flash back to your current setup because of firmware issues.

Does installing a TWRP Backup also affect phone Firmware?

Hello guys,
following situation:
Long time I had a 4.4.something Rom installed. Before I flashed a custom Lollipop rom, I followed the advice to just go back to stock and let it update to Lollipop so that the firmware will be updated accordingly and I won't run into problems when flashing a Lollipop Custom Rom. Everything worked fine. Now I had to send my phone to HTC for display repair and just to make sure they won't nag about the custom Rom I reflashed some older stock rom via TWRP backup I found here, I think it was a 4.0 or so. The question is, does this also affect my phones firmware or is it still on the current newest level? So when I get it back, would I need to update to stock Lollipop again before flashing a custom rom or can I go for it straight away?
fBx said:
Hello guys,
following situation:
Long time I had a 4.4.something Rom installed. Before I flashed a custom Lollipop rom, I followed the advice to just go back to stock and let it update to Lollipop so that the firmware will be updated accordingly and I won't run into problems when flashing a Lollipop Custom Rom. Everything worked fine. Now I had to send my phone to HTC for display repair and just to make sure they won't nag about the custom Rom I reflashed some older stock rom via TWRP backup I found here, I think it was a 4.0 or so. The question is, does this also affect my phones firmware or is it still on the current newest level? So when I get it back, would I need to update to stock Lollipop again before flashing a custom rom or can I go for it straight away?
Click to expand...
Click to collapse
It won't affect your firmware.
Okay thanks, so Firmware should still be up to date and I can flash a Lollipop Custom Rom. I don't know what they do at HTC repair, if they only reset it or if they also update it, well I'll see.

i747 or t999

i have rooted and unlocked galaxy s3(i don't know if it is t999 or i747)the imei and boatloader are for t999 and the android build is i747mvldlk4 4.1.1 official rom and i want to flash new rom but i don't know what i have to flash (t999 roms or i747)please help me....
What does it day in download mode? What about the baseband/modem version?
Best way to know for sure is to install terminal emulator and enter this:
getprop ro.bootloader
You may simply have a T999 running on an I747 based rom. The two are very compatible when it comes to custom roms.
Since it sounds like you are on pretty old firmware, you will probably need to fully update it before flashing a newer rom. Just remember to only flash firmware for your model device. So if it's a T999 do not flash I747 firmware. Once updated you can then flash custom roms from either device.
(Also check the sticker under the battery to see what model it says)
baseband:t999uvdmd5 and modem board is msm8260a
What about the bootloader?
boatloader:t999uvdmd5
And just for good measure, check the sticker under the battery.
You are currently running on T999 base firmware with an I747 based rom, so you can be pretty certain you've got a T999 model.
You'll want to flash one of the two latest firmwares for the T999. (NC2 or OH1 if I'm remembering correctly) (note that some roms may not flash on the newest OH1 firmware if they have been updated recently, so you may want to go with NC2 to make things a little easier for now.)
After flashing your firmware, flash a custom recovery and then from the recovery flash your choice of rom.
Hope that helps and good luck!
thanks so much for help....but i want to ask about the files which i need to download when i flash nc2 firmware please(do i need to download any files for modem and kernel or this files are downloaded automatially with the firmware file??
When you are dealing with firmware, it includes everything, unless otherwise stated. Download and unzip the firmware package. Then flash the .tar.md5 file with Odin. Back up data first of course, just in case.
Doing this will give you a fully updated, stock, unrooted device. Reroot using Towel root, or flash recovery then a rom if you choose.
If you haven't already, I suggest reading the first few posts of my firmware thread (sticky in dev section). There's already a lot explained there.
does flashing t999uvuenc2 relock my mobile network..and if that will happens what can i do to unlock without code
Once the phone has been unlocked via code or the free method, the phone should remain unlocked after flashing ROMs.
Yup, the unlock is permanent. You can safely flash firmware, roms, etc.
ihave flashed cm12.1 d2tmo on my t999.but the features of camera like full HD video recording and face detecting were lost..can I restore them on this rom

installing revolution HD w/ twrp?

hi guys - so i tried to install the revolution rom on my recently unlocked m9 and it'd only boot to the bootloader or download.
i found some threads back from 2012 that said twrp wouldn't install the rev rom, but suspect it's out of date - it seemed to work fine.
is there some magic here? i tried to flash my firmware to the version matching the rom (3.35.401.12) and got a code 10 failure in adb. my current firmware is 3.10.605.7. doesn't flashing the rom update the firmware too? or do i need to successfully flash the rom prior?
should i use a different recovery? twrp launched the rev aroma installer and all seemed to go perfectly smoothly... no problems came up until reboot brought me right back to bootloader.
the aroma install says it might boot loop a couple times, but i booted to bootloader 5+ times before giving up and going back to a deodexed stock vzw rom.
any help is greatly appreciated - i'm hoping to get up to marshmallow before calling it good enough and moving on.
Flashing the rom doesnt update the firmware. S-on makes sure of that.
You must be on the base firmware for the rom to take. You need the vzw marshmallow ota update before you can flash a marshmallow based rom.
Sent from my HTC One M9 using Tapatalk

Categories

Resources