Database Info

IMEI = 0 on Moto G

Last night i saw i can't connect on a carrier.
I saw on phone settings status that imei = 0
I changed a pair or ROMS (AOSB and then GPE) and i did before installing "fastboost erase all", that could be the problem?
Is there a way to have IMEI restored from 0 to what it's written on my battery?
German XT1032

surfino said:
Last night i saw i can't connect on a carrier.
I saw on phone settings status that imei = 0
I changed a pair or ROMS (AOSB and then GPE) and i did before installing "fastboost erase all", that could be the problem?
Is there a way to have IMEI restored from 0 to what it's written on my battery?
German XT1032
Click to expand...
Click to collapse
what does the telephone answer if you call the number *#06# ?

"fastboot erase.." should not to be done after ?

1pilo said:
what does the telephone answer if you call the number *#06# ?
Click to expand...
Click to collapse
IMEI=0

surfino said:
IMEI=0
Click to expand...
Click to collapse
have you tried this tutorial?
http://forum.xda-developers.com/showthread.php?t=1264021

denzel09 said:
"fastboot erase.." should not to be done after ?
Click to expand...
Click to collapse
i did fastboot erase before flashing roms,now i am back to stock 4.3 (downgraded bootloader also) but still IMEI=0 and carrier signal from nothing to 1 bar (used to 4-5 bars)

denzel09 said:
"fastboot erase.." should not to be done after ?
Click to expand...
Click to collapse
1pilo said:
have you tried this tutorial?
http://forum.xda-developers.com/showthread.php?t=1264021
Click to expand...
Click to collapse
don't know if i still have EFS FOLDER , i root it again and check. I fear by fastboot erase all or by switching roms/stock i deleted it

UPDATE:
There is no EFS directory or .nv_data file, what now?
Tried on TWRP (no Option) and manually looking with root explorer

surfino said:
UPDATE:
There is no EFS directory or .nv_data file, what now?
Tried on TWRP (no Option) and manually looking with root explorer
Click to expand...
Click to collapse
If you have completely removed that partition then imei is lost. You must try something to restore that efs directory. If possible in this particular case.

denzel09 said:
If you have completely removed that partition then imei is lost. You must try something to restore that efs directory. If possible in this particular case.
Click to expand...
Click to collapse
Grazie Denzel.
I think there's no EFS directory on Motorola Moto G anyways, only samsung or sony no?
tried mount on adb shell, no EFS partition also, but i think it's normal?

surfino said:
Grazie Denzel.
I think there's no EFS directory on Motorola Moto G anyways, only samsung or sony no?
tried mount on adb shell, no EFS partition also, but i think it's normal?
Click to expand...
Click to collapse
I don't know how help you buddy. Honestly i never had a similar imei problem. Yep, there is not efs on moto i think? Do you have tried to search how access to pds or similar?

denzel09 said:
I don't know how help you buddy. Honestly i never had a similar imei problem. Yep, there is not efs on moto i think? Do you have tried to search how access to pds or similar?
Click to expand...
Click to collapse
haven't found solution on Moto G, i even tried going back to stock, but no solution.. damn, i need this thing for work
do you think i can let restore from third part on internet as i don't have time to go to repair? (it's also german bought on amazon)
thanks

surfino said:
do you think i can let restore from third part on internet as i don't have time to go to repair? (it's also german bought on amazon)
thanks
Click to expand...
Click to collapse
I don't know. Also about warranty now... It's all to understand

Passed whole day trying to find solution.
Flashed JB Stock
Forced OTA Update to KK
Flashed pair of Roms
Erased modemst1 modemst2
No way to change that IMEI 0 and no signal on my Moto G German XT1032
If i boot without SIM it doesn't show im without SIM and if i go to phone operators it still lists the ones avaialable, don't know if it's weird or normal, just in case

UDPDATED:
On "fastboot getvar all" i can find my IMEI number but when i boot on various ROMS it gives me 0

What is the Baseband version?
Settings > About phone​

lost101 said:
What is the Baseband version?
Settings > About phone​
Click to expand...
Click to collapse
my phone is xt1032 German (bought on Amazon.de) with Italian Carrier
Currently on G+ ROM (switched many including stock)
BASEBAND: MSM8626BP_1032.340.63.00y

I read earlier this problem can occur due to a missing or not properly flashed radio firmware. You say you have already flashed stock, did you include the following commands?
flash modem NON-HLOS.bin
erase modemst1
erase modemst2
flash fsg fsg.mbn​

