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
Related
Hi all, I apologize for my low level of English. I want to tell that to write this report use the google translator.
I also thank in advance the help that you can give me.
Acontinuacion expose my problem:
I followed the steps in a tutorial, to release my samsung i9505 galaxy s4, exposed one of the most important forums, Htcmania.com my country, Spain.
By exposing my problem in the same forum that supra and receiving no response clarification about my problem, I turn to the more important to try to find a solution forum. I go to XDA-Developers.
I do a copy and paste of the report I wrote on the forum that I quoted earlier as I explained my problem well:
My s4 with Android 4.4.2 was completely "virgin" had installed the rom Stock samsung, was not released, was "Yoigo" any advanced recovery had not installed, and had no permits super user "root".
I wanted to release it (Unlocksim) seeking information HTCMania, and I found the following topic "Free S4 I9505 (Unlocksim) in 4.4.2" I followed all the steps in the tutorial. One of the "requirements" was to be root to do a backup of the EFS before touching anything, and to use the application "Region lock away"
So no, I did root, flashing by odin CF-Auto-Root 4.4.2 package.
Being root installed the advanced recovery "CWM" philz touch. And I found myself at this point I made a backup of the EFS system being completely "virgin" that is, with stock rom samsung and android 4.4.2. I followed the steps in the tutorial that I have made previously to unlocksim. One of the requirements to release the phone was change the modem to modem I9505_DXUAME2_MODEM, so I changed the phone modem and followed the guidelines set by the tutorial,
Region to use the application could lock away briefly display an error is possibly to blame for me as I'm seeing. This error could display for two seconds, but from that moment everything seemed to work well, the phone was released. So I changed the modem again for mine.
At this point I decided to choose to install a cooked rom based on stock, namely Omega rom v38.1 for s4 I9505.
And at this point is when my headaches begin to appear. I have experienced problems with the release ... see, the issue is that when the network coverage data is in H + the phone works perfectly, but only if H is not able to load websites etc. This has led me to the edge as I can not be aware every moment of the type of data coverage.
My questions are:
1. Is there a way to stop the phone as he was before unlocksim, ie leave it as it was originally being from Yoigo? (Remember to keep a copy of SAI realized when the system was completely untouched.)
2. How I can solve this problem with the network coverage data?
3. What do you advise me to do?
Please help. Greetings.
you might want to try searching sammobile to see there is a ROM you can download and flash that's for your country and ideally for your phone provider as well. I've run into issues like this on a couple of occasions. One was indeed that the country's ROM I flashed uses differant frequencies and I had the same mobile data connectivity issues you're talking about. This is rare for the international Samsung phones but it does happen. The other scenario I ran into was after flashing a port of the Google Play Edition onto tit, which gave it extended network options, and everything worked quite well but when I restored to stock from a backup on my sdcard I had connectivity issues, once again just like you're describing. In this scenario flashing a fresh stock ROM entirely solved the problem.
Note that in the second scenario I didn't redo the data partition. Presumably flashing the system fixed it or reflashing the firmware partition reinitialized things the way they are meant to work for me.
search for I9505 (or whatever the model of your phone is) where it says search for your device http://www.sammobile.com/firmwares/
Google around the codes if the results aren't revailing enough for what's stock for you and try reflashing in odin. If it persists then backup your apps, wipe the data partition, possibly backup your internal storage as well if you have a stock recover, and try again. Beyond that I haven't had to deal with further problems than that yet but I saw that no one else had responded...
I recently installed TWRP and then the latest snapshot of CM12.1 for my phone described in title. The android version was upgraded from KitKat (4.4 I believe) to 5.1.1. Everything works fine with the install except I have no network whatsoever. Can't text, can't call, can't use data etc. I made a post on the CM subreddit but didnt get a lot of help (can't post link) . Here is what I have tried: changing APN settings (which I have heard should at least let me call and text if incorrect); flashing various modems such as BOE3, BNL9, and BOD3 (all of them get a FAIL! (auth) in ODIN); restoring my KitKat backup (makes the phone unusable); trying to flash the default L rom for the phone (Also fail to flash in ODIN and TWRP). So at the current time I am basically stuck on CM12.1 and all of its amazingness with no phone functions, I basically have a small tablet at the moment lol.
Here is some information from the about of my phone, if it is helpful at all.
Model: SM-G900F
CM Version: 12.1-20151204-NIGHTLY-ktle (Installed the nightly after the snapshot didn't work, same problem persists)
Android version: 5.1.1
Baseband version: S902LUDU3AOG2
Carrier: Straight Talk
If any more info is needed, just let me know. I appreciate any help, as I am pretty much at square one still. I have googled for days to try to fix this, and haven't come up with anything. It seems no one has had this specific problem before.
If I can't fix this issue, is there any way I can downgrade back to what I had to begin with?
y tried with another sim card !!!
ty *#06# to verify imei
popmpopm said:
y tried with another sim card !!!
ty *#06# to verify imei
Click to expand...
Click to collapse
I only have one other sim card on me, and its through verizon. It didn't work on the phone either. I would definitely just buy a new sim card if that would mean it would work. The whole IMEI thing worked, but I am not sure what to do with that information.
(Definitely a G900F? Check what it says in download mode)
Checking the IMEI was to make sure you haven't wiped/corrupted the EFS partition, which contains the Radios needed to make and receive called, along with the IMEI (Hopefully you researched enough to back that up before messing with the phone)
Try flashing another stock ROM with ODIN 3.10.7, go for a different Lollipop ROM from sammobile. com
Some stock ROMs fail to flash, some work, (Phone dependant it seems)
Then boot into recovery and factory reset > try to boot
*Detection* said:
(Definitely a G900F? Check what it says in download mode)
Checking the IMEI was to make sure you haven't wiped/corrupted the EFS partition, which contains the Radios needed to make and receive called, along with the IMEI (Hopefully you researched enough to back that up before messing with the phone)
Try flashing another stock ROM with ODIN 3.10.7, go for a different Lollipop ROM from sammobile. com
Some stock ROMs fail to flash, some work, (Phone dependant it seems)
Then boot into recovery and factory reset > try to boot
Click to expand...
Click to collapse
I have tried 2 separate L roms for the G900F. It says in download mode the phone is a SM-S902L and I read somewhere to get the true model of the phone you look at the FCC id under the battery. Well the FCC id says it is a G900V. at one point in trying to fix it, I tried a stock L rom for the G900V and TWRP told me that it was intended for a kltevzw device and that mine is a klte, so that is why I assume that it is in fact a G900F. I have been using ODIN 3.10.7 to flash everything as well. (Have't tried TWRP for the most recent tries since it takes longer to setup and I doubt it would work but it's worth a try I suppose.
I looked on Sam Mobile for the SM-S902L and there is only one firmware for it, which is 4.4.2, the same one it was installed with when I got it. From my understanding SM-902L is the straight talk branding of the G900V, and trying to flash that firmware didn't work either. Every time I try to flash something it terminates with a FAIL! (auth). What I also understand is that Straight Talk has not released an official version of L for the phone. So it seems my options now are to somehow get the modem to work right in CM12, try to somehow downgrade to 4.4.2, or wait for Straight Talk to release an update for my phone which is not really an option. I just got this phone and I really don't want to have to buy a whole new one just because of software problems. In my mind there HAS to be some way to fix this.
EDIT: my bad, I should have mentioned when I tried to flash the G900V rom it was also CM12, not a stock.
EDIT AGAIN: I seem to have fixed this problem. I have no idea how I did it, but I finally got it to restore to the stock 4.4.2 rom. I seriously have no clue how it worked but it did. Texting and data once again work, but i am now having a problem where I can't make or receive calls. Call immediately ends/goes straight to voicemail. I don't suppose you know anything about that, if you do that would be awesome. I'm gonna call ST in the morning and see if they can tell me anything from their end. But otherwise, I guess my problem is solved. Lol.
I know it sounds simple or may sound stupid but have you tried entering your APN? I have to do that with most of the custom Roms I flash or I won't have service. Also, make sure the correct modem is flashed and up to date.
Flashed stock 5.01 ROM and phone call function stopped working.
When calling, there is a connection but no sound can be heard on either end of call.
It WAS working briefly and briefly managed to 'fix' it. Everything else functions correctly. Wifi calling works perfect. SMS works perfect.
I have searched forums and Googled this (about 9 hours worth so today) so quite at a loss how to proceed.
Tried forums suggestions to:
- disable Google Now/OK Google voice functions
- disable S Voice functions
- removing and replacing SIM/SD card
- wiping cache
- air dusting earphone port
- clear Google Play services cache and data
- clear Drive cache
- boot into Safe Mode, still not working
Additionally tried re-wipe cache/DALVIK/data/entire device and re-installed different stock ROM, same problem
I flashed both BELL and Rogers stock Lollipop ROM from XDA post (http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758) via Odin
Any suggestions???
The only thing that worked briefly was:
In App Info for the Phone App, I did 'clear data' and 'clear cache' for all THREE Phone Apps (yes, there are three, I don't know if this is normal or not as this is first time with Lollipop). This allowed the phone to work BRIEFLY, then problem returned.
Try flashing the latest stock from sammobile.com.
Hi,
Attempting this but both Bell and Rogers Lollipop firmware .ZIP are corrupt from Sammobile.com I've contacted their admin to advise of this as I have tried downloading multiple times with the same corrupt file result.
Are there any other reputable download site?
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
audit13 said:
Try flashing the latest stock from sammobile.com.
Click to expand...
Click to collapse
Anything to be concerned about reverting via TWRP to Kitkat
Tried Emergency Firmware recovery via KIES, no luck, re-wiped cache, did factory reset in stock recovery, still no good.
Tried swapping Sim card tray and Earphone port (had a parts phone kicking around that is stuck on boot logo ((TWRP/ODIN Flashing does not recover this phone sadly)))
Will try to revert to Kitkat via TWRP next.
Note: I AM able to make normal calls as long the device is connected via Bluetooth to my car or to my bluetooth headset. Discovered this after more googling/forum searching.
rogue_element said:
I did a nandroid / efs backup with TWRP. Would there be any problems in restoring to 4.4.2 Kitkat using that???
Click to expand...
Click to collapse
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Hi,
I'm using Win7 x64 Home Premium. WinRAR to unzip.
Since posting last I have restored Nandroid backup - phone function still didn't work and Google Play Services glitched out.
So, next downloaded 4.4.2 Kitkat from Sammobile, extracted no problem, flashed via Odin (no errors)- still no phone function
Wiped phone yet again, re-installed Kitkat one more time with Odia (no errors) - still no phone function
Used Kies to do Firmware Update and Initialization, (no errors) - still no phone function
Re-wiped again and used Kies once more, this time not doing App Restore function in case there is App causing issues and not signing into Google or Samsung Account to avoid anything restoring - still not working but interestingly there was a OTA update to 5.01 that installed fine - end result... phone function still not working.
If anybody can offer me another suggestion to try, I'll be happy to attempt but at this point I'm prepared to say f**k it and buy another phone.
I've been at this since last Saturday.
audit13 said:
What are you using to download from sammobile? I always use a win 7 machine.
What are program is being used to unzip the rom? You're only unzipping once?
Click to expand...
Click to collapse
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Yes, I've attached a screenshot. Bootloader and baseband do match. This last round of install was done via OTA update that popped up after installing Kitkat. I just rolled with it as I figured if it's coming from Samsung directly, why not.
When making calls via Bluetooth, there are no issues. It functions as normal. It is just through the Phone App itself.
Interestingly, I discovered I can make outbound call no problem via Google Hangouts dialer as well. This is incredibly frustrating.
audit13 said:
After flashing with Odin, are you able to confirm that the bootloader and baseband match each other and the rom that was flashed? The imei is correctly displayed?
Since you are able to make calls via Bluetooth, are you able to hear the other party and the other party can hear you? What about calls via speakerphone?
Click to expand...
Click to collapse
Did you try reflashing the OH1 ROM? Sounds redundant but I'm not sure what else to suggest short of putting the motherboard into another phone and trying it out.
Hi audit13,
Haven't tried installing mobo in another phone, will give that a whirl for sh*ts''grinz.
Been an incredibly frustrating process. Another interesting thing that has been happening is that I notice the boot up sequence takes a lot longer than I recall.
Have been trying to avoid using the phone.
Re-flashed OH1 using ODIN and earlier tonight, Kies. Still not working.
I'm wondering if doing something like reverting to very old ROM may do the trick instead.
Do you happen to know how old I can go? Jellybean? I will check sammobile and see what the oldest they have there.
Phone functions perfectly fine via Bluetooth still, IP calls via WhatsApp and Hangouts Dialer also work per normal. Just trying to place normal calls does not work.
Have also had bootloops lately too I notice.
You can go as far back as 4.4.2 from my experience.
You'r performing a factory wipe right after flashing in Odin?
Initial boot up after flashing and wiping usually takes a long time but it should become quicker as the cache builds up with each reboot.
@rogue_element have you found a solution?
My wife's phone is having the exact same problem.
It started happening like a couple months ago. Haven't flashed anything to it. It just suddenly happened.
Hi ImpheOtus,
No, I'm still searching for a solution. I tried reflashing and then factory reset per audit13 suggestions but still no luck. I even tried swapping the ear piece module from a parts phone and no go. Extremely frustrating. Shopping for a new phone at this point but I'm still trying for a resolution as I'm stubborn and don't like giving up.
Hi audit13,
I'm actually suspecting the something else at this point (virus/malware, etc.) in the bootloader or deeper. There has been other random odd behavior, and while I don't rule out something like a hardware problem either, the behavior has been very strange.
Perversely, my wife's phone briefly experienced the same issue as mine but it cleared up after a reboot.
I will go hunting for a tut on flashing bootloader and kernel only next to see if that helps. If you have any suggestions of where to look for tutorial and/or files please feel free.
I tried flashing 4.4.2 but no luck there either btw
Okay, try flashing with a pit file and the latest stock rom from sammobile.
audit13 said:
Okay, try flashing with a pit file and the latest stock rom from sammobile.
Click to expand...
Click to collapse
Any particular suggestions regarding locating/selecting a pit file?
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
audit13 said:
Is your phone a 16 GB sgh-i337m from Rogers, Telus, or Bell?
Click to expand...
Click to collapse
Its a Bell SGH-I337M 16gb phone
I attached a 16 GB pit file from my i337m.
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
Hi guys,
Yesterday, I installed the official 8.0 update through Odin. Right off the bat, I noticed the settings app was completely broken. I extracted the APK off of another rom on XDA but it didn't change.
I should point out most of the sub-menus available are not clickable, it's just plain text.
Do any of you experience this or am I the only one? Thanks.
How was Odin set during installation? I mean settings, files you used.
hardcore515 said:
How was Odin set during installation? I mean settings, files you used.
Click to expand...
Click to collapse
I used the files found in the official zip over on sammobile and the options in Odin were the default one, I haven't changed anything
First of all - 15 kB/s? You are patient There were better sites to download the firmware from.
Second of all, I think you've flashed home_csc (without factory reset). In situations like this doing factory reset really can help (or try flashing phone again now using csc instead of home_csc). Quite "generic" help I know buuut those things may just work for you.
If you don't want to lose data, you can wait. Maybe someone else can help
hardcore515 said:
First of all - 15 kB/s? You are patient There were better sites to download the firmware from.
Second of all, I think you've flashed home_csc (without factory reset). In situations like this doing factory reset really can help (or try flashing phone again now using csc instead of home_csc). Quite "generic" help I know buuut those things may just work for you.
If you don't want to lose data, you can wait. Maybe someone else can help
Click to expand...
Click to collapse
I used another link provided by an user on the forum on the mega thread "Official stock firmware". I checked and everything was correct so I assume it is the right version of the software.
I actually didn't flash home_csc. I wasn't sure what that was so I didn't want to flash some weird stuff so I left it out.
As far as I remember, I haven't had these problems with leaked vietnamese rom or with s9+ ports. However, I had this problem with the TWRP bump we had on the forum a couple of days ago but the additional options disappeared after a couple of seconds, not sure what was going on.
Did you fixed the problem ?
Yeah you flash the non-home_csc or do a factory reset in recovery mode. It's the system settings data from previous firmware conflicting with it which can only be fixed that way.