Database Users

[HELP] No signal no matter what I try

Hi. So here's the thing:
I was trying to unlock my Samsung Galaxy S4 GT-I9505 and I kinda messed up. I chose the DM/DUN/RmNet over HSUSB option from the *#9090# where it said that all NV data will be erased, and I chose YES. Then after reboot, I didn't get any signal from my carrier. I've tried other SIMs, but nothing changed.
Then I found out that I needed an EFS backup or something like that, which unfortunately I didn't make.
I tried flashing the original stock rom (MDE), but nothing happened. I updated the rom to MDM, but then the baseband version became unknown and the IMEI number became NULL. So I flashed the MDE rom again and I got the IMEI and baseband version back. Then I tried to root my phone. Root was successful, so I tried to use EFS Professional. I backed up everything, and restored but nothing changed,
I know the phone reads the SIM card because I can see the SIM Toolkit change to the carrier's. The problem is I don't get any signal.
Can anyone please help me?

Did you ever get any info or help with this?
poopsmcgee said:
Hi. So here's the thing:
I was trying to unlock my Samsung Galaxy S4 GT-I9505 and I kinda messed up. I chose the DM/DUN/RmNet over HSUSB option from the *#9090# where it said that all NV data will be erased, and I chose YES. Then after reboot, I didn't get any signal from my carrier. I've tried other SIMs, but nothing changed.
Then I found out that I needed an EFS backup or something like that, which unfortunately I didn't make.
I tried flashing the original stock rom (MDE), but nothing happened. I updated the rom to MDM, but then the baseband version became unknown and the IMEI number became NULL. So I flashed the MDE rom again and I got the IMEI and baseband version back. Then I tried to root my phone. Root was successful, so I tried to use EFS Professional. I backed up everything, and restored but nothing changed,
I know the phone reads the SIM card because I can see the SIM Toolkit change to the carrier's. The problem is I don't get any signal.
Can anyone please help me?
Click to expand...
Click to collapse
I did the same thing. I did make a NV Backup. Copied them back but that didn't change the no signal problem. I have tried odin back stock root and unrooted. Some how you have to get out of the DM/DUN/RmNet over HSUSB setting and back in DM/DUN over HSIC but I can't find a way. Can you get into the *#9090# without it being blanked out settings?

Did either of you ever manage to solve this? I have the same problem.

I bought a new phone for my girlfriend a s4 and copied the nv items from her new phone to my phone. I had service, changed esn spc and reflashed my phone. Everything is working great now
Sent from my SPH-L720 using XDA Premium 4 mobile app

Great news! Any chance of getting a copy of the NV items so I can try this aswell?

madmediapro said:
I bought a new phone for my girlfriend a s4 and copied the nv items from her new phone to my phone. I had service, changed esn spc and reflashed my phone. Everything is working great now
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi , can u plz tell me where is nv_data on s4 i9505 bcoz i can't see nv_data on i9505 efs folder.

If snow is coming in like its suppose to in va tomorrow. If not I will do it this weekend. I will tell everyone in detail what I did and what programs I used to restore my phone to get service back on my phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app

That would be amazing. I look forward to your post.

i'm looking forward to your post.
madmediapro said:
If snow is coming in like its suppose to in va tomorrow. If not I will do it this weekend. I will tell everyone in detail what I did and what programs I used to restore my phone to get service back on my phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

I have to start out by saying that my phone is Sprint Samsung S4(SPH-L720). I’m not sure if this is going to help you. I came here for help. Hoping that I can help out because this site has helped me so much the last four year I have been here. And of course I’m not responsible in anyway for what you do to your device. Just posting what I did to fix my phone. Programs used Win7 64-bit (WIN XP should work), Odin3 v3.07, EFS_Professional_2.0.72, QPST 2.7 Build 422, HxD, DFS CDMA Tool Demo.
My old phone and new phone I bought did not have knox bootloader on them.
First thing I did to both was flash (Oldest Firmware) SPH-L720_MDC_Rooted_Restore.tar.md5 with Odin3 v3.07. Updated both SuperSU and BusyBox from PlayStore on both phones.
Then I used EFS_Professional_2.0.72 to Backup all NV Items from new phone that had cell service. Turned phone off and pulled battery. Then Formatted all NV Items on old phone and restored backup from new phone. Restarted and had cell bars in status bar. So I knew I was good to good with flashing my service back on the device.
Using QPST 2.7 Build 422, HxD, and DFS CDMA Tool Demo verison will work just fine to do what you need to do. Go to Device Manager and find what com port your device is on. Open QPST Configuration click “Add New Port…” the com port will not be visible but if you type “COMXX” in both port and port label it will be added to qpst configuration. Example is my port COM23 so I added COM23. Close window and open DFS connect com and send spc and pwd close DFS. Note: “You have to send SPC then Pwd with DFS before using any programs on QPST.” Open EFS Explorer send spc go to directory nvm\num copy items 0 85 1943 to desktop. Use HxD to zero out items. Then delete items from nvm\num directory on EFS Explorer. Then copy the zeroed out items back to phone. Reset phone and open DFS and restore original setting that came with the phone. You should be able to restore MEID, ESN, SPC, and IMEI with DFS.
I hope XDA Developers will understand that this is just restoring your phone back to original state. That is exactly what I did. Hope this helps you.