lost101 said:
I read earlier this problem can occur due to a missing or not properly flashed radio firmware. You say you have already flashed stock, did you include the following commands?
flash modem NON-HLOS.bin
erase modemst1
erase modemst2
flash fsg fsg.mbn​
Click to expand...
Click to collapse
Yup that's what I did when I flash stock one. Maybe I should invert erasing modem before flashing hlos.bin ?
Sent from my XT1032 using Tapatalk

That didn't do the trick. Same baseband and same no signal. Maybe I'm trying from a wrong starting stock? I've used blur 4.4.2 falcon retail Germany.
Sent from my XT1032 using Tapatalk

[Fixed] 64GB now shows 12.14GB total space

Not sure what's going on here. CM nightlies. Didn't notice until I got a space warning. It used to be like 50 something when I was on stock.

X10D3 said:
Not sure what's going on here. CM nightlies. Didn't notice until I got a space warning. It used to be like 50 something when I was on stock.
Click to expand...
Click to collapse
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.

dansou901 said:
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
Click to expand...
Click to collapse
Are the CM nightlies based off the 16gb variant?

X10D3 said:
Are the CM nightlies based off the 16gb variant?
Click to expand...
Click to collapse
No, but apparently they've got the userdata.img files inside the zip (I don't know why). So please open the zip you are flashing and take a look at what you are actually flashing (including the flashing script).

Yep, you flashed the 16gb version.
Sent from my One using XDA Free mobile app

Ah, I see you found the problem was using a toolkit... That's why I never used toolkits I didn't create myself or have looked at thoroughly first!

dansou901 said:
Ah, I see you found the problem was using a toolkit... That's why I never used toolkits I didn't create myself or have looked at thoroughly first!
Click to expand...
Click to collapse
I was looking for easy. Already scripted. Fixed and ready to roll. I didn't even think about there being 2 userdata files. Monday...

How did you fixed this?
Ive got the same problem
I've found the userdata64G.img
but when i do:
fastboot flash recovery userdata64G.img it gives an error
when i do fastboot flash recovery userdata.img it also gives the same error -> ive renamed the file
--> error is : Size to big
how do i fix this problem

Fopflugel said:
How did you fixed this?
Ive got the same problem
I've found the userdata64G.img
but when i do:
fastboot flash recovery userdata64G.img it gives an error
when i do fastboot flash recovery userdata.img it also gives the same error -> ive renamed the file
--> error is : Size to big
how do i fix this problem
Click to expand...
Click to collapse
It stopped you becasue that would have bricked your phone, don't type fastboot commands without knowing what to do.
What you're telling fastboot to do is to override the recovery with a userdata which would have for sure bricked your phone.
You want to be doing fastboot flash userdata userdata64G.img
not flashing recovery.

16 to 64
dansou901 said:
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
Click to expand...
Click to collapse
Hello friends,
I'm not a technician and I have the same problem with the memory.
Can someone explain step by step how do I fix my phone?
Thanks in advance!

Maldavanin said:
Hello friends,
I'm not a technician and I have the same problem with the memory.
Can someone explain step by step how do I fix my phone?
Thanks in advance!
Click to expand...
Click to collapse
1. Download 64gb userdata (find it)
2. Flash it via fastboot.
Google on how to use fastboot.
Requires unlocked bootloader
The small little details are up to you and can be found in various stickied threads. Best of luck.

try flash this stock ColorOS from here http://forum.xda-developers.com/showthread.php?t=2772627

Can't flash due to trustzone assertion failed

Hi all,
I am in dire need of some help. I wipe / formatted my phone in TWRP. I am now trying to reflash a rom, any rom..., back into my phone. I am able to fastboot recovery back into my phone and I was able to adb push Blisspop into /sdcard/. However when I try flashing in TWRP I get an error
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"
Error exceuting updater binary in zip '/data/BlissPop-bahbahbah'
Any help would be greatly appreciated...
Thanks!

Alright I fixed it. If anyone runs into similar problem. My fix is flashing stock rom using fastboot guide
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Thanks

Gnator said:
Alright I fixed it. If anyone runs into similar problem. My fix is flashing stock rom using fastboot guide
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Thanks
Click to expand...
Click to collapse
I currently have the same issue, have you successfully installed cm12 after reverting back to stock?

