Dear all, I have installed erobot rom latest version when I was in miui 8. ended up in bootloop and returned back to miui. But there was no network and I checked my imie and it was all zeros. Turned back to stock MM. result is same..then back to stock lollipop, still it's the same...is there any way to get out of this? or I'm doomed...? please help.
Try all of this it might recover your IMEI https://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021, https://forum.xda-developers.com/showthread.php?t=1853478, https://forum.xda-developers.com/cr...lashable-zip-imei-repair-android-one-t2992846 Good luck.
Related
so yesterday i had put my phone on the charger ......then when i went back i was greated with a black screen .so i removed the battery and powered it back on and now my phone has no network no IMEI ...flashed a nardroid of the stock Rom and still No IMEI number ,No network .any help?
EDIT it works fine but it shows my IMEI no as unknown and theres no network no matter whatever I do .Changing baseband also dosent help
Maybe you could try to flash a sbf.-file to get completely back to stock. You just flashed a nandroid backup, so your phone is still rooted. Maybe this can help ...
Hello All,
Tried searching for a case peculiar as mine, wasnt able to find one so here is the lowdown.
1. Xperia C6603 , originally had 4.2.2 stock ROM which was working fine with my local network. Dont remember the baseband version.
2. Used XperiFirm to download the latest firmware as reported in the list. Dont know what does the suffix RxD (R1D--R8D) means. Anyone please explain. As per the below screenshot downloaded version "C6603_Customized HK_1270-5695_10.5.1.A.0.292_R1D" .
3. Before flashing the downloaded firmware I flashed the dualrecovery from XZDualRecovery. I made a TWRP backup of the 4.2.2 stock ROM on an external SD card, for all partitions including TA,system,boot etc.
4. Used Flashtool to convert the downloaded (step 2) firmware "FILES" format to a flashable FTF file. Flashed the firmware , which went on smoothly.
5. At the first startup I got the following screen , telling me that it is a prototype device/firmware . I went on to see that the network which was working fine with stock ROM 4.2.2 was no longer available.
I tried to go to settings to check and search for networks, which shows available networks, but unable to get itself registered to the SIM providers network. Tried all the settings combinations in menu "*#*#4636*#*#" , nothing makes it work to get the GSM network connectivity back. It is supposedly on the correct setting of LTE/WCDMA/GSM which my current operator supports. Following is the "About" screen for current baseband version.
Tried going in the "Service" menu via "*#*#7378423#*#*" , with the following info, having an unknown modem configuration.
6. Tried reverting back to the old TWRP backup, for which I needed the TWRP recovery loaded on the phone. So ran the XZDualRecovery script again (with the new 4.4 ROM on the phone), however the script hangs around in the end and never reboots the phone with the TWRP recovery. So i am unable to revert and use the stock ROM backups .
7. I dont want to root/unlock the bootloader, however I tried installing TWRP via its "XZrecovery.apk", but it requires busybox (which requires a rooted phone). So i tried the rooting script from [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader], but it also hangs around in the end and never delivers a rooted phone.
8. Tried looking around for assortment of xperia Z baseband files to check and see if flashing it separately can make it work, however to no avail the the condition persists.
Either ways having a prototype version on the phone which transmits all data back to sony is not desirable at all. So need to replace it for sure. Currently I am stuck in the middle without a clue of how to go back and restore the 4.2.2 TWRP backup, or to actually flash a "non-prototype" or retail version of 4.4.x .
Any help/guidance/suggestions to remedy would be appreciated.
Thanks.
=====================UPDATE
Ok followed the instructions at [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader] , read carefully again to flash the .230 kernel. Flashed the XZDualRecovery and got the TWRP recovery back.
Restored the old 4.2.2 TWRP backup , hoping that everything would go back to normal. However with a successul restore and a reboot, I was amazed to see I still have no network connectivity. The baseband version is "9x15A-ACEFWMAZQ-30110068-44" . Another noticeable thing was that after the restore and first boot, I still got the "prototype device" message again, which was not there when I first booted the device with original stock 4.2.2 ROM before this flashing adventure began.
Any ideas what may have gone bad.
Thanks.
=======================================
Just got to know that my device is a BROWN device, its IMEI number starts from 0044 so it is a prototype. Any ideas is it really good or bad to have one. Also I see that after another restore of the original stock 4.2.2 ROM it is barely getting the signals indoor (1 bar only). The signal reception is very weak and sporadic . Should i keep the device or not and is there any remedy or network signal strength.
Thanks.
HyperEscape said:
Hello All,
Tried searching for a case peculiar as mine, wasnt able to find one so here is the lowdown.
1. Xperia C6603 , originally had 4.2.2 stock ROM which was working fine with my local network. Dont remember the baseband version.
2. Used XperiFirm to download the latest firmware as reported in the list. Dont know what does the suffix RxD (R1D--R8D) means. Anyone please explain. As per the below screenshot downloaded version "C6603_Customized HK_1270-5695_10.5.1.A.0.292_R1D" .
3. Before flashing the downloaded firmware I flashed the dualrecovery from XZDualRecovery. I made a TWRP backup of the 4.2.2 stock ROM on an external SD card, for all partitions including TA,system,boot etc.
4. Used Flashtool to convert the downloaded (step 2) firmware "FILES" format to a flashable FTF file. Flashed the firmware , which went on smoothly.
5. At the first startup I got the following screen , telling me that it is a prototype device/firmware . I went on to see that the network which was working fine with stock ROM 4.2.2 was no longer available.
I tried to go to settings to check and search for networks, which shows available networks, but unable to get itself registered to the SIM providers network. Tried all the settings combinations in menu "*#*#4636*#*#" , nothing makes it work to get the GSM network connectivity back. It is supposedly on the correct setting of LTE/WCDMA/GSM which my current operator supports. Following is the "About" screen for current baseband version.
Tried going in the "Service" menu via "*#*#7378423#*#*" , with the following info, having an unknown modem configuration.
6. Tried reverting back to the old TWRP backup, for which I needed the TWRP recovery loaded on the phone. So ran the XZDualRecovery script again (with the new 4.4 ROM on the phone), however the script hangs around in the end and never reboots the phone with the TWRP recovery. So i am unable to revert and use the stock ROM backups .
7. I dont want to root/unlock the bootloader, however I tried installing TWRP via its "XZrecovery.apk", but it requires busybox (which requires a rooted phone). So i tried the rooting script from [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader], but it also hangs around in the end and never delivers a rooted phone.
8. Tried looking around for assortment of xperia Z baseband files to check and see if flashing it separately can make it work, however to no avail the the condition persists.
Either ways having a prototype version on the phone which transmits all data back to sony is not desirable at all. So need to replace it for sure. Currently I am stuck in the middle without a clue of how to go back and restore the 4.2.2 TWRP backup, or to actually flash a "non-prototype" or retail version of 4.4.x .
Any help/guidance/suggestions to remedy would be appreciated.
Thanks.
=====================UPDATE
Ok followed the instructions at [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader] , read carefully again to flash the .230 kernel. Flashed the XZDualRecovery and got the TWRP recovery back.
Restored the old 4.2.2 TWRP backup , hoping that everything would go back to normal. However with a successul restore and a reboot, I was amazed to see I still have no network connectivity. The baseband version is "9x15A-ACEFWMAZQ-30110068-44" . Another noticeable thing was that after the restore and first boot, I still got the "prototype device" message again, which was not there when I first booted the device with original stock 4.2.2 ROM before this flashing adventure began.
Any ideas what may have gone bad.
Thanks.
=======================================
Just got to know that my device is a BROWN device, its IMEI number starts from 0044 so it is a prototype. Any ideas is it really good or bad to have one. Also I see that after another restore of the original stock 4.2.2 ROM it is barely getting the signals indoor (1 bar only). The signal reception is very weak and sporadic . Should i keep the device or not and is there any remedy or network signal strength.
Thanks.
Click to expand...
Click to collapse
Firstly I love the detail you have provided which would save you and me a lot of time to pinpoint the exact problem and work it accordingly.
Firstly, I would suggest that if you have a box or any other receipt that shows your exact device name with its basebands. Where did you buy it from and what is your exact location so we can guess your region. This is the time to show it now. Also which basebands work in your location can also help us out.
The problem you have made it flashed basebands of a different variant which has resulted in loss of network. So to fix it we need, and there are three ways about it.
First, download Sony PC companion and try to repair your phone and see if that helps.
Secondly, download flashtool and ftf for your device (make sure you select the right variant this time. Choosing for wrong device can hard brick your phone. so beware) and flash your phone with it.
If all this fails, you go to Sony flashtool called Emma. Download it and try to flash it with that.
You can google how to use every tool on xda and I am sure you would find a lot of guides for that.
Quote me back in case you expect an answer
HELLO EVERYONE.
i have a samsung i9305T i flashed it wth L.P rom then suddenly
my imei went 0049. i tried anything bUt no luck. so i decided to flash a stock one
4.1.2 my imei was back. But when i try to insert my network sim it says.
NOT REGISTERED ON NETWORK . tho ived used this phone before here in the philippines
so im sure it is unlocked.
any help guys.? thank you in advance does my baseband caused the issue?
please help ...
Hi,
I'm not an expert at all but i have a theory :
I think you get a corrupted EFS. You flashed L.P rom so the format of your EFS changed to V2. So when you tried to return to 4.1.2, the phone can't read your efs anymore.
I think the solution is to flash a newer baseband, for example the L.P baseband or a KK baseband.
Read more about efs format => http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
Hope it helps.
Hello, I have done much research about this issue and I have come to the conclusion that this Note 5 our cell phone repair store bought has two different imei's. I believe that it has been previously rooted and had the t-mobile imei spoofed to a working metro-pcs imei.
The imei on the back glass is a valid t-mobile imei that has been blacklisted. Which is fine, because we can pay for a service to remove the blacklist.
The imei in the software of the phone (found in settings and from using the #*06# code) is not recognized by t-mobile, even though there is a t-mobile splash screen. The only network that recognizes the imei is metro-pcs. Although they cannot confirm what device this imei is connected to.
The phone came with a metro-pcs sim card when the phone was bought, which was recognized by the metro-pcs network and said (Metro-Pcs) on the unlock screen. The Knox counter has been tripped by 1. The phone had android 5.1 installed and the firmware was marked 'Custom' in the settings.
Since then I flashed the latest official firmware (android 6.0.1, baseband version N920TUVS4DQA2) using odin. Then I was able to update the software from the update menu in the phone to the latest security patch. Yet the imei stays the same and does not revert to the one on the back. It appears as though it is the original back glass, but I have not taken it off to verify.
So, I flashed a custom kernel and recovery (Stock modified kernel, and TWRP) in attempt to find a way to manually change the imei back to its Original state. Which shouldnt be illegal, since I am reverting back to the original imei? From my research, it appears as though I might be able to flash a deodexed stock rom for the note 5 and then install the xposed framework, then use their imei changer. But will this actually work to change the imei from the one in the settings to the correct one on the back glass? Is there any other way to revert back to the original imei which would show in the settings?
Any help would be much appreciated.
-cpr_centerville
[email protected]_centerville said:
Hello, I have done much research about this issue and I have come to the conclusion that this Note 5 our cell phone repair store bought has two different imei's. I believe that it has been previously rooted and had the t-mobile imei spoofed to a working metro-pcs imei.
The imei on the back glass is a valid t-mobile imei that has been blacklisted. Which is fine, because we can pay for a service to remove the blacklist.
The imei in the software of the phone (found in settings and from using the #*06# code) is not recognized by t-mobile, even though there is a t-mobile splash screen. The only network that recognizes the imei is metro-pcs. Although they cannot confirm what device this imei is connected to.
The phone came with a metro-pcs sim card when the phone was bought, which was recognized by the metro-pcs network and said (Metro-Pcs) on the unlock screen. The Knox counter has been tripped by 1. The phone had android 5.1 installed and the firmware was marked 'Custom' in the settings.
Since then I flashed the latest official firmware (android 6.0.1, baseband version N920TUVS4DQA2) using odin. Then I was able to update the software from the update menu in the phone to the latest security patch. Yet the imei stays the same and does not revert to the one on the back. It appears as though it is the original back glass, but I have not taken it off to verify.
So, I flashed a custom kernel and recovery (Stock modified kernel, and TWRP) in attempt to find a way to manually change the imei back to its Original state. Which shouldnt be illegal, since I am reverting back to the original imei? From my research, it appears as though I might be able to flash a deodexed stock rom for the note 5 and then install the xposed framework, then use their imei changer. But will this actually work to change the imei from the one in the settings to the correct one on the back glass? Is there any other way to revert back to the original imei which would show in the settings?
Any help would be much appreciated.
-cpr_centerville
Click to expand...
Click to collapse
This is such a grey area and from my understanding isn't to be discussed by any means on xda so not going to comment on changing imeis whether valid or not but can give you this link.
https://swappa.com/esn?hc_location=ufi
Run the imei thru that and will tell you valid/invalid/blacklisted/etc but give you a result of what it possibly belongs too.
Keep in mind too someone could of broke the back of their phone, bought a blacklisted and swapped the mother board out so could be correct to begin with.
I am new to Android Custom ROM and everything. I got this phone from a local vendor and it was running a custom rom called "LamLazy Rom v3.0 Dual SIM" - I researched on it and figured it was used to convert N950N to N950F or something like that.
I have the EFS and TWRP complete backup of the LamLazy ROM. I wanted to try LineageOS 17.1 on my device and flashed it using TWRP. After the successful flashing, I noticed my phone can no longer connect with my network. I cannot make or receive phone calls. I tried every possible thing that I knew. Even flashed series of Custom ROMs, on every other rom I faced the same network issue.
However, when I revert back to LamLazy it works fine. I can use both of my SIM slots and my phone shows 2 IMEI's while on lineage and other it shows only one IMEI.
Now, my problem is I want to get rid of LamLazy and try new ROMs such as Pixel Experience and LineageOS, but my cellular network doesn't work. Can someone please help me with this? :crying:
HamzaSheikh said:
I am new to Android Custom ROM and everything. I got this phone from a local vendor and it was running a custom rom called "LamLazy Rom v3.0 Dual SIM" - I researched on it and figured it was used to convert N950N to N950F or something like that.
I have the EFS and TWRP complete backup of the LamLazy ROM. I wanted to try LineageOS 17.1 on my device and flashed it using TWRP. After the successful flashing, I noticed my phone can no longer connect with my network. I cannot make or receive phone calls. I tried every possible thing that I knew. Even flashed series of Custom ROMs, on every other rom I faced the same network issue.
However, when I revert back to LamLazy it works fine. I can use both of my SIM slots and my phone shows 2 IMEI's while on lineage and other it shows only one IMEI.
Now, my problem is I want to get rid of LamLazy and try new ROMs such as Pixel Experience and LineageOS, but my cellular network doesn't work. Can someone please help me with this? :crying:
Click to expand...
Click to collapse
i bought a note 8 from someone and it was running a custom os tried to iroall stock rom and i now i get emergency calls and cant register on any networks..my phone is only a single simcard phone but it shows two imei numbers now and one is 0000000 pleass help i dont even know how to post on xda sorry for hijacking your post