madmediapro said:
I have to start out by saying that my phone is Sprint Samsung S4(SPH-L720). I’m not sure if this is going to help you. I came here for help. Hoping that I can help out because this site has helped me so much the last four year I have been here. And of course I’m not responsible in anyway for what you do to your device. Just posting what I did to fix my phone. Programs used Win7 64-bit (WIN XP should work), Odin3 v3.07, EFS_Professional_2.0.72, QPST 2.7 Build 422, HxD, DFS CDMA Tool Demo.
My old phone and new phone I bought did not have knox bootloader on them.
First thing I did to both was flash (Oldest Firmware) SPH-L720_MDC_Rooted_Restore.tar.md5 with Odin3 v3.07. Updated both SuperSU and BusyBox from PlayStore on both phones.
Then I used EFS_Professional_2.0.72 to Backup all NV Items from new phone that had cell service. Turned phone off and pulled battery. Then Formatted all NV Items on old phone and restored backup from new phone. Restarted and had cell bars in status bar. So I knew I was good to good with flashing my service back on the device.
Using QPST 2.7 Build 422, HxD, and DFS CDMA Tool Demo verison will work just fine to do what you need to do. Go to Device Manager and find what com port your device is on. Open QPST Configuration click “Add New Port…” the com port will not be visible but if you type “COMXX” in both port and port label it will be added to qpst configuration. Example is my port COM23 so I added COM23. Close window and open DFS connect com and send spc and pwd close DFS. Note: “You have to send SPC then Pwd with DFS before using any programs on QPST.” Open EFS Explorer send spc go to directory nvm\num copy items 0 85 1943 to desktop. Use HxD to zero out items. Then delete items from nvm\num directory on EFS Explorer. Then copy the zeroed out items back to phone. Reset phone and open DFS and restore original setting that came with the phone. You should be able to restore MEID, ESN, SPC, and IMEI with DFS.
I hope XDA Developers will understand that this is just restoring your phone back to original state. That is exactly what I did. Hope this helps you.
Click to expand...
Click to collapse
Thanks for sharing and i don't think it will work on my device i9505 but i do appreciate the work u have shared thumbs up.

I still think this may work. I want to attempt but I need a known good EFS pro backup from an i9505. Unfortunately it's not that easy to convince any of my friends to let them tinker with their phones. If somebody could send me one to try I would be hugely grateful.

d3v147 said:
I still think this may work. I want to attempt but I need a known good EFS pro backup from an i9505. Unfortunately it's not that easy to convince any of my friends to let them tinker with their phones. If somebody could send me one to try I would be hugely grateful.
Click to expand...
Click to collapse
Using an EFS backup on two phones simultaneously will result in blacklisting of both mobile devices.
So do not try to restore an EFS backup from an usable phone..

AlanDS said:
Using an EFS backup on two phones simultaneously will result in blacklisting of both mobile devices.
So do not try to restore an EFS backup from an usable phone..
Click to expand...
Click to collapse
I did seem MadMediaPro did not encounter this. Also it is unlikely to occur if a SIM is never inserted in the phone. The other possibility is hex editing out the IMEI in the backup.

Wanted: Flashing Guide Sprint s4 to Page Plus

