Related
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
pnz said:
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
Click to expand...
Click to collapse
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Benko111 said:
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Click to expand...
Click to collapse
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
EDIT2: And another correction. IMEI and serial showed fine after losing service, but I then rebooted the phone. Still no service, baseband is now unknown, IMEI is null and the serial number is non-zero but different than it was. However, I'm sure if I reflashed the ROM again I'd have service for a few minutes, so it doesn't seem like the EFS is entirely corrupt. I'm scratching my head a bit at this one.
pnz said:
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
Click to expand...
Click to collapse
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Benko111 said:
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Click to expand...
Click to collapse
Not generic IMEI but null IMEI. Not sure about generic serial, not sure how to tell the difference. And I'm now seeing the same on the NZ stock firmware after a reboot.
Is a Philz Touch EFS backup sufficient? Anything else I should backup as well?
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Benko111 said:
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Click to expand...
Click to collapse
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
pnz said:
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
Click to expand...
Click to collapse
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Benko111 said:
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Click to expand...
Click to collapse
Sorry, just meant that I thought somebody might have seen this exact problem before.
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
pnz said:
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
Click to expand...
Click to collapse
No, not fixed. Worked fine for a few days then the problem came back. Just tried a non-stock ROM (Omega) and same thing. Trying a CM-based ROM now (ParanoidAndroid), but not too hopeful.
Still don't understand why it works for hours/days, then suddenly stops. Rebooting it fixes it the first few times, then that stops working as well (and I get baseband unknown at this point). Flashing a new ROM always fixes it, for a few hours/days anyway.
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Any workarounds you can suggest? Just had the problem happen again on cyanogenmod, so that didn't fix it.
Try reading the freezing thread in general forum, see if the memory test tool will compete after a full wipe and fresh install of a stock firmware.
Other than that only a new motherboard, as the emmc chip is damaged.
hi,
since yesterday morning i was unable to receive/make calls on my e970. after googling a bit, i found out that imei number might be a problem. and sure enough,when i dialled *#06#, my imei no came up as "0". tried to restore a back up of lg stock jelly bean and cm11 kitkat. both haven't worked. data alone is working.
i was on cm12 nightly. how do i get back my calls functionality?
any help will be greatly appreciated
Your imei is part of the efs partition. You'll need to restore from a backup of that. Hopefully you have one. I've seen some threads where people have tried to fix without a backup, but I don't recall seeing any success. I could be wrong about that.
I am facing the same problem . I have efs partition backup with me in .IMG format. How do I restore the same.
Sent from my LG-E970 using Tapatalk 2
Had the same issue with my G2, I followed this guide and it resolved the problem. Here is the link:
http://forum.xda-developers.com/showthread.php?t=2701861
IDK if it would work with this model . If you dont find anything I would suggest you to try this. The phone has got the corrupted IMEI that's why its not working properly.
FYI, I was able to fix my IMEI using EFS Professional. It's taken me months to finally figure this out, namely because apparently nobody has looked into the precise procedure in the 3 years since this phone was released. Once you know the tricks, the procedure is pretty straightforward. I'll make a post about it shortly.
A "script kiddie" here, tried to customize my phone for the first time, accidentally installed a wrong version ROM, the phone went into a bootloop and so i decided to completely wipe the internal storage (that was so very dumb...)
Now after a day of struggle i managed to install everything i wanted - TWRP and a custom MIUI, but ever since that memory wipe i lost my signal. After searching around some, it seems that my IMEIs got lost (disconnected, corrupted, i dont know how to call it) and the phone can not detect either of my SIM cards. WiFi works fine. I do not have "nvram" folder or file anywhere on my phone.
Nocturnal22 said:
A "script kiddie" here, tried to customize my phone for the first time, accidentally installed a wrong version ROM, the phone went into a bootloop and so i decided to completely wipe the internal storage (that was so very dumb...)
Now after a day of struggle i managed to install everything i wanted - TWRP and a custom MIUI, but ever since that memory wipe i lost my signal. After searching around some, it seems that my IMEIs got lost (disconnected, corrupted, i dont know how to call it) and the phone can not detect either of my SIM cards. WiFi works fine. I do not have "nvram" folder or file anywhere on my phone.
Click to expand...
Click to collapse
Look in Q&A section/IMEI NVRAM Restore Tools post. That is allmost the only way to restore lost IMEI.
Good luck.
stympy said:
Look in Q&A section/IMEI NVRAM Restore Tools post. That is allmost the only way to restore lost IMEI.
Good luck.
Click to expand...
Click to collapse
Im getting lost in that wall of text. Cant i just replace my damaged "nvram" with someone elses working one? Switching IMEI to mine afterwards of course.
Also it says i dont have a baseband, should i be fixing that first?
Nocturnal22 said:
Im getting lost in that wall of text. Cant i just replace my damaged "nvram" with someone elses working one? Switching IMEI to mine afterwards of course.
Also it says i dont have a baseband, should i be fixing that first?
Click to expand...
Click to collapse
At the end of that tutorial look for a small word tutorial zipped. Read that one first.
Turns out all i had to do was mess around with firmware re-flashing until i got a working baseband and then use Chamelephon to set up IMEIs.
Everything was that easy.
Nocturnal22 said:
Turns out all i had to do was mess around with firmware re-flashing until i got a working baseband and then use Chamelephon to set up IMEIs.
Everything was that easy.
Click to expand...
Click to collapse
Try this: reset the phone to factory defaults. Then try to see if IMEI'S are still there.
Tell me what firmware worked. It is a valuable information for others.
Thanks.
stympy said:
Try this: reset the phone to factory defaults. Then try to see if IMEI'S are still there.
Tell me what firmware worked. It is a valuable information for others.
Thanks.
Click to expand...
Click to collapse
I wiped all the factory settings and the ROMs i used to mess around were: P780_S124_ROW_140403, flashed through flashtool, supposed to be the "official" ROM (the one i got the stable baseband from) and MIUISU_4.4.2v_P780_7.2.24_ROW (the one im using currently). All the IMEIs got restored through Chamalephon as soon as i got a working baseband and i can send/accept calls and SMS with no problem. However there is a bug with constantly changing MAC now.
Nocturnal22 said:
I wiped all the factory settings and the ROMs i used to mess around were: P780_S124_ROW_140403, flashed through flashtool, supposed to be the "official" ROM (the one i got the stable baseband from) and MIUISU_4.4.2v_P780_7.2.24_ROW (the one im using currently). All the IMEIs got restored through Chamalephon as soon as i got a working baseband and i can send/accept calls and SMS with no problem. However there is a bug with constantly changing MAC now.
Click to expand...
Click to collapse
Hi. Did you installed MIUISU over s124 ?
If you did, you must update to s228 Kitkat.
S124 is jellybean. You will get errors, if you install kitkat over jellybean.
stympy said:
Hi. Did you installed MIUISU over s124 ?
If you did, you must update to s228 Kitkat.
S124 is jellybean. You will get errors, if you install kitkat over jellybean.
Click to expand...
Click to collapse
No, i installed s124 backed up the baseband and nvram files through MTK. Then i flashed the system, installed MIUI and recovered my baseband. The unstable MAC error started in s124 already.
Nocturnal22 said:
No, i installed s124 backed up the baseband and nvram files through MTK. Then i flashed the system, installed MIUI and recovered my baseband. The unstable MAC error started in s124 already.
Click to expand...
Click to collapse
Ok. I understand.
Hello guys.
So I was flashing custom roms before, and just today realised that my IMEI got lost.
I tried restoring it by this method: https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789
And now my phone doesnt recognise the sim card and I dont have signal.
I am currently on AOSIP 5.9, my phone is redmi note 3 pro.
I have few nvram backups, from miui and cm13, what can I do to restore my EFS partition and get back my IMEI?
{s3rious} said:
Hello guys.
So I was flashing custom roms before, and just today realised that my IMEI got lost.
I tried restoring it by this method: https://forum.xda-developers.com/re.../how-to/flash-recover-efs-snapdragon-t3406789
And now my phone doesnt recognise the sim card and I dont have signal.
I am currently on AOSIP 5.9, my phone is redmi note 3 pro.
I have few nvram backups, from miui and cm13, what can I do to restore my EFS partition and get back my IMEI?
Click to expand...
Click to collapse
Don't worry. In my case, IMEI were not erased, even then sim networks weren't showing up. This happens when you downgrade or upgrade without required firmware (atleast with me). Try to flash latest miui firmware or, you can try cm14.1 firmware.
geeknoob said:
Don't worry. In my case, IMEI were not erased, even then sim networks weren't showing up. This happens when you downgrade or upgrade without required firmware (atleast with me). Try to flash latest miui firmware or, you can try cm14.1 firmware.
Click to expand...
Click to collapse
Thanks for help, I tried that but it isn't working. This isnt the solution, next advices?
edit: Solved it, kind of. I restored efs partition from backup, but I still have to get my IMEI, because when I type *#06# in dial app i get IMEI - 0
{s3rious} said:
Thanks for help, I tried that but it isn't working. This isnt the solution, next advices?
edit: Solved it, kind of. I restored efs partition from backup, but I still have to get my IMEI, because when I type *#06# in dial app i get IMEI - 0
Click to expand...
Click to collapse
Great. Now get your imei(s) from the phone box and you're good to go!
geeknoob said:
Great. Now get your imei(s) from the phone box and you're good to go!
Click to expand...
Click to collapse
I have 1 IMEI on the phone box, there is SN (serial number?), MEID (which is for cdma network) and some other 13 digit number, what is that?
Okay guys, I've tried few different methods on how to restore IMEI and neither works. What the hell!?
I tried this one: http://en.miui.com/thread-245598-1-1.html and
this one: http://en.miui.com/forum.php?mod=viewthread&tid=299779&highlight=IMEI%2Brestore
{s3rious} said:
Okay guys, I've tried few different methods on how to restore IMEI and neither works. What the hell!?
I tried this one: http://en.miui.com/thread-245598-1-1.html and
this one: http://en.miui.com/forum.php?mod=viewthread&tid=299779&highlight=IMEI%2Brestore
Click to expand...
Click to collapse
I can not help you with a solution, but I'll tell you that I have also lost IMEI, sent it on service and came back with another IMEI, not that one on the box. Since then, my phone acts extremely strange in any way, with random reboots, bootlops, errors on flashing different roms... Its just a pure hell. I don't know if the reason is that it has another IMEI then the original or its just a bad hardware, but I'm considering trying replace it with original one...
IMEI is the same on both SIMS for me. Sadly, I haven't checked before losing it.
apriores said:
I can not help you with a solution, but I'll tell you that I have also lost IMEI, sent it on service and came back with another IMEI, not that one on the box. Since then, my phone acts extremely strange in any way, with random reboots, bootlops, errors on flashing different roms... Its just a pure hell. I don't know if the reason is that it has another IMEI then the original or its just a bad hardware, but I'm considering trying replace it with original one...
IMEI is the same on both SIMS for me. Sadly, I haven't checked before losing it.
Click to expand...
Click to collapse
Have you checked if you have the same phone, redmi note 3? And also check your software, if it is official or some vendor rom.
{s3rious} said:
Have you checked if you have the same phone, redmi note 3? And also check your software, if it is official or some vendor rom.
Click to expand...
Click to collapse
Have you twrp backup specially efs then done restore it
{s3rious} said:
Have you checked if you have the same phone, redmi note 3? And also check your software, if it is official or some vendor rom.
Click to expand...
Click to collapse
It's the same one. I can easily recognize it by screen protector, applied by me.
I have flashed official MIUI, different versions by EDL and all acts the same, with random reboots and bootloops.
apriores said:
It's the same one. I can easily recognize it by screen protector, applied by me.
I have flashed official MIUI, different versions by EDL and all acts the same, with random reboots and bootloops.
Click to expand...
Click to collapse
I think it is hardware problem I face it before without playing in the IMEI and i was in warranty period so I gives my phone to the customer service and after a while they give me a new one . So try to get back the IMEI and go to the customer service with a miui rom . Flash it using mine flash and be sure about the variant is it Kate or kenzo.. I hope I helped u
@{s3rious}, @apriores, @Moody Abed, Guys I have had a lot of history with bricking and loosing IMEI, mac address, fp sensor issue, earphone issue with RN3. There were many times, when I thought, that I've damaged the hardware and it is needed to be sent for service. But let me tell you, most of these issues can be solved by making a few changes in the software. First of all, try to go to the latest global developer miui rom. Manually flash the modem partitions. Restore efs. Try all of these. You'll surely manage to correct the issue.
You can read my history with this device in this POST.
Bro I think you wiped your modem & imei. First flash the modem 1 and 2 then work for imei. Hope it helps. Here is the link
https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789
sasukay said:
@{s3rious}, @apriores, @Moody Abed, Guys I have had a lot of history with bricking and loosing IMEI, mac address, fp sensor issue, earphone issue with RN3. There were many times, when I thought, that I've damaged the hardware and it is needed to be sent for service. But let me tell you, most of these issues can be solved by making a few changes in the software. First of all, try to go to the latest global developer miui rom. Manually flash the modem partitions. Restore efs. Try all of these. You'll surely manage to correct the issue.
You can read my history with this device in this POST.
Click to expand...
Click to collapse
I've already flashed modem files manually and later followed a tutorial how to get imei back, but that didnt work. I used QSPT tools and it didnt work. Are there any other steps?
{s3rious} said:
I've already flashed modem files manually and later followed a tutorial how to get imei back, but that didnt work. I used QSPT tools and it didnt work. Are there any other steps?
Click to expand...
Click to collapse
Well it was more of a hit and trial for me, but I can vouch that THIS WORKED FOR ME, atleast once.
sasukay said:
Well it was more of a hit and trial for me, but I can vouch that THIS WORKED FOR ME, atleast once.
Click to expand...
Click to collapse
when I tried the first option, I completely lost my connection, the phone didnt recognized the sim. And then I made a restore with trp backup of efs partition and got my signal back, but IMEI was still missing.
After that I tried the second option, but I have only 1 IMEI, not 2. And in order to press start you need to have 2 IMEI-s, so what should I do?
{s3rious} said:
when I tried the first option, I completely lost my connection, the phone didnt recognized the sim. And then I made a restore with trp backup of efs partition and got my signal back, but IMEI was still missing.
After that I tried the second option, but I have only 1 IMEI, not 2. And in order to press start you need to have 2 IMEI-s, so what should I do?
Click to expand...
Click to collapse
You don't have the box with you?
Aah nevermind. The IMEI 2 is same as the IMEI 1 unto the last two digits. For me, IMEI 1 has 23 as the last digits and IMEI2 has 31. Apart from that everything is same. So, you can try putting some similar values to IMEI 2.
And, I'll tell you what. One time, I lost my IMEI and I didn't had my box with me. What I did was I made a clean flash of the miui global dev (any miui may work), and I had them back. Then I don't remember exactly, but I think I made the efs backup and .qcn backup and noted the IMEI on sheet and then flashed the custom ROM. Then restored the efs or qcn or maybe I entered the IMEIs manually, following the same tutorial I mentioned earlier. I had my networks working on the custom rom.
Good luck to you.
apriores said:
I can not help you with a solution, but I'll tell you that I have also lost IMEI, sent it on service and came back with another IMEI, not that one on the box. Since then, my phone acts extremely strange in any way, with random reboots, bootlops, errors on flashing different roms... Its just a pure hell. I don't know if the reason is that it has another IMEI then the original or its just a bad hardware, but I'm considering trying replace it with original one...
IMEI is the same on both SIMS for me. Sadly, I haven't checked before losing it.
Click to expand...
Click to collapse
sasukay said:
You don't have the box with you?
Aah nevermind. The IMEI 2 is same as the IMEI 1 unto the last two digits. For me, IMEI 1 has 23 as the last digits and IMEI2 has 31. Apart from that everything is same. So, you can try putting some similar values to IMEI 2.
And, I'll tell you what. One time, I lost my IMEI and I didn't had my box with me. What I did was I made a clean flash of the miui global dev (any miui may work), and I had them back. Then I don't remember exactly, but I think I made the efs backup and .qcn backup and noted the IMEI on sheet and then flashed the custom ROM. Then restored the efs or qcn or maybe I entered the IMEIs manually, following the same tutorial I mentioned earlier. I had my networks working on the custom rom.
Good luck to you.
Click to expand...
Click to collapse
I have a box, but only 1 IMEI is written there :/
{s3rious} said:
I have a box, but only 1 IMEI is written there :/
Click to expand...
Click to collapse
Use it on both SIMs.
apriores said:
Use it on both SIMs.
Click to expand...
Click to collapse
That's a big no no.
{s3rious} said:
I have a box, but only 1 IMEI is written there :/
Click to expand...
Click to collapse
Try doing what I said. If manually putting values doesn't work. Flash miui global dev fastboot rom using miflash.
So after mingling with qfil and going cn from global my fingerprint scanner and mobile network stopped working. It's probably because i once wiped the modem partitions without first backing them up. I tried Reflashing the rom, factory reseting the phone and changing the IMEI to the correct one but to no avail. Does anyone know a way to repair it?
Have you tried flashing the original persist from global (ROW)? If so, you probably need a scrubbed qcn and many of us are reluctant to provide one at the moment (laziness, paranoia, etc.) to get it back to normal.
Yup, tried flashing global persist. It did nothing. Sadly I also could not find a matching qcn file online. Guess I have a pretty nice music player now without the ability to call.
Malberd said:
Yup, tried flashing global persist. It did nothing. Sadly I also could not find a matching qcn file online. Guess I have a pretty nice music player now without the ability to call.
Click to expand...
Click to collapse
I think you need a qcn from a Duel 2 (not a Pro 2) which I don't have at the moment. Some digging through the forum in China may supply a generic one that matches both.
Malberd said:
Yup, tried flashing global persist. It did nothing. Sadly I also could not find a matching qcn file online. Guess I have a pretty nice music player now without the ability to call.
Click to expand...
Click to collapse
Are you flashing the modem (NON HLOS) and persist partitions before or after first boot? Both will only apply correctly before first boot with a clean unwritten data partition. Try wiping the data partition followed by QFIL flashing the original Duel 2 ROW build; personally, I'd try using Rescue Assistant first (Rescue Assistant may help reapply missing data).
Can you activate radio for WiFi and Bluetooth or is it not able to be switched on/off at all? You could gather the hardware addresses if you scan with another device to see if the phone at least transmits a signal from the chip itself, which would further assist in restoring the addressing with a scrubbed QCN from a Duel 2. As for the fingerprint hardware, pretty sure you need your original persist image to restore the functionality; but maybe restoring the qcn will provide data necessary for a rebuild of the persist partition.
Both WiFi and Bluetooth function normally. I think flashing a matching QCN would solve the problems. Sadly I could not find such file on the chinese lenovo forum