All,
Coming from Verizon Gnex and I'm reading the Verizon S3 forums and getting a bit confused on the flashing parts of this phone. I see the firmware baseband is "HE" as of a couple of days ago. I also see options to flash the radios and modem? What is the modem for? I never had to flash a modem for my GNEX. Am I missing anything else that I need to flash?
Also, if you would be so kind....I am planning to keep stock for the near future, so after I root and unlock. I need to flash the latest stock ROM which is "HE" then latest radios then modem? What is the latest version of each?
And one last thing, is it the same as GNEX where all I have to do when flashing something is just wipe cache and dalvik cache?
The current verizon updated stock baseband is vrlhe. It includes the most recent modem (radio) from that update. Once you start flashing rom's, the entire portion of the base is dependent on what the developer has built the rom on, and you can choose what radio works best for your phone. Example: synergy R73 is based on vrlg1, but flashing the vrlhe radio with it may give you better cell service.
And, NO on just wiping caches. That's only Ok if updating the same rom, based on the devs guidelines on his updated build. Full wipes between rom's always. It's not a dedicated developers device.
And before you flash anything read the thread in development on backing up your IMEI. There is a bug in this s3 variant that can lose your id when flashing. This is important if you don't want a major headache. And you'll need to unlock your bootloader too
Ha, or maybe he really likes puppies cause he'll end up with a nice chew toy for one...
Thanks for the info guys. And yes, I understand not to dirty flash when switching roms. I usually dirty flash when I'm upgrading from the same rom ie..Bugless Beast...I've dirty flashed the past 4 upgrades.
Was just confused from reading the forums of radios then I see modem....I'm like huh? But got it. Radio=Modem but refer as Radio.
Related
Can someone help me out. I can't find a straight forward answer for this. If I were to flash a new rom, would I need a radio? I know the radio deals with GPS and data and everything but that's about as much as I know. The reason I adk is I just installed a rom by mod and i flashed t after wiping a close to stock just debloated ics. My wifi is very weak, and my speed results are at an all time low. Like my download speed is 2mb and it used to hang around eight. Websites don't load terribly slow but not as zippy as they used to. My GPS takes a little messing with before it c ition. I'm on whatever kernel came with the rom cause I'm completely lost on kernels and undervolting and overclocking and everything. I'd love to to fix my battery life cause that's complete shot too but..my bad I got off topic. Do I need to flash an radio on top of the rom? Would I need to do this every time I flashed a new one or updated? And which one would I flash? Sorry for the obnoxiously long post but any help is appreciated.
If you're on at&t , the latest radio is UCLF6 .. Search for it in dev section and flash it in ODIN or CWM if you're not already on it (or flash it anyway)... Another note is preferably to use the ROM with the radio that was released with it on leaked or official builds ...
Most custom roms are radio free or at least they should ... Leaving radio choice on user ...Radio files are not topics of customaiztion..
mahanddeem said:
If you're on at&t , the latest radio is UCLF6 .. Search for it in dev section and flash it in ODIN or CWM if you're not already on it (or flash it anyway)... Another note is preferably to use the ROM with the radio that was released with it on leaked or official builds ...
Most custom roms are radio free or at least they should ... Leaving radio choice on user ...Radio files are not topics of customaiztion..
Click to expand...
Click to collapse
You're a life saver. So most roms come without radios and leave it up to you? And if I happen to be on uclf6 and I flash it anyway it won't hurt? I was wondering about that too forgot to ask. Sorry if im just tired and misreading but your last lines confused me a bit, you said that roms should be radio free but then said they're not topics of customization..?
See : if a custom ROM has radio baked with it you'll see it inside the zip for this ROM and the forum thread should mention it in the instructions...And if this is not the case your old radio will stay untouched...And yes to the other question, flashing the radio again would not hurt but I personally don't like messing with radio if not needed...And again personally I like using the latest stiff and in this case use UCLF6 although some might say try different radios until you find the one performing the best for you...
Thanks again, flashed uclf6 radio, learned I didn't need to but hey. Off to attempt different radio/kernel combos
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!
This is a little confusing so bear with me.
I installed CM for my S3 and ended up reflashing the modem to fix SMS. Eventually I noticed there were a lot more issues(GPS, signal, etc) with the phone and have went back to CleanRom (Stock-Root-I535VRUCML1-De-Odex-V2.zip) though the bars still seem a little low. I'm guessing I need to update my modem and I saw a few threads in the archives over at Scott's about the ML1 modem (d2vzw_ML1_modem.zip) can I just flash that file and everything will be fine?
Right now the baseband is I535VRBMB1. If I need to update it what should I update too? Also are there any good 4.4 alternatives? Could I go back to CM mod and flash this ML1 modem and have a good experience? Or are the modem issues I experience with CM mod just unavoidable?
Bump. Anyone have an answer?
MF1 is the commonly recommended latest unlocked radio/firmware. (You MB1 is clearly much older.) You can add the ML1 radio on top of this, but don't add the entire ML1 firmware (which includes the locked bootloader).
mastamoon has the MF1 firmware (which includes radio) on his ROM thread here: http://forum.xda-developers.com/showthread.php?t=2569769 I would suggest starting there, and then you can consider applying the ML1 radio-only which can be found here: http://forum.xda-developers.com/showpost.php?p=54520377&postcount=1343 (since invisiblek.org is down)...
At least this is how I understand it to be. I'm running the ML1 radio on the MF1 firmware on stock, rooted, BL-unlocked...
EDIT: Mind you, this assumes you're staying unlocked. Putting in an older FW/baseband on a locked BL phone can cause a brick. I expect you don't have this situation, as you were running CM (natively? or on safeboot?)... so you need to be clear on what you have, and where you want to go...
schwinn8 said:
MF1 is the commonly recommended latest unlocked radio/firmware. (You MB1 is clearly much older.) You can add the ML1 radio on top of this, but don't add the entire ML1 firmware (which includes the locked bootloader).
mastamoon has the MF1 firmware (which includes radio) on his ROM thread here: http://forum.xda-developers.com/showthread.php?t=2569769 I would suggest starting there, and then you can consider applying the ML1 radio-only which can be found here: http://forum.xda-developers.com/showpost.php?p=54520377&postcount=1343 (since invisiblek.org is down)...
At least this is how I understand it to be. I'm running the ML1 radio on the MF1 firmware on stock, rooted, BL-unlocked...
EDIT: Mind you, this assumes you're staying unlocked. Putting in an older FW/baseband on a locked BL phone can cause a brick. I expect you don't have this situation, as you were running CM (natively? or on safeboot?)... so you need to be clear on what you have, and where you want to go...
Click to expand...
Click to collapse
Thanks a ton. Yes I'm staying unlocked and I was running CM natively. Downgrading the radio was a fix to a problem a lot of people in my area had with CMs radio. I'll look into it more I guess. Going back to CleanRom was just an attempt to solve the problems CM seemed to be causing me.
Presently I have Cleanrom 8.2 http://forum.xda-developers.com/showthread.php?t=1832070 I'd like to go back to 4.4 since it felt like I got better battery life. So I'll take a look at some of the various things on the forum. I don't know if putting 4.4 on the S3 at this point is just going to cause issues or what exactly.
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.
Hey guys, I just flashed the CM13 nightly from stock 5.0 and now I'm showing no sim card. I saw a couple threads saying that newer twrp builds have issues with flashing radios, so I reverted to twrp 2.8.6 and did a clean flash, with no love. Tried flashing the radio zip, no love. Tried flashing the 3 most recent radios through fastboot, no love.
Any assistance would be greatly appreciated
Are you flashing both the bootloader and radio? If this doesn't work, I suggest flashing the latest stock MM to make sure the phone is working, then flash CM13.
Good call, trying it now
okay, flashed to stock 6.0.1, worked like a champ, flashed back to cm, now it connects to the network, but drops to no service after a second or two. Progress! Now that I know that you have to flash bootloader and radio, i'll try some different combos and see if i can get something to work. If nothing else, i can always go back to stock MM
Thanks!
Have you tried CM13 with a custom kernel? This may solve the issue.
You need to do alot of reading, no insult intended. Don't run b4 you can walk. If you didn't know to flash the radio and bootloader you need to learn alot. Luckily it's a bullet proof phone. Nightlies are not stable and not for daily drivers. They are works in progress and buggy as a result. Not for noobies, IMHO
The OP did flash different radios. It is not always necessary to flash a modem and bootloader to have a working phone.