setxperia (for doing everything in one app. including undervolt)

Sent from my X10i using XDA App

Houston we have a problem...

---

Howdy all,

Today my wife's phone has started displaying no signal and asking for the SIM card to be inserted (when it already is inserted). It also shows Baseband Unknown under the About Phone menu.
I've spent all day on the laptop so far, trawling through thread after thread about this problem and trying to fix this.

I know that you can cause this problem if you unlock the bootloader using the wrong cmd file or if the phone has been SIM unlocked via a third party company.
The thing is, her phone is an Orange UK phone and has never been SIM unlocked at all.

I unlocked the bootloader approx 4 weeks ago using qsd8250_semc.cmd - this was successful and we have been able to use custom kernels with no problems since then.
Her latest ROM/Kernel combination (Miui 1.12.2 (Cobrato) + Doom Kernel v06-1113 Cob06c) has been in use for approx 5 days with no issues then today, randomly the phone seems to be acting as though it cannot read her SIM.

I've re-locked the bootloader,
Downgraded to 2.1,
Used SE PC companion to update to 2.3,
Flashed various custom ROMs and ensure the correct baseband was also flashed in flashtool,
Unlocked bootloader again using qsd8250_setool2.cmd then re-locked it
All of which were suggested in various threads about this.

I swapped my SIM with her and my SIM had no service in her X10 as well (expected) but strangely her SIM in my phone still had no service.

The phone must be capable of finding service, because each time I downgrade to 2.1, or update to 2.3, the phone still asks for the SIM to be inserted, but then it will find service, however as soon as the phone is rebooted in any way, it cannot find service anymore.

All the threads I've found about this suggest that this only happens if your phone is SIM unlocked and you use the wrong file to unlock the bootloader, and then the problem is apparent immediately.
We have never SIM unlocked the phone, we used the correct file and the problem has only just started approx 4 weeks later -
This must be resolvable!!!!

Please please please, does anyone have any further help for me?
I'm at my wits end now.

Many thanks,
wildcardspv.

Originally Posted by wildcardspv

Howdy all,

Today my wife's phone has started displaying no signal and asking for the SIM card to be inserted (when it already is inserted). It also shows Baseband Unknown under the About Phone menu.
I've spent all day on the laptop so far, trawling through thread after thread about this problem and trying to fix this.

I know that you can cause this problem if you unlock the bootloader using the wrong cmd file or if the phone has been SIM unlocked via a third party company.
The thing is, her phone is an Orange UK phone and has never been SIM unlocked at all.

I unlocked the bootloader approx 4 weeks ago using qsd8250_semc.cmd - this was successful and we have been able to use custom kernels with no problems since then.
Her latest ROM/Kernel combination (Miui 1.12.2 (Cobrato) + Doom Kernel v06-1113 Cob06c) has been in use for approx 5 days with no issues then today, randomly the phone seems to be acting as though it cannot read her SIM.

I've re-locked the bootloader,
Downgraded to 2.1,
Used SE PC companion to update to 2.3,
Flashed various custom ROMs and ensure the correct baseband was also flashed in flashtool,
Unlocked bootloader again using qsd8250_setool2.cmd then re-locked it
All of which were suggested in various threads about this.

I swapped my SIM with her and my SIM had no service in her X10 as well (expected) but strangely her SIM in my phone still had no service.

The phone must be capable of finding service, because each time I downgrade to 2.1, or update to 2.3, the phone still asks for the SIM to be inserted, but then it will find service, however as soon as the phone is rebooted in any way, it cannot find service anymore.

All the threads I've found about this suggest that this only happens if your phone is SIM unlocked and you use the wrong file to unlock the bootloader, and then the problem is apparent immediately.
We have never SIM unlocked the phone, we used the correct file and the problem has only just started approx 4 weeks later -
This must be resolvable!!!!

Please please please, does anyone have any further help for me?
I'm at my wits end now.

Many thanks,
wildcardspv.

- Okay, unlock your bl with the semc file if you haven't used that one as last.
- flash 2.1.71 baseband from bb collection
- flash the dkmod v3 for oodie miui prime
- flash oodie miui prime (if you use ota version or pc version is wayne)
- tell me if it works or not and if not, tell me whats standing in about phone. Best would be a screenshot.



Regards,

L
sent from my miui 1.12.9 running doomkernel v06 on unlocked bootloader

Hey,
Thanks for the advice - I'll try now.
Just to clarify, what do you mean by what's standing in about the phone?

Sent from my HTC Desire, with Runnymede 5.0, using Tapatalk

Originally Posted by wildcardspv

Hey,
Thanks for the advice - I'll try now.
Just to clarify, what do you mean by what's standing in about the phone?

Sent from my HTC Desire, with Runnymede 5.0, using Tapatalk

everything what is written in settings/about phone

kernel version, build number, ...

Ok,
Last question for now -
I got dkmod v3 for oodie miui prime but its a zip file and there is no ftf inside, just kernel.sin, loader.sin and a folder called META-INF - do I flash the zip in xrecovery or do Flash these extracted files using flashtool?
If so, how do I flash them? (only ever used ftf files - sorry!)

Originally Posted by wildcardspv

Ok,
Last question for now -
I got dkmod v3 for oodie miui prime but its a zip file and there is no ftf inside, just kernel.sin, loader.sin and a folder called META-INF - do I flash the zip in xrecovery or do Flash these extracted files using flashtool?
If so, how do I flash them? (only ever used ftf files - sorry!)

Hehe, some downloadmanagers do rename ftf to zip, cause they see, it's a zip coded file. Just rename the zip to ftf and flash it through flashtool as normal.



Regards,

L
sent from my miui 1.12.9 running doomkernel v06 on unlocked bootloader

Lol,
I figured that would be the case!
Managed to do the first 3 steps, but after flashing 'dkmod v3 for oodie miui prime' I get the Oodie splash screen for a few seconds, then WLOD, so can't even get to recovery!!!

I've just flashed Doom Kernel v06-1113 Cob06c instead, then got to recovery and flashed Cobrato's MIUI (1.11.11) instead.
First boot found service after about 30-60 seconds, which is slower than it used to be but at least it found it.
Baseband version was recognised under About Phone at this point.

Just shut phone down, left for a minute and started up - found service straight away.....

Just rebooted from the notification bar - On startup, no service is found and baseband is unknown again now
I've attached a screenshot....

Any more suggestions?

Originally Posted by wildcardspv

Lol,
I figured that would be the case!
Managed to do the first 3 steps, but after flashing 'dkmod v3 for oodie miui prime' I get the Oodie splash screen for a few seconds, then WLOD, so can't even get to recovery!!!

I've just flashed Doom Kernel v06-1113 Cob06c instead, then got to recovery and flashed Cobrato's MIUI (1.11.11) instead.
First boot found service after about 30-60 seconds, which is slower than it used to be but at least it found it.
Baseband version was recognised under About Phone at this point.

Just shut phone down, left for a minute and started up - found service straight away.....

Just rebooted from the notification bar - On startup, no service is found and baseband is unknown again now
I've attached a screenshot....

Any more suggestions?

Try it again withthe newest miui. It should work with this kernel too. Do everything as I said before, only use the cob kernel you said above.



Regards,

L
sent from my miui 1.12.9 running doomkernel v06 on unlocked bootloader

Unforunately, just tried it with the same Doomkernel and MIUI.Prime.5_Oodie_1.12.9_fixed.zip, but still no service whatsoever.
I guess it's not going to be fixed!!
Just called Orange and arranged for a replacement to be sent tomorrow - better get it back to stok now!!

Thanks for all your help 9Lukas5, I really appreciate it.