[Q] SIM state - Galaxy Tab Q&A, Help & Troubleshooting

Anyone knows how you can read the SIM state?
Android (the Kernel?) reports the SIM is not inserted. But if I remove the SIM, a window appears stating the TAB needs to reboot due to SIM eject. Same happens if I insert the SIM. Once rebooted, it still claims there's no SIM in.
I tried to read the ICCID or any of the memory field to no avail. Is there something I could do to talk to the hardware directly, bypassing possibly the Kernel, removing the software corruption element? It's very frustrating, it's as if my GT is aware the SIM is there, but doesn't "want" to "talk" to it.
Help?

Glad that you opened a new question thread instead if the overcome thread.
I was going to ask you again.
When I asked you if the sim problem occurs after restock or after overcome kernel, you said after the kernel.
If that is so, that means you can use your tab fully in gb stock safe v5.
Sent from my GT-P1000 using XDA

priyana said:
Glad that you opened a new question thread instead if the overcome thread.
I was going to ask you again.
When I asked you if the sim problem occurs after restock or after overcome kernel, you said after the kernel.
If that is so, that means you can use your tab fully in gb stock safe v5.
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
No, now it happens all the time. I didn't notice when it originally occured. I tried to enable the phone part by using a pack found here called EUROPACK. I flashed .PIT, PDA modem and CSC.
Also, I tried roto's script to unlock. I had to run the CP commands manually as the CP command was not in, had to run them through busybox. Otherwise I left the EFS alone.
In another post, rotohammer suggested an empty EFS to fix another user's problem, which is the same as mine. I tried through ODIN and using his PDA file, all to no avail.
An finally, I fail at going back to completly stock. I used the files provided but Kies still claims that my unit cannot be updated using Kies, it sees something different. wonder if that "thing" is causing the SIM issue.
I'm out of ideas as the hardware failure isn't likely nor apparent.

Related

[q] no base band after flashing

Hello every body,
I have a little big problem, i flashed my samsung galaxy S with I900XWJM5 from samsung firmwares.com
And after flashing my phone loose his BASE BAND so i can not call anymore, i inserted my simcard but the phone don't detect it.
I checked phone information and discovered that BASE BAND VERSION was " unknown " !!!
I tried to flash back to original firmware the I9000JF3 but same thing. I tried to flash only the MODEM part but still samething.
I called samsung technical and they told me to check in ODIN the case " Re partition " and flash again. But in Odin when i cheked the case " repartion" the flash hangs on " don't plug off target "
I tried to flash with a new computer under win xp, but same thing i can not do " repartion " with Odin
My mobile is not simlocked when i bought it, is my phone network dead ? PLEASE CAN SOMEONE HELP ME ?
Did you try updating the firmware through Kites? Also, try flashing it again with ODIN, after selecting all the 3 files - modem, code and csc.
You need to try with "Re-partition." until it works.
Also make sure you are using a 512.pit file.
and do not forget to take ur battery off and put it back before you try to run ODIN...
vinivius said:
and do not forget to take ur battery off and put it back before you try to run ODIN...
Click to expand...
Click to collapse
You would have to do that to remove the SIM anyway.
Make sure you remove SIM and SDCARD.
sturmeh said:
You would have to do that to remove the SIM anyway.
Make sure you remove SIM and SDCARD.
Click to expand...
Click to collapse
Unrelated, but what is the reason for needing to remove the simcard (I have never done so)
Thank you every body for your help
befor this problem i use to flash with Odin 3 firmwares and had no problem.
But now i can not tick the case " Re partition " to solve the problem. I called samsung technical service and they told me to do a full " Re partition " and flash again.
The problem now is that i can't do repartition, because the flash hangs at " don't take off target" and nothing happen.
may be the phone had serious problem with memory, i had to sent back to samsung after service .
Thank you all
I have the same problem. I have flashed many times with different firmware versions, but it didn't work. My phone couldn't attach network, I couldn't see neither IMEI nor Baseband version.
try just flashing the modem file until it works
the modem file is what controls the radios
andrewluecke said:
Unrelated, but what is the reason for needing to remove the simcard (I have never done so)
Click to expand...
Click to collapse
During the flash it may take the SIM as part of the hardware and ignore it once it's done flashing.
You'll have to reflash without the SIM to get it to work again.
It's not a real issue, but if you are failing with Odin I highly recommend sticking to those recommendations.
Also remove all usb devices other then phone, mouse and keyboard. Had heaps of flashing problems due to external hhds sucking power while flashing. Now works 90% of time for me. Next thing you do is find a xp box and try again.
Sent from my Apple Newton 2100
sturmeh said:
During the flash it may take the SIM as part of the hardware and ignore it once it's done flashing.
You'll have to reflash without the SIM to get it to work again.
It's not a real issue, but if you are failing with Odin I highly recommend sticking to those recommendations.
Click to expand...
Click to collapse
I've got the same problem. I am able to get JM8/JM4 (Kernel 2.6.29 [email protected] #2), and then whenever I try to go Froyo (JPM or JP6) I always end up with baseband unknown I did remove the sdcard and sim card - still the same thing, is there any solution to that thing ?

