Hello all,
I purchased a Galaxy A52 4G dual-sim model, and am (mostly) very happy with it. I bought it specifically for two reasons: because of the dual sim support, and the fact that there was a LineageOS rom available here at XDA. So, I promptly unlocked the bootloader and flashed TWRP and LineageOS 19.0 (big thanks to Simon1511 for his work on that!).
Everything is working great except for the second sim slot, which ranges from almost-functional (everything except voice calls work, no audio at all in call) to completely non-functional (cannot even connect to the tower), depending on which of my SIMs I put in it. The other slot is fully functional with either sim.
I noticed under Settings->About Phone that the phone reports it's model as SM-A525F, but the baseband version shows as A525MUBU4BVC2. According to the info at sammobile.com, that version is intended for an SM-525M, which this phone says it is not. I have no idea how that happened, and I wish I had done some testing with the phone when I first got it, before blowing away the stock rom. Ah well.
Hoping that my sim slot problems are the result of the wrong baseband firmware being installed, I downloaded the latest version for the SM-525F from sammobile (A525FXXS4BVD1), extracted the modem.bin and NON-HLOS.bin files, and tried flashing them to the device using Heimdall v2.0.1 (Linux user here, so Odin isn't an option and the 'official' Heimdall v1.4.2 threw various libUSB errors. v2.0.1 is an unofficial fork that worked, used it to load TWRP without problems.).
It uploaded, but the download mode screen displayed SECURE CHECK FAILED, and after rebooting the version listed under settings had not changed. Everything still works as well as it ever did, which is nice. Knowing that a mistake in this area could potentially brick the phone, I decided to create an XDA account and post here looking for some advice before making further attempts.
As I was putting this post together, it occurred to me to check the invoice. I bought it through Amazon, and it was listed as an A525M on the invoice, for what that's worth. And, the fine print on the back of the phone itself reads SM-A525M/DS. So perhaps it is an SM-A525M and the baseband version is correct, with the settings showing model: SM-A525F being the error. That would explain why the baseband firmware wouldn't flash, it knows it's not the correct bin file for the phone.
I suppose there is also the possibility that it's simply a hardware problem, and the second sim slot has something physically wrong with it.
Can anyone point me in the right direction?
Hi,
I'm certainly in no capacity to guide you, but I just brought the phone myself and have been lurking this forum to harvest a few guidelines. Regarding LineageOS, I saw there might be some problem with Dual Sim there :
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com
It could be you have the same issue as the guy and this is not related to your baseband firmware?
If I may ask, as a fellow Linux user myself, would you mind describing the guidelines to use download a working version of Heimdall and use it to flash e.g. TWRP on the phone? That would be much appreciated.
Flash the proper firmware for your device using odin. Then try installing lineage again.
@Flyos: I haven't seen or used any options for turning off SIM slots, so hopefully that isn't part of the problem. The source for the copy of Heimdall I used is available at https://git.sr.ht/~grimler/Heimdall/ . You'll have to compile it yourself.
@Ryzen5950XT: Thanks, but that's not terribly useful advice, given that part of the problem is that the device is giving me conflicting information regarding it's model number.
I'm still going to take it, though. I'll assume it actually is an SM-A525M and go from there. And I'll use Heimdall. It's served me well with every other samsung phone I've used, and Odin simply isn't an option without Windows, which I don't have and am not interested in getting.
ralanar said:
@Flyos: I haven't seen or used any options for turning off SIM slots, so hopefully that isn't part of the problem. The source for the copy of Heimdall I used is available at https://git.sr.ht/~grimler/Heimdall/ . You'll have to compile it yourself.
@Ryzen5950XT: Thanks, but that's not terribly useful advice, given that part of the problem is that the device is giving me conflicting information regarding it's model number.
I'm still going to take it, though. I'll assume it actually is an SM-A525M and go from there. And I'll use Heimdall. It's served me well with every other samsung phone I've used, and Odin simply isn't an option without Windows, which I don't have and am not interested in getting.
Click to expand...
Click to collapse
There should be a sticker on the box the phone came in that tells you which variant it is.
...yes, and I touched on that, in the original post. The phone is physically stamped SM-A525M/DS, the Settings->About Phone page says SM-A525F, and the baseband version indicates SM-A525M again. Conflicting information.
Which is why, two-to-one, I'm assuming SM-A525M is correct, and will follow your advice and reflash the stock firmware, downloaded from sammobile.com.
Hello,
You can install Phone INFO ★SAM★ 3.8.5 to see the result
Phone INFO ★SAM★ 3.8.5 APK Download by vndnguyen - APKMirror
Phone INFO ★SAM★ 3.8.5 APK Download by vndnguyen - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Phone INFO pour Android - Téléchargez l'APK
Téléchargez l'APK 3.8.5 de Phone INFO pour Android. All-in-One Info et outils pour les appareils Samsung.
apkpure.com
Ok, did a bit more testing, pretty sure this is a problem with the LineageOS rom.
Re-flashed the latest stock firmware for an SM-A525M from sammobile.com (used the brazil firmware), and Settings->About Phone now reports the model as SM-A525M/DS, which is correct. Baseband firmware version did not change, nor did I expect it to.
Tested each sim individually in each slot, then both slots together, then swapped sims between slots. Audio worked in every voice call, regardless of which sim was used for the call or which sim was where.
Then I re-flashed LineageOS as per the instructions.
Starting with the VBMeta_Disabled image, then a recovery image (Used the LineageOS recovery from that thread this time, used TWRP from the TWRP website on the previous attempt), then LineageOS, MindTheGApps, and Magisk.
After re-booting Lineage, the phone once again reports it's model as SM-A525F under Settings->About Phone, and neither sim has working in-call audio when in slot 2, regardless of whether the other slot has a sim in it.
I'll add a post to the thread linked above to report the problem, and crosslink to this thread for reference.
For the moment, I've put the sim cards back in the phones I pulled them from and shelved this A52. I'll try again when a new release is available, and see what happens.
Thank you Flyos and Ryzen5950 for your assistance!
ralanar said:
Hello all,
I purchased a Galaxy A52 4G dual-sim model, and am (mostly) very happy with it. I bought it specifically for two reasons: because of the dual sim support, and the fact that there was a LineageOS rom available here at XDA. So, I promptly unlocked the bootloader and flashed TWRP and LineageOS 19.0 (big thanks to Simon1511 for his work on that!).
Everything is working great except for the second sim slot, which ranges from almost-functional (everything except voice calls work, no audio at all in call) to completely non-functional (cannot even connect to the tower), depending on which of my SIMs I put in it. The other slot is fully functional with either sim.
I noticed under Settings->About Phone that the phone reports it's model as SM-A525F, but the baseband version shows as A525MUBU4BVC2. According to the info at sammobile.com, that version is intended for an SM-525M, which this phone says it is not. I have no idea how that happened, and I wish I had done some testing with the phone when I first got it, before blowing away the stock rom. Ah well.
Hoping that my sim slot problems are the result of the wrong baseband firmware being installed, I downloaded the latest version for the SM-525F from sammobile (A525FXXS4BVD1), extracted the modem.bin and NON-HLOS.bin files, and tried flashing them to the device using Heimdall v2.0.1 (Linux user here, so Odin isn't an option and the 'official' Heimdall v1.4.2 threw various libUSB errors. v2.0.1 is an unofficial fork that worked, used it to load TWRP without problems.).
It uploaded, but the download mode screen displayed SECURE CHECK FAILED, and after rebooting the version listed under settings had not changed. Everything still works as well as it ever did, which is nice. Knowing that a mistake in this area could potentially brick the phone, I decided to create an XDA account and post here looking for some advice before making further attempts.
As I was putting this post together, it occurred to me to check the invoice. I bought it through Amazon, and it was listed as an A525M on the invoice, for what that's worth. And, the fine print on the back of the phone itself reads SM-A525M/DS. So perhaps it is an SM-A525M and the baseband version is correct, with the settings showing model: SM-A525F being the error. That would explain why the baseband firmware wouldn't flash, it knows it's not the correct bin file for the phone.
I suppose there is also the possibility that it's simply a hardware problem, and the second sim slot has something physically wrong with it.
Can anyone point me in the right direction?
Click to expand...
Click to collapse
Do you happen to know the exact build BEFORE you flashed a custom firmware?
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com
Bugs
Fingerprint sensor on A72
No audio in calls with second SIM card
Related
I need help. I happen to get my hands on a note 7 sm-n930x live demo unit here in Denver, CO, USA
SM-N930X UD
S/N RF8H71JQGFD
64GB
Exynos 8890 SoC
4x Exynos M1 @ 2.3 GHz
4x Cortex A53 @ 1.6 GHz
Mali T880MP12 GPU
I had it running by flashing a sm-n930f firmware to it, which I understand is the same phone. I then attempted to flash the hydra rom and now I can only access download mode and it stays on the "Hydra Rom N7" splash screen. I dont remember the original phone info because the paper it was written got tossed out. To further my string of bad luck the SD that stored the NAND got corrupted.
I've tried to wipe everything via PIT and reinstall the 930f firmware, but it always fails. Sometimes it fails immediately and other times it actually starts installing for a moment and then fails. I've tried to install Hyrdra again and it fails. I've repartitioned in an attempt to wipe it without success. Info on the 930x version is hard to come by as I've come to find out. Today I finally found the fw listed below is the stock firmware for the international version, but the only downloads I can find are in a foreign language and want me to pay for it which I don't trust at all. At least I think these are the stock for the 930x, please correct me if I'm wrong.
I'm not sure of the baseband because someone threw away the paper I had written it on or the imei # which is all zeros with a one on the end now . How can I fix the loop and get it working again? Is it failing because I can't wipe the cache through recovery and it's too much overwriting at this point? Since this is the "x" international variant, is it accepting of any of the exynos roms? Does anyone have access to the firmware versions below that they could share with me or clue me in as to where I can find the downloads myself?
My goal is to get the Note 7 working again with hydra, or any other rom. I just need it to work and be able to use it on my carrier which is currently at&t. I may have tried to flash the wrong ROM, the efs could be missing, andi know the imei is gone. It is probably safe to assume all are true.
Do I need to repair the imei before it will accept an install? If so, how would you suggest? I have QFIL, QPST, SPC but am unsure exactly how to utilize with great affect as I'm still teaching myself or if they are the correct programs that I need in order to remedy my situation. I'm no pro but I'm not a newbie either. I'm great at following detailed, precise instructions so please guide me to resurrecting my Note 7. I'm not sure what happened but I know I can fix it with a little assistance. All guidance and suggestions are welcomed and greatly appreciated. Cheers
SM-N930X
By admin | Published: September 19, 2016
N930XXXU1APG5_N930XPAP1APG6_All Country Android 6.0.1_3File Firmware
AP_N930XXXU1APG5_LLK_CL8613421_QB10283666_REV00_user_low_ship_meta.tar.rar
BL_N930XXXU1APG5_LLK_CL8613421_QB10283666_REV00_user_low_ship.tar.rar
CSC_PAP_N930XPAP1APG6_LLK_CL8613421_QB10300978_REV00_user_low_ship.tar.rar
N930XXXU1APG5_N930XPAP1APH2_All Country Android 6.0.1_3File Firmware
CSC_PAP_N930XPAP1APH2_LLK_CL8613421_QB10630749_REV00_user_low_ship.tar.rar
N930XXXU1BPH1_N930XPAP1BPH4_All Country Android 6.0.1_3File Firmware
AP_N930XXXU1BPH1_LLK_CL8983140_QB10625421_REV00_user_low_ship_meta.tar.rar
BL_N930XXXU1BPH1_LLK_CL8983140_QB10625421_REV00_user_low_ship.tar.rar
CSC_PAP_N930XPAP1BPH4_LLK_CL8983140_QB10749187_REV00_user_low_ship.tar.rar
N930XXXU1BPI3_N930XPAP1BPI3_All Country Android 6.0.1_3File Firmware
AP_N930XXXU1BPI3_LLK_CL9201627_QB10891616_REV00_user_low_ship_meta.tar.rar
BL_N930XXXU1BPI3_LLK_CL9201627_QB10891616_REV00_user_low_ship.tar.rar
CSC_PAP_N930XPAP1BPI3_LLK_CL9201627_QB10891616_REV00_user_low_ship.tar.rar
GRACELTE_EUR_LDU.pit
topgman80 said:
I need help. I happen to get my hands on a note 7 sm-n930x live demo unit here in Denver, CO, USA
SM-N930X UD
S/N RF8H71JQGFD
64GB
Exynos 8890 SoC
4x Exynos M1 @ 2.3 GHz
4x Cortex A53 @ 1.6 GHz
Mali T880MP12 GPU
I had it running by flashing a sm-n930f firmware to it, which I understand is the same phone. I then attempted to flash the hydra rom and now I can only access download mode and it stays on the "Hydra Rom N7" splash screen. I dont remember the original phone info because the paper it was written got tossed out. To further my string of bad luck the SD that stored the NAND got corrupted.
I've tried to wipe everything via PIT and reinstall the 930f firmware, but it always fails. Sometimes it fails immediately and other times it actually starts installing for a moment and then fails. I've tried to install Hyrdra again and it fails. I've repartitioned in an attempt to wipe it without success. Info on the 930x version is hard to come by as I've come to find out. Today I finally found the fw listed below is the stock firmware for the international version, but the only downloads I can find are in a foreign language and want me to pay for it which I don't trust at all. At least I think these are the stock for the 930x, please correct me if I'm wrong.
I'm not sure of the baseband because someone threw away the paper I had written it on or the imei # which is all zeros with a one on the end now . How can I fix the loop and get it working again? Is it failing because I can't wipe the cache through recovery and it's too much overwriting at this point? Since this is the "x" international variant, is it accepting of any of the exynos roms? Does anyone have access to the firmware versions below that they could share with me or clue me in as to where I can find the downloads myself?
My goal is to get the Note 7 working again with hydra, or any other rom. I just need it to work and be able to use it on my carrier which is currently at&t. I may have tried to flash the wrong ROM, the efs could be missing, andi know the imei is gone. It is probably safe to assume all are true.
Do I need to repair the imei before it will accept an install? If so, how would you suggest? I have QFIL, QPST, SPC but am unsure exactly how to utilize with great affect as I'm still teaching myself or if they are the correct programs that I need in order to remedy my situation. I'm no pro but I'm not a newbie either. I'm great at following detailed, precise instructions so please guide me to resurrecting my Note 7. I'm not sure what happened but I know I can fix it with a little assistance. All guidance and suggestions are welcomed and greatly appreciated. Cheers
SM-N930X
By admin | Published: September 19, 2016
N930XXXU1APG5_N930XPAP1APG6_All Country Android 6.0.1_3File Firmware
AP_N930XXXU1APG5_LLK_CL8613421_QB10283666_REV00_user_low_ship_meta.tar.rar
BL_N930XXXU1APG5_LLK_CL8613421_QB10283666_REV00_user_low_ship.tar.rar
CSC_PAP_N930XPAP1APG6_LLK_CL8613421_QB10300978_REV00_user_low_ship.tar.rar
N930XXXU1APG5_N930XPAP1APH2_All Country Android 6.0.1_3File Firmware
CSC_PAP_N930XPAP1APH2_LLK_CL8613421_QB10630749_REV00_user_low_ship.tar.rar
N930XXXU1BPH1_N930XPAP1BPH4_All Country Android 6.0.1_3File Firmware
AP_N930XXXU1BPH1_LLK_CL8983140_QB10625421_REV00_user_low_ship_meta.tar.rar
BL_N930XXXU1BPH1_LLK_CL8983140_QB10625421_REV00_user_low_ship.tar.rar
CSC_PAP_N930XPAP1BPH4_LLK_CL8983140_QB10749187_REV00_user_low_ship.tar.rar
N930XXXU1BPI3_N930XPAP1BPI3_All Country Android 6.0.1_3File Firmware
AP_N930XXXU1BPI3_LLK_CL9201627_QB10891616_REV00_user_low_ship_meta.tar.rar
BL_N930XXXU1BPI3_LLK_CL9201627_QB10891616_REV00_user_low_ship.tar.rar
CSC_PAP_N930XPAP1BPI3_LLK_CL9201627_QB10891616_REV00_user_low_ship.tar.rar
GRACELTE_EUR_LDU.pit
Click to expand...
Click to collapse
You'll find very little help with an unsupported, recalled and discontinued device. Find a new toy to play with.
Sent from my SM-S903VL using Tapatalk
Fix imei note 7 sm-n930x Needed for return
Can someone guide me in restoring the imei for the note 7? I called the return phone number and they need the imei. For some reason the serial number isn't sufficient.
Did u find a solution
Sent from my SM-N930X using Tapatalk
Variant n930x has no efs folder. How did you make it You just put a ROM of the version n930f?
topgman80 said:
Can someone guide me in restoring the imei for the note 7? I called the return phone number and they need the imei. For some reason the serial number isn't sufficient.
Click to expand...
Click to collapse
If you have the box the device came in, the IMEI should be on the box somewhere.
If you had it activated on a network, that network should have the IMEI for that device in their system.
If all you need is the IMEI to file a claim on the device then getting the IMEI from the box or from your network support team might be enough. If so, it won't require dealing with the technical issues involved with trying to restore a corrupted IMEI.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
also if he would instead have taken a device without (or at least with a lot less) planned obsolescence (aka. if he would have a device with a battery you can take out) the IMEI would iirc be on a label below it.
greetings,
I recently inherently a Samsung Note Edge (SCL24). The phone is showing its age. It is on its default rom (4.4.4) but many things aren't work. For example, it is extremely slow; it won't remember wifi passwords, etc. I am hoping that by flashing a new rom I may bring it back to life.
The spec is listed below:
SCL24
Adroid 4.4.4
Baseband: SCL24KDU1ANJ3
as I am browsing through this forum, I am a bit confused as to the flashing procedure. Assuming it is the same as every other phones I have flashed, I suppose I would need to root it, install a recovery, possibly a new basebank, and then a new rom.
Is there a guide as to how to do this for this particular phone? It has been a while
any help, and suggestion as to which rom to flash, would be very much appreciated.
ps. I am not looking for anything fancy, but in the past I've always used slim rom.
regards,
mikec_ca2 said:
greetings,
I recently inherently a Samsung Note Edge (SCL24). The phone is showing its age. It is on its default rom (4.4.4) but many things aren't work. For example, it is extremely slow; it won't remember wifi passwords, etc. I am hoping that by flashing a new rom I may bring it back to life.
The spec is listed below:
SCL24
Adroid 4.4.4
Baseband: SCL24KDU1ANJ3
as I am browsing through this forum, I am a bit confused as to the flashing procedure. Assuming it is the same as every other phones I have flashed, I suppose I would need to root it, install a recovery, possibly a new basebank, and then a new rom.
Is there a guide as to how to do this for this particular phone? It has been a while
any help, and suggestion as to which rom to flash, would be very much appreciated.
ps. I am not looking for anything fancy, but in the past I've always used slim rom.
regards,
Click to expand...
Click to collapse
Try a factory reset first.
done that many times
This phone was purchased in Hong Kong and other than the model number "SCL24" I couldn't find any other information. Judging from this forum, looks like there are many variations on this phone (vendors in North America, Japan, and others common in south asia). Also from this forum I realized that I probably need to update the baseband in order to flash any new ROMS (post kitkat).
Hence I seek your help,
regards,
The Radius Kid said:
Try a factory reset first.
Click to expand...
Click to collapse
mikec_ca2 said:
done that many times
This phone was purchased in Hong Kong and other than the model number "SCL24" I couldn't find any other information. Judging from this forum, looks like there are many variations on this phone (vendors in North America, Japan, and others common in south asia). Also from this forum I realized that I probably need to update the baseband in order to flash any new ROMS (post kitkat).
Hence I seek your help,
regards,
Click to expand...
Click to collapse
Interesting.
Is this an international phone?
I tried asking about custom ROMS for my phone (don't want brick it) and didn't receive any responses.
I did do a Google search and didn't find much of anything.
I did download Marshmallow from Sammobile and have been gutting pretty heavily.
I guess after this much time, interest is fading.
problem solved, for now
As I mentioned earlier, this phone was purchased in Hong Kong and the model number was listed as SCL24. Following the thread on Project_ECSTASY (https://forum.xda-developers.com/no...rojectecstasy-custom-rom-galaxy-note-t3545658), I managed to flash the "Global edition stock rom without any bloatware from carrier au" using odin. The step I followed was:
1) installed samsung USB drivers for the phone (directly from samsung website),
2) downloaded and executed Odin,
3) rebooted the phone into Odin mode (vol down, home, and power),
4) connected the phone to computer via USB,
5) updated the rom through Odin.
6) once the phone rebooted, factory reset
I have not had much opportunity to play with the phone but it seemed to be working thus far. I have not had a chance to put a SIM card into it so I don't know if the new rom/Odin also flashed a new baseband and if the radio works.
will report back tonight,
mikec_ca2 said:
problem solved, for now
As I mentioned earlier, this phone was purchased in Hong Kong and the model number was listed as SCL24. Following the thread on Project_ECSTASY (https://forum.xda-developers.com/no...jectecstasy-custom-rom-galaxy-note-t3545658), I managed to flash the "Global edition stock rom without any bloatware from carrier au" using odin. The step I followed was:
1) installed samsung USB drivers for the phone (directly from samsung website),
2) downloaded and executed Odin,
3) rebooted the phone into Odin mode (vol down, home, and power),
4) connected the phone to computer via USB,
5) updated the rom through Odin.
6) once the phone rebooted, factory reset
I have not had much opportunity to play with the phone but it seemed to be working thus far. I have not had a chance to put a SIM card into it so I don't know if the new rom/Odin also flashed a new baseband and if the radio works.
will report back tonight,
Click to expand...
Click to collapse
Cool.
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
ecc25 said:
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
Click to expand...
Click to collapse
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
cooltt said:
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
Click to expand...
Click to collapse
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
ecc25 said:
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
Click to expand...
Click to collapse
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
cooltt said:
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
Click to expand...
Click to collapse
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
ecc25 said:
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
Click to expand...
Click to collapse
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
cooltt said:
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
Click to expand...
Click to collapse
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
ecc25 said:
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
cooltt said:
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
Click to expand...
Click to collapse
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
ecc25 said:
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
Click to expand...
Click to collapse
Well you could flash G930U which opens up all of the radios for the US and you may have less issues but US and European devices have different chips so your never going to be able to flash any EU generic firmware. I'm addition the US and Europe are different cellular regions with different operating frequencies. You can get by with what you have but never get full functionality.
I think you were just unlucky with this phone on ebay, there are plenty which are genuine EU region devices.
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
finshan said:
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
Click to expand...
Click to collapse
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Youdoofus said:
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Click to expand...
Click to collapse
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
finshan said:
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
Click to expand...
Click to collapse
you cannot go backwards in bootloader revisions, but you can go backwards in android versions as long as theyre on the same BL revision(not likely, but who knows? I didnt look yet). Also, the worst thing that could happen if you try to flash an older BL version is that itll fail in Odin and will still allow the phone to boot normally (usually, and if it doesnt, its still fixable). The only issue with booting it after flashing new firmware with your current sim is that itll install the carrier specific stuff on the phone so long as the CSC needed for that is in the multi CSC pack you flashed on the phone, and if it does install the carrier crap you dont want, just factory reset it and reboot with the actual sim you want you use
no problem man, thats what we are here for
Hi everyone,
In August I received an OTA for my SM-G955W. I installed it and immediately after it rebooted I got an “Invalid SIM” error message.
I took my SIM card out and put it in another phone and it worked perfectly. I put another SIM in my phone and it gave the same error. So obviously the problem was with the phone, not the SIM.
There is a Reddit thread dealing with this exact problem.
https://www.reddit.com/r/GalaxyS8/comments/i9b58o/invalid_sim_card/
I managed to get my phone working by flashing an older modem version using ODIN as was suggested in the Reddit thread (posted above). But now I cannot get any future OTA updates because it says “Your current software version issue supported”. Presumably that is because I have a mismatched modem file flashed.
Is there any way out of this?
Is there any way to get LineageOS on this device? It is a Snapdragon processor and I think the unofficial LinageOS builds only work on the Exynos models. Or is that incorrect?
Thanks,
The Fish
Flash with odin original firmware for your country and carrier sammobile.com/samsung/galaxy-s8-plus/firmware/#SM-G955W .