[Issue] Baseband unknown - Nexus S Q&A, Help & Troubleshooting

Hi folks,
I flashed the radio update from 2.3.3 on my Nexus 2.3.2 which was running CM7#6. http://forum.xda-developers.com/showthread.php?t=971272
Phone came back as saying baseband unknown. I tried restore, but it didn't work. I then did a factory wipe and installed CM7#7, still baseband comes up as unknown.
Next step was to power off, take out sim, turn on, and once fully booted, turn off, and place the sim card back. Still no go.
Any help would be appreciated!
Thanks.

My original baseband said I9020XXJK8, if it is of any use.

Issue resolved by following http://forum.xda-developers.com/showthread.php?t=971239

Related

[Q] My radio wont turn on after flashing

When I flashed 2.3.4 from insert coin 2.3 it killed my radio on my tmobile sensation. I restored my backup and the radio still wasn't working, then I reflashed the radio and the radio still isn't working and it says it is turned off. When my phone turns on airplane mode is on and I turn it off but nothing happens, I also dial into test mode and try turning radio on from there but no luck. I also flashed the stock ru.exe. What else should I try?
When I take out my sim card it turns the radio on. My sim card must have died from flashing to the new rom.

[Q] Emergency calls only problem

Suddenly my nexus shows this message: Emergency calls only.
and I can't call anybody and can't receive calls.
After the problem occurred I tried to reinstall the rom, tried to change rom, to change radio, kernel.
Tried to perform factory reset, tried to format the whole phone, including sd.
Tried to restore an old backup.
Nothing seems to be working...
I read somewhere that it might be something wrong with the efs folder or IMEI...
I really don't know how to fix this problem.
Someone can help me please?
Check your IMEI bellow battery and compare it with IMEI info in OS. If those two are different then it could be IMEI problem...
I have that problem, but fortunately my Nexus is still kicking...
this is happening to me too
i'm with mobilicity... left the city and the phone connected to Rogers roaming..
now i'm back, phone doesn't connect back to mobilicity... just gives me "emergency calls only"
tried flashing roms, radios, kernels, pull battery, checked imei... i'm stumped.
i swear the only thing i haven't tried is restoring to stock completely
flashed back to stock OTA
http://forum.xda-developers.com/showthread.php?t=1063664
now i can connect to the damn mobilicity network...

Wifi Stuck on "wifi turning on"