SvMagus said:
I currently have the same issue, have you successfully installed cm12 after reverting back to stock?
Click to expand...
Click to collapse
Exactly what file were you trying to flash? Which nightly of which ROM?
Transmitted via Bacon

I was trying to install BlissPop-v1.8-bacon-OFFICIAL-20150122-1445 but that still fails after installed stock CM11s. I am going to try BlissPop-v1.8-bacon-OFFICIAL-20150120-1358 and see if this problem is due to 1445 specifically. Will update ones I tried
Update: I was able to install 1358 this might be a problem with the new 1445. Need to contact Blisspop I think

You're referring to them by the wrong name, the 1358 you're referring to is actually the 01/20 nightly, and the 1445 you're referring to is the 01/22 nightly. The 1358 and 1445 are the times of day that those builds were built. It looks as though there's an issue with a commit that was merged by CM in the last day or so, I've seen someone else having this problem when flashing the 01/23 CM nightly.
Transmitted via Bacon

Tz errors are (im 99% sure) due to not having updated bacon cm12 firmware, which will break cm11s compatibility. If you want to move forward to cm12 only then flash this.
http://104.237.50.75/bacon_firmware_update_2015_01_16.zip
That is from slimLP server that @RobbieL811 has. Note that it will break any cm11 ROMs.
If using multirom, flash this from the main twrp menu using the install button, NOT going into multirom menu and choosing the ROM etc.
Note: this flash only has to be done once. Not every time u flash a ROM
Cheers
Sent From Lollipopified Bacon Goodness!

timmaaa said:
Exactly what file were you trying to flash? Which nightly of which ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
I just reverted back to where I was before, better wait for the official CM12 OTA... I can wait.

SvMagus said:
I just reverted back to where I was before, better wait for the official CM12 OTA... I can wait.
Click to expand...
Click to collapse
If you were to flash the latest cm12 nightly it would also serve the same purpose as the zip I linked to above. It updates specific files that are now required on cm12 ROMs going forward. But breaks cm11s and cm11 ROMs. Your choice what to do
Sent From Lollipopified Bacon Goodness!

ek69 said:
If you were to flash the latest cm12 nightly it would also serve the same purpose as the zip I linked to above. It updates specific files that are now required on cm12 ROMs going forward. But breaks cm11s and cm11 ROMs. Your choice what to do
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Thanks, I will consider this trough the day, how would you say is your experience so far with the current nightly? would you recommend it, are there any considerations that should be taken before changing? Seems to me you are very comfortable with 5.x, tell me from the day you flashed until now, is the phone faster? do you feel it is a big upgrade? Not many people have the OPO I had a nexus 5 before and 5.x was amazing, but I am afraid of jumping with my OPO because I've read that not all the features from CM11s are available with CM12. Is there a huge difference now? Sorry for making a long post but I thought, since you are very helpful and resourceful, I might want to ask.

SvMagus said:
Thanks, I will consider this trough the day, how would you say is your experience so far with the current nightly? would you recommend it, are there any considerations that should be taken before changing? Seems to me you are very comfortable with 5.x, tell me from the day you flashed until now, is the phone faster? do you feel it is a big upgrade? Not many people have the OPO I had a nexus 5 before and 5.x was amazing, but I am afraid of jumping with my OPO because I've read that not all the features from CM11s are available with CM12. Is there a huge difference now? Sorry for making a long post but I thought, since you are very helpful and resourceful, I might want to ask.
Click to expand...
Click to collapse
The difference between CM11/CM11S and CM12 is massive. CM12 has very limited features, you'll find very few at the moment.
Transmitted via Bacon

I've got similar problem here:
I manualy flashed (fastboot) the XNPH44S from the official site using these steps below:
Code:
1. fastboot flash modem NON-HLOS.bin
2. fastboot flash sbl1 sbl1.mbn
3. fastboot flash dbi sdi.mbn
4. fastboot flash aboot emmc_appsboot.mbn
5. fastboot flash rpm rpm.mbn
6. fastboot flash tz tz.mbn
7. fastboot flash LOGO logo.bin
8. fastboot flash oppostanvbk static_nvbk.bin (this partition seems to have appeared in the 44S build)
9. fastboot flash system system.img
10. fastboot flash userdata userdata_64G.img
11. fastboot flash boot boot.img
12. fastboot flash recovery recovery.img
13. fastboot flash cache cache.img
Than, I flashed TWRP 2.8.4.1.
And everything works except when I try installing "cm-12-20150123-NIGHTLY-bacon.zip" from the official cyanogenmod website.
At that point I get the error as shown in the attachment.
The last thing I didn't try is:
ek69 said:
Tz errors are (im 99% sure) due to not having updated bacon cm12 firmware, which will break cm11s compatibility. If you want to move forward to cm12 only then flash this.
http://104.237.50.75/bacon_firmware_update_2015_01_16.zip
That is from slimLP server that @RobbieL811 has. Note that it will break any cm11 ROMs.
If using multirom, flash this from the main twrp menu using the install button, NOT going into multirom menu and choosing the ROM etc.
Note: this flash only has to be done once. Not every time u flash a ROM
Click to expand...
Click to collapse
Where is this info from?

