Hello all
I had restored my captivate back to stock (no custom roms used), and when the phone decides to update itself it fails at 50% every time, is there something I did wrong while restoring?
chester_cheet64 said:
Hello all
I had restored my captivate back to stock (no custom roms used), and when the phone decides to update itself it fails at 50% every time, is there something I did wrong while restoring?
Click to expand...
Click to collapse
There is no way to get back to 100% Stock, even using Odin3. I am guessing you are talking about the over the air update, this had failed the same way for a very large percentage of people and even some that were 100% stock and never did anything to their phones.
You should be able to use Kies Mini to get the update on your phone. This has failed on some but most have had success. Here is a link for download, http://downloadcenter.samsung.com/content/SW/201009/20100928040737296/Kies_Mini_For_Captivate_10082_8_1.exe
Use the search option on this forum and you will be able to get most of your questions answered and any other information you may need by reading.
chester_cheet64 said:
Hello all
I had restored my captivate back to stock (no custom roms used), and when the phone decides to update itself it fails at 50% every time, is there something I did wrong while restoring?
Click to expand...
Click to collapse
your screenshot shows a phone that is most certainly NOT stock....
Oops, yea... I did that after I redid the voodoo fix
I'm having a lot of issues with my phone running horribly and whenever I plug it into my computer it tells me that my internal storage needs to be scanned and fixed. So either my card needs to be formatted or it's going bad. I'm assuming this could also be the cause of my phone some time taking ~10 minutes to turn on. So I have a few questions:
1) can I completely format my card and still have stock experience for exchanging it? *I went ahead and did this because I'm impatient. seems to be working and I'll keep testing it and go from there*
2) I did root and flash custom roms on it before but the rom i'm running now is a flash of the original rom on my phone but rooted. Then I updated to JH7 and it got rid of the root. When I went into the store previously and had issues with it, the guy mentioned that I had a different IMEI from what they had registered. I'm not sure if this is due to the fact of flashing or if it's from having to get the first captivate exchanged for another one. Are there any steps I can take to ensure that everything is in correct order and there's no way to see that anything has been tampered with.
Any other advice on things that should be done before going to a ATT warranty store would be greatly appreciated.
Mantu13 said:
I'm having a lot of issues with my phone running horribly and whenever I plug it into my computer it tells me that my internal storage needs to be scanned and fixed. So either my card needs to be formatted or it's going bad. I'm assuming this could also be the cause of my phone some time taking ~10 minutes to turn on. So I have a few questions:
1) can I completely format my card and still have stock experience for exchanging it? *I went ahead and did this because I'm impatient. seems to be working and I'll keep testing it and go from there*
2) I did root and flash custom roms on it before but the rom i'm running now is a flash of the original rom on my phone but rooted. Then I updated to JH7 and it got rid of the root. When I went into the store previously and had issues with it, the guy mentioned that I had a different IMEI from what they had registered. I'm not sure if this is due to the fact of flashing or if it's from having to get the first captivate exchanged for another one. Are there any steps I can take to ensure that everything is in correct order and there's no way to see that anything has been tampered with.
Any other advice on things that should be done before going to a ATT warranty store would be greatly appreciated.
Click to expand...
Click to collapse
1) yes
2) Flash back to 2.1 using ODIN and you should have everything stock including your IMEI. Not JH7 but JF6.
Hopefully you backed up your stick settings prior to flashing. Sine custom roms change your product code and imei. Flashing with ODIN will not fix the product code. I'd the imei is correct I highly doubt that the tech and the DSC knows about checking the product code but you never know. Search around XDA there has been plenty of posts surrounding this topic.
Sent from my SGH-I897 using Tapatalk
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
muziling said:
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
Click to expand...
Click to collapse
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
kifno said:
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
Click to expand...
Click to collapse
radio: 2.42.02.10.29.zip
PRL: 2.20_003
ROM: aospCMod-HC-20110421-signed.zip
no tweaks
carrier: china telecom
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
kifno said:
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
Click to expand...
Click to collapse
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
Hmp, stick with a rom that works THAT YOU LIKE, not by what I tell you. But did you try these rom's?
- CM v7.0.2?
- GingerSense?
- AOSP 0.9.9.2 Froyo?
- CM6.1-RC2?
- NFX Stock Rom?
- My Sense Roms?
Try all of those and for whichever the phone calls work, take note of that. And then also I'd like for you choose what you like the best. Also did you try the update prl/pri on a sense rom? Try doing it on the rom you're on now
And glad to see it worked for ya bud
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
il Duce said:
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
Click to expand...
Click to collapse
Yes oldghost uses a Chinese carrier and I don't think he had any issues at all. But first try updating the prl/pri
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
hareofthedog said:
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
Click to expand...
Click to collapse
Try troubleshooting the problem by doing the following things one at a time to see if they work:
- Try a different radio that works for the SPRINT HERO CDMA ONLY (else you will brick your phone, if you need help finding radios let me know)
- Try without firerat's
- Try wiping everything using the latest official clockwork mod 3.0 after backing up everything
- Try s0be's kernel
- Try the official CM7 v7.0.2
i can come up with more options for you to try one by one but that should last you for about an hour or so
after doing all those let me know what happens
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
hareofthedog said:
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
Click to expand...
Click to collapse
Glad to see its working now. If you need any more help feel free to PM me or post again in the q n a forum and the community and myself will gladly answer your question asap.
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
muziling said:
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
Click to expand...
Click to collapse
if a rom isn't broke, don't fix it...stick with gingerbread, its fresh out the oven
but seriously if cm7 works, then use it. unless if you really don't like cm7....but i doubt that..i hope
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before flashing my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Coover55 said:
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before flashing my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
We continue in the other thread
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
If u remove & insert battery, & then try entering recovery mode(Home+Power keys)...u surely have accessed recovery by now
Coover55 said:
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
Which CWM version did you use? Are you running a Stock rom?