[Q]Is there anyone in the forum who can fix the baseband unknown and imei unknown - General Questions and Answers

I have been looking around for quite some time and been trying various methods mentioned by so many experienced members but unfortunately no body has come up with the solution of the baseband unknown and imei unknown problem.
I tried to root my S4 clone mt6575 phone 1 month back using the mtk droid tools. It backed up the stock rom with two folders in the backup. After rooting next day when I rebooted the phone there were no signals and after checking the settings, to my surprise the baseband was unknown and imei was not there too.
I had backed up the user data using the stock recovery option of backup the data, but its only restored through original recovery only. So reflashed the old recovery and restored the userdata everything came back but the setting shows the baseband unknown and imei blank. Still unable to call as radio is not there. Surfed a lot but till date am not able to find the solution.
This is for every senior member who is there in XDA. Can u pls help me out in this. Is there no way to restore the baseband? Because without the baseband, imei cant be written using any tool or for that matter using terminal emulator too.
Is there any method to convert the userdata backup done using stock recovery to the sp tools flashable images. I am ready to upload my backup if someone out there is ready to help.
Thanks

Related

[Q] IPhone clone H2000 Android 2.2

MOD EDIT: No IMEI spoofing or changing.
could you please upload a backup ROM from the working phone? Thanks
Factory reset of H2000
MOD EDIT: No IMEI spoofing or changing.
Hero H2000 backup and restore
MOD EDIT: No IMEI spoofing or changing.
nv_data.bin
I could not locate any file under above name on H2000. They mfr may use a different name like I read in some post nvr_list.nvr or something like that. However I saw a directory named NVD_IMEI containing 3 files. I have no clue what these files are. Normally IMEIs are encrypted and altering IMEI is illegal. I am in the same boat like you but in my case the phone never detected SIM(s) like DOA. I am returning the unit to the vendor as altering anything may void the warranty I have.
To me it looks like an epad Android is loaded and thru some additional patches the unit is made to work as a phone as well. Else I wonder how one will explain your situation that SIMs are not detected after factory reset.
I found that Android Market does not work thru wifi - as I can use only that at present - if the encryption is WPA2-AES but works well with WEP! I could browse well via WPA2.
And different wifi profiles does not seem to be assigned to different wireless networks as my WEP settings like fixed IP, etc except passphrase remained the same on WPA2-AES which uses DHCP and I had to disable fixed IP!. This could be a common problem on all Android sets.
May be some Android expert will help you with flash backup if you could post what exactly the problem that you face when you try to install ROM backup sw.
Iphone clone H2000 Android 2.2
MOD EDIT: No IMEI spoofing or changing.
Good job
H2000 and A3000
Best of luck.
I have seen two versions of A3000 available. One with 2.1 and the other with 2.2 versions of Android. The 2.2 ver phone is resistive screen with dual SIM while the other one is capacitive with single SIM. I have also read that those with A3000 landed with same problem after factory reset.
I have seen a version of A3000 ROM available in some site - sorry I do not remember - but the file name is DZA3000-20110215.zip, but no idea if it is 2.1 or 2.2.
However if no backup is possible how do you plan to restore? I am also too keen to learn having bought H2000. Hope someone comes to the rescue. ASAFIK restore is not supposed to be having any control over IMEI and few other stuff. Hence if *#06# yields "invalid" value I wonder how it will help. Hope you succeed.
Some good guys out there... HELP!
H2000 and A3000
Forgot to add... have you looked at SPMultiPortFlashDownloadProject?
Request moderators to club this with my previous post. Thanks.
Original rom and software for android h2000 phone
ORIGINAL ROM AND SOFTWARE FOR ANDROID H2000 PHONE
Hello.
I have the same problem with my H2000, i made a Factory Restore and my mobile loose my IMEI's.
I have all the software and ROM to the H2000, but i don't know how to do the recover.
H2000 ROM AND SOFTWARE:
www . megaupload . com/?d=08YXYJVR
Please help me because I don't know how to do the H2000 restore.
Regards
@zzappo
Hi,
what SW did you use to make the ROM?
what sw should be used to root this model?
thx
Alex
Hello, i have same problem, i got 5pcs of H2000 2 weeks ago and they all working fine with the factory reset, i sold 4 and keep 1 for me, now i just got 15pcs and they all have this problem, i noticed that they do not have the same Build number
build number without problem : ALPS.10Y.W10.48.MP.V1.06
build number with problem : ALPS.10Y.W10.48.MP.V2.03
i will try to update one of my phone to see if it solve the problem, i have rooted the phone with z4root and it seem to work, i can connect with ADB.
The ROM is not mine. And I don't know what to do with the official software files (ROM, root software...), that is the problem I have!
You already have the most dificil to get (all factory software that I share in megaupload link in my last post).
The files that i shared in link is the Oficial China Factory software to install in new ones H2000, but i don't know how to do that.
Regards
alexinthesky said:
Hi,
what SW did you use to make the ROM?
what sw should be used to root this model?
thx
Alex
Click to expand...
Click to collapse
H2000 coming back to life
Hi guys,
I lost my baseband software after the factory reset with Build version V2.03.
All it said was Baseband "unknown".
After reading forums for 3 days and trying different solutions I got the baseband back. My solution: in ADB type "wipe data" then reboot!
Dual sim is working again and the baseband version is back to normal.
I lost my IMEI numbers, but I hope to be able to correct that later this week.
I know how to make backups of the partitions in the phone (system/recovery/boot.etc). Unfortunately I am still unable to flash the backups into the phone. My phone ROM doesn't contain the "flash_image" command... so I'm stuck on how to flash the images back into the phone.
@vramool: It could be a good idea to try to flash the "ALPS.10Y.W10.48.MP.V1.06" version into the updated phones, just to avoid that someone makes a reset to defaults again.
Can anyone give me a pointer on how to get the img back into the phone with ADB or another software?
Let's work together and I'm sure that we will find a solution soon!
Cheers
Hello, i spend all day looking to backup my ROM from my working device to flash all my other one and I cannot find a way to install NANDROID to backup / restore rom.
from what i have read, the phone need a custom recovery rom to be able to install NANDROID.
I just tried the *ADB WIPE DATA* and it failed for me.. after reboot i still not have baseband version on my phone will try again...
H2000 and A3000
The Baseband version given by hitjock is different from what is shown in a pic in site for APhone - H2000
Take a look at dhgate, aphone-4-4gs-wifi-gps-3-5-capacitive-h2000 specs and pix particularly the second pic.
The flash file posted by zzappo contains SPMultiPortdownload tool. I am not sure if this can be used to load the phone with a given flash. I could point to Android text file for scatter file 1 but what bin file to select for the flash bin file is a big question for me. Besides will it work with the USB cable supplied or need a special cable is not known.
A sub directory named RFDAT contains info about radio control via some ini files.
With NANDROID I did not get any error after installation of Busybox after starting up NANDROID. I downloaded Busybox when NANDROID demands after it has started. It reports root access is OK and Busybox install is OK. I have yet to do a ROM backup.
Hope somebody succeeds..
H2000
Wipe data can also be performed by holding vol + and - buttons together and powering on. You can wipe cache too.
kayyappan said:
With NANDROID I did not get any error after installation of Busybox after starting up NANDROID. I downloaded Busybox when NANDROID demands after it has started. It reports root access is OK and Busybox install is OK. I have yet to do a ROM backup.
Hope somebody succeeds..
Click to expand...
Click to collapse
@kayyapan: How did you get Nandroid and busybox to work on the H2000?
I have tried everything. ROM Manager tries to install clockwork on my phone and this resulted in no more access to the recovery console....
Can you share how to get this to work on H2000?
TIP: I found that if you press the volume up + camera + power on for at least 10 seconds, the phone will go into factory test mode and gives you a menu. I was not able to select any of the menus.....
cheers!
Factory reset of H2000
When you start up in recovery mode use home and menu button in the bottom to move and select. You can use volume + and - to navigate too. First press Home. Navigate with vol + or -, select with Menu. To wipe data/factory reset go to "delete all user data" then press menu.
Since there is no APK for NANDROID I used ROM Manager with Busybox. May be I have mislead you by saying NANDROID worked for me. Sorry. My problem is with creating ext2 partition with ROM Manager. It does not boot to its own recovery. I get to start with same recovery with vol + and - and PUP button.
sdsplit does not work! It says not found.
Even assuming that it is possible to back up the current ROM as fallback how does one restore any other flash to try?
Hitjock was lucky that wipe data worked for him.

