Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Alright so... I got this N900T and rooted it and tripped the knox warrenty bit.
I installed the latest DomPop and read how the efs partrition had some issues and it being easily borked, and well I didn't wanna risk it. Rather than look into how to back it up properly using better tools, I had remembered a command from the S3, su reboot nvbackup, which is supposed to back up the efs stuff to a safe place on the phone. However, upon finishing that command it bootlooped. Well, i then ODINed back to 5.0. my baseband version is unknown, IMEI is unknown, all of the typical EFS is messed up stuff. So i tried, stupidly, the other command to restore the backup, su reboot nvrestore, and upon running that command it forced itself in download mode unable to boot.
i odined back to the 5.0 firmware about 4 more times and nothing happened.
I searched and searched and i tried following http://forum.xda-developers.com/showthread.php?t=2567133, i tried the the script it links to remake the partrition for the EFS.
My serial is still on the phone, i skipped down to the part about repairing the imei. I put my phone in RMNET+DM+MODEM, however it doesnt get picked up by EFS Professionals NV Tools. Any more ideas or help?
Also, is it safe to flash the 4.4 Kitkat without the phone bricking?
If there is anything i cannot do on my computer, are there services cheapish i can send them to and have them flash my IMEI back onto my phone?
Thanks in advance!
Me can not follow
Okay, so I used "reboot nv backup" without first researching to to back up my EFS partitions. Upon reading further into the stuff, I have found that that method destroys your partitions and shouldn't be used. I then, kind of freaking out used the other function "reboot nv restore" which is supposed to restore the backup, but instead it caused my phone to not be able to boot. So I odined back to stock 5.0. I have tried flashing just the modem, I have tried downgrading to NK3(4.4) but that had not helped me either. My baseband is still unknown and my IMEI is still null.
Is the only way to fix this with a UART cable and box? Are there any paid services I can use online to repair those partitions? I attempted to use EFS Professional, however it couldn't talk to my phone, either the SPC Code or the 16 digit security code wouldn't work so I couldn't write the IMEI back that way.
Ravenjolly said:
Alright so... I got this N900T and rooted it and tripped the knox warrenty bit.
http://forum.xda-developers.com/showthread.php?p=46436273
Not sure how is this going to help but there was a user (other than the poster) managed to recover his imei. I believe you could use any help at this moment.
Click to expand...
Click to collapse
Rosli59564 said:
http://forum.xda-developers.com/showthread.php?p=46436273
Not sure how is this going to help but there was a user (other than the poster) managed to recover his imei. I believe you could use any help at this moment.
Click to expand...
Click to collapse
Sorry, I have tried this and it didn't work. Thank you for looking for me.
Have seen many people with IMEI unknown and none of the threads I have read managed to get it back. As far as I know you are now hard bricked, at least regarding the actual phone part of your phone.
Hello,
I have this problem with my phone and i don't know how to fix it, the IMEI is Null and when i enter "*#0011#" the ServiceMode is Blank !!
I tried to use GS5_EFS_Backup but it doesn't work ! Also the phoe get hot a lot, and when i put it in charge the battery level of charge is stuck in 10% always.
My phone is rooted.
Help me Please.
Thank you
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
*Detection* said:
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
Click to expand...
Click to collapse
Thank you Detection for your answer. So where can i find another S5 EFS, and how can i restore it.
Help me Please because i tried already to take it to a repair shop but they don't know how to fix it, that's why I wanna try to repair it myself, and i think its one of the repair shops who wiped the EFS partition without making a backup (because i give to 3 repair shops and they don't know how to fix it).
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
*Detection* said:
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
Click to expand...
Click to collapse
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Nope, not if you've deleted the EFS partition - that contains the IMEI and Radios
Ok thank you, ill try to contact samsung after sales service.
Hi everybody,
I have same issue:
I needed to update SU-binaries and tapped accidentally on CWM/TWRP-Mode instead of normal. After this IMEI is null, Service Mode blank, sudden reboots and unable to install any Apps (always saying no free memory). uninstalling App causes reboot.
I have efs backup made with (PhilZ Touch) CWM, but I'm not able to fix the problem with it.
What I tried:
flashing Stock ROM + updating Bootloader in Odin
this Guide (except Samsung Tool and Terminal Emulator steps, as I can't install any App)
CWM script
I really don't know what else I can do. Does anybody have some other ideas?
Also backing up is not possible, now. EFS Professional says specified PIT file does not exist, even when I choose all partitions.
FIXED. Possible solution.
Fixed. Went to a shop to repair IMEI/EFS.
It seems there is something called "IMEI NV Generator", this should also do the magic and would have saved me some money.
samsung S5 Imei Proplem
zicozack said:
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Click to expand...
Click to collapse
I have the same problem after trying to change the original IMEI>>> any help please
Please take a look here and here.
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Hello...
Unless you have a TWRP EFS backup, there's not much you can do...
I already saw some people saying that a restore from someone else EFS backup solved the problem and their proper IMEI, etc were back. I never had the issue, so I can't confirm it really works.
Now you need to find someone who can give it to you.
Otherwise you can RMA...
Good luck...
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Sent from my Nexus 6 using XDA-Developers Legacy app
CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
Hello...
Since his IMEI disappeared, there must be infos about it somewhere in the EFS. I don't know what else...
Cheers...
CyberpodS2 said:
Is there any personal info in the efs backup? I would be happy to help but am not going to jeopardize privacy...
Click to expand...
Click to collapse
I think giving someone a copy of your efs partition essentially gives them the information needed to clone your phone, so it's not something you would want to do for a stranger.
blckhwkone said:
Hi everyone,
Google messed up ! I received the OTA for the 7.1.2 uptdate last thursday. After it my phone was unable to detect my SIM card, my IMEI number disappeared, neither base band.
The first thing i've tried is to get a new SIM card, with no result, then I tried a soft reset, an hard reset (factory reset+wipe data), and wiping the cache without any positive result either. I've contacted Google, the phone was from Google Store and my 1 year warranty expired on 25/03/17 (the update was installed on 05/04/17, exactly two week later), they refused to take it back, nor RMA, a shame! I think it will be the last Google phone I buy!
I've tried to flash the full factory image of 7.1.1. but nothing positive from it. I think the OTA corrupted my EFS data files but no idea on how to fix it. The thing is when i'm going to the bootloader, under barcodes menu i still find an IMEI number.
I don't know what to do now, I'm little bit desperate, if anyone have an advice here.:crying::crying:
Thank you in advance.
Nexus 6P
7.1.2 build N2G47H
kernel 3 .10.73-g0a21e4c
Bootloader locked
Unrooted
Click to expand...
Click to collapse
Google's been messing up along recently
blckhwkone said:
Google messed up !
Click to expand...
Click to collapse
Several people have been able to recover from this by wiping both the EFS partitions, but because your bootloader is locked (and USB debugging probably not enabled), I don't believe there is any way forward. See the link for the method used: http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
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