Hello everyone,
Vendor:
As far as I know I will need to update my vendor.img whenever I flash a new ROM version (or else I will get the warning that my vendor version is too old).
This is the only thing I need to flash in combination with the ROM version? Everything else can be flashed in what ever version I want and whenever I want?
Radio:
There are several versions, one from beta, one with "verizon" written next to it and then another one without any "additional text".
As I am from Europe I guess that the "verizon" one won't work for me.
I am don't want to try the beta version either.
So I will keep the latest "uncommented" radio version?
Bootloader:
From how I understand it it will usually just have security & bug fixes and only is taking care of the boot process. It won't have any effect on the running system?
But latest is recommended as always and can be flashed whenever I want?
Thanks !
Utini said:
Hello everyone,
Vendor:
As far as I know I will need to update my vendor.img whenever I flash a new ROM version (or else I will get the warning that my vendor version is too old).
This is the only thing I need to flash in combination with the ROM version? Everything else can be flashed in what ever version I want and whenever I want?
Radio:
There are several versions, one from beta, one with "verizon" written next to it and then another one without any "additional text".
As I am from Europe I guess that the "verizon" one won't work for me.
I am don't want to try the beta version either.
So I will keep the latest "uncommented" radio version?
Bootloader:
From how I understand it it will usually just have security & bug fixes and only is taking care of the boot process. It won't have any effect on the running system?
But latest is recommended as always and can be flashed whenever I want?
Thanks !
Click to expand...
Click to collapse
With the vendor image you do not need to flash it again every dirty or clean flash. You only need to flash a new version when the rom you are using updates to the latest security patch. This is because when you update your rom it doesn't affect the vendor partition. Go to wipe and advanced and you'll see that vendor is not there. That is because whatever you do with updating roms won't affect that partition. Updating roms will affect cache, dalvik/art cache, data and system.
With the radio, I would recommend using the most recent version that works for you. Use verizon only if your phone is from verizon or anything to do with verizon. My phone was from the google store so I don't use the verizon version.
With the bootloader it shouldn't have any possibility of having a bad affect like the radio could. It is recommended to update the bootloader every time there is an update available. Make sure with the radio and bootloader you fastboot flash via your computer.
Let me know if this helps and if you have any other questions.
Related
Hey im wondering where I can find a link to the W8's newest modem? Also do i need to flash both it and the bootloader?
butthurtlocker said:
Hey im wondering where I can find a link to the W8's newest modem? Also do i need to flash both it and the bootloader?
Click to expand...
Click to collapse
If you flash the latest firmware the modem and bootlader are allready included.
butthurtlocker said:
where I can find a link to the W8's newest modem? Also do i need to flash both it and the bootloader?
Click to expand...
Click to collapse
You didn't tell us why you want to change your modem, so it's impossible to give a certain answer to your question. It's not strictly necessary to flash both, but in most cases you would be best served to flash the full firmware, which will normally contain the modem and bootloader. Unless you have a specific reason to do otherwise, keep them a matched set.
Of course if you had done a search before posting, you'd already know this. You can search the forum or one of the many firmware repository sites for firmware. A quick look at Sammobile suggests that ANF3 or ANF4 are the newest 900W8 versions. Again, unless you have a credible reason to do otherwise stick to a modem from your carrier. i.e. the carrier that the phone originated from regardless of what carrier you will actually use it on.
If there is some compelling reason that you need to flash the modem only, you could extract the modem.bin file from the full firmware, package it as a .tar.md5 file and flash it on the CP line of Odin 3.09. If you are flashing the full firmware, enter the file name on the AP line.
.
fffft said:
You didn't tell us why you want to change your modem, so it's impossible to give a certain answer to your question. It's not strictly necessary to flash both, but in most cases you would be best served to flash the full firmware, which will normally contain the modem and bootloader. Unless you have a specific reason to do otherwise, keep them a matched set.
Of course if you had done a search before posting, you'd already know this. You can search the forum or one of the many firmware repository sites for firmware. A quick look at Sammobile suggests that ANF3 or ANF4 are the newest 900W8 versions. Again, unless you have a credible reason to do otherwise stick to a modem from your carrier. i.e. the carrier that the phone originated from regardless of what carrier you will actually use it on.
If there is some compelling reason that you need to flash the modem only, you could extract the modem.bin file from the full firmware, package it as a .tar.md5 file and flash it on the CP line of Odin 3.09. If you are flashing the full firmware, enter the file name on the AP line.
.
Click to expand...
Click to collapse
Haha. Well thanks for the highly descriptive answer bud. I wanted to flash the newest modem because I found I was having tons of problems with the newest builds of roms like Omega and Xtrestolite. for instance I couldnt send outgoing texts. I asked around and never got a clear answer so just from reading I figured I needed the newest modem to get everything going properly. Im very new to this even though ive been an xda member for awhile i only recently starting doing a lot of flashing. Anyways its now clear after flashing new builds as well as extracting the modem for the newest stock firmware and I still cant get texts! Thanks for the advice
butthurtlocker said:
Haha. Well thanks for the highly descriptive answer bud. I wanted to flash the newest modem because I found I was having tons of problems with the newest builds of roms like Omega and Xtrestolite. for instance I couldnt send outgoing texts. I asked around and never got a clear answer so just from reading I figured I needed the newest modem to get everything going properly. Im very new to this even though ive been an xda member for awhile i only recently starting doing a lot of flashing. Anyways its now clear after flashing new builds as well as extracting the modem for the newest stock firmware and I still cant get texts! Thanks for the advice
Click to expand...
Click to collapse
I think that your problem is highly unlikely to be caused by or solved by changing your modem. Have a close look at your configuration. If you can't find any errant settings. then do this:
Backup your system. Then use Odin to temporarily revert to the oldest 4.4.2 build (must be pre-June 3rd) for your carrier. i.e. you are installing a 100% stock build that is known not to have serious SMS issues. See if that resolves your problem or not to narrow down the source of the problem. And while I doubt that the problem is from your custom ROM per se, you could if you want just move to another custom ROM. There are a lot, the vast majority of which have no SMS issues.
At a guess, your problems are far more likely to be due to bad APN info, bad cache (clear your cache in recovery mode and also clear cache and data for your SMS client from the settings menu application manager) or a carrier side issue (open a support ticket).
If it was my phone, I'd be trying all of the points in the paragraph immediately above first. And only if that fails to resolve your problem (which is highly unlikely) would I be messing with modems, reverting to full stock firmware or migrating to a different ROM.
.
fffft said:
I think that your problem is highly unlikely to be caused by or solved by changing your modem. Have a close look at your configuration. If you can't find any errant settings. then do this:
Backup your system. Then use Odin to temporarily revert to the oldest 4.4.2 build (must be pre-June 3rd) for your carrier. i.e. you are installing a 100% stock build that is known not to have serious SMS issues. See if that resolves your problem or not to narrow down the source of the problem. And while I doubt that the problem is from your custom ROM per se, you could if you want just move to another custom ROM. There are a lot, the vast majority of which have no SMS issues.
At a guess, your problems are far more likely to be due to bad APN info, bad cache (clear your cache in recovery mode and also clear cache and data for your SMS client from the settings menu application manager) or a carrier side issue (open a support ticket).
If it was my phone, I'd be trying all of the points in the paragraph immediately above first. And only if that fails to resolve your problem (which is highly unlikely) would I be messing with modems, reverting to full stock firmware or migrating to a different ROM.
.
Click to expand...
Click to collapse
Ok noted. So i've reverted to stock a few times and SMS always worked. I've re rooted twice, tried different recoveries each time and tried a few different roms. heres what happens:
-Very first rom I've ever tried is Xtrestolite 1.2.2. . ZERO issues, kept updating as new versions came out till I got to 1.3.2. So even though 1.3.1 used the new firmware, I was still able to flash it with no issues. Then as soon as i tried the latest build, 1.3.2, couldnt text at all. I know its something to do with my SMSC because when i installed GO SMS pro from the playstore and manually inputted my SMSC i could text via that app, but not the stock one or even hangouts. Since 1.3.2 was using a slightly different firmware number I just assumed it was the modem. Exact same issue with Omega rom- V6 worked great, as soon as I flashed V7 no outgoing texts. Everything else worked by the way (incoming and outgoing calls, and incoming texts) Just not outgoing
So the reason for starting this thread is because i seem to only be able to use the last version of the 2 roms im interested in if I want to be able to text from the default app. I also checked with members using both roms, that had the W8 and they didnt experience these issues at all. We even went over the steps to get from stock unrooted to flashing the latest builds and my steps were identical to those people who didnt have my issue with the W8. I have no idea what to do but I will likely go back to stock for now. Thanks again
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Totemic_tHiRp said:
Hi all,
I was running my stock 5.1.1 (LPD23.118-6.1) rom rooted for a long time and wasn't able to receive OTA updates due to the obvious reason about rooting and etc. My recovery wasn't changed. So, I saw the thread about that "flashable zips" about 6.0 roms and decided to test it. Due to some crashes and forced closes, I decided to back to my previous backup of rooted 5.1.1 stock rom. But now I want to have my phone stock as hell, and the first thing that I do was flash the most updated firmware that I found in here that was available to download. I flashed the whole LPD23.118-6.3 stock rom, a little bit newer than my old stock rooted rom. Everything working, everything fine, except...
In bootloader it says "Software status: modified", and when I try to manually check about updates, it says that my software is up to date, which I know isn't true, because OTA update of Android 6.0 is already available (i have a friend who got an X Play and he already received the ota).
How can I solve this?
Click to expand...
Click to collapse
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
scottdanpor said:
The force closes you got are completely normal and if you read the thread you will have found out you just need to reboot your phone until they go away.
The status modified just means your bootloader was unlocked and doesn't matter.
You have a few options, keep trying for OTA, flash another version and keep trying for OTA, sideload one of the available OTA zip files, or try a TWRP backup.
Click to expand...
Click to collapse
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Totemic_tHiRp said:
Thanks for your reply. Actually i'm downloading the recently posted 6.0 firmware for the Brazilian/Latin American rom in firmware's thread. Unfortunately the download is very slow, but I guess I can surely update without losing anything. The only strange thing is that I didn't received any OTAs....
Click to expand...
Click to collapse
It's not necessary that if your friend has received the OTA then even you will receive it within few days. The OTA is rolled batch wise and no one knows which phone is in which batch except Moto of course. [emoji4]
Sent from my XT1562 using Tapatalk
I soft bricked my Y625-U51 (I bought it as a second phone to mess around with) and tried to install a version of cyanogenmod not made for this phone, this threw it into a boot-loop, effectively soft-bricking it, the thing is, i could just flash the stock firmware from the huawei site onto the phone right? Problem is, they don't have it up for download, or any info on it, and all the versions i found online, are older than the currently installed firmware, giving me the "can't install this package over newer build" Error, what do i do? I would be fine using the older firmware, but is there a way to disable the time check, and/or does anyone have a newer version of the firmware?
I need solution too
Dax1240 said:
I soft bricked my Y625-U51 (I bought it as a second phone to mess around with) and tried to install a version of cyanogenmod not made for this phone, this threw it into a boot-loop, effectively soft-bricking it, the thing is, i could just flash the stock firmware from the huawei site onto the phone right? Problem is, they don't have it up for download, or any info on it, and all the versions i found online, are older than the currently installed firmware, giving me the "can't install this package over newer build" Error, what do i do? I would be fine using the older firmware, but is there a way to disable the time check, and/or does anyone have a newer version of the firmware?
Click to expand...
Click to collapse
I am having same problem with same phone cant find firmware newer than installed V100R001C577B111 or one that i found needs to be installed through cwm or twrp and cannot be installed through stock recovery..
Hi.
Can some one help check my Elephone S7 (4G-64GB) bootloader status? I've tried the code and some apps, but the code doesn't work and the apps some don't work while others say "unknown" .
On another subject, stock rom related:
- After installing twrp and the latest stock rom, does OTA still work? I think it should since it's the same rom just a different recovery, but I would like confirmation.
- I don't know why but on my Elephone S7 the google startup wizard doesn't start. I even got the wizard apk, but it installs and doesn't run. So I'm thinking... (maybe I shouldn't ) can we install open gapps using twrp without any problems?
Thanks!
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900