I need to run Mobile Odin Lite to return to stock (bad USB port so this is my only option AFAIK), but it won't run because I have CM loaded (phone came that way) so it gives an error that the partitions aren't correct. Will flashing a non-CM ROM repartition the phone back to a "standard" partition layout so Mobile Odin will then run?
I get wifi but no mobile signal at all with CM 7.1, 9 beta and 9.1. IMEIs match, phone is unlocked and baseband is listed as I9000UGKG3. I'm hoping there's something messed up in software rather than hardware.
Edit: Mods - you can delete this.
Related
So basically I have a phone (not mine) that says Baseband version: unknown, no IMEI when dialing *#06# and doesn't recognize SIM card at all.
Apparently the phone is running stock KK9 2.3.6. AFAIK it has not been rooted or had custom ROM's installed.
The owner said it recently started dropping from network, and usually didn't reconnect at all. This would indicate a broken baseband chip, since now it doesn't even recognize the card?
Any suggestions what to try?
jusutus said:
So basically I have a phone (not mine) that says Baseband version: unknown, no IMEI when dialing *#06# and doesn't recognize SIM card at all.
Apparently the phone is running stock KK9 2.3.6. AFAIK it has not been rooted or had custom ROM's installed.
The owner said it recently started dropping from network, and usually didn't reconnect at all. This would indicate a broken baseband chip, since now it doesn't even recognize the card?
Any suggestions what to try?
Click to expand...
Click to collapse
Try Flashing Stock ROM, Follow link for instructions.
http://forum.xda-developers.com/showthread.php?t=1424997
Thanks for the quick reply. Unfortunately flashing did not help.
EFS corrupted? Any backup done?
No backup done.
you might wanna try this see if it helps... http://forum.xda-developers.com/showthread.php?t=1264021
Apparently there is a backup of the original EFS file - is it possible to just restore it?
do u meant the original files under /efs/? If that's what you meant, try to follow the steps in the previous SGS2 link. Else if it's an external EFS backup image, then there should be no problem restoring it ie. with EFSProBackup. good luck...
Now it's getting even stranger;
the phone works fine when the battery is removed for about half an hour and SIM card installed after that. I left the phone on my desk without the battery for the night, and now it works just fine. But I know that when I reboot it, it loses the baseband once again.
You mentioned you've flashed a stock rom before, which method did you use, pc odin or cwm/mobile odin? did u do a full wipe?
After restoring ur EFS, do a nand backup if you need to then wipe data/dalvik/cache from recovery mode and reflash via pc odin with a stock rom in ur region...
It look like to me you are having hardware problem. Send it back for replace or repairing..
Sent from my GT-N7000 using XDA App
I attempted to restore a backup via CWM and now I get the message E: unknown volume for path" in response to any options in CWM. If I try to reboot normally, I just get the SGS splash screen, which just stays there.
I can't get to the Download screen with the three keys, this just gets me back to CWM. So I feel pretty screwed now. I could order a jig but will it even work in these circumstances?
The sequence of events that led to this was that I followed the instructions here to install Jellybean 4.2. All went well, Jellybean was running very smoothly from this rom. The trouble was that I just couldn't get it to find any mobile networks at all, even when I manually entered the APN and VPN etc. My sim is a giffgaff one, which uses the O2 network, and you do have to add the APN to get the 3g to work - but the phone just wasn't seeing any networks at all. I presume this was because this version of the rom just doesn't recognise UK carriers.
So anyway, I then went into CWM to restore my last backup, which was from over a year ago. This all appeared to work but then it got as far as the SGS splash screen, as described above, and stayed there.
What else can I try?
Well, I did manage to get a Download screen in the end, although Odin running on my Win 8 desktop couldn't see the phone. However, I then put Odin on my netbook running Win XP and that can see it.
So I'm now ready to flash a stock rom to the phone. I've tried following PuggeredUK's guide to installing a stock rom, which I've used successfully in the past, but he does say you need a .pit file. I've tried loading a stock 2.3.4 and 2.3.6 value (which was the last stock firmware I had on the phone) roms from Sammobile but can't find any .pit files in any of the stock roms I've downloaded from there.
So are .pit files actually necessary? I tried sending one file to the phone and Odin said "Failed", so I thought I'd better check about the .pit files before further buggering up my phone.
I had this same problem too when I restored my backup. I got it fixed by just going back to the ROM what I had before I tried to restore. (which was CM10).
Do what I just told this guy in post #7
http://forum.xda-developers.com/showthread.php?p=38194645
Edit: and you lost your network because you flashed from GB to JB, missing out ICS. Nothing to do with the rom and uk carriers. Next time install ICS first.
Sent from my GT-I9000 using Tapatalk 2
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
I have experienced a BIG problem with my D415. I was flashing a CM12 ROM when I noticed that once it turned on, I had no signal. WI-FI does work though. I then thought it was a system defect. I decided to flash another ROM and the same thing happened. So then I decided to format /system and THEN install a different ROM. It did not work. When I flash a fully stock ROM through LG flash tool, I noticed that there was also no signal. I went into the software information section of about phone and I noticed that my Baseband version is unknown. I go into the status tab and I see under everything is unknown.
My SIM Card is inserted properly. I think it is a defect with the EFS partition.
EDIT: I found old backup files of the modem partition and flashed them! Thread Closed
After flashing 610M (csc: TPA) the phone shows "No sim - No service", even tough in sim card management it's there but no carrier is shown.
I tired:
1. IMEIs were there, but I still tried to restore EFS
2. Tried both sim card slots (the second one can at least receive messages, rather weird thing)
3. I tried to flash CP and CSC trough Odin after installation
4. CSC Changers do not work: errors
5. Tried to install similar ROMS: ResurectionRemix, AospExtended and crDroid... same problem over and over
6. Tried flashing latest Oxygen kernel v.5 - no luck
7. Tried installing without GAPPS - no change
8. Tried flashing latest modem from 8.1 official - nothing
Please, help me good people, I'm out of ideas. Currently using Millennium ROM, everything works. No possibility to buy a new phone, but I miss the simplicity and snappiness of AOSP roms. Thank you.
EDIT1:
I found out that even after flashing CSC in Odin. PhoneInfo app shows that there's not CSC or CSC firmware at all. Attached screenshot.
Have you tried checking if your IMEI numbers are blocked in your country?. Could be blacklisted by an operator.
From which state you are probably problem in restricting the device
TheFixerMED said:
Have you tried checking if your IMEI numbers are blocked in your country?. Could be blacklisted by an operator.
Click to expand...
Click to collapse
I use Millennium ROM (which is non-AOSP) right now, and cell service works perfectly. I can try checking of course (will reply later).
eXrump said:
I use Millennium ROM (which is non-AOSP) right now, and cell service works perfectly. I can try checking of course (will reply later).
Click to expand...
Click to collapse
Weird, I have the same model as you and I've flashed a few AOSP roms (Havoc OS, DotOS) and no problems with my signal.
Well, if it works in TW, then it could be the radio firmware in the AOSP roms that is causing the problem with your signal. Im not sure how you can flash the radio firmware once you are in an AOSP rom, but you could try making a backup of the radio related partitions with the Millenium ROM installed and then try to flash the backups once you flash an AOSP rom.
Make a full backup just in case something goes wrong.
TheFixerMED said:
Weird, I have the same model as you and I've flashed a few AOSP roms (Havoc OS, DotOS) and no problems with my signal.
Well, if it works in TW, then it could be the radio firmware in the AOSP roms that is causing the problem with your signal. Im not sure how you can flash the radio firmware once you are in an AOSP rom, but you could try making a backup of the radio related partitions with the Millenium ROM installed and then try to flash the backups once you flash an AOSP rom.
Make a full backup just in case something goes wrong.
Click to expand...
Click to collapse
Thanks for the reply. I did try to restore EFS and Modem partitions after flashing DotOS, but no luck. I looked at the *#*#4636#*#* menu; and there's a signal (decibels change). It's like it doesn't read SIM cards (I've tried another one with different carrier).