Hello, I was about to take my phone to a service center for check an weird noise, but since I was using CM11 with chinese modem, I decided to flash stock rom.
I'm on the old bootloader, I flashed I9500ZTOBMG1 but when I try to make a call it shows "not registered in network". I checked my imei with *#06# and it shows a generic IMEI starting with 0049...
I have already tried to reflash stock rom via odin, reflash stock modem via odin, restore to last CM backup, but problem still.
I DO have a EFS backup, it's a .tar and a .tar2.gz inside a folder called EFSProBackup, but I don't know how to use it or even how to restore my IMEI. I had already this problem before, but I don't know what I did to resolve. Can someone help me?
Problem solved: I flashed again the chinese modem via cwm after flashing a custom rom, I don't know why, but my imei is back again and working, But I still don't know how to have stock rom working....
OK - I started with a unbranded UK A300FU - CSC code BTU on 5.x
I flashed a (supposedly) UK VOdafone 6.0.1 rom using Odin and the ROM n the AP sjlot
It appears this failed - my Modem wasn't updated an WiFi failed - the advice elsewhere is to go into download from a cold phone.
Also, it would appear the firmware wasn't UK, but some germanic version
I restored from a TWRP backup
My phone details now says the "orginal CSC Code" is VD2
If I want get back to showing Original code as BT should I re-flash in Odin the firmware that matched the twrp backup ? If so , should I stil use the AP slot, or should I use the CSC slot?
Many thanks
Use CSC slot.
Also, the reason why your TWRP backup restoration didn't touch the CSC is that it has it's own partition, which one normally does not backup.
You could flash an entirely unbranded marshmallow rom of your choice, and flash the BTU CSC of lollipop, it should still theoretically work.
Hi,
Installed a Custom Rom Cm14.1 in my N9005 LTE version. After Some time i prefer restoring it to stock firmware. So I thought of restoring the TWRP backup file. Unfortunately, while restoring TWRP showed some error. Modem file not present ( not the exact error words).
Because of the error in performing a restore. I installed LineageOS. But the wifi, bluetooth and Mobile data is not working. Then I tried installing many stock firmwares of different countries downloaded from Sammobile, updato, etc but no use.
I tried downgrading my phone to Kitkat 4.4.2 and then upgrading it to Lollipop via Kies. But still wifi bluetooth and Mobile data is not working.
Please help me. Wifi and bluetooth is greyed out.
I also installed the "wifi and bluetooth fix v2.55 s5.zip" but no use.
Is there any other way. Please help.
First check your IMEI is correct .
Yes. IMEI number is correct.
Anybody to solve N9005 wifi bluetooth problem? Waiting for expert's advice. Please help.
Will restore TWRP file of stock Rom help in getting the WIFI bluetooth and Mobile data working?
If yes, can somebody upload the RESTORATION TWRP FILE (backup file) of N9005 LTE version.
Thanks in advance.
Depends upon what problem is but yes worth flashing stock rom via Odin .
Was Odin successful in flashing a stock ROM? If not, post the Odin log errors.
Thanks for the reply. ODIN stock Rom flash was successful. No problem in Odin flashing. I tried different country stockroms, No problem in Odin flashing. But the problem persists.
What is your CSC ?
DXUGBOK3
Any help?
You need a service repair .
You flashed the latest stock ROM in Odin? Tried flashing with a pit file?
Yes flashed the latest stock ROM with ODIN. But England STOCK ROM. Pit file too.
I recently updated my phone using a custom ROM, resulting in me losing the IMEI number. I installed a combination rom, G950FXXU2ARE1, to restore it. However now I am trying to install the latest firmware for my carrier, EE, G950FXXU1CRD7 and odin fails at sboot.bin. I believe this is probably related to the bootloader version (U2) - can I install another country's firmware e.g. https://updato.com/firmware-archive-select-model?record=1BAB5C246A0F11E89F15FA163EE8F90B which has the firmware number G950FXXU2CRED and still use my carrier?
I have tried to install TWRP but it fails to install with the error message "recovery image signature check fail"
Thanks
G950fxxu2are1
same probleme with her, now i don't know which stock rom use for to do working my s8 normally.
i need help thanks.
hs102 said:
I recently updated my phone using a custom ROM, resulting in me losing the IMEI number. I installed a combination rom, G950FXXU2ARE1, to restore it. However now I am trying to install the latest firmware for my carrier, EE, G950FXXU1CRD7 and odin fails at sboot.bin. I believe this is probably related to the bootloader version (U2) - can I install another country's firmware e.g. https://updato.com/firmware-archive-select-model?record=1BAB5C246A0F11E89F15FA163EE8F90B which has the firmware number G950FXXU2CRED and still use my carrier?
I have tried to install TWRP but it fails to install with the error message "recovery image signature check fail"
Thanks
Click to expand...
Click to collapse
Yes you can. I'm on EE UK also. But I use the BTU firmware. Which is UK unlocked.
Hi there, I have been using S7 Edge SM-G935F happily and a couple of days back installed the BlackDiamond NFE and was not able to connect to the cellular network or make any calls or use mobile data
Again I tried the OneUI and Pixel Experience and all seem to end up with the same problem.
Inserted the SIM into another mobile and there is no problem with the network or the SIM.
Please help me fix the problem, tell me what do I need to flash/install/update.
I guess you need to reflash the stock rom with Odin.
Thanks for the reply @ariondoneda I will flash the stock rom and will let you know how it went. Cheers
Thanks for the reply @ariondoneda I will flash the stock rom and will let you know how it went. Cheers
So, after downloading various firmware from SamMobile and all versions of Odin, I was able to flash the latest BTU firmware and with Odin v3.14.
The problem is still persistent, the same Three SIM when inserted into another mobile and in the same location gives a signal strength of -63db which is very strong.
But, when inserted back into the freshly flashed S7 Edge hardly gets any signal -113db, which is very weak
I ran out of options and looking forward for some help in getting back those signal bars back in my mobile.
Hoping someone in here knows how to solve this weird issue
Just came across such issue with another guy yesterday.. your efs got corrupted/damaged. You have to fix it either using hardware box (a local repairer shop can do)
Or
Try following this thread to word.. should give you signals back (tested by me) ..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Note : flashing firmwares again after fixing by above method would negate the fix. Above fix needs to be done after every firmware flash to get signals..
Thanks, @shan22 for pointing me in the direction of a possible solution link
I followed the guide word to word and got a success message from the box and it did reboot like mentioned in the 13th point of the guide
The final result is a no change and still, the same signal strength which is very weak of -113db and most of the times it is emergency calls only
Siddu_j143 said:
Thanks, @shan22 for pointing me in the direction of a possible solution link
I followed the guide word to word and got a success message from the box and it did reboot like mentioned in the 13th point of the guide
The final result is a no change and still, the same signal strength which is very weak of -113db and most of the times it is emergency calls only
Click to expand...
Click to collapse
Did you flashed csc or home_csc?
Try flashing dbt firmware (with the same bootloader number as your current firmware and using CSC file (NOT Home_CSC) and then doing a format data in recovery)
Then reflash btu firmware (with CSC file, NOT Home CSC) and do a format. Then retry the fix I mentioned in previous post to word..
Also tell me whats your current bootloader number.. if its less then 7 we can try fixing it via combination rom..
Sent from my hero2lte using XDA Labs
Did you flashed csc or home_csc?
A) Always a CSC and not HOME_CSC.
Try flashing dbt firmware (with the same bootloader number as your current firmware and using CSC file (NOT Home_CSC) and then doing a format data in recovery)
A) Installing the firmware as I write this.
Then reflash btu firmware (with CSC file, NOT Home CSC) and do a format. Then retry the fix I mentioned in previous post to word..
A) Will do and update you
Also tell me whats your current bootloader number.. if its less then 7 we can try fixing it via combination rom..
A) Will do
Sent from my hero2lte using XDA Labs
Hi @shan22, thanks for all your replies and time to help me out. Here is what happened. I flashed the DBT firmware which was a success and after the flashing, it started into its default recovery where it said "No command" with a dead droid symbol and died and went into the loop I forcefully started the phone into download mode, installed the TWRP, restarted into TWRP, formatted the data and started the phone into download mode, flashed the BTU firmware which also succeded and went into the same loop of "No Command". This happened a couple of times and none of the DBT or BTU firmware did actually start the system. I had no choice and finally had to install the "PixelExperience_Plus_hero2lte" custom ROM zip from TWRP which worked previously and is working now. All of this effort and it's still down to the same problem, no signal at any time
Sadly, the bootloader version is 8
Yeah version 8 .. no dice. Weird, does your phone gives any error when it gives dead android ?
Looks like you get a dm-verity error upon flashing stock firmware..
Trying flashing no verity zips in twrp after flashing stock rom..
So, your efs is indeed corrupted.
Retry all the procedure..
>flash dbt in odin using csc (not home csc)
>flash twrp in odin and boot into twrp directly without booting into phone
>flash no verity zip, then flash latest magisk zip in twp
>boot into phone
>go in download mode again and flash btu in odin using csc (not home_csc)
>flash twrp in odin and boot into twrp directly without booting phone
>flash no verity and magisk in twrp
>boot into phone and see signals..
If no signals, then from this point refer to my above posts where i gave a link of box like software to fix signals. Follow that thread to word and you should get better signals.
That's the thread : https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my hero2lte using XDA Labs
A bit of progress now. As soon as I flash, I need to disconnect the cable from the phone to boot into anything and I am carefully using the auto-reboot option in Odin.
I flashed DBT using CSC, the flashed TWRP and went into it without booting, flashed no verity, then Magisk and boot into the phone. (No errors this time)
Went into download now, flashed BTU, then TWRP and went into it directly without booting. Here when I try to flash the no-verity or the Magisk, I am seeing the error "Failed to mount /data (Invalid Argument)" followed by "Unable to mount storage" error.
Same with Magisk and if I try to wipe the Dalvik Cache or Cache.
The phone is now stuck at the flashing Samsung logo when I start it normally.
Siddu_j143 said:
A bit of progress now. As soon as I flash, I need to disconnect the cable from the phone to boot into anything and I am carefully using the auto-reboot option in Odin.
I flashed DBT using CSC, the flashed TWRP and went into it without booting, flashed no verity, then Magisk and boot into the phone. (No errors this time)
Went into download now, flashed BTU, then TWRP and went into it directly without booting. Here when I try to flash the no-verity or the Magisk, I am seeing the error "Failed to mount /data (Invalid Argument)" followed by "Unable to mount storage" error.
Same with Magisk and if I try to wipe the Dalvik Cache or Cache.
The phone is now stuck at the flashing Samsung logo when I start it normally.
Click to expand...
Click to collapse
Oof lol
You need to format data under wipe options and type yes after booting first time into twrp and then flash no verity zip and then magisk ..
This is a standard root procedure for root on android oreo, I hoped you would know that ..
Do this and re-follow all the steps I mentioned above ..
And please read forums thoroughly before messing with your phones.
Sent from my hero2lte using XDA Labs
Hi @shan22, did the steps you mentioned and passed the /data unable to mount error, followed the instructions of installing the DBT first and then BTU, somehow got the signal but, not strong as the other mobile on the same network shows. I am now doing the steps you provided the link to and will update you. Thanks again for all your help, much appreciated. :good:
Siddu_j143 said:
Hi @shan22, did the steps you mentioned and passed the /data unable to mount error, followed the instructions of installing the DBT first and then BTU, somehow got the signal but, not strong as the other mobile on the same network shows. I am now doing the steps you provided the link to and will update you. Thanks again for all your help, much appreciated. :good:
Click to expand...
Click to collapse
You won't get fully normal signals but will get atleast better or almost good signals. Since your factory efs is corrupted, it can only be restored via efs backup and combination rom with matching binary version. Since you don't have efs backup and latest combination roms aren't available, so there isn't a permanent solution for this.
Sent from my hero2lte using XDA Labs
Agreed @shan22 did go through the whole process and there is no betterment in the signal, it's just the same but a bit better than the earlier. I guess I need to look for a combination rom with the same binary:crying:
Siddu_j143 said:
Agreed @shan22 did go through the whole process and there is no betterment in the signal, it's just the same but a bit better than the earlier. I guess I need to look for a combination rom with the same binary:crying:
Click to expand...
Click to collapse
Sad to hear that, that's why I don't use fully ported/custom roms because they always have a tendency to f*** up your efs, specially if you mess with wrong options or don't know what you're doing.
Even with an efs backup(from when your phone was working correctly), you still need combination rom
And not even paid websites have version 7 and 8 binary combination roms .. the only thing I came across on a lesser known website was that name of version 7 combination rom was : G935FXXU7ATB1 . Maybe it will be of some help to anyone here
Sent from my hero2lte using XDA Labs