[Q] Galaxy Nexus radio/modem failure, baseband version : unknown

Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu
sanu.mathews said:
Hi,
I'm new to this forum.
I got a new Samsung Galaxy Nexus (unlocked GSM-i9250) mobile thruoug Google Store and got it to India.
I did an OTA upgrade from ICE Stock 4.0.4 to stock JB 4.1.1. My next upgrade to 4.1.2 failed, though detected by system failed.
So I used the phone for about 2 days and one day after charging, there was no radio service. WIFI works. Tried another SIM
and operator but in vain.
As all my efforts of factory reset, reboot etc failed, I thought of reflashing the latest images.
So I downloaded the latest images from Google site, unlocked the bootloader, followed different threads
and tried updating to 4.1.2. System now boots to 4.1.2 and WIFI works, but no GSM service still.
In the phone settings
Basebad version : unknown
Network : Unknown
IEMI : unknown
Service state : Out of service/Radio off (keeps toggling every 4-5 sec)
So I tried going back to 4.0.4 and system boots back to 4.0.4, but no GSM service
No idea what is happening. Two of us bought at the same time and got the same to India. For my friend, the OTA updates
to 4.1.1 and 4.1.2 went through fine.
I saw similar issues reported but not able to figure out how finally they solved it.
Any suggestions/help is appreciated.
Thanks in advance
Sanu
Click to expand...
Click to collapse
I had a similar experience with my previous Nexus S device. The phone would start up perfectly fine but it wouldn't catch reception. I think I flashed the wrong radio.img file (there are a lot of Nexus S variants).
I would try the following steps:
- Flash CWM recovery
- Flash a custom ROM (you can use "Mounts and Storage" in CWM recovery to gain temporary access to your internal storage - you will need to do this to copy your ROM file there)
- If you like it, just stick to the custom ROM.
If you insist on going back to the stock ROM, there are threads here that guide you to go back to stock completely. Even if you go back to a previous ICS ROM (specific to your phone), you should start receiving OTA updates normally.
Best of luck!
Thanks for the reply.
I'm almost sure the radio image is fine. I downloaded the images from
Google Nexus developers site for "takju" for Galaxy Nexus "maguro" matching with my phone.
I flashed matching ROM and radio images from Google site. Tried both ICS 4.0.4 & JB 4.1.2
I'll try custom ROMs if nothing works out. I'm going to try this first time, so need to chk the threads first. This is my first Andriod phone and already ran into trouble after just 2 days of use, that too without any manual flashing. Only OTA happened before the issue.
Could the h/w have gone bad ?
In fastboot mode, the radio version is displayed correctly, but not after phone is up and running.
If the h/w has become faulty, I still expect the "Baseband version" in "About Phone" to be correct.
Is this assumption correct ? If it is s/w issue, I'm relived and I can try some custom image. So I'm hoping its only a s/w glitch.
Thanks a lot
you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition
Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
clait said:
you flashed the wrong rom on your phone and corrupted its efs partition. If you have a backup (why should you if you didn't even know that it was that to fail your phone's radio..) you could proceed and restore it. If you don't it's a big mess and you might have to go to a repair service.
Anyway you could still try and flash the original ROM for your phone and see if it fixes the problem. If not there are tools on the web (search the forums) that could try and restore your partition even if you don't have a backup.
If you succeed in restoring your phone don't EVER forget to backup you /efs partition
Click to expand...
Click to collapse
sanu.mathews said:
Thanks.
I tried flashing as the phone radio just stopped working after I charged the phone one day morning.
Let me follow your suggestions. I didn't know about efs partition. may be its messed up
What is puzzling me is, how can the factory images from google be wrong.
Click to expand...
Click to collapse
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?
*#06# shows "OK"
clait said:
It's not the factory images to be wrong but the fact that if the /efs partition is really corrupted the stock images don't contain the info necessary to flash that partition as well.
In fact it may become corrupted after a wrong flashing but a new, correct, flash won't restore it. The only way back is the /efs backup.
What if you type *#06#? Does it show you an IMEI number or what?
Click to expand...
Click to collapse
sanu.mathews said:
*#06# shows "OK"
Click to expand...
Click to collapse
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2
Thanks a lot.
This eliminates so much un-wanted time waste/means no need to try various steps.
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
I'm under the impression that IEMI number etc should be in OTP and that can't get corrupted but efs may have some meta data regarding the same
clait said:
Between the blue line and the OK it should show the sixteen digit long IMEI number. the fact that it isn't shown simplifies the diagnosis. I'm 100% sure you've got your /efs partition corrupted.
Please do a forum search on how to restore it.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
sanu.mathews said:
Can I get efs dump from another Galaxy nexus and flash it on mine after rooting ?
Click to expand...
Click to collapse
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!
If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
clait said:
No can do, the IMEI is a per device unique number.
Check this thread and do some forum search: http://forum.xda-developers.com/showthread.php?t=1689525
You're not the only one that lost the IMEI so chances are likely to you to resolve your issue!
Click to expand...
Click to collapse
sanu.mathews said:
If I copy the IMEI number from the box or my working phone, will it work ?
What I want to know is, is it only coming from EFS or if IMEI is changed will be there be some signature that will fail etc
I have used fastboot but not sure about rooting, so need to read that before trying Rooting
In India, Samsung won't repair my phone as I got it from US.
Another worry is, let IMEI number be wrong and let there be no network, but atleast "Baseband version : Unknown" shdn't come in the phone, correct ? Coud there be any issue with radio image partition itself ?
Click to expand...
Click to collapse
Mate - I too am from India, and I too got the exact same problem, and I too tried all you did - all this about a month back. I have reconciled myself to the fact that its a hardware issue. Since samsung centers in India won't do any repairs, I'm afraid we're both stuck with really expensive music players.
My sympathies.
Fixed by sending in for warranty
Just an update...I was having all of these symptoms...unknown IMEI, Baseband, etc...basically gave me an expensive media player for a few months while waiting for a fix on XDA. After no update I decided to call up Samsung and after talking to 3 different technicians, I was able to send it in. Just a note for anyone about to do the same, they will try very hard to blame it on the carrier/SIM card, so save yourself some trouble and just say you already went to the physical store of your carrier (calling isn't enough)and they couldn't get it working. Once you get past that, they will email you a printable 2-day UPS shipping label so you can ship it to them for free. It took 2 weeks from the time I called to having a working phone back in my hands.
This was their fix:
Problem found:
NO PCS SERVICE
Solution:
REPLACED PBA
After a quick search I found that the PBA is the motherboard, so it's definitely a hardware issue. Hope you guys are still under warranty because I've heard this is ~$200 to fix otherwise.
Good luck.

[Q] Potentially Lost IMEI / Brick

My phone will not recognize Verizon as its carrier or connect to a cellular network in any way. Settings > About Phone > Status > IMEI reads "0." I have, in some capacity, "lost" my IMEI.
I understand their are a lot of threads on this topic, however, I (unfortunately and ignorantly) have done a number of things after the actual losing of my IMEI and I am not sure the current state of my device or if a backup of my IMEI exists anywhere.
First my story. I successfully managed to get one of the early nightly builds of CM10.2 running on my phone and all was well. After updating to a more recent nightly via the CM updater, I noticed I had lost cell service in all capacity. Confused, I decided to not take any chances and revert to a CWM full backup I had made while still running CM10.1 stable. Still nothing. At this point, I thought that something was wrong with my firmware, and so I flashed a zip containing the latest Verizon firmware successfully (same that was installed previously). Nothing.
Not really understanding that one could lose their IMEI or the potentially signs of such loss, I decided to go all the way to stock via odin. The image did unlock the boot loader and grant SU, but did not wipe user data. Thinking it would help, I wiped data/factory reset within the stock recovery and then reflashed the image. Of course, still nothing. This is my current situation.
So my question is this: do I have any hope of recovering or "injecting" my IMEI? From my understanding, the Samsung mechanism designed to backup the IMEI in these such instances is broken. In fact, it probably "restored" it to a bogus null value. I think this means that I now have no IMEI information on my device. If so, does this mean I can manually inject it somehow? I have tried methods that purport to build the files on a pc and then move them to the device but I cannot access any of the Qualcom menu's that necessarily put the phone in a certain USB mode via the phone dialer. I get "no mobile network available."
Also: I still have my CM10.1 full CWM backup from before I lost my IMEI. If this backup contains the information needed to restore my IMEI, is their any way I can retrieve it? I think this is my best shot, but I'm not sure.
I would like to know if my new phone is a paperweight, since I am still within the 14 day return period. If I have indeed bricked my phone, there is a slim change that I can reset everything back to stock and play dumb with Verizon to get an exchange.
I apologize for the ambiguous vocabulary and/or description. I have a good working knowledge of most of the stuff on xda, but a lot of the language used in forums regarding IMEI restoration is foreign to me.
Thanks in advance for any help!
You have to Odin a stock ics image, or restore a backup if you have it, and dial *2767*3855#.
This should fix your imei and eri status by reprovisioning your phone.
Also as soon as you reroot and get up and running again, make an imei backup so you won't have to go back to stock if you have this issue again.
You could manually inject it, but a moderator has to grant you permission to use the thread. However, manually injecting it with qpst will leave your phone in roaming (not actually roaming, but the status icon won't go away) because it won't fix your eri number.
Use this option first, if it doesn't work you can try injecting it.
Sent from my SCH-I535 using Tapatalk 2
I used qpst to restore my imei and then used this method to get back without using odin, if you haven't already done so. I also think you can get your imei and eri back without using qpst with this method. I had already restored my imei and eri wasn't saying 5 like it should.
http://forum.xda-developers.com/showpost.php?p=44871571&postcount=3
Edit : I forgot, once you have your imei and eri restored and backed up. Don't forget to flash your modem back up to the version you want.

[Completed] [Q] Baseband/IMEI missing after rom manager restore

I have a Samsung Galaxy S3 (I-747) Using Rom Manager for first time I backed up and immediately checked how the restore would work. Lots of stop errors after restore so went back to boot menu for recovery and that worked. First I noticed sim card didn't work and no IMEI number ATT told me. There is no baseband either or any kind of IMEI backed up. Found a factory restore from one of these XDA forums. Process worked but no baseband and cant use sim still. Not bricked yet but want to learn more because i want custom rom knowledge.
Hi,
Here is a similar thread you can read through and hopefully it helps... You could post there also,
http://forum.xda-developers.com/galaxy-s3-att/help/imei-null-null-baseband-unknown-t2951225
Good luck!

Lost imei after factory reset and root

Hi guys,
I have a slight problem here, I was using my rooted with magisk and running lineageos17. Unfortunately, bluetooth wasnt working so I reverted back to stock, which fixed the bluetooth problem. I tried rooting the thing then with this method:
https://www.xda-developers.com/install-android-oreo-samsung-galaxy-s7-exynos/
Unfortunately though, this killed my imei. I tried restoring my efs partition with twrp; even tried reflashing the stock firmware, all to no avail, my imei is gone.
Is there any way I can restore it or have I turned my phone into a fancy paperweight now?
Would be cool if anyone could offer me some help,
best wishes,
derelektrischemoench
// edit: I managed to get twrp installed and was able to restore my twrp- backup which i had made before this whole endeavour and voila: the device is back online, has an imei and is able to connect to a network. Hell yea. Thread can be closed, I guess.

Categories

Resources