MOD EDIT: Offer of cash to perform these tasks has been removed and is not what XDA is about. This is a development site. This thread is being moved to Q&A where you can ask help how to continue the process on your own. Bounties may be offered for significant development for the community such as unlocking bootloaders, not for personal services
I'm technically inclined enough to flash my own roms, root my phone, flash radios etc etc. I'm just a little shy of being able to flash my phone from sprint to Page Plus.
I could go to a store and have it flashed, but I mess around with my phone too much to be going back every so often and paying them $40 a pop to do something that I am technically capable of doing.
I believe, what I need is a little guide on where to put what numbers when it comes to using QPST or DFS. I'm guessing since DFS is proprietary software I just dont have the correct license to have it recognize my Sprint S4. I have got QPST to recognize my phone by setting the correct com. I assume since it appears to be reading my phone all i need to do is put the numbers in the correct spots, possibly change some settings.
Phone is Rooted, twrp recovery installed, I already have my MSL, already have QPST talking to my phone by setting the correct com port. Due note, this phone has never been active on any carrier.
It would be nice if the guide would include:
1) What needs to be installed/flashed first. IE which roms/radios/firmwares/prls.
2) How to get into Diag.
3) How to get your MSL.
4) Which software (and version) is needed to input the correct codes/numbers to flash from Sprint to Page Plus
5) Exactly where and what numbers need to be into DFS or QPST.
6) Anything else I need to get the S4 over to Page Plus
7) 3g MUST work!
However, I have already accomplished 1-4. I'm assuming (a bad idea I know) I can get any codes/number I need from this thread.
http://forum.xda-developers.com/showthread.php?t=2270191
Anyone help? .
You know what they say: give a man a fish he'll eat for a day, but teach a man to fish he'll eat for life.

I already have part of a guide.
I just need help with the last bit.
This guide is from [email protected]
Sprint S4 Diag instructions:
1.dial *#7284#
2. click qualcomm usb settings and choose DM+ADB+MODEM
3. then turn on usb debugging in the development settings
4. plug in
This part did not work for me as I was running CM. But once I flashed to stock it was easier.
The rest will assume your familiar with flashing and know what to do
16 digit passwords are the same as the s3 versions
uscc-2010031619780721
verizon-2009031920090615
sprint-01F2030F5F678FF9 or 2012112120131219
To set the verizon and uscc to nv only you will need to send both the 16 digit password and the spc
Verizon and USCC just read from the donor for your info and write to the phone make sure you set pref mode to cdma_hdr
sprint write data settings as normal sprint phone in profile 0 and 1 active will be 0 and place the 10.key in efs2 using dfs
uscc doesn't need any sim but will display the invalid sim error
sprint no errors
verizon some need a used sim some doesn't need any sim try without first
if you dont have a donor then just put the mdn and min and sid in the nam tab on dfs with a prl
and data tab user id will be [email protected] and pw will be vzw same for mobile ip tab
but don't half flash give your customers 3g if not i eventually get the business
Want to learn 3g look for my 3g flashing guide online Its free to download
Enjoy.

no one will help because it is about making money on knowledge they gained from these forums for free!!!!

SM-G900F NVRAM backup

Hi, so I was fiddling around with nvram without making a backup (stupid me) and I've erased it. I've restored the IMEI using QPST and it shows up in *#06# but there's no cellular connectivity. Would someone be kind and provide their backup of NVRAM for the SM-G900F (international)? I'm sitting here with no connectivity at all.. Thanks in advance..

Found from another website. "Losing or corrupt NVRAM data means you will not be able to use your device with any mobile network or connect to WiFi. NVRAM contains data like WiFi and Bluetooth MAC address, Baseband version, IMEI/MEID number and other essential information."
I would do it, but if there is my (different) IMEI it won't work, right?! Therefore, I would suggest to send it to a local phone shop and get it repaired...
But if I am wrong, please enlighten me. And if somebody else can contribute to solve your problem, please do so.

Someone could provide you with a NVRAM backup BUT, that person must change the IMEI in the backup or else, every carrier in the world will blacklist that IMEI because 2 phones have it, speaking of nvram, I fiddled with my NVRAM too and I'm pretty sure the IMEI is still there but what I did is I used a guide on XDA to backup my nvram and add more LTE and 3G bands to my phone but what happened was , I backed up my NVRAM and added all LTE bands by changing the NV Items 6868(something like that) and adding all GSM and 3G bands using the UMTS option in QXDM.....
Initially the phone was bootlooping on Stock and LaOS and other roms but I discovered that it had a problem to do with rild crashing because I enabled all the bands.
I removed the rild binary and I can now boot into Lineage and Stock TouchWiz but I can only see APQ8084 (Snapdragon 805) in the QPST configuration. My Modem MDM9635 no longer appears along side apq8084 and I figured out it was due to me having no rild which is required to interface with the Diagnostic Port. But if I have rild on my system, it just bootloops......
Any ideas of how I can use rild to just interface with the modem, If I figure that out , I will be good to go, I need this urgently as I will be traveling in a few days and would prefer to carry my Samsung Galaxy S5 Plus rather than my HTC Desire 620 with a cracked screen