You've got to flash the updated files first.
Sent from my A0001 using Tapatalk

scottx . said:
You've got to flash the updated files first.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Tnx. I did it this morning. TZ check now works. Installed the cm-12-20150123-NIGHTLY but it has too many flaws (automatic brightness sensor not working, only FEW tiles are available in notification drawer, profiles don't work properly, too long delay for double-tap to wake the screen, ...). I'll install the cm-12-20150124-NIGHTLY later today to see if there are any improvements. My laziness is the only thing keeping me from reverting back to official 44S (a lot more customization options there).

Is it safe to flash back to cm11s after flashing the 2401 nightly? I follow the instructions in the cm11s official thread in android original development
Inviato dal mio A0001 utilizzando Tapatalk

hughfollett said:
Is it safe to flash back to cm11s after flashing the 2401 nightly? I follow the instructions in the cm11s official thread in android original development
Inviato dal mio A0001 utilizzando Tapatalk
Click to expand...
Click to collapse
If You download the official factory image (LINK)
And do these steps:
Code:
1. fastboot flash modem NON-HLOS.bin
2. fastboot flash sbl1 sbl1.mbn
3. fastboot flash dbi sdi.mbn
4. fastboot flash aboot emmc_appsboot.mbn
5. fastboot flash rpm rpm.mbn
6. fastboot flash tz tz.mbn
7. fastboot flash LOGO logo.bin
8. fastboot flash oppostanvbk static_nvbk.bin (this partition seems to have appeared in the 44S build)
9. fastboot flash system system.img
10. fastboot flash userdata userdata_64G.img (or userdata.img if You have the 16GB version)
11. fastboot flash boot boot.img
12. fastboot flash recovery recovery.img
13. fastboot flash cache cache.img
Then it should have to work.
The files (new firmware) that are replaced when upgrading from CM11S to CM12 will be replaced.
Picture in the attachmend:
LEFT RAR - new CM12 files
RIGHT - official factory image files