Hello guys,
I flashed purity rom, used wifi to download some apps. After a while, i turned wifi off then on, and it was stuck at "turning WiFi on"... cant turn back off nor on. Reverted to stock rom... still same issue... what can i do now? is it a hardware problem ? or is there a fix or something... help please !!!
karlada said:
Hello guys,
I flashed purity rom, used wifi to download some apps. After a while, i turned wifi off then on, and it was stuck at "turning WiFi on"... cant turn back off nor on. Reverted to stock rom... still same issue... what can i do now? is it a hardware problem ? or is there a fix or something... help please !!!
Click to expand...
Click to collapse
Any problem with WiFi is a kernel related issue...the WiFi files are in the kernel...so I would flash back to stock cause it seems like a file got screwed up somewhere
karlada said:
Hello guys,
I flashed purity rom, used wifi to download some apps. After a while, i turned wifi off then on, and it was stuck at "turning WiFi on"... cant turn back off nor on. Reverted to stock rom... still same issue... what can i do now? is it a hardware problem ? or is there a fix or something... help please !!!
Click to expand...
Click to collapse
Hey all,
After more than a week with NO WIFI, i have finally figured it out.
Here are the detailed.
ISSUE: After OTA update of 4.4.3 on new nexus 5, the phone was rebooted automatically and after reboot WIFI button was greyed out. It only showed "TURNING ON".
FAILED SOLUTION ATTEMPTS: Following step DID NOT HELP
1. Factory reset
2. Battery drain and recharge after full drain
3. Power off for few hours and restart
4. Whacking the set on palm (yes, whacking, it was a recommended solution on a thread)
5. Opened the handset and checked all the hardware link, every thing was fine
6. Bootloader unlock, recovery installation (TWRP), downgrade to 4.4.2 (downloaded from google's web page)
7. Downgrade to 4.4
8. OTA update from down graded firmware
9. Sideloading the 4.4.3 update on firmware 4.4.2
10. Rooting, and installation of custom ROM (slimKat, Cynaogen mod)
11. Installation of custom kernel (linaro)
12. Flashing of 4.4.2 & 4.4 Radio/Boot images on stock rom of 4.4.3
13. Clean install of 4.4.3 (removing everything from phone except recovery)
14. *#*#4636#*#*, goto wifi and restart.
15. *#*#4636#*#*, wifi state shown "UN-INITIALIZED"
Actual Solution that worked
***** Install Paranoid Android ROM on rooted Nexus 5. The issue is with Kernel , which control the HW/OS communication. Apparently Kernel of this ROM removed the issue (but installation of SlimKat/CyanogenMod/Custom Kernel).
I then restored the backup of stock 4.4.3 from recovery and did a factory reset. Wifi & every thing else works fine now *****
monty6630 said:
Hey all,
After more than a week with NO WIFI, i have finally figured it out.
Here are the detailed.
ISSUE: After OTA update of 4.4.3 on new nexus 5, the phone was rebooted automatically and after reboot WIFI button was greyed out. It only showed "TURNING ON".
FAILED SOLUTION ATTEMPTS: Following step DID NOT HELP
1. Factory reset
2. Battery drain and recharge after full drain
3. Power off for few hours and restart
4. Whacking the set on palm (yes, whacking, it was a recommended solution on a thread)
5. Opened the handset and checked all the hardware link, every thing was fine
6. Bootloader unlock, recovery installation (TWRP), downgrade to 4.4.2 (downloaded from google's web page)
7. Downgrade to 4.4
8. OTA update from down graded firmware
9. Sideloading the 4.4.3 update on firmware 4.4.2
10. Rooting, and installation of custom ROM (slimKat, Cynaogen mod)
11. Installation of custom kernel (linaro)
12. Flashing of 4.4.2 & 4.4 Radio/Boot images on stock rom of 4.4.3
13. Clean install of 4.4.3 (removing everything from phone except recovery)
14. *#*#4636#*#*, goto wifi and restart.
15. *#*#4636#*#*, wifi state shown "UN-INITIALIZED"
Actual Solution that worked
***** Install Paranoid Android ROM on rooted Nexus 5. The issue is with Kernel , which control the HW/OS communication. Apparently Kernel of this ROM removed the issue (but installation of SlimKat/CyanogenMod/Custom Kernel).
I then restored the backup of stock 4.4.3 from recovery and did a factory reset. Wifi & every thing else works fine now *****
Click to expand...
Click to collapse
Tried all of those things, including the paranoid android part. No dice... Any other suggestions?
Bm13084 said:
Tried all of those things, including the paranoid android part. No dice... Any other suggestions?
Click to expand...
Click to collapse
I've had this issue since yesterday on stock 4.4.4. A search of the Google support forums or Twitter will show posts from people having the same issue, all from the last few days. I've done a wipe and flashed the factory image and neither fixed it.

[Q] My phone doesn't reboot after an update, i have to manually put it on..

Hello fellow xda-ers,
I have a OnePlus One, but i cannot seem to update the phone.
What is the exact problem?
- there is a system update ready, so i download the update and it asks me to install and then it tries to reboot
- the phone shuts down and doesn't reboot, i have to manually turn the phone off which makes the update sequence stop.
- the phone tells me again theres a update, but it doesnt reboot after it shuts down.
- even just giving the phone the command to reboot, just shuts the phone off and the phone doesn't reboot.
What did i try?
- via oneplus toolkit (mac) i flashed it to stock default, but still the problem persists.
- i flashed a 5.1.1. firmware straight from cyanogen mod, but still the problem persists.
- i flashed a custom recovery (while unchecking the update cm recovery), but the problem still persists.
I don't know what to do... Anybody have advice? It would be much appreciated.
I am pretty aware of what to do and not to do, i have been flashing phones since the iPhone 3gs. But this is just odd.
I was having similar problem. Except mine was booting into the bootloader. From there I tried to manually install the update. It kept failing so I gave up. Then about a week later (today) I let it try to install and it seemed to be working, except when it finally booted back up, it had completely wiped my phone!!! Now I'm midway though reinstalling all my apps and it gives me the "There's an update available for you phone". So apparently it didn't even update in that process.
I've got the exact same problem here.

Samsung Galaxy S6 G920F No SIM but it shows signal and sometimes reboot by itself.

Hi all,
A person i know have Samsung Galaxy S6 G920F and just in a sudden his phone got turn off and when he try to open it it freeze for a second and restart.
He gave it to a friend and that friend install Android 7 ROM on it but it still freeze and restart.
Then, i download the ROM and flashed it. It is on for 2 or 3 days and no issue happened. But i tried to check for updates and it froze and restarted and when it reopened it continued to check for update and tells me that all updates are installed.
The weird thing that it has NO SIM but it shows signal sometimes full signal.
why it do these things? are these errors known or rare problems?
Stock Samsung Rom? If not make sure you try that.
And that sounds like either bad battery or liquid damage inside phone.
Have you tried factory reset in recovery mode?
No sim and full signal? Completely normal if you have no sim card in there. Not normal if you have a sim card in there. If you can see baseband version and IMEI in settings then your sim reader is damaged (pins).

Categories

Resources