Hi all, I apologize for my low level of English. I want to tell that to write this report use the google translator.
I also thank in advance the help that you can give me.
Acontinuacion expose my problem:
I followed the steps in a tutorial, to release my samsung i9505 galaxy s4, exposed one of the most important forums, Htcmania.com my country, Spain.
By exposing my problem in the same forum that supra and receiving no response clarification about my problem, I turn to the more important to try to find a solution forum. I go to XDA-Developers.
I do a copy and paste of the report I wrote on the forum that I quoted earlier as I explained my problem well:
My s4 with Android 4.4.2 was completely "virgin" had installed the rom Stock samsung, was not released, was "Yoigo" any advanced recovery had not installed, and had no permits super user "root".
I wanted to release it (Unlocksim) seeking information HTCMania, and I found the following topic "Free S4 I9505 (Unlocksim) in 4.4.2" I followed all the steps in the tutorial. One of the "requirements" was to be root to do a backup of the EFS before touching anything, and to use the application "Region lock away"
So no, I did root, flashing by odin CF-Auto-Root 4.4.2 package.
Being root installed the advanced recovery "CWM" philz touch. And I found myself at this point I made a backup of the EFS system being completely "virgin" that is, with stock rom samsung and android 4.4.2. I followed the steps in the tutorial that I have made previously to unlocksim. One of the requirements to release the phone was change the modem to modem I9505_DXUAME2_MODEM, so I changed the phone modem and followed the guidelines set by the tutorial,
Region to use the application could lock away briefly display an error is possibly to blame for me as I'm seeing. This error could display for two seconds, but from that moment everything seemed to work well, the phone was released. So I changed the modem again for mine.
At this point I decided to choose to install a cooked rom based on stock, namely Omega rom v38.1 for s4 I9505.
And at this point is when my headaches begin to appear. I have experienced problems with the release ... see, the issue is that when the network coverage data is in H + the phone works perfectly, but only if H is not able to load websites etc. This has led me to the edge as I can not be aware every moment of the type of data coverage.
My questions are:
1. Is there a way to stop the phone as he was before unlocksim, ie leave it as it was originally being from Yoigo? (Remember to keep a copy of SAI realized when the system was completely untouched.)
2. How I can solve this problem with the network coverage data?
3. What do you advise me to do?
Please help. Greetings.
you might want to try searching sammobile to see there is a ROM you can download and flash that's for your country and ideally for your phone provider as well. I've run into issues like this on a couple of occasions. One was indeed that the country's ROM I flashed uses differant frequencies and I had the same mobile data connectivity issues you're talking about. This is rare for the international Samsung phones but it does happen. The other scenario I ran into was after flashing a port of the Google Play Edition onto tit, which gave it extended network options, and everything worked quite well but when I restored to stock from a backup on my sdcard I had connectivity issues, once again just like you're describing. In this scenario flashing a fresh stock ROM entirely solved the problem.
Note that in the second scenario I didn't redo the data partition. Presumably flashing the system fixed it or reflashing the firmware partition reinitialized things the way they are meant to work for me.
search for I9505 (or whatever the model of your phone is) where it says search for your device http://www.sammobile.com/firmwares/
Google around the codes if the results aren't revailing enough for what's stock for you and try reflashing in odin. If it persists then backup your apps, wipe the data partition, possibly backup your internal storage as well if you have a stock recover, and try again. Beyond that I haven't had to deal with further problems than that yet but I saw that no one else had responded...
Related
Hi everyone,
Before blasting away with comments as to why I would do this, here's my story,
I live in Canada and just brought home a i9508, a China variant of the S4. It belonged to my dad and he didn't want it so I just took it. The i9508 doesn't have Play Store, and it doesn't work on Canadian 3G network.
So to me, the phone is useless right off the start (don't intend on selling it either, who wants it?) So I had 2 options:
1) Leave the phone as it is, and probably use it once every 1-2 years when I visit HK
2) Flash custom roms on it fully aware of the risk it will have so that there's a possibility I can make it more usable
So in the end I went with option 2.
I followed a guide and flashed TWRP for i9505 using Odin onto the phone, and used TWRP to install chainfire SU, and it actually worked (but SU wouldn't open because some sort of security on the phone is blocking it)
Next step, I downloaded the CM version for i9505 and flashed onto the phone, and that worked too. Only problem I've encountered was that the phone would only boot after a fresh install. If I installed CM, turned the phone off after the initial start up, the phone wouldn't boot pass the Samsung logo.
Up until this point, I didn't make a backup, because of my arrogance, cause I have available a copy of the official firmware, in case anything happens.
So I figured at this point, maybe if I restore the original firmware, and try the whole process again, the custom rom would work. So I went into Odin, flash the firmware with PDA, and failed. It just wouldn't work. After retrying it a couple of times, and downloading different updates of the firmware, nothing worked. Only thing working right now is, I can get into Download mode, and I can get into TWRP recovery (but for some reason, I can't flash the zips that I've adb pushed onto the phone, zip can't open)
For me, if it can't be fixed, then it's really SOL. But if there's a way to fix it, I'm open to testing anything people have in mind, cause afterall, this phone is paper weight either way. I'm interested in seeing if I could enable 3G by flashing a i9505 radio, despite warnings, although, I've never actually came across a thread where someone had actually tried it before.
Either way, if someone has any idea on how to fix the phone, and wouldn't mind sharing it, that'll be greatly appreciated.
Working
I can get into Download mode, but Odin is failing (if you need the error please let me know and I'll post it)
I can get into TWRP recovery, but can't flash files
I can get into adb
This isnt the correct forum for your phone. XDA don't follow clones
Unfortunately a section for i9508 doesn't exist, so I figure the closest one would be i9505.
Anyhow, if someone has an idea of how to fix it, I'm more than happy to do testing on it, like flashing other roms or radios.
Hey im wondering where I can find a link to the W8's newest modem? Also do i need to flash both it and the bootloader?
butthurtlocker said:
Hey im wondering where I can find a link to the W8's newest modem? Also do i need to flash both it and the bootloader?
Click to expand...
Click to collapse
If you flash the latest firmware the modem and bootlader are allready included.
butthurtlocker said:
where I can find a link to the W8's newest modem? Also do i need to flash both it and the bootloader?
Click to expand...
Click to collapse
You didn't tell us why you want to change your modem, so it's impossible to give a certain answer to your question. It's not strictly necessary to flash both, but in most cases you would be best served to flash the full firmware, which will normally contain the modem and bootloader. Unless you have a specific reason to do otherwise, keep them a matched set.
Of course if you had done a search before posting, you'd already know this. You can search the forum or one of the many firmware repository sites for firmware. A quick look at Sammobile suggests that ANF3 or ANF4 are the newest 900W8 versions. Again, unless you have a credible reason to do otherwise stick to a modem from your carrier. i.e. the carrier that the phone originated from regardless of what carrier you will actually use it on.
If there is some compelling reason that you need to flash the modem only, you could extract the modem.bin file from the full firmware, package it as a .tar.md5 file and flash it on the CP line of Odin 3.09. If you are flashing the full firmware, enter the file name on the AP line.
.
fffft said:
You didn't tell us why you want to change your modem, so it's impossible to give a certain answer to your question. It's not strictly necessary to flash both, but in most cases you would be best served to flash the full firmware, which will normally contain the modem and bootloader. Unless you have a specific reason to do otherwise, keep them a matched set.
Of course if you had done a search before posting, you'd already know this. You can search the forum or one of the many firmware repository sites for firmware. A quick look at Sammobile suggests that ANF3 or ANF4 are the newest 900W8 versions. Again, unless you have a credible reason to do otherwise stick to a modem from your carrier. i.e. the carrier that the phone originated from regardless of what carrier you will actually use it on.
If there is some compelling reason that you need to flash the modem only, you could extract the modem.bin file from the full firmware, package it as a .tar.md5 file and flash it on the CP line of Odin 3.09. If you are flashing the full firmware, enter the file name on the AP line.
.
Click to expand...
Click to collapse
Haha. Well thanks for the highly descriptive answer bud. I wanted to flash the newest modem because I found I was having tons of problems with the newest builds of roms like Omega and Xtrestolite. for instance I couldnt send outgoing texts. I asked around and never got a clear answer so just from reading I figured I needed the newest modem to get everything going properly. Im very new to this even though ive been an xda member for awhile i only recently starting doing a lot of flashing. Anyways its now clear after flashing new builds as well as extracting the modem for the newest stock firmware and I still cant get texts! Thanks for the advice
butthurtlocker said:
Haha. Well thanks for the highly descriptive answer bud. I wanted to flash the newest modem because I found I was having tons of problems with the newest builds of roms like Omega and Xtrestolite. for instance I couldnt send outgoing texts. I asked around and never got a clear answer so just from reading I figured I needed the newest modem to get everything going properly. Im very new to this even though ive been an xda member for awhile i only recently starting doing a lot of flashing. Anyways its now clear after flashing new builds as well as extracting the modem for the newest stock firmware and I still cant get texts! Thanks for the advice
Click to expand...
Click to collapse
I think that your problem is highly unlikely to be caused by or solved by changing your modem. Have a close look at your configuration. If you can't find any errant settings. then do this:
Backup your system. Then use Odin to temporarily revert to the oldest 4.4.2 build (must be pre-June 3rd) for your carrier. i.e. you are installing a 100% stock build that is known not to have serious SMS issues. See if that resolves your problem or not to narrow down the source of the problem. And while I doubt that the problem is from your custom ROM per se, you could if you want just move to another custom ROM. There are a lot, the vast majority of which have no SMS issues.
At a guess, your problems are far more likely to be due to bad APN info, bad cache (clear your cache in recovery mode and also clear cache and data for your SMS client from the settings menu application manager) or a carrier side issue (open a support ticket).
If it was my phone, I'd be trying all of the points in the paragraph immediately above first. And only if that fails to resolve your problem (which is highly unlikely) would I be messing with modems, reverting to full stock firmware or migrating to a different ROM.
.
fffft said:
I think that your problem is highly unlikely to be caused by or solved by changing your modem. Have a close look at your configuration. If you can't find any errant settings. then do this:
Backup your system. Then use Odin to temporarily revert to the oldest 4.4.2 build (must be pre-June 3rd) for your carrier. i.e. you are installing a 100% stock build that is known not to have serious SMS issues. See if that resolves your problem or not to narrow down the source of the problem. And while I doubt that the problem is from your custom ROM per se, you could if you want just move to another custom ROM. There are a lot, the vast majority of which have no SMS issues.
At a guess, your problems are far more likely to be due to bad APN info, bad cache (clear your cache in recovery mode and also clear cache and data for your SMS client from the settings menu application manager) or a carrier side issue (open a support ticket).
If it was my phone, I'd be trying all of the points in the paragraph immediately above first. And only if that fails to resolve your problem (which is highly unlikely) would I be messing with modems, reverting to full stock firmware or migrating to a different ROM.
.
Click to expand...
Click to collapse
Ok noted. So i've reverted to stock a few times and SMS always worked. I've re rooted twice, tried different recoveries each time and tried a few different roms. heres what happens:
-Very first rom I've ever tried is Xtrestolite 1.2.2. . ZERO issues, kept updating as new versions came out till I got to 1.3.2. So even though 1.3.1 used the new firmware, I was still able to flash it with no issues. Then as soon as i tried the latest build, 1.3.2, couldnt text at all. I know its something to do with my SMSC because when i installed GO SMS pro from the playstore and manually inputted my SMSC i could text via that app, but not the stock one or even hangouts. Since 1.3.2 was using a slightly different firmware number I just assumed it was the modem. Exact same issue with Omega rom- V6 worked great, as soon as I flashed V7 no outgoing texts. Everything else worked by the way (incoming and outgoing calls, and incoming texts) Just not outgoing
So the reason for starting this thread is because i seem to only be able to use the last version of the 2 roms im interested in if I want to be able to text from the default app. I also checked with members using both roms, that had the W8 and they didnt experience these issues at all. We even went over the steps to get from stock unrooted to flashing the latest builds and my steps were identical to those people who didnt have my issue with the W8. I have no idea what to do but I will likely go back to stock for now. Thanks again
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?
Rogers Canada: i9505 "App stopped working" and cellular data not working off and on
Hi, I have the galaxy s4 i9505 from canada on rogers network. The actual model is SGH-i337M though. I have been using cyanogenmod but most recently, the optimized cyanogenmod 5.1.1 from alcurd. And for both OS's I have constant random app crashes from gapps and stock cyanogenmod apps. they randomly crash when i'm in them or they'll crash right away when i try to open one. they don't always crash, but it happens enough to get annoyed from it. Also my data disconnects all the time. it will say I have no service. this happens everynow and then. I've tried installing stock samsung firmware for 5.0.1 then installing cyanogenmod optimized after but it does nothing to fix it. I've even tried installing the new modem after. maybe I didn't find the right one, i'm not sure. Does anyone know what could be causing these issues and help me out with how to fix them or does anyone know a good rom that wont have these issues? I want a cyanogen like rom or pure android. I hate samsungs stuff lol. Thank you so much if you can help :]
OathVyne said:
Hi, I have the galaxy s4 i9505 from canada on rogers network. The actual model is SGH-i337M though.
Click to expand...
Click to collapse
Then you don't have an I9505.
I don't think there is a separate modem file available for your S4, unless it's in the forum for your device, so you'll likely have to download the complete ROM. The correct ROM for your S4 is here. Make a nandroid backup of your current ROM and make sure it's saved to the MicroSD card. Flash this ROM through Odin, let it boot, and let it take care of its business. Then head back into download mode, flash your custom recovery, reboot into the recovery, and restore your nandroid backup.
I would try and find just the modem and bootloader package for your S4, as none of the modem/bootloader packages here are for your device. If you can find that, then you can avoid having to do all the steps above and simply flash the modem and bootloader via Odin.
With luck, installing the right bootloader and modem will cure many of your issues.
Strephon Alkhalikoi said:
Then you don't have an I9505.
I don't think there is a separate modem file available for your S4, unless it's in the forum for your device, so you'll likely have to download the complete ROM. The correct ROM for your S4 is here. Make a nandroid backup of your current ROM and make sure it's saved to the MicroSD card. Flash this ROM through Odin, let it boot, and let it take care of its business. Then head back into download mode, flash your custom recovery, reboot into the recovery, and restore your nandroid backup.
I would try and find just the modem and bootloader package for your S4, as none of the modem/bootloader packages here are for your device. If you can find that, then you can avoid having to do all the steps above and simply flash the modem and bootloader via Odin.
With luck, installing the right bootloader and modem will cure many of your issues.
Click to expand...
Click to collapse
Would it be this: http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758 ?
It only has modem file, theirs no bootloader :/
It's marked "Modem/Baseband" so the one file should cover both. But even without the bootloader the modem should still be able to be flashed.
The Story
Don't even know where to start. Okay so I have a SM-935W8 (Canadian Version) and it was working perfectly fine running Project Dream rom the S8 one. I decided to flash angelo's Pixel rom for S7 Edge and for some reason when it booted, the network had a cancel sign meaning no network. Once I finished the initial setup, calling, messaging , and data weren't working. Luckily I have a backup for EFS and RADIO in tar, img. and tar.gz formats. So I downloaded the Partitions Backup app and restored the EFS and Radio files, it said successfully restored. I rebooted my device and the issue was still there, no network. So then I installed the stock ROGERS (Provider) rom from SAM MOBILE and it came up with some DRK error and my phone would not boot. So then I quickly used ODIN to flash twrp and then flash Superman Rom (Love it) and use dm-verity bypass.zip to get past the drk error. Then I attempted many other things but to no avail such as flashing the EFS tar through ODIN which caused a "Software Error" and phone to be stuck on a light blue software error screen so I had to use smart switch to FULLY restore the phone back to booting up, then once again I flashed twrp and Superman rom with dm-verity so I atleast have root and a decent rom to work from.
The Problem and What I Have at Disposal
So essentially, I currently have a new section in settings under Connections called "SIM card manager" for managing sim cards even tho I only have 1 slot, it shows that the SIM is ROGERS and LTE/3G/2G in there, but it can't connect to a network and keeps saying Not Registered on a Network. Also, there are 2 IMEI's since my phone thinks theres 2 SIM slots but I really only have 1 slot. BUT HERE IS THE MAIN ISSUE, THE ROOT OF ALL PROBLEMS, the IMEI is reading as "000000000000000" and the IMEISV is "01". Hence im getting Not Registered on a Network. No secret codes such as *#06# are working, keeps giving the Not Registered on a Network error.
I have the EFS and RADIO backups in img, tar, and tar.gz formats as well as screenshots of all my MAC and Bluetooth addresses, IMEI and Serial #'s and all that information. So essentially I feel fully ready to solve the problem but everything I try keeps failing. My EFS restoration says successful in the APP but upon reboot, theres no change. Flashing the EFS through ODIN messes up phone harder. When I use EFS Professional Tool, where do I place the partitions so they show up in the tool?
I used this post to try to fix it: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
BUT when I'm flashing the combination through ODIN in AP, it goes to NAND write or whatever and gets stuck, sometimes it gets stuck on Analyzing files or something. I tried every single ODIN version. I really could use some expertise on this issue. A step by step written tutorial, some method anything!!!! Help on this post or even teamviewer or skype for live help would be appreciated. Please help and I'm willing to compensate for successfully helping me fix my issue..
Did you ever sort this out? I'm in a similar situation, except that it does occasionally show my IMEI but also 'baseband unknown'. But still no network access.
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
012345678 said:
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
Click to expand...
Click to collapse
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
jamesroodney said:
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
Click to expand...
Click to collapse
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
012345678 said:
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
Click to expand...
Click to collapse
Sorry, I should have clarified. I have an S7 (SM-G930W8). I only tried this thread because the issue was identical to mine and I couldn't find anything similar referencing the S7 specifically.
For anyone coming across this thread in the future, although mine was an S7 I think the issue would apply to both. I ended up ordering a z3x in order to use the patch certificate. But it wasn't that easy; the firmware had to be downgraded to marshmallow first which wouldn't work in Odin until I tried just flashing the BL and CP files first, then rebooting and flashing the AP and CSC files separately. In fact, the AP file froze the first time but passed on the second attempt. After that, everything was downgraded to android 6 and then the patch certificate option worked and my s7 connects to the network again.
I'm having a similar problem with my sm-g935w8 Rodgers but has been unlocked. A couple days ago i looked at my phone and it was showing a no signal symbol and I look for my phones information and it showed unknown in all categories, the imei say unknown, and it's not reading the sim. Help me
I am having the same problem after installing TGP ROM.
Graschuk said:
I am having the same problem after installing TGP ROM.
Click to expand...
Click to collapse
Did u Found any solution? am still in the same position as u r in.. i have also installed TGP ROM ... I Have Also Posted there my issue that i selected the latest bootloader nd modem blah blah
Wipe everything in twrp advanced and..
Flash latest stock rom for your model and it'll fix the issue
I think u need to see this
https://forum.xda-developers.com/showthread.php?p=78868375#post78868375
These two threads are the fountains of info :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
This one specifically for S7 edge, whole lots of info.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
This one for advanced users who know what they are doing.. it isn't specifically for s7 series but has a universal approach to understand concepts.. don't use the provided drk (prov data) and csc restoring files, they aren't for s7 edge.
Always backup efs and all radio/serial related info firstly after rooting. Good luck
Sent from my S7 Edge using XDA Labs