Modem-cp crash+imei,drk lost[G935F] - Samsung Galaxy S7 Edge Questions and Answers

I flashed the combination of binary U2 to restore my i Mei and drk error but it shows modem crash in the binary mode and cp crash mode.
I hope someone can give me a solution that's useful and it's okay for me to pay by PayPal after it has been fixed.
The following is the message I sent to cubz but he doesn't seem to be free to active these days so I hope anyone else can help me.
The letter :
{{{{Hi, I've seen many posts in the xda and many people refer the solutions and fix advice to your name on comment so I think you will be the only one who can help with my issue.
Firstly, I had my S7 edge flashed with many roms before and flashed with odin ( with sim card always, not knowing if this is a major problem), but after once I did after using the encryption on the S7 edge with the lineage OS ( the 8.1.0 one in Feburary), I tried to flash with other rom without decrypted it and flashed fail. ( roms are all android 7.0 and 7.1.2)
Since then, I tried to flash other rom (7.0 like superman rom or rom from SAC) but still losing cellunar signal. then I tried to flash the original android 6.0 official firmware through odin but it failed on the step which shows DRK error on the samsung official 6.0 recovery.
After reading your post on how to fix DRK error, I tried the method but maybe because of I don't really know the steps or how to restore on the binary factory firmware, it boots up but still lose of IMEI and cellunar signal.
After the android 8.0 is released officially, I flashed the official rom and I tried using the U2 version of bootloader binary factory which you shared, but same problem happens and I also tried the V5.7 devbase rom and same.
Very seldomly the baseband and imei will show as normal and having cellunar signal but not long and after I reboot will gone to unkonwn to the imei and baseband and show as 'no sim card'. ( there was one time that I ticked clear efs on odin then i lost the imei. But after i flashed the binary firmware, imei show unknown in the binary firmware mode but when i flashed back the devbase rom with twrp, the situation of mostly showing unkonwn of baseband and imei happens but very seldomly it will load as normal which they are shown correctly)
*Btw the first flash the U2 binary firmware( Im using the U2 version because my bootloader has been updated to the oreo one), it boots into the screen that shows cp upload or modem upload error? page , then i flash again but with efs clear which was what happened as I mentioned before. ( thats the only time I ticked EFS clear as i can remember)
Dear CuBz90:
I really hope that my s7 edge can be fixed because I have had it for more than two years already and it was the first time that i buy a phone using my own my money but not my parents, I hope you can help me with this issue.
Thank you very much!!!
( its okay if I have to pay( its okay through paypal) after its fixed, but hopefully not too much)}}}}
Cp crash upload exactly same as photo I found in the following link: (please add www by yourself coz it doesnt allow me to post external link as being a new user)
.galaxys-team.fr/viewtopic.php?t=49038
Thank you for patiently read and helping me to find solution for my S7edge (G935F)

help me too
I have the same problem... idk what i can do.................:crying::crying::crying:

it's my pleasure to help you

Related

[Q] HELP NOTE 3 N900 UNKNOWN BASEBAND, NULL IMEI completely out of Nowhere!

