[Solved] Can't get past "Google" on Boot with Stock ROM - Samsung Galaxy Nexus

I know there was another thread here in the forum but since there was no real solution in it I thought I create a new thread instead posting in a older one.
I have a non rooted galaxy nexus and this morning it was still working. The alarm clock woke me up and shortly before I wanted to leave home I wanted to check when the train is coming but the app was crashing. So I though I reboot and it should be ok again. But since than I'm not able to get past the "Google" logo. It vibrates shortly, the screen goes black and is back at the "Google" logo.
I'm not rooted so there is no chance to get the data wiped.
Is there something als I can try without root?
I was on 4.0.1 (it was a sumsung build, yakjuxw or something) and after the update to 4.0.2 i had a yakju build.
EDIT: Well, now I feel kind of stupid. I'm sorry. I had no Idea how to use the recovery mode. I just found out how to wipe data from there. Once more: I'm sorry. Thread can be deleted

Related

[Q] Tablet stuck on Google start up logo - intermittent

The issue
Nexus 7 2013 has a problem where the tablet wont boot, it is stuck on the Google boot logo.
At that point i had tried the recovery mode, yet this flips back into the boot loop.
I had tried the charger option also... no luck there either.
The fix
I left the tablet for 1.5 hours then switched it on as normal.. the tablet decided to come back alive.
Its not the first time this has happened, the last time i done a factory recovery and that kind of solved it for a couple of days.
------------
It seems that this nexus 7 tablet is a lemon and needs to go back unless someone knows the answer >?
I don't know if you've unlocked the bootloader, rooted or flashed a custom recovery/ROM. If you have, I'd suggest completely returning to stock and seeing if that helps. If you haven't done those things or returning to stock doesn't help, send it back.
That's how mine started too, it will get worse until it fails completely. Mine just came back from ASUS on Monday and by Wednesday night it was already boot looping again.

[Q] Galaxy Nexus stuck in boot loop and boot loader seems broken

In need of help!
I have a rooted Galaxy Nexus. I have been having many problems since it was rooted (will not connect to Google I think...? WiFi signal grey), but if possible I'd like to keep it rooted. I used Nexus root toolkit and SuperSU seemed to mess everything up. For a while after I uninstalled SuperSU it worked OK. Then later they WiFi signal went gray again so I factory reset this morning. Internet seemed to work (even though it was still gray) so I went about finding replacements for Google apps online because my Google apps didn't work(Google play, YouTube, etc). About an hour later suddenly my screen froze then my phone crashed. When I attempted to restart it stayed on the blue, green, red, yellow, X for 2hrs. I decided to pull the battery and put it in boot loader. Instead of what boot loader normally says it instead said "Downloading... Do not turn off target!!" When I tried to use the volume keys to change the "Start" sign it did nothing. My only option (I think) was to press the power/sleep button to try to turn it on. Just like before though, it stayed in boot loop.
I'm sorry if this was too long... I'm new to XDA, could somebody please help me?
Thank you
Oh and this whole time I didn't have any form of superuser installed...
Can anyone help?
Does anybody know what to do? Please help me!

[Q&A] [ROM][4.4.4][Official] CyanogenMod 11.0

