Database Develop

Fix for no WiFi connection when Sim is active

I imported my HTC first from America and a major problem I found was that the WiFi didn't work. I was prepared to return my phone citing hardware problems but I waited and instead tried to find a solution by myself. I finally got it working.
This thread is for all others who have the same problem that I did.
Temporary Fix
1) unlock boot loader, root and do s-off
2) you must be running ruu 1.08.502.1
3) make your way to http://forum.xda-developers.com/showthread.php?t=1445766
There you can see many people have the similar problem.
Follow the instructions and install the app by the OP
(Make sure push the wifix app in the /system/app folder) verify the app is working properly by dialing the code given in the other thread. Open the wifix manager and set code to 'us'
4) if you read the thread you will see the app works for android 4.0 but most users having jellybean report it as not working
5) try the steps of post #250 (I used the AT&T code)
6) now whenever you restart make sure WiFi is switched OFF before reboot. When your phone boots up again make sure you're getting network signals, then open the market changer app and select AT&T. Then turn on the WiFi.
7) your Wi-Fi can see and connect to access points!
--------------------------------------------------------------------------------------------------------------------------
UPDATE 13/5/2014
WIFI NOW WORKS 100%
Ok with a lot of digging around I finally managed to fix my wifi. Sim inserted or not, wifi on/off at reboot or whatever, it doesn't matter because wifi always works. And no need for any annoying apps to run at boot!
For this method I had to endure a lot of headaches -_-
Had to search the whole internet, learn about adb commands, logcat, compiling .jar files etc
1) unlocked bootloader, rooted , s-off and running deodexed 1.08.502.4 . I did this on a clean install with no wifix/wifi codes/market unlocker
2)
First you have to learn how to compile and extract jar files:
http://forum.xda-developers.com/showthread.php?t=2251719
You just have to read "1. How to Decompile and Recompile *.jar file or classes.dex"
3) THIS STEP NO LONGER NEEDED *Removed*
4)
You need to read this too:
http://forum.xda-developers.com/showthread.php?t=2628707
modify "framework2.jar" which is present in /system/framework
And after you have decompiled, open on your PC
classout/com/android/internal/telephony/MccTable.smali
recompile framework2.jar , put it back in androids /system/framework and set permissions to Rw-r-r
Now we have to modify another file
This time its the /system/framework/framework.jar
after decompiling open in PC : classout/com/android/net/wifi/WifiStateMachine.smali
and edit as per the second post in the link, recompile and paste it back into system/framework,set permissions to Rw-r-r
Note : its best to use adb commands to copy and paste the framework files from android to PC and vice versa
(namely adb pull and adb push)
then do some extra steps:
"Extra step 1
click on "/system/build.prop" and open in any text editor(on android);
seek line
ro.product.locale.region=GB
and change GB to US; confirm OK for save file.
mount /system R
Extra step 2
because of first boots, in Settings database is written our country code,
which should be US.
for this: install "Sqlite Editor" (android app), run, grant ROOT access. after program finds
& lists databases, look for & open "Settings Storage" > settings.db > global:
find "wifi_country_code", select it and press menu button > Edit Record;
change value to US and press "save" "
Reboot.
Congrats!! Wifi now works no matter what you do!
(as long as your wifi is on channels 1-11 , if youre on channel 12 or 13 then I think you need to change wifi country code to an european country instead of 'us')
Note: Be sure to thank the original authors in the threads i've linked.
As usual, do these steps at your own risk, I am not responsible for your bricked devices. Do report if it worked for you.
Also I know i've made quite a bit of mess. Do tell if you have any problems with the steps. I was thinking about posting my own framework.jar and framework2.jar but i'm not sure if they are safe to share or they contain private data. I'll need to confirm from someone.

