I have been running Franco's Kernal and a stock 4.0.4 rom for a week or more now. I have had ZERO issues, and the phone was running flawlessly.
A few min ago I got a reboot when surfing the web, and when it restarted Nova launcher was not responding and kept flashing an ERROR message. I had to turn it off from the lock screen.
When I rebooted into recovery ClockWork was gone, and I got the android on his back with the red sign. I finally got it to the stock recovery and tried to wipe but it hung. Now I am getting a boot loop.
What is the best way to go about resolving this?
Thanks for any help!
Try doing mskip toolkit from scratch and that should solve it. Do you remember what your build # was?
Sent from my Galaxy Nexus using XDA Premium App
I was using WUGS toolkit. Should I just use the option to put the phone 100% back to stock?
I can't even begin to guess what happened..lol
this is why i always stay away from "leaked".
East_Coast said:
I was using WUGS toolkit. Should I just use the option to put the phone 100% back to stock?
I can't even begin to guess what happened..lol
Click to expand...
Click to collapse
That's your best bet for now.
Sent from my Galaxy Nexus using XDA Premium App
Related
like a month ago, my gsm nexus started to close every app and it got not useable. the problem is when i open the phone, it closes everything one by one. sometimes phone says launcher has stopped. when i try to flash aokp rom via cwm, it stucks at boot screen. so i can flash only stock roms. i tried 4.0.2 and 4.0.4 but nothing changed. sometimes it restarts itself. i don't know it is a hardware problem or software problem. how can i fix it?
Your best bet is to download the GNex Toolkit and use it to flash the Google Stock Image to the phone. From there you can update to Jellybean. That should fix your problem.
Geo411m said:
Your best bet is to download the GNex Toolkit and use it to flash the Google Stock Image to the phone. From there you can update to Jellybean. That should fix your problem.
Click to expand...
Click to collapse
Yes, but not via toolkit. Use Fastboot.
Smart step is to return to stock and rule out software issues.
Sent from my Galaxy Nexus using xda premium
martonikaj said:
Yes, but not via toolkit. Use Fastboot.
Smart step is to return to stock and rule out software issues.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i tried to flash stock rom via Gnex toolkit. actually this is the only way to open my nexus. but problems didn't solve. other roms stuck at the boot screen. i also tried to flash jelly beam. it is also stucked at the boot screen. but i did it via fastboot. is there another way to update it? how can i update it?
Hey guys, I need some help,
I have been using CleanGB v1.1.2 for a long time. Recently, I've been having a huge problem. Whenever I use ANY ROM, after about ten to twenty minutes, my phone just becomes *slow* as molasses. It's unnerving. It could be at the bootloader screen... it could be in the ROM itself... but if I'm using ANYthing but the stock ROM with everything unrooted, the phone just goes slow-as-*&#^-as-*&&& and I have to pull the battery out after ten to twenty minutes.
Any ideas?
My ROMs aren't corrupted. I've tested them all and I've tried installing and rooting from different computers with the same problem. I have tried CleanGB v.1.1.2 and People's 2.2.1 and Thunderhawk 5.1. All have the same problem after ten to twenty minutes.
EDIT - I should add that I have rooted (even as of today) other people's Epic 4Gs and none of them have had the same issue as mine, so I know there's something going on with my phone, in particular.
The only thing I can think may be doing this is that I use the CWM flash + the FC09 rom method to root my phone. Maybe I should be rooting it using Odin as I used to do back in the day.
When I go back *from* the root to the unroot, I always re-partition and time reset in Odin with a stock ROM. No problems after that.
Hoppingfully yours,
--SLN
Sadie, I root by odining cwm with auto reboot unchecked, pop battery out and in, 3 finger to cwm and flash ROM of choice. It definitely sounds like a strange issue.
Sent from my PantechP4100 using xda premium
kennyglass123 said:
Sadie, I root by odining cwm with auto reboot unchecked, pop battery out and in, 3 finger to cwm and flash ROM of choice. It definitely sounds like a strange issue.
Sent from my PantechP4100 using xda premium
Click to expand...
Click to collapse
Hey KG,
Yeah, I think I need to go back to performing the rooting procedure from ODIN. I just can't seem to find the links to that online. God, I've turned into an ultra-n00b again.
What do *you* think is the best way to root using ODIN? I think the problem is that I've been rooting using the easier, flash-to-CWM in Odin and then flash the rooted ROM from CWM. I think I need to do it all from ODIN and repartition at that level.
Epic Touch or S3 here I come! LOL!
--SLN
Here you go:
http://forum.xda-developers.com/showthread.php?t=1052813
That'll give your phone the enema it needs...LOL.
SadieNibblesworth said:
Hey guys, I need some help,
I have been using CleanGB v1.1.2 for a long time. Recently, I've been having a huge problem. Whenever I use ANY ROM, after about ten to twenty minutes, my phone just becomes *slow* as molasses. It's unnerving. It could be at the bootloader screen... it could be in the ROM itself... but if I'm using ANYthing but the stock ROM with everything unrooted, the phone just goes slow-as-*&#^-as-*&&& and I have to pull the battery out after ten to twenty minutes.
Any ideas?
My ROMs aren't corrupted. I've tested them all and I've tried installing and rooting from different computers with the same problem. I have tried CleanGB v.1.1.2 and People's 2.2.1 and Thunderhawk 5.1. All have the same problem after ten to twenty minutes.
EDIT - I should add that I have rooted (even as of today) other people's Epic 4Gs and none of them have had the same issue as mine, so I know there's something going on with my phone, in particular.
The only thing I can think may be doing this is that I use the CWM flash + the FC09 rom method to root my phone. Maybe I should be rooting it using Odin as I used to do back in the day.
When I go back *from* the root to the unroot, I always re-partition and time reset in Odin with a stock ROM. No problems after that.
Hoppingfully yours,
--SLN
Click to expand...
Click to collapse
This sounds like a rogue app sucking up your memory. Does it happen on stock with all your apps restored?
It happens with every Rom I use. When I flash my phone back to stock the problem goes away.
Sent from my SPH-L710 using xda premium
After you root have you updated superuser and it's binaries?
Sent from my SPH-L710 using Tapatalk
SadieNibblesworth said:
It happens with every Rom I use. When I flash my phone back to stock the problem goes away.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Is it happening with your new phone as well? I recommended flash the rom of your choice do not install any apps for a day or two. If all is fine install one app a day till you find which app. My guess would be a app that you use that needs root because it doesn't happen on stock. Just my 2 cents.
Sent from my SPH-D700 using Tapatalk 2
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250
Back story...
Using a T-Mobile S3, tried to load a T-Mobile JB build, it went sideways and would get beyond the Samsung Galaxy S3 boot screen.
Current location...
Used Odin with stock firmware, it loads the OS back on through Download, but boots to the pulsing Samsung logo and stays there. I know it should take 5 to 10 minutes to finish up, but I've been looking at this for close to an hour now.
Tried rooted and non rooted versions of ICS in hopes of getting to a working point. Was using Clockwork for recovery, but that seems to have gone tits up when the update didn't work.
Thoughts?
Ignore this... seems I was able to reload Clockwork through Odin and start over, finally
Reboot recovery, factory reset. Almost always solves this problem.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Reboot recovery, factory reset. Almost always solves this problem.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Recovery has not been reachable since the rom flash went bad, my only option has been Odin, which I've used a few times at this point in an attempt to get into a stock version of the OS with no luck. The Samsung Galaxy S3 logo boots up, the Android logo comes up next and then I get Samsung just pulsing. Everything I've seen says to let it set about 5 - 10 minutes after the restore and it should be fine, but it hasn't been.
Usually if it'll boot at all and you can get download mode you can also get to recovery. Oh well, glad you got it fixed!
Sent from my SGH-T999 using xda app-developers app
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
mrneilix said:
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
Click to expand...
Click to collapse
I have a similar issue, someone please help
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
As DeathSdoor said...flash stock.
Sent from my SAMSUNG-SGH-I747
d3athsd00r said:
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks guys! So I used odin to flash the stock boot loader and stock rom, but it is still hanging up on the 2nd samsung screen like it initially did (the one after the AT&T boot animation). Any other ideas on what could be the cause?
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The first boot can take as long as 5 minutes sometimes. So, if you haven't waited that long, then try out some patience. Otherwise, try booting into recovery (stock now) and factory reset.
Sent from my SGH-I747 using xda premium
bump!
I have this same issue. I have restored to stock rom and it does the Samsung boot, then AT&T, then it goes to Samsung pulsating with a blue pulsating LED.
I have left it in that mode for at least 15 minutes and it never boots.
I can still get into download mode.
Thanks in advance for any help!
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
I let it run for 2 hours (left the house came back and i was still on. And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
I dont know if this is relevant, but while the phone is off and plugged in, i can still see the battery meter and the Green LED (so i'm guessing it's still working, it just wont boot)
mrneilix said:
And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
Click to expand...
Click to collapse
Same here!!!
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I went into recovery many times before, I'm definitely hitting the buttons right but it still wont go into recovery, it just tries booting like normal. I can go into download mode easily, but that's it.
jbizz, did you start getting this error after flashing AOKP rom also? trying to figure out what could have caused the issue in the first place
I'm not really skilled on these things, but I once had a similar issue with my phone not booting and had to end up using Kies to emergency restore it. Odin wouldn't recognize my phone but kies would.
Although I think my issue with odin may be stemming from my computers usb ports...
Sent from my SGH-I747 using XDA Premium HD app
I actually flashed a bad kernel and the phone wouldn't boot after that.
What is the proper way to boot into Stock Recovery?
Sent from my SAMSUNG-SGH-I777 using xda premium
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
mrneilix said:
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
Click to expand...
Click to collapse
Thats bad badassness! I will try that when I get home!
Sent from my SAMSUNG-SGH-I777 using xda premium
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
jbizz said:
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Sure, I'm doing this largely from memory since I mostly figured it out by throwing stuff at the wall to see what sticks.
Open Kies->tools->firmware upgrade and initialization->enter model name then serial number (they're behind the battery) -> put the phone in download mode and plug it in. it should take care of the rest.
Fair warning, this will fully wipe your phone, i lost all my pics (thank you google+'s instant upload or i'd be PISSED) and titanium backup (there goes my 3 stars on every level in angry birds and great scores in temple run), but at least you get a phone that can function as more than a paper weight, right?
mrneilix:
You're my new best friend and I don't even know you!!!
Thanks for the help, you're a legend!
Sent from my SAMSUNG-SGH-I747 using xda premium