Database Users

CM13 for G900FD

CM13 is available: http://www.cmxlog.com/13/klteduos/#
Seems to be quite stable for its early state.
Known issue is that most apps can only read from external SD, but not write because of changes in storage management of Marshmallow.
There are also voices saying LTE & 3G are not working.
Please test and report

Not working LTE and 3G , clean install....

Yeah same here, no LTE 3G. Clean install

Bad news 1st: LTE not working seems to be a known bug, too: http://forum.xda-developers.com/nexus-4/help/cm13-switching-to-wdcma-t3280353
Good news after: It seems to be already merged since yesterday : http://review.cyanogenmod.org/#/c/125897/
I have already flashed today's nightly and maybe, later on, I can sort out if it has been already fixed...

I hava had no problem with LTE/3G since day1.

I only get either G, E, H or H+ connection, but not yet 3G or LTE...

I had no data with 31st december nightly, came back to cm12.1.
I look forward this cm13 is stable !

LTE in Germany works (T-Mobile).

Really? I am German, too, but only G, E, H or H+. Provider is Vodafone.

Really! Perhaps another band?

No problems here. But using external SD is a problem. Any solutions?

No, not yet. Marshmallow has completely new memory management...

Mi Band no works on Bluetooth.
My xiaomi Mi Band no longer works with the cm-13.0-20160112-NIGHTLY-klteduos. Just can not be detected by ROM. Someone with the same problem?

nickaaai said:
Yeah same here, no LTE 3G. Clean install
Click to expand...
Click to collapse
You have to switch to other sim and turn that sim to 2G ( u may not turned to LTE before but it automatically turned into LTE) then switch back to data sim the ntry to change it to LTE or 3G..

shakthivsb said:
You have to switch to other sim and turn that sim to 2G ( u may not turned to LTE before but it automatically turned into LTE) then switch back to data sim the ntry to change it to LTE or 3G..
Click to expand...
Click to collapse
Thank you very much!!!

thiaguinhox said:
My xiaomi Mi Band no longer works with the cm-13.0-20160112-NIGHTLY-klteduos. Just can not be detected by ROM. Someone with the same problem?
Click to expand...
Click to collapse
Possible the same Problem in my reason. The mifit APP detect the miband but can Connect with it because the miband think its still connected with an other phone.
Next update i unpair first.
Gruß

Hello everyone,
I just flashed cm13 and found 2 bugs so far.
1: no setting for disabling either sim cards.
2: no setting for not pressing ok after inserting pin to unlock phone.
Anysolutions yet??

No. CM 13 has not been officially launched yet. It is still under development and proceeds step by step.

I have updated to stock 6.0.1 and updated Bootloader and Modem accordingly.
But from then on, I can't install CM13!
it gets in boot loop.
Has anybody been able to install CM13 after updating bootloader to 6.0.1?

@pc boy: it's not working atm, see https://forum.cyanogenmod.org/topic/125006-cm-13-wont-work-after-official-mm-upgrade/

Help with MotoX Pure on Verizon. Only has cellular data, no voice/sms.

I purchased a used Moto X Pure Edition on Swappa. The phone was rooted, but the seller flashed it back to stock (as far as he told me). I was hoping that I could eventually get the OTA for nougat when it came out, so he assured me that the phone was in "stock" condition.
When I received it, I went to a verizon corp store and got a new sim and they activated the phone on my account. I see 4G LTE and data works great, but when attempting voice calls it says "no cellular network available". SMS messages don't send. I called verizon tech support and we changed some settings around, but it never worked. Guys at the corp store had no clue. The sim works fine in my old verizon galaxy SIII.
Someone on a reddit thread suggested that I check the firmware. It currently reports as: 24.12.18.clark_retus.retus.en.US.retus Does anyone know if this is correct? Is there anything I can do to get this working, or once it's rooted is it really impossible to get it back to stock, or has the seller somehow screwed it up during flashing?
Thanks!
UPDATE: It seems to be fixed after re-flashing the factory image from motorola. I used MPH24.49-18_18 from this page: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#