dramon said:
I imported my HTC first from America and a major problem I found was that the WiFi didn't work. I was prepared to return my phone citing hardware problems but I waited and instead tried to find a solution by myself. It took me 4 days but I finally got it working.
This thread is for all others who have the same problem that I did.
Here is what I did:
1) unlock boot loader, root and do s-off
2) you must be running ruu 1.08.502.1
3) make your way to http://forum.xda-developers.com/showthread.php?t=1445766
There you can see many people have the similar problem.
Follow the instructions and install the app by the OP
(Make sure push the wifix app in the /system/app folder) verify the app is working properly by dialing the code given in the other thread. Open the wifix manager and set code to 'us'
4) if you read the thread you will see the app works for android 4.0 but most users having jellybean report it as not working
5) try the steps of post #250 (I used the AT&T code)
6) now whenever you restart make sure WiFi is switched OFF before reboot. When your phone boots up again make sure you're getting network signals, then open the market changer app and select AT&T. Then turn on the WiFi.
7) your Wi-Fi can see and connect to access points!
Well that's what I did. As usual, do these steps at your own risk, I am not responsible for your bricked devices. Do report if it worked for you
Click to expand...
Click to collapse
Salaam bro how are you?? i also found the solution but for me its Wificodes and Market unlocker both together and its done wifi working..but one thing is your GPRS working?

Optimus said:
Salaam bro how are you?? i also found the solution but for me its Wificodes and Market unlocker both together and its done wifi working..but one thing is your GPRS working?
Click to expand...
Click to collapse
Lol that's exactly what I posted above.
No, I don't really use data and it isn't activated anyways. Why, does the gprs not work?
Sent from my HTC first using Tapatalk

dramon said:
Lol that's exactly what I posted above.
No, I don't really use data and it isn't activated anyways. Why, does the gprs not work?
Sent from my HTC first using Tapatalk
Click to expand...
Click to collapse
well my wifi works now but GPRS on my warid doesnt connect may be its the settings i need to get them done by warid franchise?

Optimus said:
well my wifi works now but GPRS on my warid doesnt connect may be its the settings i need to get them done by warid franchise?
Click to expand...
Click to collapse
I don't have gprs enabled, but when I get recharge my balance I'll activate a package and then update you
Sent from my HTC first using Tapatalk

dramon said:
I don't have gprs enabled, but when I get recharge my balance I'll activate a package and then update you
Sent from my HTC first using Tapatalk
Click to expand...
Click to collapse
Thanx bro do let me know .. btw is ur htc one x + international one or the At&t one?

Optimus said:
Thanx bro do let me know .. btw is ur htc one x + international one or the At&t one?
Click to expand...
Click to collapse
I don't have the HTC one, I have the HTC First
Sent from my HTC first using Tapatalk

Optimus said:
Thanx bro do let me know .. btw is ur htc one x + international one or the At&t one?
Click to expand...
Click to collapse
Gprs works. Go to Apn and enter grps settings. Data should work then

i have same problem when i insert sim card i lose wifi after remove sim wifi working
i try some roms but no success
i read that thread write solution on first post
i try but not working there is any other solution i have 2 phone in my hand
thanks in advance

I finally found the solution... update to android 4.2.2..

Optimus said:
I finally found the solution... update to android 4.2.2..
Click to expand...
Click to collapse
We are skipping that and going straight to 4.4
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
We are skipping that and going straight to 4.4
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do we have 4.4 for At&t HTC One X+ ?

Optimus said:
Do we have 4.4 for At&t HTC One X+ ?
Click to expand...
Click to collapse
Nope. But as far as I'm concerned loir is building 4.4 instead
Sent from my HTC first using XDA Premium 4 mobile app

dramon said:
I imported my HTC first from America and a major problem I found was that the WiFi didn't work. I was prepared to return my phone citing hardware problems but I waited and instead tried to find a solution by myself. It took me 4 days but I finally got it working.
This thread is for all others who have the same problem that I did.
Here is what I did:
1) unlock boot loader, root and do s-off
2) you must be running ruu 1.08.502.1
3) make your way to http://forum.xda-developers.com/showthread.php?t=1445766
There you can see many people have the similar problem.
Follow the instructions and install the app by the OP
(Make sure push the wifix app in the /system/app folder) verify the app is working properly by dialing the code given in the other thread. Open the wifix manager and set code to 'us'
4) if you read the thread you will see the app works for android 4.0 but most users having jellybean report it as not working
5) try the steps of post #250 (I used the AT&T code)
6) now whenever you restart make sure WiFi is switched OFF before reboot. When your phone boots up again make sure you're getting network signals, then open the market changer app and select AT&T. Then turn on the WiFi.
7) your Wi-Fi can see and connect to access points!
Well that's what I did. As usual, do these steps at your own risk, I am not responsible for your bricked devices. Do report if it worked for you
Click to expand...
Click to collapse
Not Working...