Q&A for [ROM][4.4.4][Official] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][Official] CyanogenMod 11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Please help!
Please Help-
I have a HTC ONE M7 from Verizon that is rooted and running CM11 snapshot M10. I recently started using the phone after a couple of months. When I started using the phone it was still on CM10.2, working fine. I upgraded to CM11 and had an issue with google play services failing, so I wiped the device and did a fresh install of CM11. The install worked fine and but I had none of my previous apps so I began the process of setting my phone back up and downloading all of my apps. Certain apps would not install and come up with an error message. ( Unknown error code during application install "-24". So I did some research and found out how to get rid of the error code but it only worked for certain apps, others still came up with the same message. I had wanted to clean out my phones memory anyways because it was getting full so I decided to do a full factory data wipe/reset from the phones settings menu, not from recovery. So I proceeded to wipe the phone and it rebooted and showed the android logo with the crazy blue lines in his stomach and the blue loading bar below. I let the phone sit for a while and nothing was happening. It stayed on that screen for a couple of hours without rebooting or showing any signs that it was wiping the device. So I decided to to hard reboot the device with the power and volume down button ( probably a bad idea I know) and reboot the device. Now when I power on the device the CM logo shows up but it just keeps spinning, never boots into the device. If I try to boot into recovery, the bootloader shows up fine, and then I select recovery and it goes back to the same screen with the android logo and cray blue lines in his stomach and loading bar below. I have let the device sit for hours both trying to boot up or boot into recovery and it just either stays on the CM loading screen or the android logo with blue loading bar. I now do not know what to do and am a little worried. I am not new to rooting and roming android devices but I am also not a pro. Please help me recover my device to any rom.
Thank you for your help and sorry for the long post.
manklee said:
Please Help-
I have a HTC ONE M7 from Verizon that is rooted and running CM11 snapshot M10. I recently started using the phone after a couple of months. When I started using the phone it was still on CM10.2, working fine. I upgraded to CM11 and had an issue with google play services failing, so I wiped the device and did a fresh install of CM11. The install worked fine and but I had none of my previous apps so I began the process of setting my phone back up and downloading all of my apps. Certain apps would not install and come up with an error message. ( Unknown error code during application install "-24". So I did some research and found out how to get rid of the error code but it only worked for certain apps, others still came up with the same message. I had wanted to clean out my phones memory anyways because it was getting full so I decided to do a full factory data wipe/reset from the phones settings menu, not from recovery. So I proceeded to wipe the phone and it rebooted and showed the android logo with the crazy blue lines in his stomach and the blue loading bar below. I let the phone sit for a while and nothing was happening. It stayed on that screen for a couple of hours without rebooting or showing any signs that it was wiping the device. So I decided to to hard reboot the device with the power and volume down button ( probably a bad idea I know) and reboot the device. Now when I power on the device the CM logo shows up but it just keeps spinning, never boots into the device. If I try to boot into recovery, the bootloader shows up fine, and then I select recovery and it goes back to the same screen with the android logo and cray blue lines in his stomach and loading bar below. I have let the device sit for hours both trying to boot up or boot into recovery and it just either stays on the CM loading screen or the android logo with blue loading bar. I now do not know what to do and am a little worried. I am not new to rooting and roming android devices but I am also not a pro. Please help me recover my device to any rom.
Thank you for your help and sorry for the long post.
Click to expand...
Click to collapse
Are you s-off? You'll find it in your HBOOT
Help
I've upgraded my phone yesterday by CM 11.0 but i cant make a phone call or even draft a massage. It said Molbie network not available
hectorvo said:
I've upgraded my phone yesterday by CM 11.0 but i cant make a phone call or even draft a massage. It said Molbie network not available
Click to expand...
Click to collapse
You probably need to update your firmware to use the newer cm. Make sure you flash the latest with no boot.img.

Duplicate Samsung Epic 4g logo on boot after re-flash

Hey there. Something strange has been going on ever since I re-flashed my phone. When I flash the kernel/rom other than the stock one I get a duplicate Samsung logo when the phone boots. (phone displays Samsung logo, goes black for a second then displays again before boot) I've been flashing and reflashing ever since I got the phone and now I'm getting this. I can get into recovery and download mode just fine and other than that there don't seem to be any other problems. This is just weird. I'm wondering if there's a way to fix this. Also, I'm wondering how such a thing can happen in the first place. I've re-flashed twice now and the result is still the same.
[EDIT]
From what I understand, the boot screen file is located in param.lfs. I've read before that you can add a screen but how in the world would a re-flash cause a duplicate screen to appear? I had a failed kernal flash happen where i couldn't access the recovery and had to start over from scratch but that's happened before.
[UPDATE]
Just tried to mod the boot logo and found out it's requesting "gaudi_bootimage.jpg" twice. I have no idea what this means. Gonna go back in and re-flash the old one back in.

This doesnt quite seem like a boot loop... Help?

So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again

Categories

Resources