This is a running journal covering my attempts to stabilize a secondhand Note 5 prone to crashing. This first post summarizes the progress, and links to the current state of affairs below.
I've just acquired a second hand Note 5. It was sold as problematic, restarting continuously after loading the stock Marshmallow. 20 seconds or so, and it reboots.
After performing a factory reset the first time, Marshmallow loaded the configuration interface without any issue at all. Select region/language, choose WiFi network, give password, choose email account, give password, etc. Eventually it loaded into Marshmallow itself, no problem. It worked fine for half an hour or more. Then it froze and rebooted, during the automatic (app) updating process. After that, the screen would freeze after 20 seconds or so.
I tried another factory reset. This time it froze and restarted twice during the configuration interface, right when entering the WiFi password. After I got through it, and eventually loaded into Marshmallow, I turned off WiFi. It has been working without issue for an hour now.
I noticed a "dm-verity error" message at the bottom of the Marshmallow stock recovery screen. Perhaps importantly, eventually I recall that on the download screen the image and binary are identified as custom, not official.
See post #3 for more details.
By post #14 the phone has stabilized somewhat. Both WiFi and cellular function and the sudden restarts have been much less frequent. I successfully flash the Russian (SER) Nougat (7.0) firmware of November 2017. The restarts end completely, the battery performance is spectacular (1% per hour on idle) but l lose the cellular network.
By post #19 I suspect either a hardware or persistent data issue is involved, and find with *#0011# that the IMEI Status is NG. I am considering how to unbork the situation, as I didn't make an EFS backup.
By post #23 I have restored network service, but no matter how thoroughly I wipe and flash stock firmwares I'm left with the original issue: constant freezes and restarts. Then, without any discernable reason everything is smooth for days. This odd behavior leaves me wondering whether it's not a hardware issue, but the previous owner borked partitions that aren't affected by flashing firmware. I decide to try and make a full backup, including all hidden partitions normally not included. And see what happens if the next time the phone starts crashing, I restore that backup. But how do I make and restore a full EMMC backup?
It turns out the internal storage of a Note 5 is actually UFS, not EMMC and XDA turned out to be a dry well on full (EMMC) backup and if Google had answers, persistent searching for a week or so didn't turn anything up. Android backup seems an ill defined and ill standardized field. Many options, many superficial. What imaging there is, is spotty and generally incomplete, "proprietary" and not easily restorable.
When after a month smooth operation things go pear-shaped again (post #24) I've got no backup to restore. Not that it would have mattered probably. I suspect it's probably a NAND/EMMC/UFS issue at the back of it all. Now, with Note 5 not officially marketed or supported in the EU, how do I find the parts that I need and fix them?
In the end I replaced the motherboard with one I bought on eBay. The process was simple, using a YouTube video to walk me through the steps. I did walk into a peculiar circuit sticker which was partly stuck to the top of the inside of the cover, and tore. The switch out worked without a hitch but I'm trying to figure out what the sticker is. See my last post.
You bought it rooted and with stock android? To my knowledge not everything is stable with stock android on the note 5! If this phone is your daily you should flash a Samsung based Rom to avoid those reboot issues... or even returning the phone back to stock via Odin!
Well. The print on the back says SM-N920F, but the Odin menu says "product name: SM-N920C". As the IMEI and serial numbers printed on the back also do not match those reported by *#06# I'd say it's a reasonable guess the phone is a fake. The device information in settings indicates the Note 5 is running baseband N920CXXU3BQA1, Android 6.0.1.
So. If the fake would work well, I wouldn't mind. It doesn't for now, though. Given the issues described in the first post, I'm thinking it may have a corrupt stock ROM or a conflict between it's actual (or compatible) model and the ROM that's either installed or it's getting updates for. As a fake, it may even have mixed components of various models SM-N920C and SM-N920I, for example.
How does one get the right ROM for a fake? How does one figure out which parts are actually in the phone, that determine which ROM is needed?
However much you paid for your note 5 can easily determine if its fake or not! Right Now a like new/mint Note 5 (according to swappa) goes for about $220 or less. There are many signs to that hint at a chinese knock off. Simply youtube search "fake v real" note 5.
If your phone is a fake Note 5 theres not much you can do software wise. Not even something like nova launcher will help you. I've seen these knockoffs in person. They are unbearable to use as a daily. The hardware in the knockoff versions aren't even close to what the real Note 5 has.
Crike said:
Well. The print on the back says SM-N920F, but the Odin menu says "product name: SM-N920C". As the IMEI and serial numbers printed on the back also do not match those reported by *#06# I'd say it's a reasonable guess the phone is a fake. The device information in settings indicates the Note 5 is running baseband N920CXXU3BQA1, Android 6.0.1.
So. If the fake would work well, I wouldn't mind. It doesn't for now, though. Given the issues described in the first post, I'm thinking it may have a corrupt stock ROM or a conflict between it's actual (or compatible) model and the ROM that's either installed or it's getting updates for. As a fake, it may even have mixed components of various models SM-N920C and SM-N920I, for example.
How does one get the right ROM for a fake? How does one figure out which parts are actually in the phone, that determine which ROM is needed?
Click to expand...
Click to collapse
It doesn't necessarily mean it's fake, it just have motherboard from other phone, download rom for n920c and flash it using odin and you should be working fine.
El Solido said:
It doesn't necessarily mean it's fake, it just have motherboard from other phone, download rom for n920c and flash it using odin and you should be working fine.
Click to expand...
Click to collapse
I can see how that might be, and why the IMEI on the back and the one reported by *#06# would then be different. The thing is, the 15 digit IMEI printed on the back (357XXX/XX/XXXXXX/X) is invalid according to www.imeipro.info, imei24.com and www.imei.info. How could that be the case on a genuine Samsung? (I tested the IMEI as a single string of numbers, without the slashes printed on the back, as given above.) Also, the IMEI reported by *#06# is resolved by the above-mentioned sites as a 2005 Philips 960. That doesn't square with the idea of a cannibalized motherboard, I'd say.
That said, the build quality is very high if it is a fake: excellent manufacture; 16MB camera; well working, slickly spring loaded, pressure sensitive S-Pen with functioning button; fingerprint reader that works (correctly distinguishing the scanned finger from others); high resolution AMOLED screen.
It's an odd duck.
Crike said:
I can see how that might be, and why the IMEI on the back and the one reported by *#06# would then be different. The thing is, the 15 digit IMEI printed on the back (357XXX/XX/XXXXXX/X) is invalid according to www.imeipro.info, imei24.com and www.imei.info. How could that be the case on a genuine Samsung? (I tested the IMEI as a single string of numbers, without the slashes printed on the back, as given above.) Also, the IMEI reported by *#06# is resolved by the above-mentioned sites as a 2005 Philips 960. That doesn't square with the idea of a cannibalized motherboard, I'd say.
That said, the build quality is very high if it is a fake: excellent manufacture; 16MB camera; well working, slickly spring loaded, pressure sensitive S-Pen with functioning button; fingerprint reader that works (correctly distinguishing the scanned finger from others); high resolution AMOLED screen.
It's an odd duck.
Click to expand...
Click to collapse
I would say thats stolen phone with random imei put on it, but I can't be sure.
PS Fake won't have working s pen
El Solido said:
I would say thats stolen phone with random imei put on it, but I can't be sure.
PS Fake won't have working s pen
Click to expand...
Click to collapse
That wouldn't explain the incorrect IMEI on the back. Perhaps a stolen fake? But then, why would it be so high grade? The S-Pen and all the specs seem to point at something else. Perhaps a recall, with a bad IMEI, resold. But even if somehow they'd sell it on as refurbished with a proper IMEI, would they leave a backplate with a wrong IMEI on it? And then that one was stolen and given a 2005 IMEI of an old Philips? It's a bit of a mystery.
Putting that all aside, how'd I pick the proper ROM? The SM-N920C has a ton of variations for regions and carriers, none of which are in the EU. I live in the Netherlands, so I'd need a version which would work in the region and doesn't SIM-lock my phone after flashing, if that's possible. The current ROM seems to be for the United Arab Emirates. Right now, it's working stable, WiFi and cellular network alike. But it has been playing up before, with the freezes and restarts that caused me to start the thread at all.
Do you have any words of wisdom?
Perhaps you could upload a few pics of the device or even a video of it? That will be a better way to get help.
Crike said:
That wouldn't explain the incorrect IMEI on the back. Perhaps a stolen fake? But then, why would it be so high grade? The S-Pen and all the specs seem to point at something else. Perhaps a recall, with a bad IMEI, resold. But even if somehow they'd sell it on as refurbished with a proper IMEI, would they leave a backplate with a wrong IMEI on it? And then that one was stolen and given a 2005 IMEI of an old Philips? It's a bit of a mystery.
Putting that all aside, how'd I pick the proper ROM? The SM-N920C has a ton of variations for regions and carriers, none of which are in the EU. I live in the Netherlands, so I'd need a version which would work in the region and doesn't SIM-lock my phone after flashing, if that's possible. The current ROM seems to be for the United Arab Emirates. Right now, it's working stable, WiFi and cellular network alike. But it has been playing up before, with the freezes and restarts that caused me to start the thread at all.
Do you have any words of wisdom?
Click to expand...
Click to collapse
To know for sure do geekbench 4 then we will now is it fake or not. And for rom you can't sim lock by installing firmware.
Crike said:
That wouldn't explain the incorrect IMEI on the back. Perhaps a stolen fake? But then, why would it be so high grade? The S-Pen and all the specs seem to point at something else. Perhaps a recall, with a bad IMEI, resold. But even if somehow they'd sell it on as refurbished with a proper IMEI, would they leave a backplate with a wrong IMEI on it? And then that one was stolen and given a 2005 IMEI of an old Philips? It's a bit of a mystery.
Putting that all aside, how'd I pick the proper ROM? The SM-N920C has a ton of variations for regions and carriers, none of which are in the EU. I live in the Netherlands, so I'd need a version which would work in the region and doesn't SIM-lock my phone after flashing, if that's possible. The current ROM seems to be for the United Arab Emirates. Right now, it's working stable, WiFi and cellular network alike. But it has been playing up before, with the freezes and restarts that caused me to start the thread at all.
Do you have any words of wisdom?
Click to expand...
Click to collapse
Also, maybe it was stolen before being registered on the network, and had imei changer beforehand activating.
El Solido said:
Also, maybe it was stolen before being registered on the network, and had imei changer beforehand activating.
Click to expand...
Click to collapse
Like being from a container of original phones that fell from a ship? Not a single one lifted by a pickpocket.
Whatever the case may be, geekbench 4 reports the same hardware as on Wikipedia. Unfortunately the CPU test keeps crashing the phone at around 60% - about a minute or two into the test. So I don't have a benchmark to compare with established Note 5 performance.
How would you recommend I pick a ROM with the best chance of functioning in the region?
Crike said:
Like being from a container of original phones that fell from a ship? Not a single one lifted by a pickpocket.
Whatever the case may be, geekbench 4 reports the same hardware as on Wikipedia. Unfortunately the CPU test keeps crashing the phone at around 60% - about a minute or two into the test. So I don't have a benchmark to compare with established Note 5 performance.
How would you recommend I pick a ROM with the best chance of functioning in the region?
Click to expand...
Click to collapse
Use russian firmware, only european rom i saw.
El Solido said:
Use russian firmware, only european rom i saw.
Click to expand...
Click to collapse
Tried flashing but Odin 3.07 seems to hang on "NAND writing started!" After 30 minutes I examined the Odin process in Windows' Task Manager, and it seemed completely inactive (0% CPU). Tried again, same result. Restarted the phone, and it booted straight into the existing ROM, which appeared completely unaltered.
I'd like to try another Odin version. Is there a trustworthy site?
El Solido said:
Use russian firmware, only european rom i saw.
Click to expand...
Click to collapse
Downloaded the latest Odin from the thread on XDA: PASS. Upgraded successfully to the latest Russian Nougat release.
Unfortunately, now I have "Emergency calls only", and I get an "Error while searching for networks" when trying Settings\Mobile Networks\Network Operators\Search Networks. Available network modes are LTE/3G/2G.
Also, geekbench 4 still crashes at around 60% as it did before.
The upgrade wasn't clean, the previous apps and settings still remained after flashing.
Perhaps a full wipe and a clean flash, perhaps again a United Arab Emirates variant? That ROM did work with my mobile network.
Crike said:
Odin: PASS. Upgraded successfully to the latest Russian Nougat release.
Unfortunately, now I have "Emergency calls only", and I get an "Error while searching for networks" when trying Settings\Mobile Networks\Network Operators\Search Networks. Available network modes are LTE/3G/2G.
Also, geekbench 4 still crashes at around 60% as it did before.
The upgrade wasn't clean, the previous apps and settings still remained after flashing.
Perhaps a full wipe and a clean flash, perhaps again a United Arab Emirates variant? That ROM did work with my mobile network.
Click to expand...
Click to collapse
Ok now first thing go flash that united arab emirates rom, after that go to stock recovery do factory reset.
El Solido said:
Ok now first thing go flash that united arab emirates rom, after that go to stock recovery do factory reset.
Click to expand...
Click to collapse
There are two UAE (United Arab Emirates) ROMs: LYS and XSG. Both fail in Odin, while the Russian ROM succeeds. I've tried multiple times.
I noticed that while the order of images (boot.img, recovery.img, system.img, etc) differs between all three ROMs, both UAE ROMs fail shortly after hidden.img.
The Russian Nougat ROM works well and is apparently stable. The only issue is that the phone can't connect to or find mobile networks and emergency calls only are possible.
Can the Russian ROM be patched with the appropriate modules from another ROM? How would I determine what kind of network module is required in the EU, and from which ROM to pilfer it?
I'm thinking about flashing the United Arab Emirates modem.bin file over the existing Russian ROM modem.bin with ADB/Fastboot. How bad of idea is that?
Another idea would be to extract a United Arab Emirates ROM, remove the hidden.bin (possibly replace it with the one from the Russian ROM) and the compress the files into a new .md5 file with Universal Android Toolkit.
Crike said:
There are two UAE (United Arab Emirates) ROMs: LYS and XSG. Both fail in Odin, while the Russian ROM succeeds. I've tried multiple times.
I noticed that while the order of images (boot.img, recovery.img, system.img, etc) differs between all three ROMs, both UAE ROMs fail shortly after hidden.img.
The Russian Nougat ROM works well and is apparently stable. The only issue is that the phone can't connect to or find mobile networks and emergency calls only are possible.
Can the Russian ROM be patched with the appropriate modules from another ROM? How would I determine what kind of network module is required in the EU, and from which ROM to pilfer it?
I'm thinking about flashing the United Arab Emirates modem.bin file over the existing Russian ROM modem.bin with ADB/Fastboot. How bad of idea is that?
Another idea would be to extract a United Arab Emirates ROM, remove the hidden.bin (possibly replace it with the one from the Russian ROM) and the compress the files into a new .md5 file with Universal Android Toolkit.
Click to expand...
Click to collapse
You could try that, but first try factory reset then try flashing rom.
El Solido said:
You could try that, but first try factory reset then try flashing rom.
Click to expand...
Click to collapse
I've checked the SIM and it's in good condition. I've tried a number of firmwares, none of which resolves the "No service" issue. I've spoken to several Dutch Note 5 owners and they seem to have a variety of Iraqi, UAE and Russian firmwares and those all work.
It would seem it either ~ is ~ a hardware issue after all or there's some borked data which isn't affected by flashing, either on the phone's own memory (like the /efs folder) or in the modem/radio itself, if that has programmable memory.
Edit: *#0011# shows "IMEI Status NG".
I do not have an EFS backup.
I need some serious guidance beyond this point.
Is there software to determine if there is a hardware issue with the modem board? What else could I do beyond this point? I'm not ready to hand it over to a repair service.
Also, if the phone does have bars and call emergency services, doesn't that mean the modem/radio itself is working? Is there a forum I should look to for more help on this issue?
Crike said:
I've checked the SIM and it's in good condition. I've tried a number of firmwares, none of which resolves the "No service" issue. I've spoken to several Dutch Note 5 owners and they seem to have a variety of Iraqi, UAE and Russian firmwares and those all work.
It would seem it either ~ is ~ a hardware issue after all or there's some borked data which isn't affected by flashing, either on the phone's own memory (like the /efs folder) or in the modem/radio itself, if that has programmable memory.
Edit: *#0011# shows "IMEI Status NG".
I do not have an EFS backup.
I need some serious guidance beyond this point.
Is there software to determine if there is a hardware issue with the modem board? What else could I do beyond this point? I'm not ready to hand it over to a repair service.
Also, if the phone does have bars and call emergency services, doesn't that mean the modem/radio itself is working? Is there a forum I should look to for more help on this issue?
Click to expand...
Click to collapse
Ok since you can't flash firmware you want, extract it from .tar and select it in CP in Odin 3.12.xx and maybe it will work then. gl
Related
Hey, thanks for clicking my post. TL;DR Since updating from ARHD 40.3 to Viper One 6.2.0, my radio has been having major intermittent issues. I have a HTC One m7_ul unlocked outright from Optus here in Australia. It is as of right now running the latest firmware linked to by the Viper One/ARHD threads, the latest TWRP, is S-OFF and superCID, running Viper One 6.2.0.
Symptoms:
1) No signal most of the time.
2) Signal appears to return during periods of movement (e.g. driving).
3) Even at full signal, there is no mobile connection (no data, no text/calling).
4) Once every few hours, when it has signal, it will gain mobile connection for a short period of time, after which it will cut out again - repeat to 1).
Here's a short story about how this came to be:
For many many months now it has been running just fine on stock firmware, rooted with S-ON running ARHD 40.3 (since that version came out).
About a fortnight ago I started noticing issues with my contacts application. Something to do with 501 contact link suggestions and certain contacts having hundreds of Facebook profile entries. This would cause issues in the People app (people just wouldn't load) and the SMS app (message histories wouldn't load, including new texts).
After some troubleshooting attempts, I resolved to reinstall a ROM. I opted to install the latest Viper One (6.2.0) successfully. It resolved my issues. However, it introduced a new one. The next morning I woke up to 4 texts from my service provider informing me I'd missed calls. I had no notifications as such, so the calls never reached my phone. I put it down to tower signal flex in my area. I left and as I walked out the door I noticed I had no signal (no bars, x above the icon in statusbar). Driving around seemed to fix the issue though, it got back up to normal values quickly enough.
However, even though I had plenty of signal and mobile data was ostensibly turned on, I couldn't get internet. I tried sending a text to myself but it failed send. Calls out simply waited on signal and then timed out. Every single other function of the device is 100% AOK (wifi, bluetooth, nfc, etc). The entire ROM is fully functional, can't find any other issues with stability or otherwise.
I put up with it for the day and get home and start troubleshooting. Here's what I tried so far, in order:
1) Change from Viper One to latest ARHD (71.1). Installed with no issues. Booted phone, no dice - no signal.
2) Checked SIM by moving to old iPhone 4 - full signal, radios work. It's not a service issue.
3) Revert to last known working ROM - ARHD (40.3). Installed with no issues. Booted phone, no dice - no signal.
4) Research research research. Think it might be a problem with firmware perhaps. Tried revone, failed because I'm not on 4.2.
5) Flash MaximusHD (11.0.0) in order to make use of revone for S-OFF/superCID. Flashed latest firmware linked in Viper One/ARHD threads.
6) Reboot phone. Still no dice with latest firmware on MaximusHD (11.0.0).
7) Retry with latest ARHD. No dice.
8) Retry with latest Viper One. No dice.
In every single instance, all the ROMs are fully functional except for mobile signal - wifi, bluetooth, nfc, etc. radios function perfectly. No issues with ADB or fastboot during any step of these processes. All my device info shows what I expect to see. I've searched as much as I can, to no avail. I turn to first-time posting here as a last resort to maybe find out what the issue is.
I am slowly reaching the thought that the hardware itself might be the issue. I'd appreciate any insight into what could be causing this - be it software or hardware - as well as if there is any way to test or diagnose the radio physically. Even just a confirmation ("Yep, sounds like your radio's FUBAR"). In the meantime, I'll be using aforementioned iPhone 4 (ugh).
Thanks for reading.
Have you attempted to flash a different radio baseband?
Look up the radio version used in ARHD 41. If you find it, search for the radio within the forums and flash it. You can still keep the most current version of your preferred ROM. Search the threads for how to flash a radio baseband, there are plenty of them.
digitalism said:
Have you attempted to flash a different radio baseband?
Look up the radio version used in ARHD 41. If you find it, search for the radio within the forums and flash it. You can still keep the most current version of your preferred ROM. Search the threads for how to flash a radio baseband, there are plenty of them.
Click to expand...
Click to collapse
I found a forum for HTC One radios here, it's in the AT&T section but apparently work on all HTC Ones. I was unable to find out which radio ARHD 41 used, my understanding is that custom ROMs don't usually come with a radio baseband of their own and they don't appear to list any on their thread that I could see. I would inquire but I think there's an issue with new users posting in development sections. Do you think it's worth trying to look further into what radio was used, or should I start flashing radios from the aforementioned list? There's a couple that stand out as possible candidates (the earliest version, the newest version, etc) but I'm not sure I want to just start going crazy on that list until something works. Or do I?
edit: To clarify, and they say explicitly in the ARHD post FAQ, they do not include radio/hboot/firmware in their ROM. So I must assume that I was simply on the stock radio the device shipped with.
edit 2: Confirmed my current baseband matches one of the ones indicated as installed from firmware package. I'm not sure what it was before I updated to Viper One or even while I was using Viper One.
Flashed the earliest radio baseband available from the aforementioned thread. Put the SIM back in, signal achieved, able to send texts/make calls/USSD codes. I was unable to get it to transfer mobile data, however.
Can't believe I didn't think about radio baseband. Didn't even know that was a thing. I just thought it was part of the firmware package. There you go I guess. Thanks again for the tip.
Whitestrake said:
Thanks again for the tip.
Click to expand...
Click to collapse
No problem, just remember that if you're having issues with certain partitions on the device, each partition is technically flashable if you are S-Off and SuperCID.
digitalism said:
No problem, just remember that if you're having issues with certain partitions on the device, each partition is technically flashable if you are S-Off and SuperCID.
Click to expand...
Click to collapse
I've tried just about every radio in that forum. They all seemed to have the same issue for me - at first it seems to have no signal, then it gets normal signal, receives/sends any buffered texts, and then fails to work after that for any purpose regardless of signal. I think I'm back at square one; I don't suppose there are any other simple things to try?
Whitestrake said:
I've tried just about every radio in that forum. They all seemed to have the same issue for me - at first it seems to have no signal, then it gets normal signal, receives/sends any buffered texts, and then fails to work after that for any purpose regardless of signal. I think I'm back at square one; I don't suppose there are any other simple things to try?
Click to expand...
Click to collapse
If you are having issues still, the other alternative is to flash a different firmware version than what the ROM provides. Firmware and radios tend to "talk" to each other in certain ways, so maybe your firmware isn't using your radio the way you need it to. Also, make sure you are installing firmware particular to your device. For instance, do not install firmware originally meant for an AT&T phone if you use Verizon or another carrier. They tend to write the code particular to these things. I would do some research through the forums and see if you can find a good combination in your area that people have tried. Maybe even a Google search will help out if the forums seem daunting to dig through.
And don't forget, the iPhone has a Quad-Band receiver that's capable of receiving cellular signals much clearer. The HTC One, in my opinion, does not match hardware compared to the iPhone. The iPhone will always technically be superior, no matter what opinions people hold to both.
First, thanks again for your patience and assistance.
digitalism said:
Also, make sure you are installing firmware particular to your device. For instance, do not install firmware originally meant for an AT&T phone if you use Verizon or another carrier.
Click to expand...
Click to collapse
I was not aware of this restriction. I suspect I may have flashed firmware for a different region. I isolated the Optus firmware RUU numbers and got a firmware package matching, and the android-info.txt matches the device original CID and modelnum. I'll try it soon.
I'm still having trouble understanding, though, how it could have failed in the first place. My phone was S-ON when the radio stopped working; surely changes to firmware/radio couldn't have occurred anyway? None of the ROMs I've touched have firmware or radio included as far as I could tell.
Flashed the firmware appropriate to my region (4.20.980.1). Came with radio. Rebooted, put in SIM, no signal for 5 minutes. When I get signal, texts don't send and calling times out, USSD codes give connection problem errors. Same as before. How likely is it the actual hardware could be damaged? I did drop it on concrete, on the front of the device at the top, around the time this started happening - very shortly before I flashed Viper One to fix the contacts issue. There was no visible damage.
Whitestrake said:
Flashed the firmware appropriate to my region (4.20.980.1). Came with radio. Rebooted, put in SIM, no signal for 5 minutes. When I get signal, texts don't send and calling times out, USSD codes give connection problem errors. Same as before. How likely is it the actual hardware could be damaged? I did drop it on concrete, on the front of the device at the top, around the time this started happening - very shortly before I flashed Viper One to fix the contacts issue. There was no visible damage.
Click to expand...
Click to collapse
Quick question:
Are you installing your firmware and software without the SIM card in? If so, I would leave the SIM card in and have all the software installed during the process. Damage to the phone should not cause problems for connecting to the cellular network. Have you tried leaving the house, going outside, or getting into a different area to try your signal? Maybe your house is a deadzone and the phone is having a hard time picking it up. My room gets like this since I live in Florida where houses are built with cinder blocks to prevent hurricane damage. It really messes with my signal.
digitalism said:
Quick question:
Are you installing your firmware and software without the SIM card in? If so, I would leave the SIM card in and have all the software installed during the process. Damage to the phone should not cause problems for connecting to the cellular network. Have you tried leaving the house, going outside, or getting into a different area to try your signal? Maybe your house is a deadzone and the phone is having a hard time picking it up. My room gets like this since I live in Florida where houses are built with cinder blocks to prevent hurricane damage. It really messes with my signal.
Click to expand...
Click to collapse
Good ideas, but unfortunately not - every firmware and radio package I've flashed, I've done once with the SIM, once without, thinking along a similar line.
I'm in a known good cell location - coverage in my area is fantastic with my provider (Telstra, usually get 5 bar signal on 3G - I do not get LTE on my plan). I test in multiple places - next to my PC, outside the house, down the street, etc. The behaviour I've noticed is that I have no signal regardless of where I go, for about 5 minutes after booting the phone, after which it gets signal, sends/receives any buffered texts, and then fails to communicate successfully after that (i.e., I get the test text I sent myself, then I resend another test, and it fails to send). The iPhone 4 I've been moving my SIM to has been receiving full signal (as expected) at every place I've been testing the HTC One.
Hmm...
You might have to go into your APN settings to change some things in order to get it to work properly. Go to your Settings, then Mobile Data, then Access Point Names. From this menu click the current APN saved with the phone. After that, it will have you insert some information. Check this website for the specific APN information for your carrier. Make sure it's for your carrier as there is a large list of different ones on there.
http://ausdroid.net/apns/
Other than that, I honestly couldn't tell you what your issue is.
digitalism said:
Other than that, I honestly couldn't tell you what your issue is.
Click to expand...
Click to collapse
Tried the APN thing. There was indeed a few things different from the listed settings, but honestly, they were pre-populated with a bunch of Telstra data beforehand when the SIM was in. I made the changes and noticed no difference.
Thanks again for your help. As a last step I will return it fully to stock. After that I suspect my only recourse would be taking it back to Optus and asking if they'll quote me to fix it.
Unfortunately it does seem to be hardware issue from the history of what you have tried and posted.
Use nkk71's guide listed in my signature to go back to stock for warranty but substitute your local RUU/nandroid/etc.
SaHiLzZ said:
Unfortunately it does seem to be hardware issue from the history of what you have tried and posted.
Use nkk71's guide listed in my signature to go back to stock for warranty but substitute your local RUU/nandroid/etc.
Click to expand...
Click to collapse
Thanks for the link, that's actually one HTC One return-to-stock guide I haven't seen yet and it looks very concise. Cheers.
Whitestrake said:
Tried the APN thing. There was indeed a few things different from the listed settings, but honestly, they were pre-populated with a bunch of Telstra data beforehand when the SIM was in. I made the changes and noticed no difference.
Thanks again for your help. As a last step I will return it fully to stock. After that I suspect my only recourse would be taking it back to Optus and asking if they'll quote me to fix it.
Click to expand...
Click to collapse
Sorry about that, I know having a custom ROM is a lot of fun, but there can definitely be some cons along with it.
Good luck with your phone!
So as of saturday my unlocked TMobile Note 4 stopped working as a phone, and won't let me make calls.
Information:
-Was on Dr. Ketan L3 version of his rom when it stopped working
-Using the N910T on AT&T
-IMEI is fine and not damaged, both numbers match (using *#06#)
-It shows bars, but when I go to make a call "Not Registered On Network"
What I've Done:
-Flashed Stock Firmware via Odin (Autoboot, and F.Time Rest checked)
-Factory Reset after odin flash
-Checked APN
-Set on LTE/WCDMA/GSM
-Searched for Networks, finds them, but when I choose AT&T it takes forever and then finally kicks me out and then in notifications, I get the "Not Registered to Network"
-Did the remove the battery thing, and removed sim
-Went to AT&T and got a new sim, worked for 1hr (sporadically) and then went back to "Not Registered on Network"
-At the store I was on phone with AT&T tech trying to troubleshoot the problem and that is when it was working shortly
-Called T-Mobile and checked to see if they blocked my IMEI number, nope they didn't, couldn't help me out further than that
-AT&T was showing that it was a Note 4 so not having that coming up as a Blackberry issue that some reported, so that's not it
-*#0011# shows service limited, but it is unlocked and everything is fine, the IMEI is good, and all is well but the limited service
-Put it in Airplane mode and woke it back from there after 5+minutes
-cleaned the connectors on the sim (new sim anyways so shouldn't really need them)
I'm running out of options, the only thing I can think of being the problem is that I might have started out using this phone on COD2, and when I flashed a COG2 firmware it didn't like that and so my phone's account settings didn't fully transfer.
Also I was messing around with the bands settings (*#2263#) what should they be on? Automatic, LTE/GSM only, or what?
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
kabuk1 said:
Settings should be on automatic. One more thing to try is go for a drive with the phone, at least 5 miles from your house, and see if it does this when connected to other towers. I had this same issue years ago and it turned out to be a malfunctioning tower by my house.
If it still does it on other towers, then it may be hardware-related
Click to expand...
Click to collapse
Thanks, yeah it kicks in randomly for like a minute and then dies, I take it to my parent's house (about 10 miles away) and along the way I get a good signal, but then when I reach their house, back to nothing. I was using it just fine the week prior. I partially blame Dr. Ketan, ever since installing his rom, I had multiple issues. I since uninstalled it and tried going back to stock. Any idea on what a good "safe" band setting is? I have that settings set to automatic, but if there was a good "safe" band that would be great. A common LTE tower. Even when I do connect or get connected, I can't register on that network, my phone won't let me. I've tried that. The bars drop to zero. I damaged my antenna wire (white one) and I just replaced it with a new one I purchased, but the hacked together one seemed to be doing the same quality job as the new one is. It shows the signal, but as soon as you try tying it down to a network it rejects it. I was afraid that when I flashed the stock image via odin it removed the unlock, but it was still there. I just hate that now I have a $500 pda, when it was a phone and now i'm relegated to using a f*ing flip phone.
i think your antenna cable is damaged. the only way to know that is be close to a tower, and see if your work or not.
bought and replaced with new ones, I get full bars, in my bedroom, but apparently they're tied to Tmobile since when I try to register it to AT&T they magically disappear, but when I close the app, they come back at the same strength level. I can't register them to Tmo since the sim. Yet my phone is telling me it's unlocked (*#0011#), IMEI = PASS, 1;
I think the prob is due to the different frequencies.
Your baseband would not be tied to a rom(ie Dr Ketan) Unless that rom contains Modem.bin
Your apn needs to be att if that's your Sim obviously.
International version has a different chipset. .. I know it's not your case. .
But it's open to any Sim. ..
I can say this.. I have a N2 unlocked (tmob) I run an Att Sim it works but the sig is really spotty... COD6/ COG2 may not be lining up frequency wise with your att Sim. ..
Try rolling your baseband back even further. .
Flashvetrin
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
dcoke said:
Any clue on to what i should use for best results? Like 850/1900 or 900/2100? What is a good LTE band? Where could I find a map of LTE bands used by carriers, I know how to get to that secret menu and manually change it to see if I get better results?
Click to expand...
Click to collapse
Well I would think automatic is out for sure.. the other prob would be after reboot the chipset will search for the default.. but I could be wrong.
I do not know what the numbers would be for band identification.
You may get lucky when calling Att and ask for someone in a higher tier. To give you some numbers for frequincies .
But you have ruled out hardware correct??
By putting a tmob Sim in????
Cuz I know you posted you did antenna work..
And I do know you said you get bars then it fades..
The fact it fades and doesn't lock into even a G band for example. Just leads me to believe the apn can't lock down based on the frequincie and the built in lte chipset...
It would be nice to just flash an att modem wouldn't it?? But don't even think about it.. lol you'll soft brick..
I wish I had a better solid answer you. You may just start testing those different bands and see if you get closer to a lock.
Flashvetrin
U rock, lol. Thx man
My Tricked Out N910P
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
dcoke said:
But what could have happened that made it crap out like that since it was working just fine beforehand for 2 solid months on custom roms and what not? That's the frustrating part, I've been flashing different modems on my phone, but none have been successful. Apparently there are 3 different N910T, how do you know which ones to play with? I flashed N910T(3) bands, that failed, I did try N910A, obviously failed. Then I lost my IMEI number, got terrified, tried reflashing EFS in TWRP, nothing. Then reflashed COG2 bands, it came back. Is there an app on the Playstore that would definitively tell you if your network chip is damaged? I wouldn't know what to look for.
Have you taken apart the Note 4, what are all those contact points, are those antenna things? One of those were damaged, they're like folded metal spring boards with gold tips (same kind of thing that is used to install a qi receiver, same design). I took my tweezer and fixed it, but could that be the culprit, since on the surface, it seems like the network is fine. Works really well in WCDMA, but not much else. I was able to make calls using GSM only, but my signal was 1 bar and the audio quality was questionable, so I left it alone for 10 minutes on that hoping it would force a reconnect. This is frustrating, since I wasted $500 on this phone and not having it work after two months means now I'm back to a featureless phone.
Thanks for your advice thus far. Flashing different modems hasn't been working out well, I just wished I could remember what baseband version the guy had the phone on when I first got it? I thought it was COD6, it was definitely on Lollipop, but if it's a 910T(2) would I know, how would I know?
How do you flash NON_HLOS and modem.bin at the same time in Odin? I know Modem does bands, but what does Non-Hlos do? I thought i read LTE, so if those aren't in sync and on two different versions could that be the issue? I extracted them from the full TAR firmware files.
Click to expand...
Click to collapse
Heres
A simple method for COD6
And try odin 3.07
I need to think about this some more and get back to you...
This is a partial firmware.. it consists of the modem and bootloader COD6.
Also to rule out damage if you can get a T Mobile Sim put it in the device and see if it locks down a signal....
Flashvetrin
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
dcoke said:
That was my next move, not having any real income but disability and little coming from that, I thought that was the next logical step too. I'll get a tmobile to go sim and try it see if it can't lock on to that, and see if that doesn't set it on the right path. Have you heard of other people having COG2 issues on AT&T unlocked? Maybe that was the problem, something there broke the connection. I don't know, but whatever it is, I can't thank you enough, you've at least given me more options to try that I couldn't think of on my own. I'll try that file.
Click to expand...
Click to collapse
You are the first of this kind that I'm aware of.. in regards to this issue..
Make sure you read the detail in if your device bootloops, to reboot recovery and flash the Rom.. if you want flash the Rom in the op that I've linked you to.
Wipe sys/dal/cach/data..
And flash it can't hurt.. [emoji16]
I really hope a Tmob Sim and or COD6 gives you results...and good ones at that.. [emoji2] [emoji106]
Flashvetrin
Got the sim card, $65 for that crap, and it didn't work. Called T Mobile customer service, explained my situation and how I was calling on another phone on another carrier and they insisted on calling me back on the broken not working phone. I guess I'm just screwed, and lost $500, which like I said, I can't afford to have. It's just so frustrating. I also tried the COD6 partial firmware, and nothing there also. I'll try t-mobile again. The only and last option I have, if possible, is to try to relock my phone and re-unlock it since there isn't any real way to tell if my GSM is damaged. I think my unlocked status got damaged when my phone upgraded to COG2, and since it's in that weird limbo state I can't use my phone. Do you know how to relock it?
Edit: When I look at my IMEI Number through *#06# it shows that the last two digits (independent of the actual IMEI number, since that matches everywhere) to the right of the "/" as 14, yet through "about device" it shows my imei version as 10. I assume that the 14 in the "06" screen is the version it's reading off the phone, could that be causing the issue? How would you even fix that? I don't know. but thanks again, you've been helpful.
Hello, my S5 mini has the first problems 1 year after bought, sometimes there was the error not registered on network. I have sent it twice to the support, but it was returned with "no error".
Now warranty over i have the error not registered on network, and can not use it for telefoning. The IMEI was correct, i can receive the network, but i can not register to it. I have the last marshmallow update flashed over OTA.
in former times, i have to remove the sim and reinsert it, to get it work again, but now this does not work. The simcard ist changed from the provider, and i bouhgt another simcard from another networkk, to test it.
Can i fix this problem?
Garfield62 said:
Hello, my S5 mini has the first problems 1 year after bought, sometimes there was the error not registered on network. I have sent it twice to the support, but it was returned with "no error".
Now warranty over i have the error not registered on network, and can not use it for telefoning. The IMEI was correct, i can receive the network, but i can not register to it. I have the last marshmallow update flashed over OTA.
in former times, i have to remove the sim and reinsert it, to get it work again, but now this does not work. The simcard ist changed from the provider, and i bouhgt another simcard from another networkk, to test it.
Can i fix this problem?
Click to expand...
Click to collapse
Sam here, call me cynical but happened 6 months after phone ran out of warranty. Done all the basics, diff SIM from different provider reset phone, even re-flashed phone and no joy, tried all the modem software going and phone will only work on 2G. Samsung support said take it to repairers hmmm wonder what that's going to cost. New phone, New manufacturer I think. This is 2nd Samsung ive had issues with
I've only just got my first Android phone from a mate after obnoxiously using iPhones for years+, an S5 Mini that lags and ****s itself at every moment. I've now got a gangsaf little unit learning anything I can about this phone and after all my errors, not once have I seen this.
Just for relevancy, I have a G800Y model but I'm using one of the two kernels I could find that looked decent which the devs have listed under G800F and as far as I can tell or what I've read, there's no real difference other than a difference between the LTE bands they can access (someone please correct me if I'm wrong). If it would be so much as to ask what exactly is the software specifications of both of your devices? By this I mean:
- What ROM are you running; [Stock] or [Custom]?
- Have you rooted your device?
- Have you tried finding your device's most recent stock modem software?
- Did anything lead to this or is there anything you believe could have contributed to the occurence of such a problem?
- What carrier are you with in what location? If you do not wish to say for whatever reason, have you tried a search for devices with similar problems and a possible resolution method?
Hello, i have stock rom, IMEI is intact, not rooted,
Basisbandversion G800FXXU1CQB2
Kernel Version 3.4.39-895f4887
Buildnummer MMB29K.G800FXXU1CPL1
AP: G800FXXU1CPL1
CP: G800FXXU!CQB2
CSC: G800FDBT1CPL1
SIM-Card from Telekom or blau.de, both does not work.
I can receive the Providers, but can not connect.
Monday I updated the FW of my US unlocked Note 8 (N950U1 / SD-version) with N950U1UEU5CRG6.
After the update I noticed that in Settings - About Phone, My Phone Number is listed as UNKNOWN. I am using the phone in The Netherlands with provider Hollandsnieuwe (=Vodafone). I am certain that the actual phone number was correctly displayed prior to the FW update.
Not sure if related, but Find My Phone/Device does no longer work via Samsung or Google. Is does work through Bitdefender Anti Theft...
Anyone has this or other issue after the update? Thoughts?
OnnoJ said:
Monday I updated the FW of my US unlocked Note 8 (N950U1 / SD-version) with N950U1UEU5CRG6.
After the update I noticed that in Settings - About Phone, My Phone Number is listed as UNKNOWN. I am using the phone in The Netherlands with provider Hollandsnieuwe (=Vodafone). I am certain that the actual phone number was correctly displayed prior to the FW update.
Not sure if related, but Find My Phone/Device does no longer work via Samsung or Google. Is does work through Bitdefender Anti Theft...
Anyone has this or other issue after the update? Thoughts?
Click to expand...
Click to collapse
Hi, on my 2 Note8 dual sim, it is said : phone number⇒ unknown. And this from the beginning (on every firmwares). I'm in france using two french sim cards in the phone and i bought my phones on samsung shop. Until now, no problem, everything works great.
My branded, but unlocked 950F, as I paid for it the full price to use it as a prepaid phone displays the same, unknown number, since day one, I bought it directly from the major carrier in Mexico which is Telcel, everything works fine, all services and VoLTE
You mean like this seeing on my screenshot? This number is only visible if it's saved into your SIM card. Since a while, the carriers/operators don't write longer the numbers into the SIM card
So if you don't see it now, you never saw it before!
But there was an xposed module (if I remember right on android 4.4.2) where you can change this (showing) number.
(It don't changed your registered phone number!)
At that time I had found that thread
https://r.tapatalk.com/shareLink?ur...share_tid=2106490&share_fid=3793&share_type=t
That should be the correct GitHub link:
https://github.com/OXINARF/SIMNumberChanger
But it looks like there is a newer xposed module called SIMEditor - maybe that still works (when your device is rooted and xpised installed)
http://repo.xposed.info/module/com.gnufabio.simeditor
Greetings
Spoiler
Sorry for German language. The first line: Eigene Telefonnummer means "own phone number"
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
I've never had my phone number displayed in the information menu. As far back as the Note 3, no matter what firmware, official or custom, or even other phones. I live in South Africa. After reading @Logel's explanation, it now makes sense to me why it never showed to me, because of the way South African carriers assign numbers to customers.
OnnoJ said:
Anyone has this or other issue after the update? Thoughts?
Click to expand...
Click to collapse
I know it's not the exact same model, but my N950F/DS shows my phone number there like normal. Not sure why it's not showing in your case though.
So I bought a brand new Sim-free sealed note 9 from eBay last week here in Germany. Take it from the box turn the phone on and see the OPTUS logo when I power it on and then I was thrilled like WTF is this a fake phone? (didn't know what that logo is) so I searched on google and found out that is just an Australian service provider so was relaxed and then I put different SIM card in the phone and I can do phone calls and use mobile data without any problems. The only problem is that the service provider SW is Locked on Optus Australia (OPS). I downloaded different stock firmware's from SamMobile for Germany (DBT), UK (BTU) Even Australia (XSA) and still in settings at the software info/service provider is shown: OPS/OPS,OPS/OPS and every time when I turn the Phone ON/OFF the annoying OPTUS logo is shown... I tried just only flashing the CSC in Odin but still no changes... I contact the buyer on eBay and he is willing to take the phone back and full refund me. But I want to keep the phone really like the Note 9. Please help me :angel:
You have to change the CSC using a combination file ROM, as they use a multi-CSC now. In some ways, it's better than the old system but in others, it's worse.
This took me ages to figure out but after finding a guide and the right combination ROM (must match the current bootloader version else it won't boot), it worked.
Here's the thread that helped me: https://forum.xda-developers.com/t/...9-s9-csc-only-same-model-numbers-csc.3870836/
Look through all the comments if you have issues. I believe I mentioned, somewhere in that thread, the exact steps I took to make it work.
Newer versions of SamFirm have a combination ROM download option to simplify finding one (new SamFirm builds don't seem to be on the website yet but the guy who maintains it now also has a YouTube channel where he posts links. Seems to be fine except the very latest version seems a bit ad-filled).
Just so you're aware, the N960F shouldn't be carrier-locked. You just can't change the CSC like older phones could. S7 and Note 7 were the last Samsung phones that used the old CSC system, if I remember correctly. Getting rid of the carrier logo is worth it, though, in my opinion.