0v3rl0rd said:
Tnx. I did it this morning. TZ check now works. Installed the cm-12-20150123-NIGHTLY but it has too many flaws (automatic brightness sensor not working, only FEW tiles are available in notification drawer, profiles don't work properly, too long delay for double-tap to wake the screen, ...). I'll install the cm-12-20150124-NIGHTLY later today to see if there are any improvements. My laziness is the only thing keeping me from reverting back to official 44S (a lot more customization options there).
Click to expand...
Click to collapse
This link might be of use to you
http://www.cmxlog.com/12/bacon/
I'm on temasek ROM right now and it's got a decent amount of customization going on. Nothing like cm11s of course since for one xposed doesn't yet run on ART AFAIK but feature wise its getting there.
And yeah that one step you didn't do that I posted was the one step required haha [emoji12] [emoji106]
Try it different ROMs and see which one you like
Sent From Lollipopified Bacon Goodness!

hughfollett said:
Is it safe to flash back to cm11s after flashing the 2401 nightly? I follow the instructions in the cm11s official thread in android original development
Inviato dal mio A0001 utilizzando Tapatalk
Click to expand...
Click to collapse
I went back to CM11S half an hour ago. Was using the exact steps I wrote in my last post. Works like new now
ek69 said:
This link might be of use to you
http://www.cmxlog.com/12/bacon/
I'm on temasek ROM right now and it's got a decent amount of customization going on. Nothing like cm11s of course since for one xposed doesn't yet run on ART AFAIK but feature wise its getting there.
And yeah that one step you didn't do that I posted was the one step required haha [emoji12] [emoji106]
Try it different ROMs and see which one you like
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Yes, that step was the one needed. I didn't know that those files aren't included in custom ROMs. Anyway, TNX for the info, but, as I stated above, I'm back to factory CM11S. It has all the customization I need. Lollipop looks great, really great, and it's so smooth. It's just that it isn't a finished product for the OPO yet. I hope they release an official build in a month or so

ek69 said:
Tz errors are (im 99% sure) due to not having updated bacon cm12 firmware, which will break cm11s compatibility. If you want to move forward to cm12 only then flash this.
That is from slimLP server that @RobbieL811 has. Note that it will break any cm11 ROMs.
If using multirom, flash this from the main twrp menu using the install button, NOT going into multirom menu and choosing the ROM etc.
Note: this flash only has to be done once. Not every time u flash a ROM
Cheers
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Thank you! This worked! :good::good::good::laugh::laugh:

I'm getting same error:
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"
E:Error executing updater binary in zip '/sdcard/Download/Euphoria-OS-1.0-bacon-20150318.zip'
Error flashing zip '/sdcard/Download/Euphoria-OS-1.0-bacon-20150318.zip'
Updating partition details...
FAILED
This started happening after I went from stock 44s to omni unofficial 5.1. The 5.1 works fine but limited features so I tried to flash back down to a 5.0.2 rom whether euphoria or bliss and I get that error in twrp. I can flash the 5.1 rom with no issues though. I've tried going back to 44s updated to 55 on stock and then to the 5.0.2 roms and still failed. Of course clean wipes with all my flash attempts. I did flash a 33r and then a 44s oneplus one modem to test out battery life, could be unrelated but can anyone explain how I can resolve my issue? ThANks

No cellular service because radio is off?

I'm not sure what exactly caused it but about a week ago I lost cell service on my xt1032. When I dial *#*#4636#*#* it says the radio is off and the turn radio on button doesn't do anything. Wifi and GPS are working fine. Around that time I had updated the bootloader to 41.18 so that I could flash cm12.1 nightlies, erased modemst1 and modemst2 in fastboot, and flashed cm12.1. I had com.android.phone crashes like a few others did which they resolved by flashing backups.
I have tried to fix it by clean flashing cm12.1, flashing the latest XT1032_GPE_3112.97.00R radio, and clean flashing an old cm12 nightly but the radio remains off.
Any ideas?

I'm having the same issue. Dit you find a solution?

Have either of you tried flashing stock firmware?
Sent from my XT1031

ATTACK said:
Have either of you tried flashing stock firmware?
Sent from my XT1031
Click to expand...
Click to collapse
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?

BiggyB99 said:
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?
Click to expand...
Click to collapse
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031

ATTACK said:
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031
Click to expand...
Click to collapse
Thank you for your reply's. I'm now flashing stock rom from here (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510). Let you know in a sec
edit: still nothing Flashed the stock rom, wiped dalvik cache after. Rebooted a couple of times, but nothing seems to work.
Any other ideas?
edit2: Tried the optimized 'stock' rom, no success either. Also, I ruled out a SIM failure before, just did it agian because this is making me crazy!

Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031

ATTACK said:
Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031
Click to expand...
Click to collapse
Searching for the smiley that hits a hammer into his head. Sorry for my noobness! Flashing the firmware now.
edit: hanging on (bootloader) Preflash validation failed . Search xda learns me that that means the bootloader is locked, but the message says it is unlocked. I'll just go ahead and search some more
edit2: trying the bootloader unlocking procedure learns me that the bootloader is already unlocked: (bootloader) Device already unlocked!
What can I do next. (btw, the error comes on step 2 of the guide, where I put in: mfastboot flash motoboot motoboot.img. Everything else comes woth an OKAY. (http://forum.xda-developers.com/showthread.php?t=2542219)

You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031

ATTACK said:
You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031
Click to expand...
Click to collapse
I do not have a flash-all.bat (or something in that way) in my folder. Downloaded the firmware from the site you gave, the mfastboot from the Guide (http://forum.xda-developers.com/showthread.php?t=2542219) and I runned the commando's named there (for a xml.zip file).
edit: could it be that my bootloader is newer than the stock firmware is expecting? Running 41.18 now...
edit2: WORKED! I just kept trying to flash the stock firmware, error kept the same. Tried another recovery, did the flashing again but skipped the recovery step (error with bootloader still came up). After that I booted, and it worked! Sticking with stock 4.4.4 for now
Thanks for the help!
edit3: Working on 5.0.1 (stock) Did the OTA, failed because of my custom recovery. Flashed stock recovery, did OTA again --> works like a charm

Awesome!
Sent from my XT1031

Oneplus no signal

Hey guys, had a bit a problem, had to flash the phone as it got stuck in a boot loop. Had some trouble with that but managed to get cm 12 on now.
The only thing is that I don't get any signal at all. In my network selection it says there are no networks available. I've tried taking the sim in and out, resetting the access points. Tried to change the preferred network type but it can't be changed from Lte/GSM auto (prl).
Just a bit of history, I had to flash to color os then to cm 11 now it has updated to cm 12.
Has anyone got any tips for me please?
Also I put in *#*#3646#*#* and I read to go into phone info and to turn off and turn on the radio, but the button said turn on radio but it didn't do anything. What does the radio do?
Thanks

si_d_2003 said:
Hey guys, had a bit a problem, had to flash the phone as it got stuck in a boot loop. Had some trouble with that but managed to get cm 12 on now.
The only thing is that I don't get any signal at all. In my network selection it says there are no networks available. I've tried taking the sim in and out, resetting the access points. Tried to change the preferred network type but it can't be changed from Lte/GSM auto (prl).
Just a bit of history, I had to flash to color os then to cm 11 now it has updated to cm 12.
Has anyone got any tips for me please?
Also I put in *#*#3646#*#* and I read to go into phone info and to turn off and turn on the radio, but the button said turn on radio but it didn't do anything. What does the radio do?
Thanks
Click to expand...
Click to collapse
Did you have a corrupt efs before this? It sounds like you followed the corrupt efs fix guide. Flash twrp 2.8.6.0 and then flash the oxygenos modem. That might fix it.

I don't know what a corrupt efs is. But I couldn't do anything with the phone. Followed some YouTube guide by using some Chinese programme and flashing color os the fastbooting cm11. How would I flash the oxygen modem? Through twrp or fastboot?
Will having cm12 and an oxygen modem be OK?

si_d_2003 said:
I don't know what a corrupt efs is. But I couldn't do anything with the phone. Followed some YouTube guide by using some Chinese programme and flashing color os the fastbooting cm11. How would I flash the oxygen modem? Through twrp or fastboot?
Will having cm12 and an oxygen modem be OK?
Click to expand...
Click to collapse
Be careful when following these guides, if it's outdated (and it looks like it is) it can cause damage to your phone.
What I'd recommend is flash twrp 2.8.6.0 or katinatez's unofficial TWRP 2.8.7.0.5
Download the modem here
Flash the modem through twrp

Thanks XDA
I got my fixed by installing modem via Fastboot.
Follow these steps:
- Boot to fastboot and run command : fastboot flash modemst1 modemst1.bin
- Once done, install Cyanogen OS 12.1 via fastboot and reboot.
Above steps got my phone fixed, it was not showing imei no, unknown baseband previously and everything is fixed now. :highfive:

Rajneeshgadge17 said:
I got my fixed by installing modem via Fastboot.
Follow these steps:
- Boot to fastboot and run command : fastboot flash modemst1 modemst1.bin
- Once done, install Cyanogen OS 12.1 via fastboot and reboot.
Above steps got my phone fixed, it was not showing imei no, unknown baseband previously and everything is fixed now. :highfive:
Click to expand...
Click to collapse
You have same response in every modern related topic. That must be one heck of a fix. Lol whats that modems baseband?
Sent from my A0001 using Tapatalk

ikaraca said:
You have same response in every modern related topic. That must be one heck of a fix. Lol whats that modems baseband?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
That's right, instead of posting link to a post I copied text and posted, and yes I also had to flash color os using that Chinese tool as my phone hard bricked while trying to fix modem issue. But that Chinese tool revived my phone and when flashed CyanogenOS12.1 I flashed that attached modem which fixed the No SIM card issue.
The baseband version is 00241.
Hope this helps.

Rajneeshgadge17 said:
That's right, instead of posting link to a post I copied text and posted, and yes I also had to flash color os using that Chinese tool as my phone hard bricked while trying to fix modem issue. But that Chinese tool revived my phone and when flashed CyanogenOS12.1 I flashed that attached modem which fixed the No SIM card issue.
The baseband version is 00241.
Hope this helps.
Click to expand...
Click to collapse
Ok. Thanks. I ll give ir a shot.
Sent from my A0001 using Tapatalk

Have you tried turning it off and on?

ndnpwn said:
Have you tried turning it off and on?
Click to expand...
Click to collapse
You Sir, you deserve a Medal.