[Q] Nexus AOKP flash - Samsung Galaxy Nexus

Hi all,
New to forums and to android in general. Wanted to ask a quick question about flashing through CWM. I am on a Galaxy Nexus, running 4.0.1 (ITL41F), on Telus, in Canada.
I used the Gnex toolkit for root/cwm flash. Initially I had tried 5.4 but I couldnt get into recovery mode; the device would briefly show the (unlocked) google screen, and then hang at what I can only assume is an android error screen (android on its back, front panel open with red arrow pointing up?) before rebooting. After that initial CWM install and recovery mode issue, I was experiencing some random restarts and some freezes on my unlock screen. I resolved to try Gnex 5.5, installing that version of CWM and it allowed a problem free boot into recovery.
I have since flashed AOKP (Milestone 3/Maguro) and the install was smooth. However, after rebooting out of recovery mode my device is hanging on the team kang boot logo screen. It's still animated and I assume the first boot after an install will take a considerable amount of time for configuration/etc....but its been about 25min.
My question, then, is should I wait longer? Or does this length of time indicate a problem with the install?
Thank you in advance for any help.

Go back into cwr and wipe all data, wipe cache and advanced - wipe dalvic. Then reboot
Sent from my Galaxy Nexus using xda premium

Should I be pulling battery to boot? or will holding power turn it off without causing issues from this boot screen?

Hi and welcome
wrongOne said:
Hi all,
New to forums and to android in general. Wanted to ask a quick question about flashing through CWM. I am on a Galaxy Nexus, running 4.0.1 (ITL41F), on Telus, in Canada.
I used the Gnex toolkit for root/cwm flash. Initially I had tried 5.4 but I couldnt get into recovery mode; the device would briefly show the (unlocked) google screen, and then hang at what I can only assume is an android error screen (android on its back, front panel open with red arrow pointing up?) before rebooting.
Click to expand...
Click to collapse
That is no error screen but the stock recovery screen. If you push vol up + vol down +power button again you see the options of stock recovery.
After that initial CWM install and recovery mode issue, I was experiencing some random restarts and some freezes on my unlock screen. I resolved to try Gnex 5.5, installing that version of CWM and it allowed a problem free boot into recovery.
I have since flashed AOKP (Milestone 3/Maguro) and the install was smooth. However, after rebooting out of recovery mode my device is hanging on the team kang boot logo screen. It's still animated and I assume the first boot after an install will take a considerable amount of time for configuration/etc....but its been about 25min.
My question, then, is should I wait longer? Or does this length of time indicate a problem with the install?
Thank you in advance for any help.
Click to expand...
Click to collapse
25 minutes is way to long. Dit you wipe data cache and dalvic cache before flashing the AOKP ROM?
GR36 beat me to it
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
wrongOne said:
Should I be pulling battery to boot? or will holding power turn it off without causing issues from this boot screen?
Click to expand...
Click to collapse
None of the above. Scroll through the options with your volume buttons and choose the right one with the power button (in recovery that is)

Sorry, I wasn't particularly clear about my current status.
The device is currently hanging at the team kang loading screen with the animated logo. In order to get into fastboot/recovery I will need to shut down. Is this best accomplished by pulling the battery at this point?
Thanks for the quick responses!

wrongOne said:
Sorry, I wasn't particularly clear about my current status.
The device is currently hanging at the team kang loading screen with the animated logo. In order to get into fastboot/recovery I will need to shut down. Is this best accomplished by pulling the battery at this point?
Thanks for the quick responses!
Click to expand...
Click to collapse
Try holding the power button for a few secs. If that doesn't work: yeah... a battery pull will do the trick

wrongOne said:
Sorry, I wasn't particularly clear about my current status.
The device is currently hanging at the team kang loading screen with the animated logo. In order to get into fastboot/recovery I will need to shut down. Is this best accomplished by pulling the battery at this point?
Thanks for the quick responses!
Click to expand...
Click to collapse
Pretty much pull the battery you are boot looping
Sent from my Galaxy Nexus using xda premium