Hello Fellas, am posting here as I haven't found help elsewhere. Kindly Respond to my woes. I have a rooted Galaxy Note 3 N900 running official Lollipop with IMEI Null/Null and No Baseband version. The IMEI just disappeared totally out of the blue as no custom ROM has been flashed on the device!! This has happened 2 months after updating from 4.3 Jelly bean. With no prior EFS Backup here's what I have tried:
1. EFS Professional (backup&restore complete but no luck)
2. EFS Restore express ( backup.bat>Odin restore)
3. GSII Repair tool
After hitting no luck with the above tools and without any "/EFS mount errors" in recovery either and WIFI working fine, I came to a conclusion that most probably the EFS folder partition on my Note 3 is still intact and most probably this could be a case of a bad modem which would explain the loss of Baseband Version and thus the Null IMEI. So I tried flashing back to KitKat with N900XXUENG1 firmware and separately flashed a few modems compatible with Samsung's new EFS System: N900XXUENG1_MODEM, N900_XXUENF2_MODEM_CWM and also gave a shot at recommended N900_XXUENE1_MODEM_CWM.ZIP which seems to restore baseband for many users with this issue but this failed as well. After much searching I found a 4file_N900XXUGBNL8 Lollipop Firmware with PIT from Dev-Host, flashed all files in Odin&even repartitioned the device but still no baseband!!! WIFI&everything else runs smooth except the damn baseband/Null IMEI! Almost Exhausted my options...
Now I trust we have some informed members and developers here, NEED YOUR VALUABLE IDEAS HERE mates! Someone, anyone.....Thanks!
Have got any guarantee of the device?If so,send it to service ıf your guarantee continiues.
If you bought the device from another country,This may occur ıf you didn't register it.(In my country this is how it works.Turkey)
Or someone cloned your imei,check your imei ıf it is valid.
This is not because you upgraded your device to android 5.
If ıt was the case,you would have already faced the problem after just the flash.
I would say flash another modem
But,You say you tried flashing other modems.So no luck with that.
I had seen s3 with the same problem.I had flashed a modded modem.
It worked.I dont know if there is one for your device.
Briefly this is an imei/modem problem.
I don't know ıf the suggestions above help you.
I hope so.
Good luck.
try flashing stock rom from sammobile via odin. you need to backup efs folder everytime you flash a new rom, that's my opinion. may be wrong.
I think I used to had this problem with my Note 2 as well. If you come from 4.3 you should flash stock ROM Jelly bean 4.3 from Sammobile or Samsung-updates website. Then flash lollipop 5.0 over 4.3 when you can see your IMIE. Maybe it will work.
So. If u in L bootloader. U must! Flash the L modem that sometimes didnt get flashed by the odin while flashing stock rom. So just extract the modem.img and things for modem. Then just flash it using dd command or make flashable zip. Then it works fine. I have it on s4 exynos. That if i in L bootloader then even i install kitkat rom with L bootloader. U must still flash the L modem. K. Hope it works
1. İf you couldnt recover with efs professional , probably you've been lost your original imei files like nv_data.bin etc. and there is no backup...
2. So try to remake this kind of files with-again- with efs professional. But there is not so much info about this "creation" process.
3. I had the same situation. . . . And i'm still sorry. . . ( . . . The other solution is JTAG, more easy, cheaper in total and psychologicaly healty !!!)
GOOD LUCK....
m6112 said:
1. İf you couldnt recover with efs professional , probably you've been lost your original imei files like nv_data.bin etc. and there is no backup...
2. So try to remake this kind of files with-again- with efs professional. But there is not so much info about this "creation" process.
3. I had the same situation. . . . And i'm still sorry. . . ( . . . The other solution is JTAG, more easy, cheaper in total and psychologicaly healty !!!)
GOOD LUCK....
Click to expand...
Click to collapse
All EFS folder files are present including nv_data.bak&.bin Am a bit reserved to go the JTAG way just yet.
white7561 said:
So. If u in L bootloader. U must! Flash the L modem that sometimes didnt get flashed by the odin while flashing stock rom. So just extract the modem.img and things for modem. Then just flash it using dd command or make flashable zip. Then it works fine. I have it on s4 exynos. That if i in L bootloader then even i install kitkat rom with L bootloader. U must still flash the L modem. K. Hope it works
Click to expand...
Click to collapse
Thanks for that but as I already said I was lucky to find a 4file partitioned Lollipop ROM with separate modem. Flashed that through Odin and even repartitioned the device but that hit a rock as well!
longcoming said:
Have got any guarantee of the device?If so,send it to service ıf your guarantee continiues.
If you bought the device from another country,This may occur ıf you didn't register it.(In my country this is how it works.Turkey)
Or someone cloned your imei,check your imei ıf it is valid.
This is not because you upgraded your device to android 5.
If ıt was the case,you would have already faced the problem after just the flash.
I would say flash another modem
But,You say you tried flashing other modems.So no luck with that.
I had seen s3 with the same problem.I had flashed a modded modem.
It worked.I dont know if there is one for your device.
Briefly this is an imei/modem problem.
I don't know ıf the suggestions above help you.
I hope so.
Good luck.
Click to expand...
Click to collapse
It's an old device, no warrants. Am indeed looking at the possibility of someone else allocating the IMEI to their device, though i doubt. But if that was the case shouldn't the Baseband at least be present?
Did you try downgrading to 4.3 with official stock files?
If not,give it a shot.
Droidsan said:
It's an old device, no warrants. Am indeed looking at the possibility of someone else allocating the IMEI to their device, though i doubt. But if that was the case shouldn't the Baseband at least be present?
Click to expand...
Click to collapse
I have explained it earlier, Actually it is kernel. Newer kernel makes some changes on EFS partition and that changes can not be read by old kernel but in this case once you flash newer modem it will be solved. If your issue doesn't solved by flashing latest stock ROM then only possibility is messed up EFS partition and for that you must have a backup which was created when your device was normal. If your EFS partition is corrupted and you don't have backup then i think only option you have is to go to service station they can repair it easily. Though your device is not under warranty but you have official bill then still they can do it with paid service. Now a days samsung have changed policy and restoring IMEI they needs to do it online with samsung server (this information I got from service center owner in my city who is my friend and he did same for one of my friend)
UPDATE:
dr.ketan said:
I have explained it earlier, Actually it is kernel. Newer kernel makes some changes on EFS partition and that changes can not be read by old kernel but in this case once you flash newer modem it will be solved. If your issue doesn't solved by flashing latest stock ROM then only possibility is messed up EFS partition and for that you must have a backup which was created when your device was normal. If your EFS partition is corrupted and you don't have backup then i think only option you have is to go to service station they can repair it easily. Though your device is not under warranty but you have official bill then still they can do it with paid service. Now a days samsung have changed policy and restoring IMEI they needs to do it online with samsung server (this information I got from service center owner in my city who is my friend and he did same for one of my friend)
Click to expand...
Click to collapse
Thank you Dr.Ketan for that information. You have been a great help to many. I have followed your posts about this issue and I feel there is still hope.
UPDATE:
I WAS ABLE TO RESTORE THE BASEBAND AND NOW THE IMEI IS GENERIC, READS 004999010640000. [/B] I was able to restore nv_data backup from /Efs folder and deleting bad nv_data. Here's what I did:
Using root Explorer in /EFS:
Deleted corrupt files;
nv_data.bin ( 18 April 2015)
nv_data.bin.md5 (18 April 2015)
Renamed backup files (dated 31 Jan 2015) to apply;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
Using ADB shell:
Code:
adb shell
su
umount /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
Reboot
However, the baseband and generic IMEI come&go across reboots and seems not to stick permanently. Any possible steps from here???
NOTE: Previously I have been able to restore Unknown Baseband and Null IMEI in Galaxy S2 i9100 using the above adb method (Code Only) http://www.selftechgenius.com/?p=284
NOTE: Previously I have been able to restore Unknown Baseband and Null IMEI in Galaxy S2 i9100 using the above adb method (Code Only) http://www.selftechgenius.com/?p=284
Try this out
I always have that problem when I downgrade to jellybean but solving it is easy. Just flash THIS modem file under the AP option Odin. Tell me if it works.
Muthumbi said:
I always have that problem when I downgrade to jellybean but solving it is easy. Just flash THIS modem file under the AP option in odin mode. Tell me if it works.
Click to expand...
Click to collapse
If flashing modem via Odin you MUST turn off the phone then start it in DL mode. Simply doing a 'reboot' into DL mode will not let the modem be flashed.

