1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.
Related
Hey guys,
After discovering the latest root method I was excited to try it out. Unfortunately, I botched it up and had to reflash the stock firmware. I downloaded the T-Mobile PD8 file from Sammobile for the G935T and flashed all the packages. I got root working, and everything seems to be fine except for the absence of these three features. There are no options for any of them in settings or their respective apps. I live in an area with bad coverage so I am pretty dependent of Wi-Fi calling. Even reflashing that HOME_CSC file didn't help. Now I'm not sure what I have to do to get these features back.
Any help would be appreciated.
You're sure that you used HOME_CSC for T-Mobile? I'm thinking that either you didn't download the correct firmware (example being that you may have downloaded for Cricket or something of that sort) or you could have used the CSC_TMB file by mistake. As far as I know, they should both be the same, only HOME_CSC doesn't wipe the data from your device. Remember seeing an error of any kind after flashing?
Binary100100 said:
You're sure that you used HOME_CSC for T-Mobile? I'm thinking that either you didn't download the correct firmware (example being that you may have downloaded for Cricket or something of that sort) or you could have used the CSC_TMB file by mistake. As far as I know, they should both be the same, only HOME_CSC doesn't wipe the data from your device. Remember seeing an error of any kind after flashing?
Click to expand...
Click to collapse
Yeah I'm pretty sure it's the right file...
HOME_CSC_TMB_G935TTMB3APD8_CL7856276_QB9546824_REV02_user_low_ship_MULTI_CERT.tar.md5
No errors, I also reflashed the BL and CP to no effect... Not gonna do the AP because it will make me lose root.
bump
I flashed the entire stock firmware and the features are STILL missing. I'm getting tired of reinstalling all my apps. Does anyone have any ideas?
TheDoolster said:
bump
I flashed the entire stock firmware and the features are STILL missing. I'm getting tired of reinstalling all my apps. Does anyone have any ideas?
Click to expand...
Click to collapse
Without going through the why or how that all happened and the ways to resolve without reflashing, I'd just recommend that you download the full PD8 firmware from this thread http://forum.xda-developers.com/showthread.php?t=3331528
I would skip the repackaging .tar part to preserve /data. Worked for me and hopefully will for you.
(PROVIDING YOU STILL ARE EXPERIENCING THAT ISSUE)
Before yesterday, I found myself in the exact same situation. I had a rooted device with all of my apps installed - including Xposed modules. But I had lost WiFi Calling. I didn't even see VoLTE settings in the Phone app. So I started from scratch. I wiped out my system. I then used ODIN to flash ADB8 firmware from T-Mo. WiFi Calling was there. I then used ODIN to flash EngBoot. WiFi Calling was still there. I then rebuilt my entire system w/o Xposed. WiFi Calling was still there. I then started to add all of my modules, one at a time. After loading everything, WiFi Calling was still there.
I then started AFWall+. Lo and behold, WiFi Calling completely disappeared. I turned off the firewall. WiFi Calling was there. So I left it turned off and started to configure my modules. WiFi Calling worked - until I loaded the crowd-sourced rules for XPrivacy. I turned of XPrivacy and WiFi Calling returned.
It all makes sense. I know know that the Phone app must connect to a wireless network via TCP/IP. And if it can't, then WiFi Calling is disabled. So I spent several hours working through XPrivacy and AFWall+ rules. And at the end, I now have a fully functional phone.
I don't know if you use AFWall+ or the XPrivacy Xposed module. But you might check any control systems that could limit the connection between the Phone app and the network.
Don't use HOME_CSC. Use CSC. This will wipe data unfortunately, but i had different issues using home. And using the non-home fixed them.
Flashing the July 9th updated firmware from sammobile worked for me. Lost root, but I would rather have these features.
I unrooted my Galaxy s7 edge with Rogers and I am miss the option for volte any ideas on how to get it back?
Not the right csc
The home_csc is not the right one for t mobile. It should be home_tmb_csc
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
vexx32 said:
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
Click to expand...
Click to collapse
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
dirtydodge said:
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
Click to expand...
Click to collapse
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
vexx32 said:
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
Click to expand...
Click to collapse
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
dirtydodge said:
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
Click to expand...
Click to collapse
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
vexx32 said:
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
Click to expand...
Click to collapse
Yea it works. I know that one does. You'll get a message that says "unauthorized SIM card: or something like that. Just ignore it and use WiFi to setup the phone. Once you have it setup use package disabler or titanium to freeze "setup wizard" and that'll get rid of that notification. You'll have to manually setup your AT&T APN. After that your golden.
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
Hi, I got a S7 Edge SM-G935A from AT&T at the end of December.
That same night I tried to root my phone(i got a bootloop), and I didn't know the bootloader was locked.
So I re-flashed a SM-G935U rom, but I would like to go back to the basic one in order to get a new start(SM-G935A), without root and nothing.
Knowing that I have a problem connecting to the wifi, maybe because of the rom that doesn't match.
And also i dont have samsung updates, i'd like to have the latest one im currently on 7.0.
If someone could help me to get my phone with original firmware, I'd be grateful.
Ok, first off, you can run any US/Qualcomm variant software on your device. Unless you just have a hankering for AT&T firmware, the U firmware will work just fine. Either way, find a full copy of either A or U firmware and ODIN it down, and you will essentially factory reset your device in the process.
There are links to both in this forum. I personally prefer U because it is faster and less bogged down with carrier crap, but if you are an AT&T customer, there are decent enough reasons to stick with A.
NOTE: you may need to use Prince Comsy's ODIN tool if you get a mismatch error. Unfortunately, there is no universal ODIN tool, but as a general rule, if you are CHANGING variants you need Prince's. If you are writing over the same version, you need the official.
jshamlet said:
Ok, first off, you can run any US/Qualcomm variant software on your device. Unless you just have a hankering for AT&T firmware, the U firmware will work just fine. Either way, find a full copy of either A or U firmware and ODIN it down, and you will essentially factory reset your device in the process.
There are links to both in this forum. I personally prefer U because it is faster and less bogged down with carrier crap, but if you are an AT&T customer, there are decent enough reasons to stick with A.
NOTE: you may need to use Prince Comsy's ODIN tool if you get a mismatch error. Unfortunately, there is no universal ODIN tool, but as a general rule, if you are CHANGING variants you need Prince's. If you are writing over the same version, you need the official.
Click to expand...
Click to collapse
Im not living in the USA and AT&T doesnt exist where i live, but sometime i have a issue with my wifi "internet may not be available" is because of the rom?
Leqz said:
Im not living in the USA and AT&T doesnt exist where i live, but sometime i have a issue with my wifi "internet may not be available" is because of the rom?
Click to expand...
Click to collapse
Then this is easy. Go download the U firmware and use Prince's ODIN to convert it to a G935U. If you aren't on an AT&T network there is zero reason to keep your device on A firmware, starting with the fact that you will never get updates. (AT&T firmware will only update if you have an AT&T SIM installed.)
jshamlet said:
Then this is easy. Go download the U firmware and use Prince's ODIN to convert it to a G935U. If you aren't on an AT&T network there is zero reason to keep your device on A firmware, starting with the fact that you will never get updates. (AT&T firmware will only update if you have an AT&T SIM installed.)
Click to expand...
Click to collapse
Only add-on is to perform this from a Windows 7 pc and not 10. Prince kept crashing on 10 and worked fine on 7.
Has anyone had success using the U modem with the newer firmware on a carrier outside of Sprint?
There is an article here about it and you can disable any warning messages with a package disabler.
Since the U firmware doesn't work, just wondering if anyone has tried this.
I have one I am willing to sacrifice if you want me to test something out. I'd like to try and flash it to Verizon for a friend.
If doesn't have the latest firmware, I wouldn't even bother because you can just put the offical u or verzion firmware on it.
Here is the process in a nutshell:
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in verizon sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Thanks for the info. I just screwed up and updated to the latest firmware. So with that said the sacrificial lamb still stands...
V3racious said:
Thanks for the info. I just screwed up and updated to the latest firmware. So with that said the sacrificial lamb still stands...
Click to expand...
Click to collapse
Like I said, I see the additional bands, but have no idea if they are useable since sprint doesn't use them.
lvpre said:
If doesn't have the latest firmware, I wouldn't even bother because you can just put the offical u or verzion firmware on it.
Here is the process in a nutshell:
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in verizon sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Click to expand...
Click to collapse
Can I do this if I am on the latest firmware?
V3racious said:
Can I do this if I am on the latest firmware?
Click to expand...
Click to collapse
Yes, you are just changing the modem [ap slot]. It worked for me and the bands show up for me as options, but no way of knowing they actually work. I have sprint, so testing a carrier with different bands is the only way.