Just wanted to extend a more personal thanks to all for the help. AOKP 4 running perfect now.

Related

Galaxy Nexus in reboot cycle

Hi
My Galaxy Nexus has just started into a constant reboot cycle. The Google logo comes up and the the multi coloured animation thing like normal and then it goes back to beginning.
I never get to enter my pin or anything.
Has this happened anybody else?
It also gets quite hot after been in reboot phase for 20-30 mins.
Thanks
Brian
Need more details: what ROM/kernel you're using? Do you have ClockWork Recovery installed? What did you do to your phone before this happened?
Sent from my Galaxy Nexus using xda premium
MS. said:
Need more details: what ROM/kernel you're using? Do you have ClockWork Recovery installed? What did you do to your phone before this happened?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Im not sure on exact details other than its as it was when I bought it apart from 4.0.2 is installed
I didnt root it or change radio etc
I was just using it as normal, was going in to check battery level I think
ClockWork isnt installed
If I hold down power button and volume button and go into recovery options reocovery mode doesnt work, restart bootloader doesnt help either
Only other options I have are Start and Power off
When I try and go back into those options again all I get is a screen with green Android and Start > Downloading > Do not turn off target
It can stay in this screen for 5 mins or more and go nowhere
This happened earlier on as well so I just turned it off
I tried the same procedure again and I got the recovery menu again but it still didnt work and then tried it again and I just got the Downloading message again
Not sure if any of that helps, I cant check the kernel version anywhere right now.
Oh and its the GSM release of the Nexus
bmulvany said:
Im not sure on exact details other than its as it was when I bought it apart from 4.0.2 is installed
I didnt root it or change radio etc
I was just using it as normal, was going in to check battery level I think
ClockWork isnt installed
If I hold down power button and volume button and go into recovery options reocovery mode doesnt work, restart bootloader doesnt help either
Only other options I have are Start and Power off
When I try and go back into those options again all I get is a screen with green Android and Start > Downloading > Do not turn off target
It can stay in this screen for 5 mins or more and go nowhere
This happened earlier on as well so I just turned it off
I tried the same procedure again and I got the recovery menu again but it still didnt work and then tried it again and I just got the Downloading message again
Not sure if any of that helps, I cant check the kernel version anywhere right now.
Oh and its the GSM release of the Nexus
Click to expand...
Click to collapse
Try removing the battery and then turn it on, works for me; have you installed some new apps before this happened?
quiro91 said:
Try removing the battery and then turn it on, works for me; have you installed some new apps before this happened?
Click to expand...
Click to collapse
have tried that several times
installed nothing new in last few days but even if I did I have no way of getting in to uninstall it if thats what was causing the issue
bmulvany said:
have tried that several times
installed nothing new in last few days but even if I did I have no way of getting in to uninstall it if thats what was causing the issue
Click to expand...
Click to collapse
and you can't remove the battery and then boot in recovery mode? are you sure?
quiro91 said:
and you can't remove the battery and then boot in recovery mode? are you sure?
Click to expand...
Click to collapse
I choose recovery mode and the phone restarts, Google logo comes up and it then goes to a picture of android robot with a red excamation mark over it
It just stays there on that screen for about 2-3 minutes and then retarts
After restarting it goes through sme sequence as before constantly going from Google Logo to multi coloured animation and then restarts again. At no stage do I get to login screen.
Only other option I get when I hold down power button and volume button is to restart bootloader, start and power off.
bmulvany said:
I choose recovery mode and the phone restarts, Google logo comes up and it then goes to a picture of android robot with a red excamation mark over it
It just stays there on that screen for about 2-3 minutes and then retarts
After restarting it goes through sme sequence as before constantly going from Google Logo to multi coloured animation and then restarts again. At no stage do I get to login screen.
Only other option I get when I hold down power button and volume button is to restart bootloader, start and power off.
Click to expand...
Click to collapse
try this, from step 4:
http://forum.xda-developers.com/showthread.php?t=1366806
it should work
quiro91 said:
try this, from step 4:
http://forum.xda-developers.com/showthread.php?t=1366806
it should work
Click to expand...
Click to collapse
that worked thanks
the hardest part was getting my laptop to pick up my phone in bootloader mode but my laptop is getting old and on its last legs, the usb ports are dodgy for everything
Just to warn you, there's a good chance it will happen again eventually. A few days ago it happened to me for the second time (completely stock).
I decided this time to root it and install a custom rom seeing as how I'd have to flash stock again anyway. I'm hoping that whatever bug that caused it has been fixed in 4.0.3.
case0 said:
Just to warn you, there's a good chance it will happen again eventually. A few days ago it happened to me for the second time (completely stock).
I decided this time to root it and install a custom rom seeing as how I'd have to flash stock again anyway. I'm hoping that whatever bug that caused it has been fixed in 4.0.3.
Click to expand...
Click to collapse
how often has this happened to you where the phone goes into reboot cycle?
are you on 4.0.2 as well I assume its the gsm phone as well?
its handy to sort but a pain in the whole having to install all the apps again
bmulvany said:
how often has this happened to you where the phone goes into reboot cycle?
are you on 4.0.2 as well I assume its the gsm phone as well?
its handy to sort but a pain in the whole having to install all the apps again
Click to expand...
Click to collapse
The first time it happened was the 11th Jan, on 4.0.1, and the second time was the 29th Feb, on 4.0.2. And yeh it's GSM.
Yeh exactly, sucks having to install apps again etc. Now I'm rooted I've got a nandroid backup just in case it happens again.