if you really want backup of my EFS chip tell me

AlBaraa98 said:
if you really want backup of my EFS chip tell me
Click to expand...
Click to collapse
SM-G900F NVRAM backup I'm also shaking one

Verizon Note 3 - No ServiceMode

I have an SM-N900V that I acquired on PL1. I promptly downgraded to OF1, rooted, unlocked bootloader, flashed TWRP, and started with custom ROMs. I wanted to see if I could get LTE band 4 enabled from the ServiceMenu. This obviously isn't available in custom ROMs so I used the stock OF1 image and flashed from TWRP.
Upon booting and getting everything setup (And enabling dialer codes in /efs/carrier/HiddenMenu), the ServiceMode code doesn't work. I know Verizon updated to block this out so next I flashed 4.4.2 (and the accompanying modem). Other dialer codes worked but still no SerivceMode.
Question is: Is there something on the EFS partition that Verizon changed to block this out? EFS is the only common denominator between every setup that I have tried. I haven't been able to access SeviceMode anywhere.
Any help is greatly appreciated, thanks.

I don't have an answer, only a few suggestions and a hypothesis.
If you have an old efs partition dump (debrick image anyone?) you could (loopback) mount that blob of bytes (read-only) and do checksum of all files or simply just file timestamp checks against a more recent backup (or partition blob dump). That would give you a shortlist of things that change within efs. Won't tell you if any of those changes are relevant to your inquiry though.
Speculation: some dialer codes are simply intercepted via the framework in order to launch "hidden" Android activities. Others however actually pass dialcodes to Verizon's network (e.g. activation). If that's the case here then the possibility is that the disabling of the functionality is instrumented within Verizon's infrastructure rather than on the device. If that is the case using dialcodes won't help you.
I'm not saying that's the case; I don't know. But it's one of many possibilities.
You can browse through activities using apps such as "Activity Launcher" (Adam Szalkowski) or "App Browser" (Brian Estey), but you might have to launch them from the command line in a root shell using the "am" command (Activity Manager). If I am recalling correctly, you can get around certain permissions problems (e.g. the Browser apps not having the correct set of Android privileges) launching exported activities this way. (I hope I am remembering this correctly). If the activities on the phone only rely on some feedback from Verizon only to launch them, then using this approach (the activity manager) might provide an end-run around using dialcodes.
Finally, if you are looking for hypotheses, you might find something like this useful for generating some more places to look at:
Code:
cd /system/lib
for x in *ril* ; do
echo "LIBRARY FILE $x"
strings $x | grep -i efs
echo ' '
done
I see a number of references to filesystems in /efs within some of those radio interface libraries.
good luck. I suppose you were hopeful for a "simple answer"; but a reply of "here's where you can start some heavy lifting" is better than no response at all.

parkerlreed said:
I have an SM-N900V that I acquired on PL1. I promptly downgraded to OF1, rooted, unlocked bootloader, flashed TWRP, and started with custom ROMs. I wanted to see if I could get LTE band 4 enabled from the ServiceMenu. This obviously isn't available in custom ROMs so I used the stock OF1 image and flashed from TWRP.
Upon booting and getting everything setup (And enabling dialer codes in /efs/carrier/HiddenMenu), the ServiceMode code doesn't work. I know Verizon updated to block this out so next I flashed 4.4.2 (and the accompanying modem). Other dialer codes worked but still no SerivceMode.
Question is: Is there something on the EFS partition that Verizon changed to block this out? EFS is the only common denominator between every setup that I have tried. I haven't been able to access SeviceMode anywhere.
Any help is greatly appreciated, thanks.
Click to expand...
Click to collapse
I use an app Phone Info+ by vndnguyen available on Google Play
Hit the menu bars upper left, then other tools then service mode (root)
Sent from my SM-N900V using Tapatalk

Invalid IMEI - Is Samsung Galaxy Grand Prime Plus G532F an MTK chipset at all?

