I have a T-Mobile Galaxy S2 That i have rooted and still running the stock rom vers. 4.0.4. Everything runs fine except the ability to restart or shutdown the phone.For some reason it gets stuck on the pink goodbye screen. Also i have tried to flash different roms only to get a boot loop. The only way i can get the phone to start is to restore a old backup. Sorry for being such a noob.thanks for any help!
you have to un-root and then upgrade to the latest firmware 4.1.2 then re-root/..... the 4.0.4 had some bug when you root it wont shut down and they never fixed it from what i can tell
krazierokz said:
you have to un-root and then upgrade to the latest firmware 4.1.2 then re-root/..... the 4.0.4 had some bug when you root it wont shut down and they never fixed it from what i can tell
Click to expand...
Click to collapse
Thanks man! I really appreciate the help!
no problem man and if kies fails on you might have to take the odin approach all these tmobile firmwares that came out for this phone have all been buggy or glitchy and off course they have done nothing about it so good luck
No...the problem is not from ICS 4.04..Something is corrupted around your system or data partition...That happened to me after I used dark side wipe and restored an old nandroid backup...I had to odin to stock and that fixed it...
In your case, Odin the JB stock UVMC6 , after you reboot, boot into recovery then do factory reset .
Related
Well its been a while since I have modded this phone. I had turned it back to stock to wait for ics and I used the odin method and it worked fine. But then two days ago I wanted to try some of the new ICS roms out so I rerooted and installed the darkside ics rom and it was good but then today I see there is an update with some important patches so I decided to go ahead and update. So I pulled the odin file in the ICS thread to update but I did not wipe and go back to GB and now it installed and passed fine but the phone is not working at all. It powers on and gets to the start screen but when I press the android to get started it gives me a force close for the android services and framework. I have tried both of the odin files that I have one was the first update to 2.3.6 and the other is the newset update with the patches. But I know that the first one the original update is good because I used it a month ago to put the phone back to stock. So does anyone have any ideas? I am thinking of tring to reinstall CWM via odin then flashing the superwipe then installing a stock GB rom then tring the odin methode again. if not then maybe the keis recovery mode I dont know I will let you guys throw out some suggestions first.
mojorisin7178 said:
Well its been a while since I have modded this phone. I had turned it back to stock to wait for ics and I used the odin method and it worked fine. But then two days ago I wanted to try some of the new ICS roms out so I rerooted and installed the darkside ics rom and it was good but then today I see there is an update with some important patches so I decided to go ahead and update. So I pulled the odin file in the ICS thread to update but I did not wipe and go back to GB and now it installed and passed fine but the phone is not working at all. It powers on and gets to the start screen but when I press the android to get started it gives me a force close for the android services and framework. I have tried both of the odin files that I have one was the first update to 2.3.6 and the other is the newset update with the patches. But I know that the first one the original update is good because I used it a month ago to put the phone back to stock. So does anyone have any ideas? I am thinking of tring to reinstall CWM via odin then flashing the superwipe then installing a stock GB rom then tring the odin methode again. if not then maybe the keis recovery mode I dont know I will let you guys throw out some suggestions first.
Click to expand...
Click to collapse
After flashing through Odin did you factory reset the phone? I believe it is a must when flashing back to GB via Odin from ics.
Sent from my SGH-T989 using xda premium
okay update I sucsessfully installed cwm through odin then I was able to superwipe and install good ol juggs 5.0 phone works fine now so the next step is to figure out why those odin packages did not work I guess I will redownload them and try again. Will keep this thread updated for anyone else having problems
No I did not factory reset because I could not get into the phone to do so althought I guess I could have just used the key combo to do it but I didnt even think of that. Anyway I am now back on a gb rom and I am trying again thanks for the info though.
Okay that was the problem. I guess if you want to odin back to a gb stock from ics you should install a gb rom first then run the odin package. Or if you forget then try the key combo for the factory reset. I dont know if that will definitly work but it makes sence. but the first thing i said is what worked for me. So now all is well I am now stock gb.ULVDE 2.3.6 with kernel 2.6.35.11 and that is how I will stay until the ics update comes out. Thanks for trying to help out
Hey all need help bad and fast. So yesterday I attempted to flash my phone back to stock so I can do the new firmware update as I'm in Canada with Telus. Everything seemed to be working fine and ODIN flashed the rom just fine, but my phone since then has been stuck at the SAMSUNG screen with glowing font after the boot animation, I made an attempt last night and it stayed on that screen all night, now at work I've flashed the latest rom from the "[Guide] Installing LH1 OTA for Canadian S3" but it's the same thing, I'm not sure what's going on or how I should restore it as the options I use in the toolkit and odin seem to just get me to this screen and stop there. Please help guy I need it.
See the last post in this thread
Shels said:
Hey all need help bad and fast. So yesterday I attempted to flash my phone back to stock so I can do the new firmware update as I'm in Canada with Telus. Everything seemed to be working fine and ODIN flashed the rom just fine, but my phone since then has been stuck at the SAMSUNG screen with glowing font after the boot animation, I made an attempt last night and it stayed on that screen all night, now at work I've flashed the latest rom from the "[Guide] Installing LH1 OTA for Canadian S3" but it's the same thing, I'm not sure what's going on or how I should restore it as the options I use in the toolkit and odin seem to just get me to this screen and stop there. Please help guy I need it.
Click to expand...
Click to collapse
if you flashed a custom kernel you may need to flash your stock kernel if you want the stock rom to run properly. whend you flashed your stock rom did you perform a full wipe (format data/ factory reset, wipe dalvik, format system, format cache) ?
also, are you sure you have the proper stock kernel for your device?
Shels said:
Hey all need help bad and fast. So yesterday I attempted to flash my phone back to stock so I can do the new firmware update as I'm in Canada with Telus. Everything seemed to be working fine and ODIN flashed the rom just fine, but my phone since then has been stuck at the SAMSUNG screen with glowing font after the boot animation, I made an attempt last night and it stayed on that screen all night, now at work I've flashed the latest rom from the "[Guide] Installing LH1 OTA for Canadian S3" but it's the same thing, I'm not sure what's going on or how I should restore it as the options I use in the toolkit and odin seem to just get me to this screen and stop there. Please help guy I need it.
Click to expand...
Click to collapse
Do you have cwm(clock work mod) installed?
Hey, not sure why i can't update to jb leak ota 4.1.1 . I had no issues doing it on my GF's sgs3 t999. I am on uvalh2 stock, i renamed it to update.zip on the external sdcard, i put usb debugging on, and after i applied update from external sdcard it said "emmc/dev/block/mcbl####". My phone is rooted but not sure if that's the problem. If anyone can help me that would be awesome. Thanks in advance,
Jake
Before you go down that road....
themadzionist said:
Hey, not sure why i can't update to jb leak ota 4.1.1 . I had no issues doing it on my GF's sgs3 t999. I am on uvalh2 stock, i renamed it to update.zip on the external sdcard, i put usb debugging on, and after i applied update from external sdcard it said "emmc/dev/block/mcbl####". My phone is rooted but not sure if that's the problem. If anyone can help me that would be awesome. Thanks in advance,
Jake
Click to expand...
Click to collapse
See my thread below- It can be done if you return to unrooted stock, but then the fun really begins as I cannot now root. On the plus side the ROM is awesome and runs perfectly- SMS and Calls over WIFI work. I think they are VERY close to release.
I am reflashing 4.04 to get Root back
My thread: http://forum.xda-developers.com/showthread.php?t=1883359
Fonz said:
See my thread below- It can be done if you return to unrooted stock, but then the fun really begins as I cannot now root. On the plus side the ROM is awesome and runs perfectly- SMS and Calls over WIFI work. I think they are VERY close to release.
I am reflashing 4.04 to get Root back
My thread: http://forum.xda-developers.com/showthread.php?t=1883359
Click to expand...
Click to collapse
Thanks fonz, I'm going to try that. But if i have to unroot with i update to JB. Can i access CWM to restore nandroid backup? I wonder if the issue you are having is the same that i had. When i flashed cwm with odin, i had to make sure auto reboot was not checked, and after it passes, pull the battery and go straight into cwm. If it restarts it goes back to Android stock. I had that issue With uvlah2. I'm not sure if that's an issue with 4.1.1 too. But if i can't access cwm after updating to JB i think ill wait till the update, because i just wanted to test it and then restore nandroid B. i wish there was an exact date for JB release, I'm getting kinda antsy. Every JB custom rom I've flashed had too many bugs to stick with. thanks again
Jake
themadzionist said:
Thanks fonz, I'm going to try that. But if i have to unroot with i update to JB. Can i access CWM to restore nandroid backup? I wonder if the issue you are having is the same that i had. When i flashed cwm with odin, i had to make sure auto reboot was not checked, and after it passes, pull the battery and go straight into cwm. If it restarts it goes back to Android stock. I had that issue With uvlah2. I'm not sure if that's an issue with 4.1.1 too. But if i can't access cwm after updating to JB i think ill wait till the update, because i just wanted to test it and then restore nandroid B. i wish there was an exact date for JB release, I'm getting kinda antsy. Every JB custom rom I've flashed had too many bugs to stick with. thanks again
Jake
Click to expand...
Click to collapse
That may be it! I will try that next. I had auto reboot on and it went to stock as you say. I have reverted the phone twice today so if you want to play you can. The ROM is really excellent. I think I will try one more time and then wait for release or at least for an Odin compatible ROM (tar.md5)
Just make certain to have Titanium Backups- I could not easily restore from Nandroid, but Titanium worked well. I restored by reflashing stock and then rooting again. Then restore from Titanium...
Fonz said:
That may be it! I will try that next. I had auto reboot on and it went to stock as you say. I have reverted the phone twice today so if you want to play you can. The ROM is really excellent. I think I will try one more time and then wait for release or at least for an Odin compatible ROM (tar.md5)
Just make certain to have Titanium Backups- I could not easily restore from Nandroid, but Titanium worked well. I restored by reflashing stock and then rooting again. Then restore from Titanium...
Click to expand...
Click to collapse
Oh yeah that's a great idea. I didn't think of that, so basically flash stock back through odin and then after rerooting, restore nandroid backup. I'm going to try it now. And yeah, uncheck the auto reboot, after it passes, exit odin and just pull the battery out or just power off, and then vol up + home + power and you should go straight to cwm, don't let it start up or else you lose cwm and will have to reflash. And what sucks is that every time it boots up you lose cwm but i just flash CWM thru rom manager everytime and after it flashed i just hit reboot into recovery. Thanks again Fonz
I am rooted running Jellybean on Sprint Samsung Galaxy S3, tried to install wi fi tether kept asking for superuser permission then froze. On rebooting phone is stuck on samsung logo. Tried unbricking by flashing stock rom with Odin, no success. Is it because I am on Jellybean and am trying to revert to ICS? Please help someone!!! Thanks in advance.
trinihoney said:
I am rooted running Jellybean on Sprint Samsung Galaxy S3, tried to install wi fi tether kept asking for superuser permission then froze. On rebooting phone is stuck on samsung logo. Tried unbricking by flashing stock rom with Odin, no success. Is it because I am on Jellybean and am trying to revert to ICS? Please help someone!!! Thanks in advance.
Click to expand...
Click to collapse
Its because you reverted and didnt wipe data. Reboot to recovery and factory reset
billard412 said:
Its because you reverted and didnt wipe data. Reboot to recovery and factory reset
Click to expand...
Click to collapse
Unfortunately, forgot to mention I tried that several times ....no success. Thank you for your reply.
That's odd. Well if youre trying to revert to ics try flashing this in Odin then. This should set you straight
http://forum.xda-developers.com/showthread.php?t=1774722
Thanks
billard412 said:
Its because you reverted and didnt wipe data. Reboot to recovery and factory reset
Click to expand...
Click to collapse
Unbelievable, I decided to try that one more time after you posted....and Voila! It works!!!! Thank you again!!!:good::laugh:
For the jb odin tar go here
http://forum.xda-developers.com/showthread.php?t=1941546
And btw don't know why you froze but superuser popping up 15 times was normal. I recommend using super su with that wifi tether app
Same thing happened to me
So I am on Stock jelly bean which I downloaded the OTA from here and I am rooted. After installing the wifi mod I went to start it and it keeps asking for superuser permissions over and over. Then it said something about you phone is operating at a unstable state please reboot you phone and now it will not bootup, it gets to the Samsung word after the sprint logo and stays there. I have tried booting into safe mode by holding down left button at logo, by tapping it while it boots. Nothing. Any help would be appreciated.
What the hell this cant be coincidence.
I really need data from an app any suggestions?
dlovedesigns said:
So I am on Stock jelly bean which I downloaded the OTA from here and I am rooted. After installing the wifi mod I went to start it and it keeps asking for superuser permissions over and over. Then it said something about you phone is operating at a unstable state please reboot you phone and now it will not bootup, it gets to the Samsung word after the sprint logo and stays there. I have tried booting into safe mode by holding down left button at logo, by tapping it while it boots. Nothing. Any help would be appreciated.
What the hell this cant be coincidence.
I really need data from an app any suggestions?
Click to expand...
Click to collapse
Use the link I provided for the jb odin tar. I would recommend the deodex version for you. Shouldn't have to wipe data
Ok ill try
billard412 said:
Use the link I provided for the jb odin tar. I would recommend the deodex version for you. Shouldn't have to wipe data
Click to expand...
Click to collapse
Thanks Ill give it a try.
But just to confirm I flashed the OTA JB when it first was release from a Sprint update. I am stock rooted with custom recovery and possibly I shouldnt have to wipe data.
Worked!
dlovedesigns said:
Thanks Ill give it a try.
But just to confirm I flashed the OTA JB when it first was release from a Sprint update. I am stock rooted with custom recovery and possibly I shouldnt have to wipe data.
Click to expand...
Click to collapse
Excellent I flashed the deodex version in previous reply and the pulled battery after flashing in Odin and booted straight in, no data loss.
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
JaedenRuiner said:
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
Click to expand...
Click to collapse
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
lvpre said:
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
Click to expand...
Click to collapse
I eventually found a 4.4.2 full stock ROM and was able to get that over. Of course this wasn't until after some sight suggested a wipe user data could help, so I'm re-building the phone from the base...*sigh* It happens. I'm about due for an upgrade anyway, so I can make due.
Thanks for the response,
J"SD"a'RR