[Q] Stuck in ParanoidKANGdroid boot up screen *Please help!*

Hey guys, I"m new to the forums (as well as android).. Got my S3 yesterday (ditched my iPhone 5 for it and found touch wiz to be gruesome) So I rooted my i747 device, and installed the latest CWM, and put the new paranoidkangdroid ROM on my S3. I had it working all day, and it's incredible! I love every aspect of it. However, my phone just recently after trying to set a passcode rebooted itself and is stuck in the boot screen.. (the glowing pink android)..
I've tried rebooting, removing the battery, connecting to my computer, and tried to boot into the CWM screen without any success. Any suggestions for how I can get this thing to work again?
Thanks a lot for your time
- Ryan
Volume up+home button+power button until it disappears, let go of power and keep hokding other two. Yoh will see samsung screen with blue letters in top left for a brief second.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Jammol said:
Volume up+home button+power button until it disappears, let go of power and keep hokding other two. Yoh will see samsung screen with blue letters in top left for a brief second.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply, tried your advice.. screen went black, vibrated every few seconds, showed the samsung logo quickly, restarted itself again, and is still stuck in the boot loop...
Any other ideas?'
[update] : got my phone into the CWM recovery (v6.0.1.4) Any ideas on my next step? I cleared my cache and rebooted, it restarted and a screen popped up saying "updating android" and it was updating all my apps, gave me a little bit of hope. But then it proceeded to go back into the boot loop. This is getting really frustrating, if anyone has any other suggestions I'd really appreciate it
thecartographersden said:
Thanks for the quick reply, tried your advice.. screen went black, vibrated every few seconds, showed the samsung logo quickly, restarted itself again, and is still stuck in the boot loop...
Any other ideas?'
[update] : got my phone into the CWM recovery (v6.0.1.4) Any ideas on my next step? I cleared my cache and rebooted, it restarted and a screen popped up saying "updating android" and it was updating all my apps, gave me a little bit of hope. But then it proceeded to go back into the boot loop. This is getting really frustrating, if anyone has any other suggestions I'd really appreciate it
Click to expand...
Click to collapse
sorry for the double post - screen is all black no... getting no response at all now from the device, asides from an occasional vibration when I hold down the volume up + home + power...
please help
I just noticed the post for that ROM today so it is obviously fairly new, bugs are to be expected. Can you get to download mode, same process as recovery except substitute vol down for vol up. If so you can flash the stock rooted ROM of your choice and either try again or use a different ROM until they work the bug out. I would also suggest posting in the ROM OP so the dev is aware of the problem, or incase he has any suggestions.
EDIT - Just noticed you only have 3 posts, the forums require 10 to post in the development sub forums.
thecartographersden said:
sorry for the double post - screen is all black no... getting no response at all now from the device, asides from an occasional vibration when I hold down the volume up + home + power...
please help
Click to expand...
Click to collapse
That happened to me. For that rom to work, don't change any settings.
Make sure it's disconnected from the power wire. Hold, Volume Up and Home button then hold the power button. Wipe both caches, and factory reset. Reflash PK and Gapps. Wipe caches again and reboot. It should work. If not flash back to PA like I did. I'm gonna wait for the next update.
Sent from my SAMSUNG-SGH-I747 using xda premium
thecartographersden said:
Thanks for the quick reply, tried your advice.. screen went black, vibrated every few seconds, showed the samsung logo quickly, restarted itself again, and is still stuck in the boot loop...
Any other ideas?'
[update] : got my phone into the CWM recovery (v6.0.1.4) Any ideas on my next step? I cleared my cache and rebooted, it restarted and a screen popped up saying "updating android" and it was updating all my apps, gave me a little bit of hope. But then it proceeded to go back into the boot loop. This is getting really frustrating, if anyone has any other suggestions I'd really appreciate it
Click to expand...
Click to collapse
Wipe "cache" AND "dalvik cache" found under advanced tab. If that fails, try a more stable rom. Cm10 nightlies maybe, which are more mature with less problems.
Also, you didn't flash a different kernel did you? From what I read only the kernel provided will work. Furthermore, make sure you flash the proper gaaps. That also will cause problems.
And of course. Welcome to XDA and Android. Once you get the hang of flashing you will be obsessed and never go back to iFail. Trust me.
Sent from my SGH-I747 using xda app-developers app
thanks a lot everyone above - I managed to reset all caches earlier, wiped the device, and then re-installed the ROM and gapps and everything is working fine now. I'll take your advice and not alter too many of the settings on this ROM (asides from this error, this OS runs beautifully!) I tried to post this problem in the post for this specific ROM but wasn't allowed as I have less than ten posts.. haha.
Again, thanks for all the help. I'm loving the device, iOS doesn't come close to what I've experienced so far.. And I've only been using it for a couple days.