I'm on VZN - was rooted running CM13 then Slim Rom then went back to stock (PITA) So it can be done ( my firmware : 24.221.4clark_retus.retus.en.US retus) but why would you want to go stock? I only did thinking we were getting Android N soon but that doesn't seem to be happening. Root the phone and throw a custom Rom on it. You will be happier. Have you checked the network type? and the APN?

MedzHovig said:
I'm on VZN - was rooted running CM13 then Slim Rom then went back to stock (PITA) So it can be done ( my firmware : 24.221.4clark_retus.retus.en.US retus) but why would you want to go stock? I only did thinking we were getting Android N soon but that doesn't seem to be happening. Root the phone and throw a custom Rom on it. You will be happier. Have you checked the network type? and the APN?
Click to expand...
Click to collapse
I've switched the network type (global and then LTE/CDMA). The APN that is default selected is Verizon Internet. But, I've tried all the other APNs as well.
I'm worried at this point that I'll never get it to work with voice, whether it is rooted and rom'd or not.

Try Flashing to CM 13 or Slim6 both worked for me.. Please dont hate me for asking.. you sure you have the sim in the right way? I know this try is tricky

MedzHovig said:
Try Flashing to CM 13 or Slim6 both worked for me.. Please dont hate me for asking.. you sure you have the sim in the right way? I know this try is tricky
Click to expand...
Click to collapse
Not hating. I'll take any help I can get. Yes, I'm certain I put the sim in correctly. Cellular data works, and the phone shows as being on the Verizon network, just not voice enabled.
I'd rather not root and flash at this point, as I'm likely going to return it as non-working. Unless someone has any other ideas?

Well, I guess I fixed it. I reflashed the factory image from this page: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images# and the sim is reporting voice and data, and calls and sms are working. I'm not sure what image the guy that sold it to me flashed, but it was obviously wrong or he didn't do it right. Thanks for the help!

Can't connect to LTE

Hi,
So I have only 3G connection on my Note 3, can't connect to LTE. I think it broke down a while ago when I was updating MagmaNX to UX10. ROM was working fine so I decided I don't want to break it down further and decided to go on with just 3G. But recently I decided to switch back to RR N by vidwhal, becuase Magma became laggy so I started playing with different modems and the result was either bootloop on older modems or just 3G connection on later ones. Currently I'm on CP_N9005XXUGBPG1 but I tried almost all of modems and BL from this thread https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504
It's apparently not ROM dependant as it's broken on both MagmaNX and RR N. Any other ideas on how to fix it?
Oh, and GPS also became pretty bad, it takes a few minutes to get the first fix.
If it matters I live in Poland.

Usual reply wipe phone flash stock rom .

Wouldn't connect to LTE on stock as well. Finally I found out it was not my phone's fault but carriers. Other SIM card in my phone has LTE and my SIM in another does not.

mobile network is unavailable after custom ROM install.

Hello Guys,
I bought an S4 and I discovered that I was scammed (it was the sprint version and not the GT-I9500 as it was indicated on my about phone tab). It comes with 4.4.2 and everything was working fine (the only things that bugs me was that I was unable to receive updates). Recently I encountered some little issues so I decided to install a new ROM. I tried the Vanir and Commotio ROM and for a moment I was super satisfied (it was an amazing experience). However after putting back my SIM card, each time I try to deal a call, I got the error "mobile network is unavailable". I thought it was an issue from the ROM I used so I tested the LineageOS and same issue. Finally I tested the STOCK ROM Lollipop and the same issue again except this time the WiFi does not work. Now my phone is completely useless, so can anyone help please ?
PS: When I go to settings->about->status, everything about the SIM info(network, my phone number,...) is set to unknown. the IMEI is intact (non null). IMEISV is 00.

Delayed Texts and Unknown Carrier with Custom ROMs (7.1.2 / 8.1) on Verizon S5-G900V

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!