Related
Long time lurker, but i dont think i have posted before...so sorry if this is on the wrong place/already been answered, if that is the case i would love be be redirected to where i should go.
Anyways, after updating this morning, everything worked fine other that some occasion lag. But when i opened up handcent, it was just a black screen. so i reinstalled it, and still no dice. the default messaging app had the same problem. If someone texted me i wouldnt get it, and there was no way for me to send out a text. then, when my battery went down to red, all of a sudden it worked like normal. i was able to charge it and even when the battery was full it still worked. However, when i reset my phone, it stopped working again, and resumed working when my battery got to red. Im pretty sure those are the only symptoms i noticed...Any ideas on what is going on/what i can do to remedy it?
And fyi, i was rooted before the upgrade and have rooted since. I had oclf, but disabled it before i upgraded.
Shameless bump, I really need help
Only thing I can think of is a bad install of the update. I would suggest going back to 2.1 using odin and then reinstalling the froyo update
Sent from my SAMSUNG-SGH-I897 using XDA App
So step one of http://forum.xda-developers.com/showthread.php?t=884364
Then follow the installation of 2.2 as samsungs website outlines? Would that require me to restore all of my apps and settings from tibu again?
Thanks
ahurley said:
So step one of http://forum.xda-developers.com/showthread.php?t=884364
Then follow the installation of 2.2 as samsungs website outlines? Would that require me to restore all of my apps and settings from tibu again?
Thanks
Click to expand...
Click to collapse
Yea if you are going to flash back to odin you will need to back up all user apps using titanium backup. Make sure you do not restore any system apps though as that can cause problems. Also you will lose your texts so I would recommend backing them up. I use sms backup+
Sent from my SAMSUNG-SGH-I897 using XDA App
My friend had the same problem and had to go back to 2.1 and re-install the update and then it worked. Seems like the update didn't install correctly on a handful of Captivates.
okay so i still haven't done this because of how long restoring everything with tibu takes, but if I am gonna have to go through this process again, should i just make my first venture into flashing a custom rom? Am i correct in thinking that flashing wont be messed up because of the current glitch i have because it all reverts back to stock as the first step anyways?
So I found a trader who's looking for a Droid Charge, but he wants the phone to be completely stock, no root, CWM, or roms of any kind. I am currently running a rooted, lagfix enabled, EE2 rom from imnuts and I want to know the proper steps to fully get the phone back to stock settings with no root, CWM, or anything loaded. Can anyone link me to a guide or just tell me in what order to do things? Thanks!
Before I start I'd just like to say I haven't personally tested this yet, this is just what I've heard on these forums.
First you should disable Voodoo(you always want to do that before flashing) and then flash this
http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!
OR this
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
Again, I haven't personally done this so if I were you I would wait for another response to confirm this before doing anything.
Tried it
I tried the method from the mydroid forum. It worked great despite me being unable to diasble the voodoo for whatever reason (I just wiped everything I could through CWM). I am still a bit worried but I have't received one error or hiccup since reflashing to stock last night. Go for it, super easy.
braveally said:
I tried the method from the mydroid forum. It worked great despite me being unable to diasble the voodoo for whatever reason (I just wiped everything I could through CWM). I am still a bit worried but I have't received one error or hiccup since reflashing to stock last night. Go for it, super easy.
Click to expand...
Click to collapse
So when you re-flashed to stock, CWM was removed as well?
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
I used the my droid world link referenced in the post above. I tried the gingerbread leak and wanted to go back to the old baseband due to bugs. It worked perfectly, it took me back to the way the phone was shipped.
I believe it was. But I haven't tried too load it up since I got the tom back up. Well try in a bit
Sent from my SCH-I510 using XDA Premium App
Hello everyone. It seems like the issue is getting worst and I think I've narrowed down the problem... Now I just need a solution and we can all be happy
So sometimes my phone decides to restart itself and it will not boot back up. The only solution is to remove the battery and try again. It could be solve after a couple tries in the past, and now I find myself sitting for half an hour + trying to get this phone running again. I do have clockwork installed, and it seems like my issue is with my SD card. When trying to mount/unmount my SD card via clockwork, there is an error doing do. Sometimes I can't access my pictures because of the same problem. Does anyone know if there is anything I can do to remedy this situation?
Thanks!
ritzbits said:
Hello everyone. It seems like the issue is getting worst and I think I've narrowed down the problem... Now I just need a solution and we can all be happy
So sometimes my phone decides to restart itself and it will not boot back up. The only solution is to remove the battery and try again. It could be solve after a couple tries in the past, and now I find myself sitting for half an hour + trying to get this phone running again. I do have clockwork installed, and it seems like my issue is with my SD card. When trying to mount/unmount my SD card via clockwork, there is an error doing do. Sometimes I can't access my pictures because of the same problem. Does anyone know if there is anything I can do to remedy this situation?
Thanks!
Click to expand...
Click to collapse
are you using a custom rom or kernel?
I used to, but now it is just stock rom rooted
Edit: I lied, seems like when I restored, the kernal stayed the same.... I assume I can just flash a stock kernal over my modded one?
ritzbits said:
I used to, but now it is just stock rom rooted
Click to expand...
Click to collapse
have you tried redownloading the rom and reflashing it?
Note the edit above. Just checked my settings and it looks like I still have my old kernal..( non stock) I dont seem to be able to find a stock kernal anywhere... Do you happen to know where I can find one?
theres probably a version of the stock rom floating around with the stock kernel already included. check the developement threads.
Stock rom, check stickies in General section.
Sent from my Nexus S using XDA App
I reverted everything back to stock with the exception of the bootloader still being unlocked. I thought the issue was fixed, and I have not had issues with the phone since. Until today when I decided to restart it. Same issues as before not being able to mount the sd card, which seems to be required to boot. Any ideas? Is the sd card in the nexus s actually there? Maybe it came loose?
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Sounds to me that you obviously are not getting a true "PASS" with pit file. If you had you would have no files saved on phone. But if you followed the instructions to a "t" like you allude to...
Sent from my SCH-I510 using xda premium
I have followed the instructions fully (and multiple times to boot), and I have always gotten a PASS.
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
dwitherell said:
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
Click to expand...
Click to collapse
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
jderig said:
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
Click to expand...
Click to collapse
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Hindle1225 said:
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I currently have Clockwork. I am unable to tell at this moment what my file system is, as I can't install Voodoo, and the method of adding/deleting folders on my SD card doesn't work. However, I do recall during one of my many attempts at using different kernels/radios/roms I did get the creepy female Voodoo bootup voice, but even though that said it was a success I was never able to tell whether it actually worked.
As of right now I am capable of ODIN and Clockworking any Rom/kernel/etc., but they all bring along the Ghost Image.
kvswim said:
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
jderig said:
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
Click to expand...
Click to collapse
NAND is just a type of flash memory. If you recognize the word nand then you should have an idea. If not, it's not really important.
jderig said:
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Click to expand...
Click to collapse
just covering bases by asking, did you go ALL the way back to ed1 with that pit file or a more recent version (gb or something along those lines)
From what I understand, the phone is still working, but is very unstable. The PBJ kernel does NOT support Voodoo Lagfix (but still supports EXT4). Can you try flashing imoseyon's kernel (which supports it) and enabling/disabling Voodoo? It can be found at RootzWiki. Also, when you get into CWM, it says the version at the top.
Sent from my SCH-I510 using xda premium
Here you go....i have been here.
Get into clockwork(CWM) - mount everything via usb and backup what you need to backup.
Perform a quick format of your sdcard so that when you see your phone on the pc, its blank.
Go back to stock odin and boot up, report any issues.
Sent from my SCH-I510 using XDA
What happened next
I tried what you said because I'm in the same boat. I still get the FCs and it tries to walk me through the setup. It gets stuck at the Checking Account step in the setup wizard. I let it sit there for about an hour while I went to lunch to no avail.
So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.