same here not working i tried on both official and custom rom that solution but not working
any other solution or working kernel ?
with sim card wifi not work

imeicodes said:
same here not working i tried on both official and custom rom that solution but not working
any other solution or working kernel ?
with sim card wifi not work
Click to expand...
Click to collapse
Details?

Thread updated
@moonmoon8 @imeicodes

Optimus said:
I finally found the solution... update to android 4.2.2..
Click to expand...
Click to collapse
Can you post here tested 4.2.2 rom link here that fixes the WIFI problem with SIM card?

Wifi solution
..::Angel::.. said:
Can you post here tested 4.2.2 rom link here that fixes the WIFI problem with SIM card?
Click to expand...
Click to collapse
Salaam, here is the link (http://forum.xda-developers.com/showthread.php?t=2023889&highlight=boot+img) but you should know how to root and then put a custom rom..furthermore this is a rom for AT&T htc one x + NOT for the international one ok..this rom worked for me since mine is AT&T version....i hope the same goes for u. dont forget to hit thanks ...goodluck

Optimus said:
Salaam, here is the link (http://forum.xda-developers.com/showthread.php?t=2023889&highlight=boot+img) but you should know how to root and then put a custom rom..furthermore this is a rom for AT&T htc one x + NOT for the international one ok..this rom worked for me since mine is AT&T version....i hope the same goes for u. dont forget to hit thanks ...goodluck
Click to expand...
Click to collapse
Walikum assalam,
Did you mean this rom worked with HTC First aka MYST_UL ??? Thanks!

Gt-N7000 imei and power problem

Hello All,
I have Gt-N7000 note mobile. I am running JB germany official rom. Suddenly my phone has restore it default imei "0049999010640000" so i can register on any network. Also, the power button problem appeared to me. When i press it for a long press the menu of restart does not pop up instead the phone just power off and if i pressed for a short one, the phone will just turn off the screen so if press it again or the home button, the phone would just open and bypass the lock screen.
Thanks for ur help guys

vamp_89 said:
Suddenly my phone has restore it default imei "0049999010640000" so i can register on any network.
Click to expand...
Click to collapse
Try to explain this again.
Can you register on a network?
Or can't?
This IMEI is not a "restored" one. You simply lost your original one. If you did not make and do not have a backup of your /efs then it's lost.
So: was your device rooted? What did you do before "suddenly"?

i really mean suddenly. The phone was OK then it lost its imei. I can not register to my network anymore. the mobile internet is working fine but i can not make any voice calls. The phone was not rooted then but i root it now.
For the EFS folder, i do not have a backup

vamp_89 said:
i really mean suddenly. The phone was OK then it lost its imei. I can not register to my network anymore. the mobile internet is working fine but i can not make any voice calls. The phone was not rooted then but i root it now.
For the EFS folder, i do not have a backup
Click to expand...
Click to collapse
Workaround 1: disable SIM pin number. After that the network should work
Workaround 2: use an older version of android.policy.jar (from an unofficial developer release from Samsung). In this versions the check for a corrct IMEI seems to be disabled.
I have this problem myself and was lucky to get an upgrade with the so called developer imei. Since then I use the android.policy.jar from this upgrade.
But please try W1 first. If you'll get the network then it is solvable with W2.
If W1 doesn't work then even W2 will fail.

ThaiDai said:
Workaround 1: disable SIM pin number. After that the network should work
Workaround 2: use an older version of android.policy.jar (from an unofficial developer release from Samsung). In this versions the check for a corrct IMEI seems to be disabled.
I have this problem myself and was lucky to get an upgrade with the so called developer imei. Since then I use the android.policy.jar from this upgrade.
But please try W1 first. If you'll get the network then it is solvable with W2.
If W1 doesn't work then even W2 will fail.
Click to expand...
Click to collapse
I tried W1 and it worked. how to proceed with 2?
Thanks alot man

vamp_89 said:
I tried W1 and did not work. So, it is not a good option to go with W2?
Click to expand...
Click to collapse
Of course you should try it.
First root your device. Go to Philz kernel thread and download the kernel for your JB version (XXLT4?).
Tomorrow I will connect to my PC in Germany and download the old version from there (right now I'm in Thailand).
Will attach it here.
With a rooted device and a file explorer with root options you can copy it to your device.

ThaiDai said:
Of course you should try it.
First root your device. Go to Philz kernel thread and download the kernel for your JB version (XXLT4?).
Tomorrow I will connect to my PC in Germany and download the old version from there (right now I'm in Thailand).
Will attach it here.
With a rooted device and a file explorer with root options you can copy it to your device.
Click to expand...
Click to collapse
Great..thanks alot.
And for the power problems? do u have any opinion?

sorry but it worked on an operator and did not on another. i could not register on my main network using the W1 solution.

vamp_89 said:
Great..thanks alot.
And for the power problems? do u have any opinion?
Click to expand...
Click to collapse
Yes, same reason. When I use the other jar this problem disappears too.
I just copied the file from my N7000 and attached it here.
Copy it to /system/framework. Change permissions to rw-r-r.
For this you need a rooted device and something like Total Commander with /system mounted as writeable. And before you do this make a backup of you android.policy.jar.
If you do not understand these things right now: start searching and reading here about root explorer, mounting /system, permissions. There are enough examples and descriptions.
But first: root

Handsfree Activation Bootloop FIX

Hi Guys. First off I'm posting this for information in hopes to help anyone else having this problem. I'll go over the problem I was having. What caused the problem for me and the steps I took to resolve it.
Problem:
A Handsfree activation bootloop. More specifically, no matter which rom, RUU, OTA, recovery or firmware I flashed, my phone would go threw a HFA and PRL update, say that it was successful and reboot on it's own and start the process over again. If at some point by chance I could catch it and disable the vDM.apk would be the only way I could stop it and boot normally. I tried resetting my profile, factory resets, Sprint support (which was completely useless) and everything else mentioned above. I even threw the kitchen sink in for good measure. lol. I was able to make phone calls, receive text and mms. I even had LTE and 3G service. But my wifi calling and sprint zone didn't work. So I knew something wasn't activating properly.
Cause:
Well for me it started when I accidentally flashed a M7 rom. Yeah don't laugh, it happens. Anyway, in recovery it said it failed but not before it formatted "/dev/block/mmcblk0p37" which is the system partition on the M7. But on the M8, it's the /carrier partition. So it erased all my info and filled it with a bunch of s**t. To the point that the partition was full and activation couldn't write to it. It also injected a bunch of s**t in "/dev/block/mmcblk0p39" which is the /devlog partition on the M8. So just a big mess. This is just how I got to this point. I'm not saying this your cause but the fix might help you.
Fix:
1 Get your self to a point that you are booted up to a rom. If you can't, try flashing an international rom made for sprint like "insert coin" for example. Those don't HFA bootloop from my experience.
2 Download MSL reader from the market. And get your MSL you'll need it later.
3 With a good root explorer, go to /carrier folder, do a backup of it (just in case) open the folder and delete everything in the folder.
4 Go to /devlog folder, open it and delete everything in there. (You don't need this stuff, it will rewrite itself).
5 Download the zip at the bottom of the post, extract it and copy the contents to your /carrier folder. Don't worry about the /devlog folder. leave it empty.
6 Now your going to flash a RUU. Download the one you want. I used https://www.androidfilehost.com/?fid=95784891001604379 (Don't worry it won't get you S-on or lock your bootloader). It will probably do a HFA again and it should fail. If not, try disabling it. Because we need to get to the dialer.
7 In your dial pad enter ##786# and go to edit mode. Enter your MSL if it asks you. Go to the menu button at the upper right and hit reset. Go threw the promps, the phone should reboot and restore. Let it boot up. It will go threw HFA again. But now you'll notice it activated properly. At this point your all done. Flash a custom recovery again. Profit.
Special Thanks to @Captain_Throwback You rock.
Let me know if this helps. Please post any questions and I'll try guiding you threw.

Dude iv been having some serious issues with data. I'm going to try this and see what happens thanks.

sprkat85 said:
Dude iv been having some serious issues with data. I'm going to try this and see what happens thanks.
Click to expand...
Click to collapse
Hope it helps.

Macropoutsis said:
Hope it helps.
Click to expand...
Click to collapse
It definitely helped out. Thanks for posting this again.

sprint htc one m8 h/k edition
u have mentioned in point 3 download root explorer
but in my case I am facing hands free activation page with emergency button .. and cant go further
how can I get rid of it ..
please help me .. i shall be very thankful to you

sprkat85 said:
It definitely helped out. Thanks for posting this again.
Click to expand...
Click to collapse
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys

I ended going completely stock running an ruu then took steps to flash the newest firmware after I rooted. The problem I had was I flashed the wrong firmware. I do not have the HTC one m8 anymore.

gag_dhiman said:
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
Click to expand...
Click to collapse
What ROM?
If it is stock based you can try this, either go through TWRP and select file manager or do this in the zip before flashing.
Go to system/app/HtcOMADM_SPCS and rename the apk by adding .bak after .apk.
After the phone boots and you pass setup you can always rename the file by removing the .bak
You might get better results by posting this question in that ROM thread, or make a thread in the Q&A and put the ROM name in the title of the thread.

gag_dhiman said:
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
Click to expand...
Click to collapse
Hey bud. Didn't get my notifications on this thread. Are you still having a problem?

Hello senior.
I am ising the stock rom in sprint m8 harman kardon edition.
I still facing the problem. Cant rename htc omadm. Spcs file.
Moreover . In notifications area one line is written ( device management is running)
Sorry senior. For late reply.. i was in roaming.
Do guide me

HFA loop !!!!!!!!!!!!!!!!!1 never ending
I installed twrp .. in bootloader under twrp recovery,then advanced and in file manager /.. I go through system folder but no app folder is there .. and I am still facing the hands free activation loop/... do something seniors.....
dopy25 said:
What ROM?
If it is stock based you can try this, either go through TWRP and select file manager or do this in the zip before flashing.
Go to system/app/HtcOMADM_SPCS and rename the apk by adding .bak after .apk.
After the phone boots and you pass setup you can always rename the file by removing the .bak
You might get better results by posting this question in that ROM thread, or make a thread in the Q&A and put the ROM name in the title of the thread.
Click to expand...
Click to collapse

gag_dhiman said:
I installed twrp .. in bootloader under twrp recovery,then advanced and in file manager /.. I go through system folder but no app folder is there .. and I am still facing the hands free activation loop/... do something seniors.....
Click to expand...
Click to collapse
You have to mount system first.

Yes ... Seniors ... Yes... Got the solution... Thanks a lotttt..

hi i have bought on aliexpress a htc one m8 looks is m8 sprint from imei .my phone show bootloader unlocked
m8 whl pvt ship s-off
cid-11111 hboot -3.16.0.000
radio -1.00.20.0.120
running on kitkat 4.4.4
can any one help i try this tutorial but not show gsm network

Does Sprint M9 work with this method?

[Q][GT-I9305] EFS, IMEI Repair

Okay everybody,
I decided to write a new thread for my problem because I think my prob is a very special thing.
I'm from germany, so please don't wonder about my english. I think it is a understandable.
The story begins with a software update for my GT-I9305. After the update, the IMEI was just "null", after some work with google I found out that the efs partition was broken. With my bad knowledge for this case, I destroyed the whole EFS folder. I installed perseus kernel. And, there it was! The whole and correct IMEI. The solution was the perseus kernel (stock doesn't work, neither reflash). But then, after a while the phone doesn't boot anymore. I flashed Android 4.4.4 and my phone was revived but the IMEI was again "null". I have no backup or anything else!
So I spent approximately 20 hours or more to understand the efs thing. I found much solutions but nothing worked for me. So, here I am.
What I've tried before
-reflash KitKat
-reflash Perseus (not compatible anymore)
-formatting efs partition for a blank and new EFS for editing
-tried to edit nv_data.bin with HEX
-tried to backup efs with a 3rd party app and edit this with hex (the app doesn't support my GT-I9305)
and then, there it was:
-tried to use a working EFS partition from another GT-I9305
-editing with Qualcomm NV Tools! (I think THIS is the solution!)
I tried NV-items_reader_writer (1.0) and EFS Professional (2.1.73), but in both can't find my phone:
What I've done in NV-items_reader_writer
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened NV-items_reader_writer
-checked the both boxes near the SPC box
-selected the right port (last: COM4)
-clicked on "connect"
-clicked on "read"
-> here it search the phone, but it can't find it and says "Failed.. Phone does not answer"
What I've done in EFS Professional
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened EFS Pro
-clicked on "Qualcomm NV Tools"
-refreshed the Available COM Ports
-selected "SAMSUNG Mobile USB Serial Port" (last COM4)
-clicked on "Connect"
-> Here it takes few seconds and he stops and says: "Phone connection has been lost!" and "Unable to send SPC to the Phone!"
What I've tried to solve this problem
-tried QUALCOMM USB Settings: "DM + MODEM + ADB"
-reinstall all Samsung drivers
-tried to install Samsung Modem with Qualcomm drivers (failed due to wrong platform; I've Win7 X64)
-reinstall Samsung Kies (for actual drivers)
-tried to dial *#9090# (in my case, this menu is totaly blank)
-tried in factory mode
It could be that I forgot some....
Now, my question to you all is, do you know what I've done wrong? I mean, this is working for the most users, but why not for me? What do you think? Did you think I really forgot something?
Some informations:
Phone: GT-I9305
Android: 4.4.4 KitKat
Kernel: Stock (3.0.31-2760029 ; [email protected] #1 ; Fri Sep 12 13:08:24 KST 2014)
Buildnumber: KTU84P.I9305XXUFNI3
Windows: Windows 7 X64
Do you need more informations? Post it!
Please help me, I want to bring this phone back to life!
And yes I know, to change the IMEI to a number which is not your own is ILLEGAL and to prevent this, it is not well seen to talk about, but this is MY PHONE and I want to change the "null" IMEI and IMSI to MY ORIGINAL IMEI. If this is a problem, I can send a PM to an mod with my phone (where you can see the IMEI), my username on a sheet of paper and the original box with the IMEI printed on. All on one picture!
Simply... I need a hero! Be MY HERO!

im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.

take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.

vnholden said:
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
Click to expand...
Click to collapse
Thank you for your reply!
I tried this, already. But I can't downgrade from 4.4.4. I don't read very much about this. I just know that this is a new security option from samsung (or Android)... I will tell you when I know more
qasim799 said:
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
Click to expand...
Click to collapse
Thank you for your reply!
The warranty is already expired...
This will be the last step I will do. Before this, I will try my very best to do this at home... But thank you for this tip
Edit:
What do you all think about this idea:
-I try to find somebody with a working EFS on GT-I9305 Android 4.4.4
-I get a backup from him
-I restore this backup to my phone
-I edit the duplicated IMEI with NV Tool to my IMEI
This requires that the NV Tool will with work with an existing IMEI and the the phone will be THE WHOLE TIME IN PLANE MODE to prevent IMEI ban...
What do you think? Will this work? Do I need somebody from germany (DBT) or is this not needed?

Take it to a phone repair shop they might have a way to fix it. And if they don't they might know someone who can and it would likely be cheaper than Samsung service center
Sent from my GT-I9305 using XDA Free mobile app

Identical case (Solved)
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!

When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056

WesleyPs said:
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
Click to expand...
Click to collapse
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
viktorak said:
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...

Hello,
someone could give me an EFS file because I deleted mine but my camera would not boot and remains on bootloop
thank you in advance

SurrendeR1993 said:
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Click to expand...
Click to collapse
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
---------- Post added at 05:00 AM ---------- Previous post was at 04:46 AM ----------
banjomike said:
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
Click to expand...
Click to collapse
Sorry dude just found out only samsung can restore Imei give phone shop a try but I don't think they could sorry

I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app

SurrendeR1993 said:
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.

viktorak said:
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
Click to expand...
Click to collapse
Hm okay. I applied a "old bootloader" before here from xda. I don't know what it was exactly. There was a boot.so or so in it.
I will try my best. I mean, if I can beat this, this is a really great success for me. My next step is to restore a full NAND backup from a friends of mine (from a GT-I9305).
I wondered about that, after I restored a working EFS, there were no NV data.
My journey to restore a corrupted GT-I9305 without pay some money
Sent from my GT-I9300 using XDA Free mobile app

how did you success ?

how did you success ?

Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed
hope this helkps anyone, took me some 20 hours of tinkering

Oakhand said:
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed(
Click to expand...
Click to collapse
Can you post the links you used?

EwOkie said:
Can you post the links you used?
Click to expand...
Click to collapse
aside from the dropbox link in my post above I did not use much else. I downloaded a stock kitkat rom, but don't know from where.

Lost imei number and device number

My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?

BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...

Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.

I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick

Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...

mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work

mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help

Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time

No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)

[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!

Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!

mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help

That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.

mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it

Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)