Hello All,
Earlier I had a boot loop problem, which was easily solved with One Click Unbrick Heimdall. After which I installed entropy's daily driver, installed CWM, and updated to CM10. For whatever reason, I kept losing signal and data. Originally, I thought it possibly a bug in the rom, but after trying Paranoid Android and also qkster's Clean_Wipe script, I decided to go back to stock.
After going back to stock, I now get an "Invalid Sim Card!" message after a few minutes with the screen off (I have signal and data working before this), and this problem persists until I reboot the phone. After rebooting, it will show this message again.
One weird thing I noticed was that I do not get the "Invalid Sim Card" message, nor do I lose signal when my phone is plugged in and charging. Any ideas on what is causing this and what I can do to fix it? It's the same sim card I've had all along.
Thanks
I've had the CM10 issue where EFS folder gets lost, which wipes out all radio functions, but never an invalid SIM error message. I don't have anything to offer that'd address your specific problem.
One thing that may be worth trying would be to Heimdall back to stock again, and then flash the bootloaders. After the initial flash, leave the Heimdall screen running and check the "Flash Bootloaders" box. Once the phone is booted up after the initial flash, shut it down again and boot into download mode. Then flash again, but this time it'll also install the bootloaders.
May or may not help, but there's always the remote possibility that something could have somehow been corrupted with the first flash, and this will at least help eliminate a variable and let you start troubleshooting with a clean slate.
ApexPredatorBoids said:
I've had the CM10 issue where EFS folder gets lost, which wipes out all radio functions, but never an invalid SIM error message. I don't have anything to offer that'd address your specific problem.
One thing that may be worth trying would be to Heimdall back to stock again, and then flash the bootloaders. After the initial flash, leave the Heimdall screen running and check the "Flash Bootloaders" box. Once the phone is booted up after the initial flash, shut it down again and boot into download mode. Then flash again, but this time it'll also install the bootloaders.
May or may not help, but there's always the remote possibility that something could have somehow been corrupted with the first flash, and this will at least help eliminate a variable and let you start troubleshooting with a clean slate.
Click to expand...
Click to collapse
I didn't get the invalid SIM error message on CM10 (just lost signal), only on stock gingerbread. But I'll try flashing bootloaders and let you know if that fixes my problem.
EDIT: I keep getting a message saying it cannot upload pit file. Any suggestions?
Reboot PC and try again. Sometimes it's just a random USB quirk. Maybe try switching USB ports. If you do reboot the PC, you'll have better luck with getting a good connection afterwords if you pull the phone's battery and reboot it into Download Mode.
---------- Post added at 07:40 PM ---------- Previous post was at 07:33 PM ----------
I guess I should put out this warning: IF you're having alot of trouble getting a reliable USB connection for Heimdall, you should be cautious when considering flashing the Bootloaders. From my understanding of things, a bad Bootloader flash is about the only way to really brick an Infuse.
ApexPredatorBoids said:
Reboot PC and try again. Sometimes it's just a random USB quirk. Maybe try switching USB ports. If you do reboot the PC, you'll have better luck with getting a good connection afterwords if you pull the phone's battery and reboot it into Download Mode.
---------- Post added at 07:40 PM ---------- Previous post was at 07:33 PM ----------
I guess I should put out this warning: IF you're having alot of trouble getting a reliable USB connection for Heimdall, you should be cautious when considering flashing the Bootloaders. From my understanding of things, a bad Bootloader flash is about the only way to really brick an Infuse.
Click to expand...
Click to collapse
I rebooted. No such luck. I can still boot into download mode and recovery, but not into the actual OS now. I've flashed the bootloaders before when I was semi bricked, so I thought that it would work again. This was the only computer I had success on before. So I'll have to see if I can get another computer to work.
oeusr said:
I rebooted. No such luck. I can still boot into download mode and recovery, but not into the actual OS now. I've flashed the bootloaders before when I was semi bricked, so I thought that it would work again. This was the only computer I had success on before. So I'll have to see if I can get another computer to work.
Click to expand...
Click to collapse
I always keep a decent selection of ROM zips on my internal SD for such occasions. Since you can get into CWM, see if you can mount USB storage and transfer a different ROM to your phone, assuming you don't already have some saved on it. It'll at least give you functionality again, while you figure your Heimdall issues out. Assuming that it was a wiped-out EFS folder that caused your JB connectivity issues, I'd try flashing back to that for now. I've only had that happen once, in approximately 10 JB flashes, so it seems to be a bit of an unlikely occurrence, for the most part. Odds are, it'll be fine this time around.
ApexPredatorBoids said:
I always keep a decent selection of ROM zips on my internal SD for such occasions. Since you can get into CWM, see if you can mount USB storage and transfer a different ROM to your phone, assuming you don't already have some saved on it. It'll at least give you functionality again, while you figure your Heimdall issues out. Assuming that it was a wiped-out EFS folder that caused your JB connectivity issues, I'd try flashing back to that for now. I've only had that happen once, in approximately 10 JB flashes, so it seems to be a bit of an unlikely occurrence, for the most part. Odds are, it'll be fine this time around.
Click to expand...
Click to collapse
Err I don't have CWM anymore since I used Heimdall to go back to stock. And I don't think it was the EFS folder for my connectivity issues, because I had the same issues on stock.
EDIT: got it back to stock on a different computer. Will post again if I encounter the "invalid sim card" problem again
[EDIT2: back to stock, still have the problem /I]
Maybe there was a slight issue with the SIM card reader and the flashing about exacerbated the problem to where it showed itself. If you're still within your warranty period, maybe look into getting a replacement?
ApexPredatorBoids said:
Maybe there was a slight issue with the SIM card reader and the flashing about exacerbated the problem to where it showed itself. If you're still within your warranty period, maybe look into getting a replacement?
Click to expand...
Click to collapse
Not within warranty unfortunately. Are there any other options do you think? Forgot to mention, I put my sim card in a non smartphone for a little while. perhaps that messed with my sim card?
oeusr said:
Not within warranty unfortunately. Are there any other options do you think? Forgot to mention, I put my sim card in a non smartphone for a little while. perhaps that messed with my sim card?
Click to expand...
Click to collapse
Seems unlikely. As far as I know, the only thing that can be written to the SIM card is new contacts. If you happen to have another AT&T SIM card available, I'd try putting it in and seeing if it still gives the same error message. If it does, obviously, it's something with the phone, or at least the software. If not, maybe the SIM did somehow manage to go bad. It's not a problem I've ever run into. I'm out of ideas.
oeusr said:
Not within warranty unfortunately. Are there any other options do you think? Forgot to mention, I put my sim card in a non smartphone for a little while. perhaps that messed with my sim card?
Click to expand...
Click to collapse
did you remove SIM when flashing the JB roms???
OP's have warnings about leaving SIM card in for flashing, at least first flash anyway.
also suggests doing EFS back up.
always tell people "read read read"
not trying to do the "told you so" thing here, probably not helping.
can't you get new SIM from store?
captemo said:
did you remove SIM when flashing the JB roms???
OP's have warnings about leaving SIM card in for flashing, at least first flash anyway.
also suggests doing EFS back up.
always tell people "read read read"
not trying to do the "told you so" thing here, probably not helping.
can't you get new SIM from store?
Click to expand...
Click to collapse
Perhaps you should take your own advice, and "read read read" again. You have your cards mixed up. The recommendation is to remove your external SD card, not the SIM card. I've never removed my SIM for flashing, and never had any issues because of it.
oeusr said:
Hello All,
Earlier I had a boot loop problem, which was easily solved with One Click Unbrick Heimdall. After which I installed entropy's daily driver, installed CWM, and updated to CM10. For whatever reason, I kept losing signal and data. Originally, I thought it possibly a bug in the rom, but after trying Paranoid Android and also qkster's Clean_Wipe script, I decided to go back to stock.
After going back to stock, I now get an "Invalid Sim Card!" message after a few minutes with the screen off (I have signal and data working before this), and this problem persists until I reboot the phone. After rebooting, it will show this message again.
One weird thing I noticed was that I do not get the "Invalid Sim Card" message, nor do I lose signal when my phone is plugged in and charging. Any ideas on what is causing this and what I can do to fix it? It's the same sim card I've had all along.
Thanks
Click to expand...
Click to collapse
If I read this correctly, you went directly from gb to cm10.
Your error wasn't so much as sim or signal. It is due to the mtd conversion from gb voodoo.
Seems like the correct way would be: gb to cm7/cm9, then cm7/cm9 to cm10.
If you check about phone, you will likely see garble on the imei line.
qkster said:
If I read this correctly, you went directly from gb to cm10.
Your error wasn't so much as sim or signal. It is due to the mtd conversion from gb voodoo.
Seems like the correct way would be: gb to cm7/cm9, then cm7/cm9 to cm10.
If you check about phone, you will likely see garble on the imei line.
Click to expand...
Click to collapse
Sorry, I left out that I did go to cm9 before hand.And i did not have an imei garbled line; mtd conversion went fine.
haha I'm not that much of a newb
oeusr said:
Sorry, I left out that I did go to cm9 before hand.And i did not have an imei garbled line; mtd conversion went fine.
haha I'm not that much of a newb
Click to expand...
Click to collapse
http://catb.org/esr/faqs/smart-questions.html
gl
qkster said:
http://catb.org/esr/faqs/smart-questions.html
gl
Click to expand...
Click to collapse
Sorry qkster, I didn't mean any disrespect! I was just trying to playfully say that I had read the OP and followed the directions beforehand.
oeusr said:
Sorry qkster, I didn't mean any disrespect! I was just trying to playfully say that I had read the OP and followed the directions beforehand.
Click to expand...
Click to collapse
np...I have always recommended ppl to specifically state the problem they are experiencing in complete detail, step wise and leaving nothing out.
It helps those to are willing to help others better understand where you are coming from.
In your instance, to isolate the hw vs firmware issue, you may want to consider Heimdall 1 click uckj4 or uclb3 package with complete boot loader box checked to get back to a complete stock.
Or Odin one of the leak package with pit and repartition.
If you have successfully done this and the sim issue or signal remain, it is possible that it's a hardware issue
qkster said:
np...I have always recommended ppl to specifically state the problem they are experiencing in complete detail, step wise and leaving nothing out.
It helps those to are willing to help others better understand where you are coming from.
In your instance, to isolate the hw vs firmware issue, you may want to consider Heimdall 1 click uckj4 or uclb3 package with complete boot loader box checked to get back to a complete stock.
Or Odin one of the leak package with pit and repartition.
If you have successfully done this and the sim issue or signal remain, it is possible that it's a hardware issue
Click to expand...
Click to collapse
Yes, after using Heimdall 1 click and back to stock a few times, I'm starting to think it's a hardware issue. Thanks ApexPredatorBoids and qkster for the help.
oeusr said:
Yes, after using Heimdall 1 click and back to stock a few times, I'm starting to think it's a hardware issue. Thanks ApexPredatorBoids and qkster for the help.
Click to expand...
Click to collapse
Try taking a friends att sim, pop er in see if it'll work if it does go to att getcho self a free sim if not you might need a new similar reader :/
Sent from my Nice 'n' Stock-y Infuse 4G
Related
After many issues trying to get phone working again, I was able to flash ED1stock and the phone will boot up to the android setup screen.
Problem is, I get an error message after I click Next. I have went to verizon and got a new SIM but the same message comes up. Verizon will not exchange the phone due to my wife taking the phone up when the phone would not boot and when they were looking at it, voodoo started talking to them so they Red Flagged my phone.
So now I'm stuck with a phone that will not finish the setup. At this point, I just want to get it back to stock working so I can sell it.
Here is the message that I am getting.
"Sorry, this SIM card is not supported or readable. Please contact your wireless service provider."
Any help would be great.
Thanks
It sounds like you're in the same boat as me with regards to your phone's operating status; I'm going to Verizon today to try a new SIM card. I'll let you know if that does the trick.
empyreandance said:
It sounds like you're in the same boat as me with regards to your phone's operating status; I'm going to Verizon today to try a new SIM card. I'll let you know if that does the trick.
Click to expand...
Click to collapse
Please do. I did the same but it didn't work. Only thing is when I got home, I tried to re-flash the phone and I might have left the new sim in the phone that could have caused it to go bad.
Starting to think that its a radio problem. Wonder if there is a stock radio we can flash?
Well, the bad news is multiple new SIM cards did not work and many other members are experiencing the same problem. Keep your eyes out for a radio update to flash.
empyreandance said:
Well, the bad news is multiple new SIM cards did not work and many other members are experiencing the same problem. Keep your eyes out for a radio update to flash.
Click to expand...
Click to collapse
If that is the reason. Don't know any other reason. I even tried to flash a couple kernels but failed also.
Only thing I could think of is the radio being the issue.
juttschallenger said:
After many issues trying to get phone working again, I was able to flash ED1stock and the phone will boot up to the android setup screen.
Problem is, I get an error message after I click Next. I have went to verizon and got a new SIM but the same message comes up. Verizon will not exchange the phone due to my wife taking the phone up when the phone would not boot and when they were looking at it, voodoo started talking to them so they Red Flagged my phone.
So now I'm stuck with a phone that will not finish the setup. At this point, I just want to get it back to stock working so I can sell it.
Here is the message that I am getting.
"Sorry, this SIM card is not supported or readable. Please contact your wireless service provider."
Any help would be great.
Thanks
Click to expand...
Click to collapse
Mine has been this way since Wed. night. Sorry to say, but you are probably up a creek right without a paddle.
What were you trying to recover from? and did you flash anything prior to ed1
ShotgunSam said:
Mine has been this way since Wed. night. Sorry to say, but you are probably up a creek right without a paddle.
What were you trying to recover from? and did you flash anything prior to ed1
Click to expand...
Click to collapse
I made the mistake of trying to run a backup from clockwork. That started it all. Then wiped the phone and tried to flash every rom out there to get it to work again. Nice that its booting up to android but sucks that it will not see the sim.
Can anyone point us in the right direction on this? The phone is starting to collect dust sitting here.
Has anyone been able to recover from this?
juttschallenger said:
I made the mistake of trying to run a backup from clockwork. That started it all. Then wiped the phone and tried to flash every rom out there to get it to work again. Nice that its booting up to android but sucks that it will not see the sim.
Can anyone point us in the right direction on this? The phone is starting to collect dust sitting here.
Has anyone been able to recover from this?
Click to expand...
Click to collapse
This is exactly what I was trying to recover from. I had to use the "almost everything" package that Imnuts posted and then flashed ed1 and boom, no sim card.
So far I haven't been able to get a dev really to look at the possibilities.
ShotgunSam said:
This is exactly what I was trying to recover from. I had to use the "almost everything" package that Imnuts posted and then flashed ed1 and boom, no sim card.
So far I haven't been able to get a dev really to look at the possibilities.
Click to expand...
Click to collapse
Hey is there any DEV's of there that could give us a hand? I'm sure there are going to be many people out there that could use a fix for this issue.
Thanks
This just happened to me. I got a new sim card, it worked, it was on an ed1 stock kernal, it then software upgraded and boom, sim card no longer works. Going in tomorrow to get another sim card with an ed2 stock kernal to see if it will keep. Anyone figure out why this is happening?
Steve
smgrajeda said:
This just happened to me. I got a new sim card, it worked, it was on an ed1 stock kernal, it then software upgraded and boom, sim card no longer works. Going in tomorrow to get another sim card with an ed2 stock kernal to see if it will keep. Anyone figure out why this is happening?
Steve
Click to expand...
Click to collapse
There is a known issue with sim cards being fried frequently on this phone that Verizon is aware of.
Some people are temporarily removing the sim prior to flashing.
smgrajeda said:
This just happened to me. I got a new sim card, it worked, it was on an ed1 stock kernal, it then software upgraded and boom, sim card no longer works. Going in tomorrow to get another sim card with an ed2 stock kernal to see if it will keep. Anyone figure out why this is happening?
Steve
Click to expand...
Click to collapse
I would first have to ask why are you still on ED1??? odin the latest stock EE4 package or OTA upgrade it and see what happens then... those OG roms (ED1/2) are so borked there's issues even with the odin packages
blazing through on my 4G Droid Charge
Im new to all of this hacking stuff, so I just updated to what I could find. Ill do the ee4 update tonight.
Thanks!
Steve
Try flashing EP1W from herethen flashing use the PIT file from here.
Hey guys,
I'm looking for a little help here. My Skyrocket seems to be having radio/modem issues.
Instead of having a symbol that displays cell signal, I have a circle with a line through it. This is true with or without a working SIM inserted. For baseband version it says "unknown".
I've tried flashing to stock and that didn't seem to make a difference. I got this phone second hand so I don't know if the previous owner tried to flash an incompatible rom and borked up the radio firmware possibly?
Any thoughts about what I can try?
That all depends on which method and tar you used. Some tars dont come with the radio. and with the wrong radio on a rom you will get a RIL mismatch and no signal
xcrazydx said:
That all depends on which method and tar you used. Some tars dont come with the radio. and with the wrong radio on a rom you will get a RIL mismatch and no signal
Click to expand...
Click to collapse
So I'm unsure how it got to its current state. (meaning the circle with a line through it) To return to stock I used the K0nane tar that's in the sticky in the dev section. I don't know if that has a radio in it or not but flashing that didn't seem to change things.
JimmyStale said:
So I'm unsure how it got to its current state. (meaning the circle with a line through it) To return to stock I used the K0nane tar that's in the sticky in the dev section. I don't know if that has a radio in it or not but flashing that didn't seem to change things.
Click to expand...
Click to collapse
That doesn't have a radio in it. Look in your "about phone" and tell me what your baseband and android version says.
After that I will probably say to flash the sammobile tar...
Also, Did you have the correct plan added to your service when you switched phones?
baseband version = unknown
JimmyStale said:
baseband version = unknown
Click to expand...
Click to collapse
Right..
Assuming your plan has been provisioned for the new lte phone, I would flash the sammobile tar in odin
I'm going to give that a try. I suppose I'll just search for sammobile?
The SIM i'm using was provisioned for my previous Skyrocket. I ended up trading that but used the same sim in my new phone. So, I'm assuming the SIM/my account should be proivisioned for LTE since I never had AT&T change anything on their end.
And just to clarify, this doesn't really seem to be a "no service" type problem since its as if the radio isn't even recognized by the hardware.
JimmyStale said:
I'm going to give that a try. I suppose I'll just search for sammobile?
The SIM i'm using was provisioned for my previous Skyrocket. I ended up trading that but used the same sim in my new phone. So, I'm assuming the SIM/my account should be proivisioned for LTE since I never had AT&T change anything on their end.
And just to clarify, this doesn't really seem to be a "no service" type problem since its as if the radio isn't even recognized by the hardware.
Click to expand...
Click to collapse
Right, seems to be a ril mismatch.
Factory reset and then flash the sammobile tar
http://www.sammobile.com/firmware/
I'm downloading now. I'll report back after I flash.
JimmyStale said:
I'm downloading now. I'll report back after I flash.
Click to expand...
Click to collapse
Cool, hope it works for ya!
every time I see a thread like this, I can only count the number of posts until x says "flash Sam mobile tar," and then poof! problem solved. lol I just wished people read around a little more
icenight89 said:
every time I see a thread like this, I can only count the number of posts until x says "flash Sam mobile tar," and then poof! problem solved. lol I just wished people read around a little more
Click to expand...
Click to collapse
There you are! Where ya been man?
icenight89 said:
every time I see a thread like this, I can only count the number of posts until x says "flash Sam mobile tar," and then poof! problem solved. lol I just wished people read around a little more
Click to expand...
Click to collapse
Lol, I appreciate the helpful info in your reply. Just so you know, I don't seem to be having the same issue as any other post that I've seen. Unlike the other posts I've read, I don't have "no sim" or no signal, or no LTE. My problem almost seems like an issue with the SIM slot itself. I think I can rule that out because I've actually replaced the SIM slot with a known good SIM slot. The other reason I think I can rule this out is because I am unable to access the radio related content from within the service menu. Unfortunately I don't think there will be a :oof:: that fixes what I have going on. (I wouldn't mind being wrong on this)
So I flashed the sammobile tar (multiple times) but no luck. The baseband version still reports as "unknown". What's more, my phone reboots after about 15 or 20 seconds. Very odd. Any other thoughts on things to try?
JimmyStale said:
Lol, I appreciate the helpful info in your reply. Just so you know, I don't seem to be having the same issue as any other post that I've seen. Unlike the other posts I've read, I don't have "no sim" or no signal, or no LTE. My problem almost seems like an issue with the SIM slot itself. I think I can rule that out because I've actually replaced the SIM slot with a known good SIM slot. The other reason I think I can rule this out is because I am unable to access the radio related content from within the service menu. Unfortunately I don't think there will be a :oof:: that fixes what I have going on. (I wouldn't mind being wrong on this)
So I flashed the sammobile tar (multiple times) but no luck. The baseband version still reports as "unknown". What's more, my phone reboots after about 15 or 20 seconds. Very odd. Any other thoughts on things to try?
Click to expand...
Click to collapse
post a screenshot of the about phone
flash cwm via Odin, flash my efs fix from the sticky, and then re flash the Sam mobile tar via Odin.
xcrazydx said:
There you are! Where ya been man?
Click to expand...
Click to collapse
dude life got BUSY all of a sudden. I come back, u got team waffle, u traded in our wip rom for an aokp t989 port, and a whole bunch of other stuff poppin off (ucle2). WTH lol, I wish I coulda been apart of at least a lil of it.
Flash the stock rom and radio and radio then dial #*2263# and click automatic. Then wait a minute or so and see if it goes back to showing the bars.
Sent from my Skyrocket 4G LTE using XDA Premium
I'm going to try the multiple suggestions I got and report back. I'm also attaching the "screen shots"
Hopefully the attachments are here
I flashed EFSFix through CWM and then SAMMOBILE tar through ODIN. No luck, but ODIN did take about twice as long as it did the first time I tried flashing the sam .tar. Same symptoms, circle with a line through it and phone reboots itself after about 20 seconds. The baseband version still reports as "unknown".
I flashed back to stock through ODIN, flashed CWM with ODIN, and then flashed EFSFix again. Same exact results as the first time.
Next I flashed back to stock using ODIN, and flashed UCLE2 ROM through ODIN. Flashing this causes the reboot issue to go away, but the radio issue remains. (I thought to try the UCLE2 ROM because that's what was loaded when I first received the phone and the phone wasn't rebooting itself then)
aight so ive searched and searched for all kinda different methods. and done all of them. is it possible to have a permanent brick?
heres the story. i had been running cm10 for prolly 4 or 5 months. no problems. i wanted to check out liquid smooth rom. so i flashed it. no problems. had been running it for a month or so then one day at work when i went on break my network was gone. my apn's were deleted. came home inspected some more and my imei was unknown as well as baseband and many others were unknown. i took it back to stock many times using. gtg method. using heimdel. using odin. with different stock files. from different websites. including xda. i have tried just about everything to re do the phone. including going back to cm10. and other known working roms. ive *#*#4636#*#* and manually switched to gsm which wont change when i click it it still says unknown.
i dont belive it is a rom problem. i have been overclocked 1300mhz. what else is out there can i try. \
\
any help will be very appreciated
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
FauxAffliction said:
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yea i went to stock and back to cm10. still nothing. buttt now im unable to do any kinda flashes. im on rooted 2.3.6 threw odin. and no matter what i flash it will say somthing on the lines of failed to find file signature or what ever that code is. i tried changing the cwm in different ways still wont get off the what is it 2.5.2 cwm blue. ive basicly gave up. it seems its to far bricked or whatever the case may be
im sorry i need to correct that. i have not been able to flash to any other roms. i didnt go to stock and then cm10, due the the signature deal on cwm. i was thinking of another time i had problems. so no i have no been able to go to jb after the imei has went unknown
Did you flash a custom kernel to get cwm after going back to stock?
andros11 said:
Did you flash a custom kernel to get cwm after going back to stock?
Click to expand...
Click to collapse
im in able to flash anything.....
really? no one can help me?
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
psal217050 said:
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
kritz84 said:
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
Click to expand...
Click to collapse
but im pretty sure the problem isnt with cwm im more interested in why and how to the imei isnt known and how to fix this problem if theres a cure
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
andros11 said:
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
Click to expand...
Click to collapse
i guess u didnt read my first post. ive already done that. ive done many things....
but anyway weirdest thing just happend. i have been using my phone via wifi. so its been on a while without a sim card inside of it.
\
i noticed i had signal bars. i looked at the imei and its was a number. it was a different iemi then what its supposed to be but there was a imei. baseband was still unknown but anyway i shut the phone done and inserted my sim card. btw its a straight talk sim. and restarted it now im back to unknown imei......
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
kritz84 said:
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
Click to expand...
Click to collapse
odin or heimdall back to stock.
follow andros11's guide on how to flash jb
he spent the time to write the guide; spend the same amount to time to read the guide
Seems IMEI was kidnapped about a month after Liquid
Ironically, I seem to have EXACTLY the same issue that this original poster has. I have been flashing my Infuse for a little over a year now and I Flashed Liquid, I'd say about 3 weeks ago, maybe end of November. Everything has been smooth sailing. About a 2 days ago I started noticing that my network would just drop - for no reason. But at first it came back. Ok, no problem, probably just a glitch. However yesterday morning it happened again and then I was without the use of data for most of the day until around 6pm. It came back but the bars were grey but I was able to make a phone call. Once I made another call it did not go through, I tried to hangup and it just hung there. there was nothing I could do to get it to hang up. Rebooting the phone resulted in no bars at all. Nothing, nada, ziltch. So last night I reflash it a couple times and notice that there was an update to Liquid (2.1 beta). cool. I wipe, flash 2.1b and it is beautiful. EXCEPT for the fact that I have no network. wifi works fine, but no carrier whatsoever. GRRRR. I decided to back every thing up (have done so several times in the past), stock back down to 2.3.6. Barebones and all it all looked great until I hung up the phone... Same thing. So I went all Rambo on the phone, wiped it down to the very last compound. AT&T wouldn't know the wiser if they took it from me. Master Reset, wiped files, data, I think I took an IC out with all of the wiping I did... Result? No IMEI, circle with the slash. Upset, disappointed and dejected I slumped back to XDA (after I went on Craigslist feeling my phone was broke) to see if I missed anything. That was where I found some links about missing IMEI. To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Dnice808 said:
To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Click to expand...
Click to collapse
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
After this, check your imei and band. If it works, no further back up is needed.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
So it is in the .tar format that your script backed it up in. Finding another link on the we (which he also linked back to XDA, http://forum.xda-developers.com/showthread.php?t=1264021 I was able to take my backup (that I used with your script) and follow his steps -mostly- (my/your backup had a 'root' folder that had the nv_data.bin file in the afs/settings folder while the instructions did not mention that. I followed the backup location settings (which in turn was also the same as the default that I had backed up)) and replace the EFS folder. It still did not restore it in any flash image just like that. Still had the the circle w/slash. However while I was still searching and typing out that loooong last passage I wrote, my phone network came back for a little while. I know this because I began receiving a bunch of texts. I was able to make a phone call. But it still happened again when I made another, it did not go through and when I hung up, it just stayed there looking at me with its grey, blank look. Even killing the phone app did not work. I rebooted back to the same drama.
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
I actually was on 2.3.6 using your posts, first the basic rooted flash having to then using the Entropy kernel and then I did the lazy flash that was already rooted and just having to add the vold file to /system/etc/blah/blah. I do want to add that I DID have wifi active at this time and it may not be associated, but the first poster did mention he felt it may have had something to do with it. With wifi on, after awhile of me NOT looking at the phohe (actually doing so made me want to HULK SMASH), the network came on and my texts came in. I was able to look in settings and see ATT, and my IMEI. I was almost finished with my passage to you so I decided to update to Liquid 2.1 beta, but moving up to JB, then to LiquidSmooth. Of course doing so I got the circle w/slash, but wifi started restoring my apps.
Earlier I mentioned that I did a whole rubba dub dub, meaning I did do the /settings/privacy -reset thingy, wiping the phones carcass. I will do it again (at this point nothing to lose), following everything you ask to a 'T'.
808
Click to expand...
Click to collapse
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Done.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
Done
After this, check your imei and band. If it works, no further back up is needed.
Sigh, did not do a darn thing. Circle w/slash.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Done.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
Went in Root Explorer, did the toggle, deleted the contents of efs then copied the contents of my backup into there. Rebooted. Nada.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
I then was going to try the other link using Odin, but I cannot get Odin to see my phone. I read some thread talking about if I use Heimdall I will have problems using Odin because they use the same ports? How frustrating. The weird part is now that I have the flashed, rooted 2.3.6 image and using wifi, at some point tonight my network may come back on. Or it may not.
808
Click to expand...
Click to collapse
Bugged out, huh?!!???
Dnice808 said:
Bugged out, huh?!!???
Click to expand...
Click to collapse
I wasn't sure if there was a question there.
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
qkster said:
I wasn't sure if there was a question there.
Click to expand...
Click to collapse
Me stating that it is bugged out, was me just confirming that it is Weird!
qkster said:
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
Click to expand...
Click to collapse
Ok just to explain myself better. I have been saying that I was going from GB to JB when in fact I meant to say that I was going from GB to ICS. Sorry for that. Also, the reason my responses have looked wacky is that I was trying to select the multi quote button and getting no response. Hopefully this response is a little more organized.
qkster said:
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
Click to expand...
Click to collapse
See that is what confuses me too. I have flashed back and forth several times at this point, and sometimes the /efs and imei do come back, but now they have never stayed. It is the only reason why I have tried to pretty much rule out a hardware issue. Even when I flash and there is no imei, there is the same /efs folder. And when I wipe the whole thing sparkling clean, even the newly formed /efs folder has the correct imei but it is just not being recognized on the phone.
qkster said:
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
Click to expand...
Click to collapse
Of course what I did was accidentally leave my phone home preventing me from testing it out with Odin on another machine. Its all good though.
qkster said:
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
Click to expand...
Click to collapse
I have an AT&T prepaid phone and the sim from the Infuse works in it flawlessly...
808
Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.
I thought I would change the title of my thread as the issue seems to have changed. I hope that isn't a problem. I am able to get into loader mode just fine and have loaded CWM twice through ODIN but am unable to get the internal SD Card to mount or USB mode to work. HAs anyone seen this before? I searched carefully and could not find any reference to my problem. I was careful to uncheck re-partition but there is a chance I may have not, I suppose. Would that cause my problem? Any input would be most appreciated....I'm stuck.
Well, the good news is as long as you have Odin mode nothing is broken that cant be fixed the bad news is, I've been following your progress, and I'm stumped and out of ideas :-/ the way I understand it, you have a working Clockwork Mod recovery, you can boot to recovery. Correct? When you try to mount USB mode in Mounts and Storage, it gives you an error? Do you have an external microSD that you could copy a ROM over to and try to flash from there?
Which version of CMW did you flash,I found issues with ver 6.XXX and went back to ver 5.XXX non touch. In the newer versions including touch USB and mounting the drives didn't work for me. I thought it was my phone because of everything I've done since rooting
Sent from my GT-N7100 using xda app-developers app
flyers00 said:
Which version of CMW did you flash,I found issues with ver 6.XXX and went back to ver 5.XXX non touch. In the newer versions including touch USB and mounting the drives didn't work for me. I thought it was my phone because of everything I've done since rooting
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
i believe (based on the other thread he was in) that he's using the 5.xxx version from k0nane's thread (which is what I'm using)
jparnell8839 said:
i believe (based on the other thread he was in) that he's using the 5.xxx version from k0nane's thread (which is what I'm using)
Click to expand...
Click to collapse
I wasn't sure either that's why I threw it out there. I'm using the same version from k0oane 5.XXX as well
Sent from my GT-N7100 using xda app-developers app
Interesting Thought
jparnell8839 said:
Well, the good news is as long as you have Odin mode nothing is broken that cant be fixed the bad news is, I've been following your progress, and I'm stumped and out of ideas :-/ the way I understand it, you have a working Clockwork Mod recovery, you can boot to recovery. Correct? When you try to mount USB mode in Mounts and Storage, it gives you an error? Do you have an external microSD that you could copy a ROM over to and try to flash from there?
Click to expand...
Click to collapse
Sounds interesting, but wouldn't this explode needing to access the internal SD? i don't know if my PC has a SD Slot, but that is easy enough to fix. I'll try the solution below then this one.. One step at a time. Glad I've got a stumper even if it is a pain in my @ss.
Thanks again to all for the thoughts.
Mike in Houston
CWM 5.0.0.4
flyers00 said:
Which version of CMW did you flash,I found issues with ver 6.XXX and went back to ver 5.XXX non touch. In the newer versions including touch USB and mounting the drives didn't work for me. I thought it was my phone because of everything I've done since rooting
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I'm using CWM 5.5.0.4 Still stumped. IF I did something stupid I sure wish I knew what it is. Phone is one week old and of course store claims it is my fault..........rrrrgh. I bought a Galaxy Express to hold me over until I get this fixed. The store offered me a job if I could fix it and as I'm not working, I'm calling in all the troops to help me here if possible........Thanks a million. or a thousand. They don't pay much.I Just checked and the sd card ext will not mount either in CWM and gives errors. I'd like to mod the express I bought to replace this one but am a bit gun shy now. It seems this problem is buried pretty deep.
Stil grateful but in need of help..
Ready to send it off to a JTAG repair shop but as I can still boot into both download and recovery modes there must be something I can do myself to fix this. Anybody out there??????
mikesmccurdy said:
Ready to send it off to a JTAG repair shop but as I can still boot into both download and recovery modes there must be something I can do myself to fix this. Anybody out there??????
Click to expand...
Click to collapse
All you've gotta do is Odin the ORIGINAL GB or ICS from Sammobile. Your soft bricked (no biggie). Your more than likely missing a few important files that GB or ICS could fix. I'd go with GB, IMO
Close but no cigar.
jbats said:
All you've gotta do is Odin the ORIGINAL GB or ICS from Sammobile. Your soft bricked (no biggie). Your more than likely missing a few important files that GB or ICS could fix. I'd go with GB, IMO
Click to expand...
Click to collapse
I went to Sammobile and downloaded the firmware but it comes in Zip format and Odin does not recognize that rrgh. I can't get it onto a sd card because it won't mount in CWM. Thanks for the suggestion. I'll hold off for another response before I ship it out. Seems like I should be able to find something to flash on here somewhere, but i'm stumped.......
You need to unzip the file and extract the files there's a tar file inside. Use the instructions in konanes thread with the file you have. I can walk you through it better tommorow when I get off work, its very easy.
jbats said:
You need to unzip the file and extract the files there's a tar file inside. Use the instructions in konanes thread with the file you have. I can walk you through it better tommorow when I get off work, its very easy.
Click to expand...
Click to collapse
I can't imagine someone would be so kind as to take their time to walk a stranger through a process. (Even if I would). I'm having a hard time finding konanes thread on this subject and would appreciate any direction to it so I won't be such a bother. Sorry for the delay in response, but I've been on a short vacation. Thanks to all.
mikesmccurdy said:
I can't imagine someone would be so kind as to take their time to walk a stranger through a process. (Even if I would). I'm having a hard time finding konanes thread on this subject and would appreciate any direction to it so I won't be such a bother. Sorry for the delay in response, but I've been on a short vacation. Thanks to all.
Click to expand...
Click to collapse
Here is the thread http://forum.xda-developers.com/showthread.php?t=1591601 now just grab the GB zip from sammobile and extract the tar and follow the instructions in the thread.:good:
Progress but no prize......
jbats said:
Here is the thread http://forum.xda-developers.com/showthread.php?t=1591601 now just grab the GB zip from sammobile and extract the tar and follow the instructions in the thread.:good:
Click to expand...
Click to collapse
Well I found it before you replied and low and behold I am able to boot my phone. Now it won't recognize the sim card. I made sure the SIM works in another phone. BTW this is a T-Mobile phone originally but I run on simple mobile. I tried the unlocking process but I did not pay for an unlock code because it won't boot to the unlock code screen. It just goes all the way through and then reports "no sim card Emergency calls only" Thanks for getting me this far. The phone worked fine before I started playing with it. Now I'm really stumped...rrgh.
Thanks
Mike in Houston with dead Blaze. And the store was going to offer me a job if I got it working....
Moving backwards
mikesmccurdy said:
Well I found it before you replied and low and behold I am able to boot my phone. Now it won't recognize the sim card. I made sure the SIM works in another phone. BTW this is a T-Mobile phone originally but I run on simple mobile. I tried the unlocking process but I did not pay for an unlock code because it won't boot to the unlock code screen. It just goes all the way through and then reports "no sim card Emergency calls only" Thanks for getting me this far. The phone worked fine before I started playing with it. Now I'm really stumped...rrgh.
Thanks
Mike in Houston with dead Blaze. And the store was going to offer me a job if I got it working....
Click to expand...
Click to collapse
Also of note only flashing T769UMB1 from Sammobile will allow the phone to boot at all. Whet I try to flash the root kernel the phone locks up as always at the blue bar when it completes and when reflashing T769UMB1 I go into CWM and am still unable to mount the SD Cards or USB Storage. Appears my little bit of progress was in vain. When it does boot as mentioned above, I still have "no sim card" Any advice would be appreciated. Being a NOOB, I am unsure if I started out with GB or ICS in the first place it that offers any assistance.
Any advice is greatly appreciated.
You need to buy an unlock code, than you can enter it through your dialer.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
You skipped the next step. You can't flash from GB to the latest. You have to do it in steps first GB than ICS uvlh5 than uvlmb1, uvlh5 was a prerequisette to the latest mb1. Start over...
Still grateful and lost.....
jbats said:
You need to buy an unlock code, than you can enter it through your dialer.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
You skipped the next step. You can't flash from GB to the latest. You have to do it in steps first GB than ICS uvlh5 than uvlmb1, uvlh5 was a prerequisette to the latest mb1. Start over...
Click to expand...
Click to collapse
I have done as you suggested and really appreciate all the time you have taken to help me out. When I loaded UVLH5 the phone said it was updating 62 apps as it booted and I was in the same predicament. The phone boots and recognizes the internal memory card but will not recoginze my SIM card. I thought it was supposed to ask for an unlock code when it saw the foreign sim as I have seen that on other sites. The phone just boots and says "No SIM card" whether or not one is installed. Would sending it off for a JTAG repair solve my problem? I think I may have screwed the pooch so to speak when I loaded uvimb1. I am determined to fix this phone. It shouldn't be so difficult, famous last words. I think there may be a way to force the dialer to allow me to enter an unlock code, but before I spend more money on the phone I want to make sure that is what I need to do. I also cannot seem to get back into CWM for some reason. Maybe the button sequence has changed with the update. Confirming that procedure would be quite helpful.
mikesmccurdy said:
I went to Sammobile and downloaded the firmware but it comes in Zip format and Odin does not recognize that rrgh. I can't get it onto a sd card because it won't mount in CWM. Thanks for the suggestion. I'll hold off for another response before I ship it out. Seems like I should be able to find something to flash on here somewhere, but i'm stumped.......
Click to expand...
Click to collapse
You need an account with samfirmware and you should be downloading a .tar.md5 file. Shouldn't be a zip. Just curious, what's inside the zip?