Related
Hi guys !
I've just bought a samsung galaxy s4 (i9505) (a used one not new) and i flashed Imperium v7 and modem GNF1 and bootloader GNF1 (initially the phone was on stock 4.2.2 and the problem was already there).
My problem is that i don't get the network i rarely see two or three bars but it directly goes to zero (i can see the no network sign) and stays like that until a reboot (as said it drops to no network very fast).
So my question, is it software ? (should i flash the latest samsung stock firmware ?) or is it hardware ? (replace the internal network ship ?)
Or is it a common problem on S4 i9505 and no solution cannot be found ? :crying:
Could it be related to CSC ?
Anyway, i hope anybody can help me because i really like this phone and the rom that i just installed ..
Feel free to ask me about additional informations.
EDIT : I already tried :
1) the modem+bl FNDA => same result
2) force the phone to gsm only => same result (maybe better but even it solves the problem there is no point to not having 3g activated all the time)
mbmb8989 said:
Hi guys !
I've just bought a samsung galaxy s4 (i9505) (a used one not new) and i flashed Imperium v7 and modem GNF1 and bootloader GNF1 (initially the phone was on stock 4.2.2 and the problem was already there).
My problem is that i don't get the network i rarely see two or three bars but it directly goes to zero (i can see the no network sign) and stays like that until a reboot (as said it drops to no network very fast).
So my question, is it software ? (should i flash the latest samsung stock firmware ?) or is it hardware ? (replace the internal network ship ?)
Or is it a common problem on S4 i9505 and no solution cannot be found ? :crying:
Could it be related to CSC ?
Anyway, i hope anybody can help me because i really like this phone and the rom that i just installed ..
Feel free to ask me about additional informations.
EDIT : I already tried :
1) the modem+bl FNDA => same result
2) force the phone to gsm only => same result (maybe better but even it solves the problem there is no point to not having 3g activated all the time)
Click to expand...
Click to collapse
It's going to be pretty difficult to narrow this down with what you've posted. You say the problem was "already there" when you got the phone -- how long did you use it on the stock 4.2.2 rom before flashing a new one? Did you see exactly the same behavior before you started mucking with it?
Hi ! Finally an answer So i used it for about 3 days and i really can tell that it is the same behaviour
My fear is that it may be related to hardware .. I am gonna try to flash the latest samsung stock firmware (with its csc and modem) ?
Anyway any idea ??
mbmb8989 said:
Hi ! Finally an answer So i used it for about 3 days and i really can tell that it is the same behaviour
My fear is that it may be related to hardware .. I am gonna try to flash the latest samsung stock firmware (with its csc and modem) ?
Anyway any idea ??
Click to expand...
Click to collapse
In general I'd say it's worth getting the phone to "current" stock, or as close to it as possible, and seeing what kind of situation you're in (i.e. if the behavior disappears or changes in any way). If you're seeing it on every configuration, it seems reasonable to suspect that it could be a hardware issue -- especially given that you got the phone used.
Perhaps someone else knows of a more definitive test you can try.
Hey ! Thanks for the idea ! already flashed the latest samsung firmware and same problem .. i stayed in touch with the guy that sold it to me so he took it back to samsung sav where his friend (who work there) told him that this is a famous bug in the i9505 4g serie and that the only solution is a
nvm restore (something like that). Of course he'll do it for free cause we agreed that if a problem come out he'll have to solve it on his own.
Anyway, i hope to get it back tomorrow or monday ! I'll let you know what happened as soon as i get it back !
solution?
Were you able to solve the problem? in case u were, how? i have the same issue sometimes i have 3g network, then it goes to gprs then edge, sometimes when im connected to wifi i cant receive calls, but i can do calls, any idea?
Hello guys. I have the n900t, I am now running tweaked s5 base n4 style v6.0. And I run alot of n9005 ROMS as well. With that said here is my issue. For only the past few weeks ( month tops) every time i make or recieve a phone call my data drips down to hspa. The second i hit call and right before my phone rings is when it happens. After my call the data takes a very long time to jump back up. This is a new issue and i have no idea what it is. However, i did flash back to a stock ROM and the issue was solved. And i forget which rom it was but it was soley TE based and there were no issues. I did try to flash a modem but it didnt take. Is anyone else experiencing this problem? Or can anyone suggest a fix for it.
Thank you for your help.
bump.
Still having the issue. I tried to flash a new modem and it just failed anyway. Dont know if I should try a radio. I just cant fivure out why this happened out of no where. I was fine no matter what ROM I was running. Now...this crap. Please guys, 40 people saw this, can SOMEBODY please help.
mattdiehl83 said:
Still having the issue. I tried to flash a new modem and it just failed anyway. Dont know if I should try a radio. I just cant fivure out why this happened out of no where. I was fine no matter what ROM I was running. Now...this crap. Please guys, 40 people saw this, can SOMEBODY please help.
Click to expand...
Click to collapse
1) Quite strange - your picture suggests you are on Verizon yet you comment about a N900T in the forum for the INTERNATIONAL Note 3. On what network are you? Are you aware that there might be network-specific factors involved which could only be visible for other users on exactly the same network in exactly the same region?
2) Try stock ROM (with corresponding stock modem) from a location with very good signal.
5 he physical device is an n900t, however, I am running as of now, the hyper drive note 5 port with n4 UI. When I do flash back to a full stock TW ROM all is good, A FEW TW based ROMs seem to be OK. Like this one, the calls do not affect the data signal. But most ROMs do effect it in that way. You said that it shows I'm running Verizon?
But I am very curious why all of the sudden I am having this issue. I have never had it before. Except with a few specific AOSP based ROMs. I just can't figure out what it is that's causing it. I have done vigorous wipes of the phone to no avail.
And I am in Philadelphia so there really is no place that is actually bad reception (except in the susubways of course...lol)
And thank you for your reply.
mattdiehl83 said:
5 he physical device is an n900t, however, I am running as of now, the hyper drive note 5 port with n4 UI. When I do flash back to a full stock TW ROM all is good, A FEW TW based ROMs seem to be OK. Like this one, the calls do not affect the data signal. But most ROMs do effect it in that way. You said that it shows I'm running Verizon?
But I am very curious why all of the sudden I am having this issue. I have never had it before. Except with a few specific AOSP based ROMs. I just can't figure out what it is that's causing it. I have done vigorous wipes of the phone to no avail.
And I am in Philadelphia so there really is no place that is actually bad reception (except in the susubways of course...lol)
And thank you for your reply.
Click to expand...
Click to collapse
1) Your avatar mentions Verizon for some reason.
2) If it is all OK with the stock ROM then it is a problem with the custom ROM, ask in the specific thread for that specific ROM. Most likely it has something to do with the modem and the corresponding RIL.
So when ever a new ROM is flashed the modem is flashed as well. Unless the dev says otherwise?
Hi at all! I'm new on this forum, so I hope I didn't break any rule. Anyway, I'm trying to recover a friend's phone, a Samsung Galaxy S3 (i9300) International Version.
He said he installed a rom called "Android Revolution HD", which appears to be an improved version of the stock rom. Anyway, now the phone does not register on the network.
The IMEI in the settings menu is correct, also the signal appears to be ok, but when I try to select a network, the phone does not register.
So, I tried almost all the solutions I have found on this site, from trying a bunch of different modems, to installing the whole stock ROM (Android 4.3).
But none of these worked. So, there is a real solution I can try?
Thanks in advance!
TestDriver89 said:
Hi at all! I'm new on this forum, so I hope I didn't break any rule. Anyway, I'm trying to recover a friend's phone, a Samsung Galaxy S3 (i9300) International Version.
He said he installed a rom called "Android Revolution HD", which appears to be an improved version of the stock rom. Anyway, now the phone does not register on the network.
The IMEI in the settings menu is correct, also the signal appears to be ok, but when I try to select a network, the phone does not register.
So, I tried almost all the solutions I have found on this site, from trying a bunch of different modems, to installing the whole stock ROM (Android 4.3).
But none of these worked. So, there is a real solution I can try?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem for months now i have tried a lot of solution but nothing works. i am hoping a senior member can help fix this issue. And just incase some has a viable solution, they should kindly help out. :fingers-crossed:
What I think is you've updated it from 4.1.2 without any EFS backup. Well I had been through the same situation and couldn't find I single thing. In the end I had to get my S3 repaired from a local shop. I think you should go too.
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!
Okay, so I used to love rooting my phones, but I mostly dealt with flagship phones in the US which made rooting and flashing a cakewalk. I understand some of the nitty gritty, so when I got my first phone in Japan, I was super excited about rooting it. But after reading this forum for hours, I have so many questions...my phone build is A2017G JPV1.1.0B03.
I read this but this mostly focused on using an update on this phone.
https://forum.xda-developers.com/axon-7/help/a2017g-japan-to-a2017g-european-a2017g-t3608411
1. If that thread is correct, that means I technically just have the European version of the phone with Japanese modems installed. Is that correct?
2. Also, does that mean (if I were not to root the phone) I would need to install a European Axon 7 Oreo update for it to actually work on the phone? Would the US version fail?
3. I can't seem to find the modem for my phone. I can upload some screenshots later but can someone clarify if I'm right that it's a "B03" or am I looking at the wrong information?
4. There is no Oreo release for Japan, so does that mean I can't flash an Oreo ROM because there won't be any modems for this?
That's all for now, but I'm sure I have a lot of follow-up questions to your answers. Your help is greatly appreciated.
Unlock bootloader, install twrp, instal "G" model bootstack, instal any custom rom, then flash "G" modem in twrp, reboot. No matter where you device are from, the model matters. If its "G", its a european version and its only what you need to know. If you want stock oreo and didnt recieve through OTA, download the update in ZTE website for your "G" version, put it in a sdcard then reboot your phone to recovey then select "install update from sd card" option.
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
RobboW said:
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
Click to expand...
Click to collapse
I'm so used to dealing with multiple modems for the same model of phone in the US (between the major carriers and stuff) that I was overthinking it.
Thanks a ton. That simplifies things so much...and also makes me wonder why updating never occurred for the Japanese release. It's not like there isn't language support for newer versions of Android, but maybe not for the MIUI? I need to be more careful choosing my next phone then, though probably it should be an AOSP phone like the Zenfone or Pixel.
Guess I have my work cut out for me this weekend. Time to run a giant backup and start rooting. Thanks again for all your help. I like this phone (though I often accidentally hover/touch the home button when typing, and I hope there's a sensitivity fix for that :laugh so I want it to last for a while before I get my next one.
It's still a good phone, I look at new phones and think, hmmm, nice, but what will I gain on a daily basis? Nothing more to be honest. The A7 has enough power for me still. The one thing I could really use would be a higher capacity battery. Was looking at Huawei phones but now, well.....
For updates, they had issues with OTA and reverted to only releasing for a whole ROM download for update from SD card.
I personally won't apply an OTA for mine even now at Oreo. Must be a whole ROM to flash with the updater. That's all I've done with it since purchase and it works great still. A lot of people seem to have all sorts of weird issues after applying OTA updates.
Sweet. As someone with some experience with this stuff, do you have any tips or tricks I should know moving forward? I'm going to try rooting it tonight.
-EDIT: Quick little question, my phone says the Android version is 7.1.1 but that would be Nougat, right? Or is it actually Marshmellow?
7.1.1 yeah, Nougat. That doesn't make sense from your first post.
Was it used when you got it or new? Have you checked the model from what's on the back of it, not what software says it is?
I keep mine stock, can't advise on rooting etc. I use it with personal and work SIMs and it has to pass requirements including encryption to run Microsoft InTune and our company portal and use it in work mode. Bootloader hasn't even been unlocked. The most I did was uninstall some built in user apps through ADB.
I also have a 2017G bought in Japan. I unlocked it and worked on it based on this forum, and I can say that it behaves as any other 2017G. I am not interested to use the stock ROM, but yes, I remember that it was on Nougat version when I received it.
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
darth_antz said:
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
Click to expand...
Click to collapse
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
The Zenphone 6 is looking a viable buy now.
My Axon 7 is still good so not really looking but I did just get a new Axon 7 Mini for use as a media player. It still has AMOLED screen, stereo speakers, headphone jack, DAC for the jack etc. No hi res bluetooth though. Cost me AU$149 new in box from retail store. Bargain! How much is a dedicated music player which is crap at movies or just cant do them?
Chucked my 128Gb SD in. Sounds good playing through the car hifi, lower 3.5 jack output matches HU aux in impedance better than Axon 7 which can overload the input at high volume. Very balanced and clean sound.
TheZen said:
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
Click to expand...
Click to collapse
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
darth_antz said:
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
Click to expand...
Click to collapse
I bought it at Rakuten Mobile. There was a super sale and it was like 80% off, lol.
I tried using the guide over the last couple of days and no matter what I've done, I can't seem to get to recovery after doing the flashing (step 9). I was able to flash a stock image back on, but then when I try again it's the same results. I'm at a loss as to why but...there's another guide using the Axon7Tool.
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
The downside is that I work two jobs tomorrow so I won't have time to try this new one out but I think I downloaded everything already. This is kinda frustrating though..
-EDIT: I used the unbricking guide to EDL flash the B10 Nougat and it is a different experience than what I had before...geez, seems the Japanese version was severely neglected. If I run into problems with the other guide I feel comfortable EDL flashing Oreo. Really appreciate the support guys, let me know what you think. Before I started this, my battery was lasting barely 8 hours with only LINE and Chrome being the main background apps...
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
GeoffUK said:
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
Click to expand...
Click to collapse
you can't. There are 3 modem variants by region (US, china, global) and many versions for each, but they are not interchangeable and flashing another has already wiped some IMEIs long ago (doesn't always happen though)