dm-verity verification failed

2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.

[SOLVED] IMEI lost after flashing a rom

Hello,
Today I tried to flash KING OF NOUGAT v13 but my phone got stacked on Samsung Logo(+30min). I was forced to restart it(Power+Volume Up) and flash the recovery that made before flashing. To my surprise when the phone boot there was no connection(only Wi-FI). As far as I can see IMEI, Bluetooth and Mac address are unavailable. I tried different backup(I have two on SD card) but the problem was the same.
When I created the backup I made a full backup including EFC, but for some reason, it's not working.
I also tried this article , and put those commands in the terminal but no result.
I know there is an option to fix it if I flash the stock rom . But i would like to know if there is another options
there is sticky thread with info how to get imei back, so just read and follow
yaro666 said:
there is sticky thread with info how to get imei back, so just read and follow
Click to expand...
Click to collapse
Actually, the problem was the the Bl and Cp, After I flashed the latest everything workout
Can you please share the link to the latest BL and CP ...i am facing the same issue after flashing the leaked oreo update...and i cant flash older BL verrsions anymore,and i cant use any sim either....
download the newest rom and extract it yourself, easy as unpacking
yaro666 said:
download the newest rom and extract it yourself, easy as unpacking
Click to expand...
Click to collapse
I tried but it still shows this error
SW REV check fail device 2 binary 1
it flashed without any bl other ap cp and csc but gives error while flashing the BL file....did u flash the nougat BL file,or any other one ?
Sariful Alam Fahad said:
I tried but it still shows this error
SW REV check fail device 2 binary 1
it flashed without any bl other ap cp and csc but gives error while flashing the BL file....did u flash the nougat BL file,or any other one ?
Click to expand...
Click to collapse
same here i downloaded the latest version i could find and i cant flash the bootloader and flashing CP doesnt fix anything

IMEI number lost after flashing ROM (no backup)

I know there might be another similar topic but I couldn't find any help so far.
Basically two days ago I flashed custom ROM on my phone, I didn't make any backup. At first it worked perfectly. I decided to flash ROM again and formated my phone and found out that EFS partition was lost. I didn't get any mobile data and my IMEI number was lost (0000000). I've read that IMEI is actually stored on some chip so is there any way to restore it back? My phone is Samsung Galaxy A5 2017. Any help will be appreciated.
Trying to flash latest stock rom from sammobile but after flashing it with odin it starts bootlooping and saying "no command" again and again. When holding power + home + volume up I can NOT access recovery. Any solutions, please?
Anyone? Is there any solutions for my problem??
Is it possible to downlaod EFS file for my phone and somehow change IMEI in the file?
just flash stock rom, i did on my galaxy ace i flashed custom rom and imei gone, after stock flashed via odin imei back.
Thanks for your answer! I tried indeed flashing latest stock rom from sammobile with latest odin. But when I bootet phone up it said "no command" with dead android logo and kept bootlooping. I can try different version of rom, maybe it helps.
Still my problem is unsolved. Any clues what to do would be great.
You probably flashed a wrong firmware which is not for your variant.
Can you remove your battery? If so remove it and put it back and enter download mode by pressing volume down,power and home button. Afterwards, find the firmware which is for the specific variant of the phone. Only get the "HOME_CSC" version or else you will lose all you data. In odin, if it says added, flash the stock firmware and see if it boots to the system. If you could give me your variant, I could help and give you an even more detailed guide.

S7 Edge no cellular network

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

Categories

Resources