[Q] Sim Card Locked to I9000XXJPC

I9000XXJPC has become a major headache, and now the sim card won't work with other firmware. The first time I updated via Kies, everything was fine for a little while. After realising it's buggy, I went back to JG4 and renamed nv_data.bin etc..
The second time I installed JPC for a bit of a play around was via Odin, and that went fine, but still buggy firmare. This time when I went back to JG4, the sim card doesn't work properly. It asks for the PIN, sits on "Unlocking Sim Card" for a bit, then asks for the PIN again, saying it's incorrect. After entering the correct pin another 2 or 3 times, TWlauncher appears, but there is no service.
Odin didn't make a backup of nv_data.bin, but I had made a copy myself just in case. Restoring this does allow Kies to see the proper product code, but makes no difference with the sim card.
Is there anything at all I can try? It seems as though flashing JPC via Odin has altered more than just the /efs directory, but I don't know what. It might also be possible that anyone else on JPC will discover the same if they go back to 2.1, but I hope it hasn't done too much damage. I tried another sim card from another network and it's the exact same situation (works only with JPC).
To anyone who hasn't tried I9000XXJPC, don't! It's not worth the hassle.
Basically, sim cards now only works with JPC..what can I do? I have 3-button recovery, so can try just about anything if need be.
http://forum.xda-developers.com/showpost.php?p=7940762&postcount=1
Thanks, I read and tried so much but somehow missed that. At least it's a known problem thanks.
Edit: I thought it had something to do with the dates of the files. hmmm now I'm stuck.

[Q] Flashing JH2 problems