CM10 Boot Loop? Help!

I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Flightfreak said:
I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Click to expand...
Click to collapse
Download mode couldnt get any simpler bud
Edit: just incase if you dont know its down home power button to get to it, find your galaxy s3 firnware (ATT/Bell etc...) and your back stock nonrooted. And then you can root againif you wanna
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
Did you read the question bro.. he said he CAN'T go to recovery mode only other option is download mode
No, the option is to boot into recovery and perform a factory reset (which may fix his problem). IF that doesn't fix his problem, he can flash a different ROM from recovery, provided he had custom recovery.
The only difference in getting to download as opposed to recovery is which volume button you use. Chances are if he can't 3 button into recovery, download will be the same result.
Thanks
Got it fixed guys, thanks for the help, now I'm back at Stock Rooted 4.1.1, but am still on the quest for a deodexed rom!
Excellent suggestion - it worked for me
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
I got a Galaxy S III on 23rd Dec 2012 with Ice Cream Sandwich installed. A couple of weeks later it updated itself with a little help from me to the latest Jelly Bean. Since then it's gone into the reboot loop 3 times without any provocation; i.e. I get it out of my pocket and it's in a reboot loop but it had been fine the last time I used it. I tried pressing various buttons alone and in combination and eventually it came out of the loop. At no time did I have to remove the battery. The only mod I've made to it is the addition of a 64GByte SD card, apart from the upgrade to Jelly Bean. I've seen many posts on this problem but yours is the first that confirms my solution for getting out of it. It's obviously a common problem so somewhere there must be a description of what causes it and, hopefully, how to prevent it as it's a real nuisance when you want to use your phone and it's in a reboot loop. If and when I find a definitive article I'll post here again.
Thanks MrHaley.

