I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
Related
First off this is my first post, and I gotta thank everyone cause I've been able to do some cool stuff with my phone and without the support of the community and the vast knowledge some of the guys (and gals) have on xda, I would be just another average consumer. And I'm still learning.
So a few days ago I tried to update my rooted Vibrant (with the lag fix) through Tmobile, like a noob, without unrooting my phone and everything was going great until the phone rebooted and got stuck on the "Samsung" startup screen.
I was able to fix that after reading through the odin3 fix and got the phone up and running again. Decided I didn't need froyo that bad and just reinstalled all my old stuff with Titanium backup.
Then after reading through the forums a little more I got the itch to try 2.2 again, so I was a little smarter this time, undid the lagfix, unrooted the phone and started the update. But once again, frozen at the "Samsung" screen...
Odin to the rescue again. But this time as odin was doing its thing, the power went out in my house, ughhh! Got everything back up and running and when I tried to turn the phone on it goes to a screen I haven't seen before, with a "phone" icon, two dots, a "triangle caution" icon, two dots, and a "computer" icon, and it wont get out of it. It won't connect to my computer so it won't connect to odin.
I'm usually decent at finding the solutions on the forums and I could have sworn I read somewhere about this type of problem, but I guess I'm wording my searches wrong so nothing is coming up.
So how do I get my phone out of this mode? Or is it bricked?
Also does anyone now why the phone would freeze like that after the update? I probably should have just flashed one of the froyo roms, but I figured it would be easier to return if the OS was from Tmobile.
steambrick said:
First off this is my first post, and I gotta thank everyone cause I've been able to do some cool stuff with my phone and without the support of the community and the vast knowledge some of the guys (and gals) have on xda, I would be just another average consumer. And I'm still learning.
So a few days ago I tried to update my rooted Vibrant (with the lag fix) through Tmobile, like a noob, without unrooting my phone and everything was going great until the phone rebooted and got stuck on the "Samsung" startup screen.
I was able to fix that after reading through the odin3 fix and got the phone up and running again. Decided I didn't need froyo that bad and just reinstalled all my old stuff with Titanium backup.
Then after reading through the forums a little more I got the itch to try 2.2 again, so I was a little smarter this time, undid the lagfix, unrooted the phone and started the update. But once again, frozen at the "Samsung" screen...
Odin to the rescue again. But this time as odin was doing its thing, the power went out in my house, ughhh! Got everything back up and running and when I tried to turn the phone on it goes to a screen I haven't seen before, with a "phone" icon, two dots, a "triangle caution" icon, two dots, and a "computer" icon, and it wont get out of it. It won't connect to my computer so it won't connect to odin.
I'm usually decent at finding the solutions on the forums and I could have sworn I read somewhere about this type of problem, but I guess I'm wording my searches wrong so nothing is coming up.
So how do I get my phone out of this mode? Or is it bricked?
Also does anyone now why the phone would freeze like that after the update? I probably should have just flashed one of the froyo roms, but I figured it would be easier to return if the OS was from Tmobile.
Click to expand...
Click to collapse
Email me [email protected]
Thegreat520 said:
Email me [email protected]
Click to expand...
Click to collapse
That's nice of ya GreatOne
+1 vote for personalized help...
~SB
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
The last link you put up is a theme, not a Rom. Which ROM are you currently using?
Be sure when changing roms to wipe data and cache. Not doing so will cause a boot loop, which you described above. Also, if you have to reactivate your phone and can't get a dial pad, long press the menu button to bring up the keyboard and use the keyboard numbers.
Sent from my ultra fast Liberated Droid 2
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
I don't know what all roms you have tried that won't boot but there was one person who's phones could not boot my cfsv6 through cfsv8 kernels. I fixed the issue in cfsv9 kernel so check to see if the roms you have tried are using those kernels. I know the one you said booted was an older rom and was not using my kernel. CELBFroyo is using the v9 kernel if you want to test that. If that is your issue you can just download the cfsv9 kernel and flash it after flashing the rom of your choice. It was something to do with the hardware in a small percentage of eris's that the kernel would not work with. Maybe you have the same hardware as that case...
This is the deal:
I bought my wife and I Vibrants back in February and from the minute I got it I started looking into updating from eclair.
I was following the info on xda after researching about rooting phones, so I rooted my phone using the Superonclick method. Just before getting ready to flash custom roms, I read that froyo was available through kies. So I did that. It worked well enough for me, so I updated my wife's phone as well and hers works beautifully. I also changed the home launcher to LauncherPro. love it.
Mine however has been going on the fritz. I'm in the middle of using an app or I'm doing nothing at but turning on my phone and the screen will be all black with nothing but the notification bar showing.
The media scanner is constantly running.
No gsm is detected.
I keeps vibrating after touching the screen.
No amount of turning it on and off gets it past that state.
It just randomly decided to start working on its own.
Any Ideas?
Should I unRoot my phone. I don't want to,
I'm still researching changing the bootanimation, (waiting for a Portal 2 theme, also researching how to do it myself).
SOS guys.
sorry if tldr.
I would suggest restoring your phone back to stock Via Odin, and starting fresh. The problem you most likely had is that you updated to Froyo through Kie's while your phone was rooted.
Or, at the very least do a factory reset on your phone.
But if you need to go the Odin route, just search the forum, can't miss it.
oh wow, I didn't know that was an issue updating while rooted. I must have missed something while reading (so many threads -_-).
Guess I have some more light reading to do...
thanks.
Did a little research, should I unroot my phone first before factory reset? or is there a method that will take care of removing the root?
Hello folks of XDA,
I came here because I have not heard any response on the MIUI forums and UI guess is because the community over there is not as big.
Anywayas, I flashed 1.8.5 MIUI, and I suddenly could not see the screen after I dialed a phone number. Then I also noticed that I could not see the answer screen when someone called me.
Everything else worked like a charm, so I thought to myself, well, maybe I have not been back on JFD for a while, so I went ahead and restored the phone back to stock, follow even the MIUI procedure for the massive JFD restore, and it does not matter.... Any Rom from stock to MIUI or CM7.1 all give me the same problem or an app force close, of phone freeze. I can hear the person on the other side if I call, but there is no human way I can answer the phone.
I believe the phone.apk might be the problem, but after trying to do all kinds of factory reset and format, I am still in the same place.
So my first question is, is there a way to fully format the phone and put it with stock apps. Like out of the box? using CWM gives you the option to format the mount points, but I am afraid to format everything and then have a true bricked phone.
Any comments suggestions, questions, please let me know. I been working on this for 2 days now with no avail.
Bump. I have no phone, so it is very frustrating
So I called tech support and see if they had any idea of what could it be. in the end I am back on stock, so what more harm can I do to it right? Well the tech said something that really leave me thinking. He said that the proximity sensor could be damaged. Now that makes a lot of sense, in the end the phone is already somewhat old and I have had my mishaps dropping it from time to time, but luckly no scuffs on it. What do you guys think?
This though is gonna mean that I have to go get me a new phone today ....
Hello XDA,
I apologize in advance if this topic has been covered, but I cannot seem to find any threads describing the problem I have.
Please read below the post that I have put in the Noob Guide thread... After attempting to root my Note for the first time, somehow during the initial process the touch-buttons have completely stopped working
"I don't know how or why, but the touch buttons on the bottom of the phone are no longer working. Is it broken? I was using the stock ICS version on the Note, decided to root it using your guide. I followed the steps, but it locked up on the Samsung logo on bootup. So I then went to restore the phone to stock and try again, and now the buttons are not working at all??? What happened??
By the way, the touch screen is working totally fine. I just cannot press the home, menu, back and search buttons. Also, when I followed the process to bring the phone back to stock, the phone would hangup during boot as well. It would freeze this time on the ATT white and blue logo screen. I followed the advice by Da G and did a factory wipe, and then it finally booted up, but no buttons!!! How do I fix this??
So I've been experimenting as much as possible to try and figure out where I went wrong in this process to break the capacitor buttons. I've tried flashing the stock rom through Odin several times, still no buttons. Without the use of the buttons, I've been able to flash CWM and root the phone, and then was able to flash a rom with no problems at all (since CWM only uses the volume and power buttons to function). I chose a random rom and flashed it, Novena (Alliance Rom), and that process went smoothly. But I still have no touch buttons!!!! What happened??
Is this an unfixable problem? Considering I've been able to do anything with the phone except for touch the buttons, it doesn't seem like it would be a software problem.. But what could I have done to break the buttons? I'm so frustrated.. am I going to have to claim a new phone through insurance? If so, I'm pretty damn scared of trying to root the phone again!"
I would take a look at the ussd codes and see if there is one to test this specific setting!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Thank you for the reply! I looked through all the USSD codes on this thread: http://forum.xda-developers.com/showthread.php?t=1953506&highlight=ussd+code
I could not find anything that would help me. In CWM boot menu, there is a "Key Test" feature in the Advanced section. When I choose that, it registers "Key: 114, 115", etc. when I press the volume up, down and power buttons, but there is no reaction when I touch the capacitive buttons. It says that you have to press "Back" to get out of this test mode, so I'm stuck in the mode and have to reboot since the stupid button doesn't work. >_<
I'm so frustrated. Has anyone ever had this problem?? It seems so bizarre...
that happen to me with my brand new skyrocket.something went during root process.i couldnt fix it.i tried everything.i end up calling att .they replaced it with refurbished unit.good luck.you must have done something wrong while rooting.because samsung phones are hard to ****up.i know what i did.i ran a app from playstore to unlock sim after i rooted it.thats what messed up my buttons.
mintu123 said:
that happen to me with my brand new skyrocket.something went during root process.i couldnt fix it.i tried everything.i end up calling att .they replaced it with refurbished unit.good luck.you must have done something wrong while rooting.because samsung phones are hard to ****up.i know what i did.i ran a app from playstore to unlock sim after i rooted it.thats what messed up my buttons.
Click to expand...
Click to collapse
Aw man, that's discouraging. I can cough up the $200 and get a replacement phone through insurance, but now I'm scared to root it again! I don't know what I did wrong.. I followed all the steps I was supposed to as far as I know.
If I get a replacement phone and try to root it, if this happens again the warranty is void right? So I'd have to go through insurance again to get a new one?
only time i have seen this happen was with a friends epic touch. he flashed a rom for different galaxy sii device. it booted and only problem was buttons not working. you do have a note i717? just checking. you could flash a rom that you can enable navigation bar with onscreen buttons. i am running eclipse and it has this feature and i dont have any problems with rom.
s89281b said:
only time i have seen this happen was with a friends epic touch. he flashed a rom for different galaxy sii device. it booted and only problem was buttons not working. you do have a note i717? just checking. you could flash a rom that you can enable navigation bar with onscreen buttons. i am running eclipse and it has this feature and i dont have any problems with rom.
Click to expand...
Click to collapse
Thanks for the reply.. That is actually a good idea, I will have to try that if the buttons break again. I say "again" because **update** the buttons are magically working now!! Wtf?? I received a phone call and talked for a bit, set the phone down and when I picked it up again the buttons are all working like nothing was ever wrong.
Of course, they magically started working AFTER I called Assurion and ordered a replacement... Ugh. That is the second time I've ordered a replacement and cancelled it.
Another update...
They're broken again. UGH. No idea why or why they started working for a few minutes. I'm getting that replacement phone and I'll try again. I really hope it doesn't happen again...