Alright, I'm pretty uniformed when it comes to these things, but as it stands I need some help. I have a Bell Galaxy S (GT-I9000M) that I unlocked to use on Telus and then rooted a month later in an attempt to trouble shoot a reception issue (don't ask). Trouble shooting failed and now I'm trying to get the circumvent the warranty issues by trying to re-flash back to the stock bell ROM, which is from what I can tell the I9000UGJH2. I downloaded it from (samfirmware). I'm trying to use Odin and am having some troubles. When I extract the file there is only a single .tar file inside (I9000UGJH2-PDA-Kernel-Bootloader-CL490514-Low). As such I am unclear as to what to enter for the PDA/PHONE/CSC fields. I assume this file is the PDA, and inside is the modem file if I look. Do I need to extract this to use in the modem field? I'm so confused.
Also, a couple of things. Ive had 'success' flashing using just the the one file in the PDA field, as well as that plus the modem file found inside extracted and selected in the MODEM field. HOWEVER, in both attempts though it seem to boot into the OS fine, neither recognize my SIM card. Clearly this is some sort of failure. Any suggestions?
Oh, and yes, I can get into download mode. That's the only reason I'm fiddling.
since the phone boots into the OS
and you have the 3 buttons working
you can try flashing it back to stock (JH2) using KIES
and see if you can get it to recognize your Telus SIM card with that.
before you go ahead, do you have friends or family with Fido or Rogers SIM you can try?
just to make sure it's not a Telus SIM card problem
I'm pretty sure I did flash it to the stock JH2. When I plug into kies and search for firmware updates it says there are none. Am I doing something wrong?
maybe if I flash the update prior to JH2? Then it will see it need an update and go to town?
on the registry just change all the JH2 references to JG9
then it will offer you JH2 for "upgrade"
or you can use this
http://forum.xda-developers.com/showthread.php?t=799810&highlight=i9000m
done and done. used the regedit. prompted to update. did so. loads the galaxy s screen, then goes to black. i kind of want to kill myself ;(
try booting into recovery mode and wipe data + wipe cache
see if it can boot after that
Sent from my GT-I9000M using XDA App

RESOLVED [Q] SIM not detected?? (ATT + polish GNOTE)

I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
I had a similar SIM card issue when I tried to activate the 1700MHz band in Service mode (for fun). Wipes and stuff didn't solve anything. The way to revert it for me was flashing a full stock Samsung firmware in Odin.
Can you provide more details on how you did this?
Where does one get a full stock sammy note firmware?
Are there some good instructions on this?
I have flashed my SGT via odin several times. Same odin? Same process?
In the development section you will find some versions.
The key for me was flashing a new Modem (Radio/base band) image via Odin I think. I changed Kernels and ROM's but only flashing a ROM including the Modem got rid of my SIM issue. Not sure because in the end I flashed a full N7000OXAKJ1 firmware in Odin from here:
http://forum.xda-developers.com/showthread.php?t=1310513
It did the trick, though the tread is dead. I think any ROM including Modem might help, I currently running the 2.3.6 N7000ZSKK1 firmware and it is great, also included a Modem.
http://forum.xda-developers.com/showthread.php?t=1342797
fwelland said:
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
Click to expand...
Click to collapse
when this happened to me, also due to turning on 1700, I was able to reset my phone by doing a factory reset. Unless your modem.bin is corrupted, you should not have flash a new rom.
- frank.
ugh....
you mean factory reset via Settings->Privacy->Factory Reset?
Tried that... No affect. Is there another way to do this?
Was hoping to fix w/o the flash. NOTE: I did go into that service menu with the 3G Freq are listed. I was curious when I saw the post. But I never changed anything. Just saw the screen and thought "neato". I wonder if there is another service screen that has an option for 'unfuck'???
Still searching for answers, before trying the ROM route...
fwelland said:
ugh....
you mean factory reset via Settings->Privacy->Factory Reset?
Tried that... No affect. Is there another way to do this?
Was hoping to fix w/o the flash. NOTE: I did go into that service menu with the 3G Freq are listed. I was curious when I saw the post. But I never changed anything. Just saw the screen and thought "neato". I wonder if there is another service screen that has an option for 'unfuck'???
Still searching for answers, before trying the ROM route...
Click to expand...
Click to collapse
Here is Chodthewacko posted about it:
http://forum.xda-developers.com/showthread.php?t=1335920
Factory reset and toggle band settings seems to have worked for him. I got frustrated and Odin flashed everything, that worked for me.
whoa....
when I try that procedure (* # * # 1 9 7 3 2 8 6 4 0 # * # * ) I get a pretty empty screen...can't do much of anything...just some useless buttons on the bottom of screen when I select the menu button...
I think I recall seeing another number for doing a similar thing...
fwelland said:
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
Click to expand...
Click to collapse
OMG I have the EXACT same issue as you, and I got mine from NEGRI also! It was working perfectly until last night --- all of a sudden I got that circle and I've been trying to fix it since then! Please keep me posted if you find a solution, I was going to try and contact Negri tomorrow for an RMA.
still nothing.
I did a root. No changes...
I did a rom flash of kk1 ... no changes....
I was trying to reflash the modem with KJ6 modem....but have a signature failed problem...
now what???
I solved my issue by a combo of those steps.
I did full flash in Odin of jk1. When I rebooted that didn't solve things so I wanted to flash the other recommendation, kk the Chinese rom.
Upon entering recovery I noticed I lost 2e and was on 3e. So I had to download chainfire's rooted jk1 kernel and do that zerg rush to get root. It was while I was doing that that suddenly my similar got recognized. By the time it finished installing the rooter kernel I had full reception again. I flashed kk just for good measure and its been smooth since. Hope it works for you too and I'd love to know what the heck broke it in the first place??
Sent from my GT-N7000 using XDA App
hi fwelland, it's hk1981...so you tried the rom flash and it didn't work?
Hi hk1981,
No the KK1 rom flashed fine. By all accounts it works well, except that pesky phone part. This KK1 rom is really 'clean' and very little bloat-ware and it installs a vanilla boot animation (not a carrier one). All that is nice, but didn't help my problem
I did notice a peculiar thing: while in recovery (android recovery, not cwm) I get some warning about "CSC something or other, fixing".
I have a short list of things to try before I have exhausted my DIY options -- the post just above looks promising.
I think the answer is out there. We just need to keep looking and keep attention on this thread and others like it. This place and others like it are a huge help and I'd like to solve it and then give back a good set of instructions.
FWIW: I wonder if there was some voodoo in the polish rom that caused some issues in the modem when a different than expected sim was installed? Or if one of those funky polish apps that updated it self before I could turn off auto-updates has something to do with it (doubt this -- I don't think apps can do stuff unless rooted...)...
Still searching....I got this other pesky problem to deal with now: w-o-r-k
fwelland said:
Hi hk1981,
No the KK1 rom flashed fine. By all accounts it works well, except that pesky phone part. This KK1 rom is really 'clean' and very little bloat-ware and it installs a vanilla boot animation (not a carrier one). All that is nice, but didn't help my problem
I did notice a peculiar thing: while in recovery (android recovery, not cwm) I get some warning about "CSC something or other, fixing".
I have a short list of things to try before I have exhausted my DIY options -- the post just above looks promising.
I think the answer is out there. We just need to keep looking and keep attention on this thread and others like it. This place and others like it are a huge help and I'd like to solve it and then give back a good set of instructions.
FWIW: I wonder if there was some voodoo in the polish rom that caused some issues in the modem when a different than expected sim was installed? Or if one of those funky polish apps that updated it self before I could turn off auto-updates has something to do with it (doubt this -- I don't think apps can do stuff unless rooted...)...
Still searching....I got this other pesky problem to deal with now: w-o-r-k
Click to expand...
Click to collapse
I had that problem too, it doesn't detect that CSC and then goes ahead and applies something. Check to see if you are in 3e recovery, I think you are after having flashed vanilla JK1.
Re-flash Chainfire's rooted kernal for your appropriate version and then go back into recovery and it should be 3e and you can flash thru CWM then.
Also note; each time I flashed, I also wiped data/cache/davlik just to be sure.
yes it does say:
Code:
Android system recover (3e).
So I will need to try the methods you (crippenx) suggested.
FWIW, the CSC message that I get when I first enter recovery is:
Code:
# MANUAL MODE #
--Updating application...
Successfully update application.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'TGY'
Sucessfully applied multi-CSC.
I have no idea what this means. It does it every time I enter recovery.
FWIW, I never flashed this gnote with ODIN (I have used ODIN on my SGT several times). I got to KK1 by first rooting via http://forum.xda-developers.com/showthread.php?t=1329360 (using 'forget the above steps') and then using the CWM 'kk1-wipe.zip' from here http://forum.xda-developers.com/showthread.php?t=1342797 -- I didn't use ODIN to get to kk1.
I see on the Root/Unroot thread, there is a KK1 kernel option for 'simple'. I think I will try that with rooted already script.
But I am open to any/all suggestions...
Code:
Baseband
N7000XXKJ6
Kernel
2.6.35.7-N7000ZSKK1-CL706440
[email protected] #2
Build Number
GINGERBREAD.ZSKK1
fwelland said:
whoa....
when I try that procedure (* # * # 1 9 7 3 2 8 6 4 0 # * # * ) I get a pretty empty screen...can't do much of anything...just some useless buttons on the bottom of screen when I select the menu button...
I think I recall seeing another number for doing a similar thing...
Click to expand...
Click to collapse
My rough guess is that the phone has a list of 'valid service menu options', and it cross references it with what is on the SIM card.
Once the phone decides it's not going to read your sim card, the service menu is blank. This is a real headache.
That's why once I set the 1700+2100 combo, and my phone boycotted my sim, I wasn't able to set it back.
That's really dumb, imho, to have a one way toggle like that. I'm fine for settings to enable/disable other settings, but for a setting to disable itself? ugh.
I would really like to know what's going on. I was planning on switching to AT&T before my next trip (which is soon) but I can't risk my phone glitching out like that during the trip.
Actually, the ROM is on my SD card so I guess it wouldn't be THAT horrible, but it's certainly not something I want to do. Perhaps we just need a way to flash back the modem.bin, assuming it's corrupted.
- Frank
Sorry typo on my part. You are in 3e recovery because of that base flash, now you need 2e recovery which you can get via chainfire's rooted kernel. His installation procedure runs a batch file that uses that zerg rush exploit which I gather is partially from gingerbreak. It was during this procedure that my baseband suddenly came back, my sim card finally detected.
Once that was done, I entered 2e cwm with volume up,power,middle button and did erase of data,cache,davlik and then flashed kk rom via zip file.
Sent from my GT-N7000 using XDA App
fwelland said:
yes it does say:
Code:
Android system recover (3e).
So I will need to try the methods you (crippenx) suggested.
FWIW, the CSC message that I get when I first enter recovery is:
Code:
# MANUAL MODE #
--Updating application...
Successfully update application.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'TGY'
Sucessfully applied multi-CSC.
I have no idea what this means. It does it every time I enter recovery.
FWIW, I never flashed this gnote with ODIN (I have used ODIN on my SGT several times). I got to KK1 by first rooting via http://forum.xda-developers.com/showthread.php?t=1329360 (using 'forget the above steps') and then using the CWM 'kk1-wipe.zip' from here http://forum.xda-developers.com/showthread.php?t=1342797 -- I didn't use ODIN to get to kk1.
I see on the Root/Unroot thread, there is a KK1 kernel option for 'simple'. I think I will try that with rooted already script.
But I am open to any/all suggestions...
Code:
Baseband
N7000XXKJ6
Kernel
2.6.35.7-N7000ZSKK1-CL706440
[email protected] #2
Build Number
GINGERBREAD.ZSKK1
Click to expand...
Click to collapse
For me flashing all partitions via Odin worked (no pit file or repartition). Tried all sort of stuff from recovery first with no result.
I don't know what partition flash from Odin did the trick, but you could try Odin flashing a Modem separately and check if that works. If not try the rest?
Finally got back to this.
After much fusing I finally got KK1 and cwm working. It was odd, I had to re-run the whole root process again.
At that point I could apply the KJ6 modem w/o any problems (via cwm)
no dice!
Still dead!
Not sure where to go next???
Can some one provide a few details about flashing a modem,rom and/or kernel via ODIN? Perhaps that method will work....
fwelland said:
Finally got back to this.
After much fusing I finally got KK1 and cwm working. It was odd, I had to re-run the whole root process again.
At that point I could apply the KJ6 modem w/o any problems (via cwm)
no dice!
Still dead!
Not sure where to go next???
Can some one provide a few details about flashing a modem,rom and/or kernel via ODIN? Perhaps that method will work....
Click to expand...
Click to collapse
Oh when you flashed jk1 I assumed you did it the old way via Odin and the multiple files. That's how I did it and you're right, that may be what fixed it as when I used to brick my sgs and sgs2, it was always a full Odin flash of stock that brought it back from the dead
To flash in Odin put your phone in download mode. Fire up Odin. In csc point to csc file. In phone section point to modem and for PDA you point to the code file. Don't put anything for pit or bootloader and unchecked the repartition toggle.
Connect your phone and wait for Odin to detect it and show yellow in the status window. Press start and you're good to go. Hope this does it!
Sent from my GT-N7000 using XDA App

HTC Vivid Radio/Baseband issue

Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Cor-master said:
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes I have tried a different sim card. I don't believe thats the issue though being that it worked with the same sim after I let the phone sit overnight. From reading about others experience, it doesn't seem that the sim is the issue but more the baseband version and imei information missing.
centro7710 said:
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Click to expand...
Click to collapse
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
Click to expand...
Click to collapse
I found the download link, but the website says they're updating their drives, so who knows how much longer that will take.
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
centro7710 said:
I tried finding a download link for the AIO kit on the link provided, but I must be blind?
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
Click to expand...
Click to collapse
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
centro7710 said:
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
Click to expand...
Click to collapse
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
centro7710 said:
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
Click to expand...
Click to collapse
And I have a question, if the radio/baseband files are included in the RUU flash, what is happening as to why it is not being reflashed, or if it is being reflashed, why it is disabling the mobile network and providing an Unknown version to Baseband and clearing the IMEI number?
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Here's where I am:
I successfully unlocked my bootloader, downgraded to GB, rooted. Tried to gain root access through adb terminal but it was not working properly.
I relocked my bootloader. Installed the ICS RUU AT&T ROM update. Unlocked my bootloader, rooted.
I see the commands you ran in your previous post. I am also receiving the same message of N/A when running the getprop ro.baseband
I tried the second command setprop ro.baseband 3.26.5XXX and then restarted the phone. I have tried it as posted, and also with swapping out the version that is located in my android-info.txt file: 3.26.502.56
Still no luck with setting the baseband version. IMEI still is cleared out.
Am I doing something wrong?
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
Click to expand...
Click to collapse
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
ayulatins said:
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
Click to expand...
Click to collapse
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it.
centro7710 said:
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it, as is, on ebay instead to get a few bucks out of it and getting a new phone.
Click to expand...
Click to collapse
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
ayulatins said:
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
Click to expand...
Click to collapse
Exactly. It was my sister's phone. The sh*tty thing is we bought two off of ebay at the same time, 1 for me, 1 for her. Well, her phone was not in the box (either never shipped or stolen) so I had to file a claim through eBay which took 3 weeks to get the money back. Meanwhile, I gave her my phone (which is the phone in reference) to use instead. I bought her an iPhone instead now, along with purchasing one myself. I loved Android, but the bugs and fragmentation is getting too much for me to handle.
Dude, if you don't have an IMEI showing up, something is WAY wrong. That goes beyone the RIL not working... The RIL is probably fine. If your phone doesn't have an IMEI somehow, the cell towers are NOT, NO WAY, NEVER EVER going to register your phone on their network. You can put a billion SIM cards in there, or flash a billion stock ROMS, and if you don't have an IMEI, you will never be able to connect.
Something is probably corrupt or broken in your firmware or the hardware itself. I think your device is probably screwed.
My advice, is follow the steps to put your phone back to stock (including changing the bootloader message back to **LOCKED** and S-ON), and get it back to the phone company. They will be able to tell something is boned on the phone right away since it isn't displaying an IMEI.
Sorry to be the bearer of bad news and for your many wasted hours... But on the plus side, you now know a LOT about flashing and how your phone works now
Good luck with everything man! Hope they get you up and running soon!
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
anyone got the Radio.img?
inick73376 said:
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
Click to expand...
Click to collapse
That's weird..you try creating the apns again? I don't see how a factory reset would do that. Try toggling airplane mode too
Sent from my De-Sensed HTC Vivid using xda premium
I am currently having the same issues right now, it works if i leave the phone off for 1 hr it will work until i reboot then its down again, tried every thing possible, airplane mode will crash, reflashing the radios from gb and ics does nothing, setprop does nothing really. from this point it feels like a hardware issue.
sorry to revive an old thread, i just wanted to know if anyone came across this issue and had it fixed
i will get a log to see if there is errors showing up
Return it.
Sent from my HTC Holiday using Tapatalk 2

Categories

Resources