[Q] Stuck in boot loop after enabling second screen in developer options.

While attempting to get HDMI working, I stupidly enabled second screen in developer options in my aosp ROM, which immediately rebooted the phone. I'm now stuck in a loop whereby the phone boots and then restarts when loading the lock screen (presumably it's enabling the second screen).
Is there a simple way of resetting settings to default or bypassing this during boot? I'm away from home else I'd wipe and recover, so any help would be appreciated.
I'm using teamwin recovery if that's relevant.
Try clearing cache, if that doesn't work restore backup.
I think there is a safe mode, not sure how to activate it.
Also, factory reset is possible.
BenPope said:
I think there is a safe mode, not sure how to activate it.
Also, factory reset is possible.
Click to expand...
Click to collapse
It can be activated only once the phone is booted afaik.
Sent from my HTC One X
Thanks chaps,looks like a recovery cache didn't work. Lesson learned!
So you got out of boot loop or what?
Sorry, to clarify clearing cache didn't work. I ended up wiping and recovering.
Sent from my HTC One X using xda app-developers app
I know this is an old thread but I think I found a solution.
If you wait until the boot animation is already showing and then hold down the buttons like you were trying to boot into recovery it should boot your phone into safe mode. Then you can go into settings and disable the second screen. It may be different on the one x than on my phone though. I have a note 2. I am just trying to keep anyone else who has this problem from having to wipe their device unnecessarily.
captivate999 said:
If you wait until the boot animation is already showing and then hold down the buttons like you were trying to boot into recovery it should boot your phone into safe mode. Then you can go into settings and disable the second screen. It may be different on the one x than on my phone though. I have a note 2. I am just trying to keep anyone else who has this problem from having to wipe their device unnecessarily.
Click to expand...
Click to collapse
Instructions:
Restart the phone, After the boot-screen appears, press and hold Vol UP and Vol DOWN keys.
(Tested on GT-N7000 / Paranoid Android)
mshussain said:
Instructions:
Restart the phone, After the boot-screen appears, press and hold Vol UP and Vol DOWN keys.
(Tested on GT-N7000 / Paranoid Android)
Click to expand...
Click to collapse
wow, did work !! thank you

[Q] Post install: Nexus 5 vibration thumping regularly, seeing eye logo

Hi, all,
I'm an android newbie and followed directions to rooting my Nexus 5. Finished rooting it, installed TWRP for custom restore, then installed paranoid on the advice of friends. Perhaps I did something wrong, but my phone is never finishing the OS boot. It has booted to paranoid (I think) and is showing the eye logo, with tri-color circles spinning around it. It is vibrating (thumping) regularly in my hand. I let it do this for about 15 minutes before giving up. Restarted again with the same results.
I should add that after its first boot the phone did show "updating Android applications" for a few seconds. And now any effort to power the device off by holding the power button actually forces a reboot. There seems no way to power the system off or get to the recovery mode.
Any suggestions/guidance about what I should do?
Thanks!
When you flash a new ROM you are supposed to do wipe>factory reset in your custom recovery
#stayparanoid
Pirateghost said:
When you flash a new ROM you are supposed to do wipe>factory reset in your custom recovery
#stayparanoid
Click to expand...
Click to collapse
Thanks. As I said, I'm completely new to this. I must have missed that.
I ultimately unplugged the device and let its never-ending boot deplete the battery. That killed the boot, obviously. From there I was able to recharge and boot to recovery. I then fixed the install.
Thanks for the reply.
For future reference, you can just hold down the power button for 10 seconds,and when it reboots, hold vol down. It will boot you into recovery
#stayparanoid

Categories

Resources