Related
So Ive had this Verizon Note 3 since day one. Finally unlocked my bootloader... What are the rules on what I can and can't do now. Can I install any Android rom? Can I only install note 3 roms from any carrier... Can I install only Verizon note 3 roms? Or is it a hybrid... I can install any rom if I replace the firmware and or modem.
I really want something on 7.1 but I'd rather take 6 and have something custom... Fast and responsive.
Thanks community.
You are in luck. :crying:
There's hardly anything to choose from; maybe 3 or 4 ROMs and about the same number of kernels.
AFAIK, there are no Nougat ROMs and only one Marshmallow ROM (AryaMod6.6).
Normally, when a dev ships a "ROM", there are two important pieces: the /system image (what some folks call "the ROM"), and the boot image. The boot image is what some folks erroneously call "the kernel"; but it is really a combination of kernel + ramdisk. The ramdisk has all the scripts in it that the "init" process reads to start up all the low-level daemons and services... as well as the Android UI as well.
The kernel is very tightly tied to the specific hardware in a given handset - both the processor/gpu and all the sensors/leds/peripherals.
So that's the reason you can't just flash any old ROM. In the least bad case, your device wouldn't boot; in the worst bad case the kernel would boot up far enough go off in the weeds and possibly damage some of your hardware.
You might be tempted to think "we'll, what if I find a boot image for the "hltevzw" SM-N900V device... can I flash that after I have flashed 'any old Android ROM'? Won't that take care of things?"
Well, not really. The system library binaries in /system are possibly compiled with instruction-set optimumization tweaks that are only supported by specific CPU and GPU hardware chips. Moreover, other peripheral chips such as GPS have unique "downloadable" vendor firmware in the system image... so again, there's the issue of hardware dependencies of the /system image.
Beyond that, there's carrier-specific "setup and activation" software that differs between ROMs, so even using ROMs that are from a different carrier's version of the exact same handset hardware might not work fully - specifically in the telephony function areas. Everything else might work fine though. For instance if you wanted to use the device as a WiFi-only unit for kid's games etc.
Note BTW that the "International" Note 3 GSM phones are not the same hardware - they use an Exynos processor.
good luck in your quest
Thanks
That was very helpful... Looks like Araya is my best bet. I'll leave jasmine rom to try it.
I was hoping that I could get another note 3 rom on this forum and flash the CDMA modem for networking... But doesn't seem like that's an option.
If I'm still stuck to Verizon Note 3 rom... What is the purpose or benefit of unlocking the bootloader... Was that really just to avoid Odin so I can flash my couple rom choices easier?
I appreciate your time!
cyberoptics said:
That was very helpful... Looks like Araya is my best bet. I'll leave jasmine rom to try it.
I was hoping that I could get another note 3 rom on this forum and flash the CDMA modem for networking... But doesn't seem like that's an option.
Click to expand...
Click to collapse
I might have very slightly overstated the case for pessimism. There is a "consolidated" Verizon Note 3 Forum which is meant for devs to provide development tools and even ROMs that could potentially be used on devices from more than one carrier. But the world being organized the way it is, that means that you are more likely to find multi-carrier GSM ROMs over there than multi-carrier ROMS which support GSM and oh by the way CDMA and LTE as well.
If you want to fool around over there, I recommend that you proceed with great caution to make sure that the ROMs you choose specifically target Qualcomm MSM8974AB Note 3 handsets, and you should read the developer notes very carefully to see whether you need to flash an "hltevzw" kernel separately. If the dev does not mention "supports hltevzw" or "supports N900V" (for example here) you might be taking chances with your hardware.
I suppose it is possible that the radios are 100% "software defined" in the sense of which bands they can support. Maybe you can get what you want by simply flashing the desired carrier's "modem" firmware, but I have never done that so I can't say for certain whether that works or you are risking a brick (or hardware damage) by doing that. I simply don't know (e.g.) if the chips and antennas in a T-mo version of the Note 3 are identical or different from a Verizon Note 3's hardware
cyberoptics said:
If I'm still stuck to Verizon Note 3 rom... What is the purpose or benefit of unlocking the bootloader... Was that really just to avoid Odin so I can flash my couple rom choices easier?
I appreciate your time!
Click to expand...
Click to collapse
Well, for one - having a custom recovery allows you to make backups - even if you never change ROMs
People don't think of backups as being "sexy", but they allow you something which is really valuable: freedom to mess around and experiment with the knowledge that "if something goes wrong, I'll just restore the backup".
And with Odin, you only had the choice of Stock Roms. Now you have a few more.
cheers
Yes you can install Any rom for note3
Here is my experience with installing roms on note 3 after unlock bootloader
you should Flash twrp-2.8.7.0-hlte-4.4.img by ODIN for the hlte roms or twrp-2.8.7.0-hltevzw-4.4.img if you looking to flash verizon roms ,
im on Phronesis Rom N7 now and i tryed many roms
AryaMod N7 & S7 Edge
MagMa-NX from NXT TEAM
Resurrection Remix Nougat 7.1.1
CM 13 ROM 6.0.1 for Trader418
Purify CM13 6.0.1 ( the best CM13 till now )
and more ...
i have only one problem that i cant get LTE in mobile network always on H+
i tryed to add screenshot but i couldn't its my firist reply :laugh:
@ALPHA85
Pretty informative first post - thanks, and welcome aboard!
Are you on a Verizon SIM? If not, have you been flashing modems from other Note3 devices?
Just curious; I don't have much experience with radio issues or carrier activation issues. Trying to port a carrier-specific ROM elsewhere (esp starting from a VZW ROM) looks like a massive pile of interlocking software dependencies, though. My respect to anyone who can succeed at it.
Feel free to write a brief summary about what's broken in each - any of them have NFC working? I was on CM13 (trader418) for a long time and would have been happy to stay there were it not for all the GPS issues.
Thank you ,:angel:
i dont use Verizon SIM becouse im from egypt, i bought my verizon note 3 by wrong , when i bought it i saw N9005 under the battery and in the boot screen also inside the rom ,it was lollipop 5.0 ,but sinse i did factory rest i surprised it change to N900V even the imei changed , till now i cant understand how they flashed N9005 rom for N900V device with locked bootloader
i'm on OF1 bootloader unlocked and i flashed PL1 Modem i thought maybe it help me to get LTE but still the same H+
about NFC i really didn't try it at all , i always disable it by titanium pro
ALPHA85 said:
when i bought it i saw N9005 under the battery and in the boot screen also inside the rom ,it was lollipop 5.0 ,but sinse i did factory rest i surprised it change to N900V even the imei changed , till now i cant understand how they flashed N9005 rom for N900V device with locked bootloader
Click to expand...
Click to collapse
When you first got it, did it appear to have a Verizon ROM on it? (For instance, the Verizon splash screen?) Or some other carrier's logo?
Actually, that cleared something up for me. Well, except for the part about the IMEI changing
Apparently there were both LTE and GSM models of the "Note 3" that were sold in international markets. I understand the LTE version was originally sold in China, but the GSM model is more common?
The SM-N9005 is an LTE phone (I don't know about CDMA) with the Qualcomm MSM8974 processor
and the N9000 is the GSM model with an Exynos 5420 processor
So that probably explains the binary compatibility of the SM-N900V and the SM-N9005 - same processor, and both phones were designed for LTE service.
But your report should give @cyberoptics a little less pessimistic view of things; thank you for that.
But I wouldn't go so far as to say you can flash ANY Note 3 ROM. Even though both the Exynos and Qualcomm processors use ARM cores, they are fairly different - the Exynos has 8 cores, half of which are Cortex-A15, and the MSM8974 has only four cores which are Krait- something or other. I think they are not quite compatible. Note that in theory, ARM code that was compiled to earlier standards (e.g. thumb, armv5) would certainly work on both devices - but if they compiled ALL the code in ROM libraries that way they would be giving up a lot of performance on either device. So.... to the extent that they target processor specifics for either Cortex-A15 or Krait, they will be incompatible.
cheers.
bftb0 said:
You are in luck. :crying:
There's hardly anything to choose from; maybe 3 or 4 ROMs and about the same number of kernels.
AFAIK, there are no Nougat ROMs and only one Marshmallow ROM (AryaMod6.6).
Click to expand...
Click to collapse
bftb0 I just wanted to thank you once again for your consistently helpful, verbose posts about the N900V. I've been using CM13 thinking it was the best thing going, when, as nice as it was at the time, it doesn't hold water compared to AyraMod, which I switched to yesterday after reading this thread.
Now my GPS won't take me sailing past Easter Island when en route to a noon meeting downtown. Maybe Google Cardboard will even work, now that NFC appears to.
Thanks again, and please don't ever bore of being a great and helpful resource, we need you!
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
drewcu said:
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
Click to expand...
Click to collapse
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Fear_The_Fluff said:
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Click to expand...
Click to collapse
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
drewcu said:
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
Click to expand...
Click to collapse
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
drewcu said:
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
Click to expand...
Click to collapse
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Fear_The_Fluff said:
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Click to expand...
Click to collapse
Thanks for the quick reply!
You tried the deleting the modems fix or the link in your prior post for your Spring S5? And what is a "forget network" fix -- just resetting all network settings in Android?
Yeah I was really hoping the replacement SIM would fix it but sadly it was a dead end.
I have tried several messengers like the stock Lineage one, Google Messenger, and landed on Textra because it has the most configuration options.
Yeah I tried Odining modems from both the link you referenced and extracting them myself from the firmware. Not sure if this is essentially the same thing as overwriting the modems in the corrupted TWRP modem guide. I am tempted to try this over the weekend after making an EFS backup. Hard for me to believe that deleting modemst1 partitions and not restoring them afterwards as is what seems to be the fix... Does the system automatically rebuild them or something?
Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
drewcu said:
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
Click to expand...
Click to collapse
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Fear_The_Fluff said:
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Click to expand...
Click to collapse
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
My Verizon S5 (this is the working phone) is a CID 15 (I don't have the phone with me right now to get the CID ID), I can look around for the setup I used. It was some months ago when I ran the bootloader unlock and root. BUT! the phone I had an issue with the LTE was a sprint S5 that was unlocked for years before they started locking the bootloaders. This bug affects all carriers, but mostly sprint and verizon.
drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Fear_The_Fluff said:
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
drewcu said:
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
Click to expand...
Click to collapse
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Fear_The_Fluff said:
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Click to expand...
Click to collapse
Pretty sure this whole unlocking the bootloader on CID 15 requires that you change your CID to match the Developer CID. I know that my current CID is referenced in the thread https://forum.xda-developers.com/ve...locking-galaxys-s5-bootloader-t3337909/page39 back when this was all just coming out (and when I first unlocked it using the old method 4 - https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909). I used to have a different CID that's saved somewhere else.
Any chance you can look your CID to see if it matches 1501004d414732474300bd6d97165100?
Thanks!
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
Worry not, I have the same problem on an international unlocked G900F.
The problem is inexistent on latest stock firmware, but it is present on the Oreo custom roms i've tried so far, such as lineageOS, CrDroid, Resurrection Remix.
The Only Workaround i've found so far is to enter the info menu on lineage os, dialing *#*#4636#*#* and turning off radio and On, on the Device Information menu, also updating SMSC proved to work on a few ocasions.
Needless to say, I've tried EVERYTHING this forum suggest, such as full wipe from stock recovery and running latest stock for a few days, or even flashing the latest baseband alone, but it doesn't work. I've read some interesting post about this issue on a Xiaomi Oreo device, and i'ts supposed to be an issue of Oreo roms and the way it measures the signal bars, but no fix so far.
Anyway if anyone finds a way to fix this annoying issue on the next Lineage16 I'd be grateful
Having similar issues with G900V on verizon. I've tried many ROMs old and new, latest LOS16 / RR. also I've tried other network fixes as in original post, and different hardware. I have a few of these, all EMMC15 unlocked bootloaders
Are there any developments here?
Weird thing is, SMS/MMS/calling 'works' two blocks away but I always have the 'roaming indicator off' no matter where I am, and there is a delay in sms IF it work at all. Also, this just started last month. (?) I've been using LOS 16 without network issues for a few months prior. It's is possible Verizon has changed something in the service in my area? I went to verizon to verify compatibility and try a new sim, they were mostly useless but otherwise confirmed that the g900v was on the 2020 list of compatible phones. been trying older builds (including starting fresh on the one that was working last month) but nothing but using stock QL1 magisk rooted ROM works - and that one works very well, reliable, and fast. everywhere. grrr, I'm not ready to retire my fleet of s900v, and I would rather retire them than go back to MM if this can't be fixed.
Hi, first post here. Installed TWRP and upgraded my wifes phone to LineageOS 16. Most things are working well, but the menu key is constantly activating without a key press. I'm a networking guy by trade and phone fiddling not really my strong point. My Google Fu always seems to fail me in situations like this too.
Any ideas? There's also an issue with Bluetooth which constantly crashes if used. Do I need to raise a new thread for that?
The phone itself is a UK version, so that's also a bit confusing when there's builds offered for AT&T, Sprint, Verizon etc. Also I've not upgraded further past this nightly build. Should I try this? Am I right in that the process should be to wipe only system partition then apply the upgrade?
Cheers.
Oh if you need me to post any further details about phone or whatever just shout and I'll get on it.
Reads as you may have installed for the wrong phone model .
I don't think so. The options presented to me over at download.lineageos.org were;
Galaxy Note 3 LTE (N9005/P) hlte
Galaxy Note 3 LTE (N9008V) hltechn
Galaxy Note 3 LTE (N900K/L/S) hltekor
Galaxy Note 3 LTE (N900T/V/W8) hltetmo
The phone model number is SM-N9005 and so the specific image I installed, after a full backup and full wipe is;
lineage-16.0-20200905-nightly-hlte-signed.zip
Non xda rom suggest you go back to the source .
Is there another rom that anyone could recommend?
So back when I got my phone in Feb 2020, I did what most people do when they have a new device, update it. After some googling, I found plenty of threads about how great the google version of Android 9 is for the v35. Removing the ATT bloatware was my main reason for flashing to it.
I've read on a few different websites that if you flashed to the stock google android 9 rom, that there is no way to flash back to the ATT roms, or upgrade to the current android 10 att rom. My phone is unlocked and is of course, the ATT version.
Model: LM-V350AWM (doesn't show that it's google I guess)
Hardware: Rev 1.0
I have not bought an ATT sim card or gotten there service to upgrade because of what I read. Is it possible to flash back to stock ATT ROMs or to OTA with an ATT sim if I flashed to the google version? Anyway to go back (stock 8.0 even)? I really don't want to switch to a new phone since I got this baby for 190$ and finding something equally good or better in this price range is not happening. I'd appreciate any information you guys have on this.
Thanks!
It isn't clear from your note what you want to do. If your objective is to get to A10, I highly recommend following cloud's guide to localize the Korean A10 rom. That would require unlocking the bootloader. Everything on that rom works at least for me and my use cases. Browse around here in the v35 forums and you'll find the threads you need.
If your aim is simply stock A10 with ATT, there is one option. Someone posted a partition dump. You could try writing partitions one-by-one usind qfil. I haven't seem any reports of anyone doing that....
Okay. So is it confirmed that if you flashed the stock Google Fi Android 9 onto your att phone that you can't flash back to atts? Different partition sizes end up bricking the phone? I can't find any att kdz anyway. Not even the older android 8. I know att $oesnt release theirs but plenty of folks normally upload their stock kdz for the community.
Really confused with how dead the LG V30/35 community has been since day 1. I remember when I was learning how to root my viewsonic g tablet and galaxy 3 (2011-12) the forums were bursting with people and stock kdz loaded everywhere. And 30 different roms were being worked on for one device. I think the galaxy S5 community is still more active than this one. Smh
Thank you for the reply. I'll look for the post you mentioned. I haven't worked or played around with modifying android in 10 years. Only thing I've done is a quick flash of googlefi kdz back in 2020 which was brainless. Just looking at the tutorials to root this phone seems daunting now lol.
Jebsauce said:
Okay. So is it confirmed that if you flashed the stock Google Fi Android 9 onto your att phone that you can't flash back to atts? Different partition sizes end up bricking the phone? I can't find any att kdz anyway. Not even the older android 8. I know att $oesnt release theirs but plenty of folks normally upload their stock kdz for the community.
Really confused with how dead the LG V30/35 community has been since day 1. I remember when I was learning how to root my viewsonic g tablet and galaxy 3 (2011-12) the forums were bursting with people and stock kdz loaded everywhere. And 30 different roms were being worked on for one device. I think the galaxy S5 community is still more active than this one. Smh
Thank you for the reply. I'll look for the post you mentioned. I haven't worked or played around with modifying android in 10 years. Only thing I've done is a quick flash of googlefi kdz back in 2020 which was brainless. Just looking at the tutorials to root this phone seems daunting now lol.
Click to expand...
Click to collapse
AT&T does not release kdz. Don't know why you think that needs to be confirmed. Partitions for AT&T A10 have been dumped. You can write them one by one by qfil.
As to why V30/V35 development is dead, a huge factor is that lg exited the mobile phone market. LG, despite making good hardware, was also not developer friendly. The V35 is 4 years old.
As for rooting a V35, just follow the instructions if that's what you want or move to newer models with 5G, more memory, and greater battery capacity.
I am still rocking my V35 Fi phone happily.
cmrntnnr said:
AT&T does not release kdz. Don't know why you think that needs to be confirmed. Partitions for AT&T A10 have been dumped. You can write them one by one by qfil.
As to why V30/V35 development is dead, a huge factor is that lg exited the mobile phone market. LG, despite making good hardware, was also not developer friendly. The V35 is 4 years old.
As for rooting a V35, just follow the instructions if that's what you want or move to newer models with 5G, more memory, and greater battery capacity.
I am still rocking my V35 Fi phone happily.
Click to expand...
Click to collapse
I thought people who were more tech savvy than me could pull a stock KDZ off their own ATT phone. That's what people did in the past anyway (I believe).
The phone is still great and I'm glad you are happy with it. I just wanted android 10 on my phone. Stock. English. I might try the Korean route since I'm less likely to brick my phone. Who knows, we'll find out. Thanks for the replys.
The localized A10 Korean rom has been fantastic for me. Everything works.
Make sure you backup ftm and efs partitions before starting. You will lose the S/N but it is easily restored. If you are in US, I suggest you flash the localized OP partition. Links are in the localization thread started by cloud.