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
Related
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
bvsbutthd101 said:
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
Click to expand...
Click to collapse
what are the steps you're using in odin? put the battery back in to flash stuff (if you don't already have it in) if it keeps failing... also what are you trying to flash and where are you trying to end up rom/kernel wise?
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
bvsbutthd101 said:
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
Click to expand...
Click to collapse
Yeah if an odin flash fails and you unplug it and boot it up it will start the last rom you were running. You can still get it into download mode for odin right? Strange that its not flashing right... Try using a different USB port on your pc (as well as plug in your pc for good measure), disable any antivirus software you may have or run Odin as administrator, then put the battery back in for odin as always only use PDA and/or PIT sections
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
bvsbutthd101 said:
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
Click to expand...
Click to collapse
I probably would've tried a little more to fix it, its extremely hard to brick this phone or make it so you can't recover or get back to stock... anyways thats good, hope its easier to odin with the new one
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
bvsbutthd101 said:
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
Click to expand...
Click to collapse
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
anoninja118 said:
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
Click to expand...
Click to collapse
Exactly, pretty important part if I do say so myself. I'm happy though. They didn't give any problem. I didn't even ask to get a new phone. They just told me that we'll just send one out to you.
So I tried to flash two of the new Roms in the dev section and now I cant boot anything at all nor can I restore my old Rom through recovery. I get to the MD5 checking then it says MD5 mismatch and doesn't let me restore. Anyone have any ideas? My phone wont boot....
After the massive googling that took place after this post I decided to just ODIN this sucker back to stock. Stock restored, root added, and CWM working again in under 10 minutes. Gonna make another backup and try reflashing again
DarkKnight worked fine for me except for some known bugs... i could'nt get the Noble Series 8.0 or 8.1 to boot at all though weird just stay at the blaze 4g splash screen
dispozable said:
After the massive googling that took place after this post I decided to just ODIN this sucker back to stock. Stock restored, root added, and CWM working again in under 10 minutes. Gonna make another backup and try reflashing again
Click to expand...
Click to collapse
I'm not to familiar with odin, this is the first time i had to use it with my blaze. how do return back to stock from odin? i don't need to at the moment, just good knowledge to have, if i got stuck in same scenario as you.
trevor7428 said:
I'm not to familiar with odin, this is the first time i had to use it with my blaze. how do return back to stock from odin? i don't need to at the moment, just good knowledge to have, if i got stuck in same scenario as you.
Click to expand...
Click to collapse
Its the same procedure you use to root your device. Put the phone in download mode and plug in usb cable. But instead of selecting blaze-root-kernel.tar (the rooted kernel you used), you'll instead select SGH-T769-UVLB7-hitsquad.tar. I have not needed to restore my device yet, so I have no experience. Just knowledge from reading. So don't take me for granted!
Sleeps17 said:
Just restore back to stock firmware using Odin. You need to download a file called SGH-T769-UVLB7-hitsquad.tar and blaze.pit, load those up in Odin and unselect all options except Reboot. And carefully make sure Repartition is unchecked as well.
Click to expand...
Click to collapse
To return back to stock I used this link: http://forum.xda-developers.com/showthread.php?t=1591601
After that I used this link: http://forum.xda-developers.com/showthread.php?t=1591598
I'm sure it wasnt the roms (I tried flashing both) that caused it because I couldn't restore my backups either, though I still don't know what happened. Safe to say the restore to stock was very fast, and now I have no worries if I soft brick again.
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
Hey guys, I am at the end of my rope here, so maybe you can help me out.
I have been dealing with the Media service bug that drains battery super fast for the last few days on my wifes rooted SGS3, and I have been jumping between roms, deleting SD files, searching for corrupt apps/media all to no avail. Tonight, in an effort to fix this issue, I flashed the most recent CM10 nightly as I heard it had a fix for this issue. I have no idea if that is true, because when I got to the setup screen after flashing, I kept getting an error that said that setup crashed and could not run. I had to boot back in to recovery, flash again, only to find the same error.
I then attempted to flash clean rom, except now I see that her phone is always roaming where my Note2 right next to it is on 4G. I flashed an older CM10 nightly for her, and the same issue popped up where it is only roaming.
Did the failed CM10 flash screw something up? How can I get her off roaming and back on 3/4G? Thanks!
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
x714x said:
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Click to expand...
Click to collapse
Good advice, but I'm pretty sure he would need to repair his imie before the code
If I helped you in some way.... pass on the favor and help the next person!
x714x said:
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Click to expand...
Click to collapse
OK, so I was able to get signal back (shows 4/3G), however she is unable to actually text or call from her number. She can use google voice though, so I am guessing it is something specifically with her number. Maybe the IMEI thing you mentioned. Assuming she has her signal back, would dialing that set of numbers reactivate her, or would I still have to do the ODIN steps?
It there is data then that dialer code should fix the calling, but you need to be in ics to do it
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
It there is data then that dialer code should fix the calling, but you need to be in ics to do it
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Yeah, I am pretty sure she has data. She is not at home, and when she left a bit ago we thought all was well (since she had the 4G indicator whereas before it said roaming) but she just used GVoice to text me to say that she cannot call or text using her VZW credentials. When you say that she needs to be in ICS, would any ICS rom do? She is in the newest version of Cleanrom right now, so I will have to flash something else I think. As for using ODIN, that is kinda out of the question because we are on vacation and the internet here sucks. It would take 2 weeks to download the stock VZW image, but if that is the only option then I guess that is how i goes. Thank you in advance for all your help!
Mindstar1 said:
Yeah, I am pretty sure she has data. She is not at home, and when she left a bit ago we thought all was well (since she had the 4G indicator whereas before it said roaming) but she just used GVoice to text me to say that she cannot call or text using her VZW credentials. When you say that she needs to be in ICS, would any ICS rom do? She is in the newest version of Cleanrom right now, so I will have to flash something else I think. As for using ODIN, that is kinda out of the question because we are on vacation and the internet here sucks. It would take 2 weeks to download the stock VZW image, but if that is the only option then I guess that is how i goes. Thank you in advance for all your help!
Click to expand...
Click to collapse
I know it didn't work on some custom. I do know it works on route 66, but I've got a solution. Use mobile Odin and download the ROM straight to the phone.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
I know it didn't work on some custom. I do know it works on route 66, but I've got a solution. Use mobile Odin and download the ROM straight to the phone.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Im actually downloading a torrent of the stock image for regular desktop ODIN and it is moving fairly quickly. That being said, using a custom rom would be easier (wouldnt I not have to use ODIN at all, just flash it like a normal rom?). If that is the case, can I download your route 66 rom, boot into recovery, wipe, flash then use the dialer code?
EDIT: Whoops, I misunderstood your previous post. I think we are talking about the same thing. I am torrenting the route 66.tar file right now. You are suggesting that I use VZW 4G on her phone to dl the tar file then flash with mobile ODIN? I have never used mobile ODIN to my knowledge so I am not sure how to go about that.
EDIT 2: I just checked out mobile ODIN on the market, and that seems easy enough. So I just finish this .tar dl, put it on her SD, load the app and follow its directions to flash it. Once that is flashed, reboot and dial that code. Then Flash whatever rom I want (say, back to cleanrom). Is that about right?
Mindstar1 said:
Im actually downloading a torrent of the stock image for regular desktop ODIN and it is moving fairly quickly. That being said, using a custom rom would be easier (wouldnt I not have to use ODIN at all, just flash it like a normal rom?). If that is the case, can I download your route 66 rom, boot into recovery, wipe, flash then use the dialer code?
EDIT: Whoops, I misunderstood your previous post. I think we are talking about the same thing. I am torrenting the route 66.tar file right now. You are suggesting that I use VZW 4G on her phone to dl the tar file then flash with mobile ODIN? I have never used mobile ODIN to my knowledge so I am not sure how to go about that.
EDIT 2: I just checked out mobile ODIN on the market, and that seems easy enough. So I just finish this .tar dl, put it on her SD, load the app and follow its directions to flash it. Once that is flashed, reboot and dial that code. Then Flash whatever rom I want (say, back to cleanrom). Is that about right?
Click to expand...
Click to collapse
That's pretty much it, with mobile Odin you'll just click open file. It will put the different parts (kernel, recovery,etc) in the correct section. Then you click flash, support easy and faster then normal Odin. Also if you make a backup before doing this you can just restore your backup after fixing the network problem.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
That's pretty much it, with mobile Odin you'll just click open file. It will put the different parts (kernel, recovery,etc) in the correct section. Then you click flash, support easy and faster then normal Odin. Also if you make a backup before doing this you can just restore your backup after fixing the network problem.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
You are awesome! I am sure you factored this in to your suggestion, but if I backup her current rom, then ODIN, then restore, it will not undo what I did with ODIN, correct? Again, I am pretty sure it wont, but I was also pretty sure I knew what I was doing when I flashed CM last night and look how that turned out. Thanks again!
Same problem!!!
Mindstar1 said:
Hey guys, I am at the end of my rope here, so maybe you can help me out.
I have been dealing with the Media service bug that drains battery super fast for the last few days on my wifes rooted SGS3, and I have been jumping between roms, deleting SD files, searching for corrupt apps/media all to no avail. Tonight, in an effort to fix this issue, I flashed the most recent CM10 nightly as I heard it had a fix for this issue. I have no idea if that is true, because when I got to the setup screen after flashing, I kept getting an error that said that setup crashed and could not run. I had to boot back in to recovery, flash again, only to find the same error.
I then attempted to flash clean rom, except now I see that her phone is always roaming where my Note2 right next to it is on 4G. I flashed an older CM10 nightly for her, and the same issue popped up where it is only roaming.
Did the failed CM10 flash screw something up? How can I get her off roaming and back on 3/4G? Thanks!
Click to expand...
Click to collapse
Can someone give me a very simplified rundown to fix this problem. I flashed the CM10.1 nightly and lost service as well. I noticed someone posted the solution in the comments but i don't understand all that funky talk. PLEASE HELP
Mindstar1 said:
You are awesome! I am sure you factored this in to your suggestion, but if I backup her current rom, then ODIN, then restore, it will not undo what I did with ODIN, correct? Again, I am pretty sure it wont, but I was also pretty sure I knew what I was doing when I flashed CM last night and look how that turned out. Thanks again!
Click to expand...
Click to collapse
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
stk162 said:
Can someone give me a very simplified rundown to fix this problem. I flashed the CM10.1 nightly and lost service as well. I noticed someone posted the solution in the comments but i don't understand all that funky talk. PLEASE HELP
Click to expand...
Click to collapse
Haha, this is why CM warns us not to flash the nightlies unless we know what we are doing, which you and I did not I guess.
Basically, to get your cell signal back you need to flash back to a different firmware version. You do this through a program called ODIN which is a desktop program for Windows or a paid app in Android. I am going the paid app route mostly because it is a bit easier, but the desktop version is free.
I have not tested the solution yet, but I have read on other posts that it works. If you do the app route, you select the firmware file with the app, run the process (it should be self-explanatory in the app), then once the new firmware is on, you dial a special verizon code to get your signal stuff fixed. Below are the files you need.
http://forum.xda-developers.com/showthread.php?t=1762204 (this is the firmware file that you will flash using ODIN)
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en (this is the mobile ODIN app)
Dial *2767*3855# once you have the firmware on to in theory fix the signal issue
After that, you can reflash your rom, but do not flash the CM nightly again!
kintwofan said:
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
OK, so a bit of a hiccup. I ran ODIN with the .tar file you suggested, and after going through the expected flashing and what not, the screen went black with my LED notification light blinking blue. I pulled the battery after about 10 minutes of this, booted into recovery then rebooted and it did the same thing. Ideas?
kintwofan said:
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
To clarify, it takes me to a menu called "Android System Recovery" with the following options:
reboot system now (takes me to the black screen)
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Any idea what I should be doing or what I did wrong?
Mindstar1 said:
To clarify, it takes me to a menu called "Android System Recovery" with the following options:
reboot system now (takes me to the black screen)
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Any idea what I should be doing or what I did wrong?
Click to expand...
Click to collapse
That's stock recovery. Not sure why it's not booting correctly. I would say just use desktop Odin and re flash
If I helped you in some way.... pass on the favor and help the next person!
Did you get this fixed?
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Did you get this fixed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Its not looking good... I am in desktop ODIN and it is running, but already there was a failure in the first block, and the log says "cant open serial COM port"
Mindstar1 said:
Its not looking good... I am in desktop ODIN and it is running, but already there was a failure in the first block, and the log says "cant open COM port"
Click to expand...
Click to collapse
Make sure you have the drivers installed and have rebooted computer. Also did you verify the md5 of your download
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Make sure you have the drivers installed and have rebooted computer. Also did you verify the md5 of your download
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did not reboot after the driver install, so I will do that. As for the MD5, what is that and how do I verify? You are talking about the firmware download, right?
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.