Hello folks,
I ran into a poblem with my old Samsung Galaxy Grand Prime Plus. 3 years ago I was messing up with the phone and I ran into an invalid IMEI problem. As I was a real newbie, I brought it straight to a friend of a friend of a friend who had a phone shop, and he fixed it for me.
Everything OK until last week, when I suddenly realized that probably the guy had flashed the wrong IMEI to it, mistyping 2 numbers of one of the two IMEIs.
Currently, I then have a perfectly working phone, but the IMEI is incorrect and I need to fix it.
I don't have the box anymore, but luckilly the numbers under the battery are perfectly clear and readable, although this is quite an old device.
As the shop of the guy who did the work is long gone, I started to look around for instruction on how to deal with the problem, and I followed all the possible tutorials, but apparently I'm not able to fix the issue.
I just know it can be done, as this was done to the very same phone in the past, creating the problem. I just do not happen to know how he did...
Here's what I tried so far:
1. APP: Mobileuncle Tools
Whenever I tap onto "IMEI Backup Restore (MTK)" I get an error message that says "No support".
2. APP: MTK engineering mode
I open the app, and whenever I tap onto "MTK Settings" I get an error message that says: "Cannot find EngineerMode App - Mediatek chipset is mandatory and stock ROM must be installed".
I tried both Mobileuncle Tools and MTK Engineering mode with 3 different ROMs downloaded from different sources, before and after rooting the device with Super SU, but to no avail.
3. With any xposed module
This could be a solution... but not a real one.
At least according to all the documentation I found (also here on the forum), any xposed module like "IMEI Changer", "chamaleon", "device changer", "hijack suite free" etc only mask the IMEI in front of other apps, but do not really change the IMEI of the phone.
So basically I would still have a phone with an illegal IMEI on it.
Not ideal: this is not what I am looking for.
4. IMEI Maker and IMEI Repair
I followed the tutorial I found here:
https://forum.xda-developers.com/showthread.php?t=2399037
I encounter no errors at all, and TWRP shows a clean log, nothing seems to be wrong. But after flashing the new IMEI, nothing changes: with *#06# I can still see the wrong IMEI there.
The file in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 just remains the same, dating 2016, and does not get replaced by the new one.
I tried to replace the file manually, using ROM Toolbox Lite. At the beginning I could not delete the original MP0B_001 file, even after changin permissions to 775. It kept saying "File deleted" but the file remained there.
I then installed BusyBox Free, and it did the trick: now using ROM Toolbox Lite I definitely can delete the MP0B_001 file. The problem is that the original file keeps coming back again and again, after every reboot.
Nevermind if I place the new MP0B_001 file in the folder copying and pasting it or flashing it with TWRP, it will get overwritten by the old file with the wrong IMEI.
5. Flashing a Combination ROM
I didn't find a specific tutorial for this one, but I just tried to flash the combination ROM and see whether I could get any luck touching things in there.
No luck!
6. With SN write tool (windows software)
Here the big problem is, I can't find the BP file anywhere.
No AP_BP_database seems to contain the BP file for the MT6737T (that is the chipset of the G532F). As I am writing, I am thinking about trying to use a different BP file, from a different chipset. This will probably won't work, but after trying all of these, I mean, why not...
I also tried to look for the BP file into the folder /system/etc/mddb/ , as advised here: https://forum.hovatek.com/thread-11609.html . I looked for ir with any of the 3 different stock ROMs I tried to install. Yet again, absolutely nooooo luck here.
7. MTK Droid Root & Tools (windows software)
This won't even connect to the phone. That is, whenever I connect the phone to the PC, I get the following errors:
" --- Estructura de ROM desconocida, no se puede hacer backup ! "
That would be something like: "Unknown ROM structure, cannot perform backup"
The device gets recognized (hardware, model, build number...), so it should be a problem of drivers, cable or USB port. Also because I used the same setup to install all the stock ROM, TWRP, Super SU etc...
---------------------------
And here I am. After one week of try and fail, getting tired of all this!
I'm surprised on how persistent that wrong IMEI is, as I can't get rid of it in any way.
Do you have ANY kind of idea of what can I do?
As the points 1, 2, 4, 6 and 7 are specifically advised for MTK chipset. I'm starting to doubt that this is an MTK chipset altogether!!!
Thanks for your help
Peter

Update:
I tried with NCK Dongle AndroidMTK 2.5.6.2
Still no success (phone apparently not supported).