I have an unlocked HSPA+ Galaxy Nexus imported from the UK to the US. Ordered from Negri Electronics.
It's not rooted or modded in any way.. Mainly because I don't know how to. As far as I know, it's running stock ICS.
I was using it normally, (using the fb messenger app if it makes any difference) when it suddenly rebooted by itself. The Google logo comes up, then the start up animation, and sometimes the home screen will appear but is not touch sensitive (i cannot slide it to unlock), and then it 'hangs' and the screen goes black. Repeat.
I've tried to fix this by myself and there's a video on youtube (sorry, noob here. can't post links. video is by robbidwv and title is "my galaxy nexus won't boot..") of the same problem that I have, but the posted solution doesn't work for me.
So far, I have entered Coin Mode and pressed Start. Entered Fastboot mode and gone into Recovery Mode (no options appear after that. it just starts booting up and the loop begins), and I've also tried Restart Bootloader.
I've almost given up. Now all I want is to extract my SMS, if they're still on my phone. I can't access the folders on my computer because it won't boot up and connect. Is there a way that I can extract my SMS by using DOS in either Coin Mode or Fastboot mode?
Or even better, does anyone have a solution to this boot loop problem? I'll contact Negri Electronics tomorrow and hopefully they can send me a replacement.
Please help!! Thanks
that problem just started happening with me an hour ago!!
i hate this!!
we need a solution please!
Hey guys, sorry about the issue.the major problem I see here is you wanting to retrieve your txt messages, which might be possible with a little Modding, but if yourwilling to lose them to get a working phone back, then this is what your going to have to do. Make sure your phone is completely off. Hold the 2 volume buttons and the power button together. You will get into a mode with an android Guy. Press the volume button up or down until it says reboot recovery at the top. Press the power button. It will rebootand come to a screen with an android. Hold volume up,down and power at the same time. A menu will come up. Go down to wipe data. Click it, and after it is done reboot. Your phone should work now.
If this helped you, or you simply appreciate me taking the time to write this out then please press the thanks button
Hey!
Thanks. Yeah I 'fixed' it already. I was just about to post something similar. After a while I just gave up on trying to recover my data. Good thing that Google syncs everything so the only issue would be recovering my messages, which I decided weren't worth sending it in for a repair which would probably not be able to recover anything anyway.
The thing I didn't know about was to press power + volume up WHILE on the recovery screen. I thought navigating to the recovery screen was it!
Still, this kind of sucks. I love my GNex, but I can't help but be slightly pissed seeing that my crappy iPhone 3GS never did this in the 2 years I had it. Oh well, hope it doesn't happen again!
hey guys! i also did a complete wipe on my phone and got it working again!
but i wonder why this happened in the first place?
last application i installed before the crash was double twist, i dunno why but i feel that it was the reason behind the boot loop!
Sorry for reviving this thread, but I just had this happen to me TWICE!
It happened to me first last Monday, the 23rd - the phone crashed when trying to send an email with an attachment - and went into a boot loop - Google logo would appear, no make it to the animation, and reboot....
I performed a full reset and things worked again. I didn't install all the apps I had before - figuring it must have been due to some app messing with the OS.
Well, it happened again to me yesterday! I was connecting to my bluetooth headset when the phone crashed and went into the boot loop. Full reset worked again, and I've installed even fewer apps - essentially only those that I use on a daily basis.
My phone is still on 4.0.1 and I'm hoping once 4.0.4 is pushed this may get resolved? I have a canadian GNex from Negri. I will call them again (I called the first time, but when the full reset worked I never contacted them again).
I would like to this this is a software issues, and not hardware.
I have the same problem. If you figure it out let me know.
Today my phone also entered a boot loop: [Google logo]->[black screen]->[vibration]->[Repeat]
I tried Recovery Mode, but this is what happens: (sorry for the link but I am not trusted with powerful tools such as outside links apparently, as I have not yet reached the maturity of a person with eight posts... )
dl(dot)dropbox(dot)com/u/53568097/Android.jpg
This is what I see when I navigate to Recovery Mode
For a split second I can see an image of an Android with spinning cogs in his innards, but then this little sad fellow appears. WTF is this?
EDIT:
Oh, and I'm running Android stock 4.0.2, never rooted or unlocked, Swedish. At the time when the phone started doing this, I was using Endomondo, and was about to set off on my bike when it died on me.
Stock ROM galaxy nexus bootlooping after wiping data also.
Hi,
My GNex went into a bootloop so i searched xda and found that factory reseting would be helping my prob. But after wiping the data also its still in going through the loop . Please help .:crying:
Related
Good day to all. I'm here resorted to ask about my problem here because I really can't handle it. I been googling for days. I'm ran out of resources from both google and tablet. So, I hope you can help me here. Note I'm going to write this in FULL detail here, so expect this to be a extremely long post. (I been warning you) So here goes....
Anyone uses the brand Ramos?(kind of unpopular brand) I use Ramos W21, it's been using it around 1 year and a half, and it endured a lot of problems, but fixed by researching on online forums and apply various methods there. Now, I think it's finally gave up...
One time, when I opened it and play my usual apps and browsing, it caused the errors " unfortunately
google.process.gapps has stopped", unfortunately browser has stoped",and "unforturnately google play has stopped". Then, I tried to clear data the similar apps in settings as usual, and even disabling them. Then more errors exploded, and "unfortunately launcher has stopped" appears. The menu screen(where the usual wallpaper and shortcut apps are located) turns black, while my running apps are still there running. When I pressed the back key to exit the app, now only tons of errors from the launcher appears endlessly(while the screen is black.
The time I finally turned it off by hard reset it made its way to the main problem: the bootloop.
Okay, here's where the thing gets real. It opens with the usual ramos logo, but the next one is a silver flashing android logo instead of enlarged ramos logo with spinning fire from the letter o(which is NOT my usual boot up screen) When I turned it off, it reopens again up to flashing silver android logo and the cycle repeats, even with pin reset until battery dies out. No recovery mode, so I can't use it to fix this. USB connections can't be recognized when inserted to PC. And no, the tablet is not rooted, and I don't customized anything, no mods, and no fancy roms. Just using a stock rom.
So now what? All I have here is just a sd card slot, which I think there's hope in there. Right now it has two options, deal with it and fix with all of might, or repair it in the nearest repair shop(something that is pretty risky, a lot of fakes and robbers here)
Well, this is the first time I post here, so sorry for anything that goes wrong. Thanks in advance.
Hi, thank you for using XDA Assist. It sounds like a rouge app has replaced your boot animation. Rather than try to chase that down and try to fix it I'd flash the stock firmware and start all over. Unfortunately there is very little about your device on XDA. So you'll probably have to google that.
Solved!!!
Update: I FINALLY FIXED IT!!! IT WAS A MIRACLE!!! O.O
After I keep on wrecking it's power buttons and volume buttons, I discovered something decisive!
This tablet actually HAS RECOVERY MODE! Again, it has a recovery mode! However, the way how to input it is very unique compared to most devices, including other devices from the same brand!
Now having the power of recovery state, I first selected "wipe data cache". The old large Ramos logo with spinning fire appeared again! But it's still bootlooping. So I went back on recovery state, selected "factory reset" and boom, IT BOOTS LIKE BRAND NEW!!! (sacrificing my old data though)
Okay, I don't want this recovery mode powers to be kept only by me. So I'm going to share it to all Ramos users,especially the model W21, like right now!
1. To do this, you need power button and volume up button.
2. While bootlooping, hold the power button and volume button at the same time and it will turn it off(Then expect it to turn on back up again automatically)
3. When it opens up again to the small Ramos logo(no fire animation), now RELEASE the POWER BUTTON ONLY, and keep holding the volume up button. Note, this is important! If you do anymore than this, it will either black out, go bootlooping once again, or ultimately, nothing.
4. Keep holding the volume up button, then the ramos logo will disappear, and now it will enter to our holy grail, RECOVERY MODE! Congratz!
Now when you finally have a normal working Ramos tablet again, you may go there again by turning it off by "Power Off" (assuming that your tablet is open) then holding the power and volume up(then follow above!)
I hope this will help a ton for Ramos users! :laugh:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
jd1639 said:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
Click to expand...
Click to collapse
Well thank you then for the link. Gotta go there!
Thread closed.
I do not normally post on here, just read and learn =) However, I'm having an issue with my G2 for AT&T. I have a Nexus 6 and cracked the screen, I was trying to get my G2 up and running until my replacement gets in. I had CyanogenMod on it but did not turn on the phone in quite a while. Got an update, did that and nothing was working. Could not even get Google Play services working at all. Flashed a random ROM to see if it would help and now I cannot even get into recovery. The phone operates fine, however if I try to do the power button + volume down button to reset the phone, I get to the point where I hit the power button twice and the phone resets. I've selected rebooting into recover a hundred times with no luck, it will get to recovery and before I can hit anything....reboot. Last night I tried to go back to stock with LG Flash Tool (after downloading everything I need to download) but keep getting Fail after unplugging my phone and plugging it back in download mode. I know long paragraphs are not well liked here but i feel i'm sort of o ut of options other than reaching out to you awesome people! Just wanna go back to stock at this point. I've never had this issue where I cannot even get into recovery but the phone work perfectly fine! grrrrrr
Hey guys,
I spent about 2 days reading through every piece of guide I can find in here to resolve my issue and now, here I am. So the thing that started this whole pileup is that I did a cache and dalvik wipe. After which it booted to till the bootanimation and stayed there............Forever. I understand this is fixable, but here is the real problem. My volume button doesn't work. So I cannot go into recovery or download mode (download mode was accessible for a while until that button failed too). So then I tried rebooting with adb. But then it says that the device in unauthorized (I remember that the USB debugging option was set to ON a long time ago). In a desperate attempt to fix things, I opened the phone and checked out the volume buttons to see if anything can be done. The buttons are like fully damaged from the wear and tear over the years and I'm not just talking about the button but also the contacts. It still boots up to the bootscreen. At this point I'm only interested in getting my data back. My last backup was done a month ago.
Can someone please help me?
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.
Good day, this would be a pretty lengthy post. I'd like to describe my experience clearly since I don't know what I possibly skipped over as I am very positive that my efforts have been correct basing on prior XDA forums. I even made this account solely for posting this to ask for help formally along with archiving this problem I'm having for those having a similar experience.
I've been working on my mom's phone this whole day and there are fruits of my current hard work. I am immensely stressed and despairing with my situation.
The Problems
Infinite boot looping
Can't access the recovery menu (power, volume+, even with home button)
Can access the ODIN / Download menu
Can't turn off either (holding down power button has no effect)
What I've done so far
I read XDA forums about similar experiences. Can't really access the recovery menu so I've factory reset.
We live in the Philippines and this phone is open line, so I went with those requirements while searching stock ROMs.
I downloaded the stock ROMs of the phone model via galaxyfirmware.com which was positively shared in the forums.
Did trial and error with it and eventually got the right one. I have formed a level of understanding with the filenames and eventually knew which is compatible.
Used Odin3 to Flash the BL, AP, CP, CSC, and even go Nand Erase and got the PIT file inside the CSC (Opened it using winrar)
The flashing is actually successful and quite fast to be honest.
The phone reboots itself and shows that it is still sadly boot looping.
Also, despite the several files used for the Flash, still can't access the Recovery Menu.
With that said, I have also tried using Frija which automatically downloaded the stock ROMs based on the model name and CSC type. Placed it in ODIN again and no changes, still boot looping.
I also can't put the TWRP I got here because of the FRP Lock, which can be undone via the settings of the phone. But since it's boot looping, I can't really do much about installing a custom ROM.
Currently, my dad is letting the phone drain its battery, since we can't really turn it off. The phone model doesn't have easily detachable battery as well, unlike the old days.
For some additional notes of what happened prior to this incident
My mom was just playing with her phone as her usual days went on. That day, she installed a new hotel-themed game she saw on Google Play. As I assume that it's from the app itself and not on some shady apk website, I saw no problem with it and didn't think it was the cause of all this. I went with the theory anyway and with the flashing, using CSC instead of HOME_CSC (which apparently saves the existing data on the phone from wiping), and even used the Nand Erase in the end. It's still stuck at boot looping.
I would appreciate anyone's reply to this discussion. I am truly desperate to fix this for my mom. If worse comes to it, I'll save money to buy her a brand-new phone.
You don't have a working android, so you won't remove the RFP. TWRP will not help you with this.
The symptoms you describe indicate a defective power button.
You manage to enter download mode because the power button is constantly on.
Because of the constantly on power button, you have no way to turn off the phone. Bootloop can also be the result of a constantly on power button.
To sum up, you should fix the power button.
1. The easiest way is to blow with compressed air and press the edge of the button with your fingernail, rapidly releasing the pressure. Perhaps the fuzz has blocked the button. Unfortunately, this rarely works.
2. Take the phone to a local service center.
Hi ze7zez! Me and my dad greatly appreciates your insight and we were definitely enlightened on this angle.
We didn't really think that the power button was stucked pressed on because you can clicking sounds when you press on it. The phone never had problems with the buttons along the 6 years it accompanied us, perhaps its age does start to show.
We're going to look into it tomorrow. Thank you very much! You gave us the idea that it may be shorted inside or some sort. Thank you again!
A bit of update.
I pried open only the back case of the phone so I can see and clean up the power button. I used tools specifically for it and made no damage on the phone during the process.
We couldn't really see anything busted from there. The buttons on the circuit still do the neat clicking sounds on it. Battery still looks the same.
Testing out the theory that the power button was stuck on:
We tried to only press and hold the volume down and power button. It didn't go to the download menu. We needed to press down all three together to access it. It is confusing since we believe it would be a power button issue too, as the phone instantly turns on by itself when plugged to a power source (it's completely drained by now and we still can't turn it off manually)
Perhaps it's an internal circuit problem with the power button? It's confusing with the fact we still have to press on it to access the ODIN menu if it was like "on" the entire time it's looping.
Thank you in advance for further insights.
Try restarting by pressing home, power and volume up all at once.
Hi Pranav2406,
I have tried that as well in order to access the Recovery menu to factory reset, but no luck.
We have given up on repairing the phone and went out yesterday to buy a new one in a rush.
We will still send this broken phone to a repairman.
If he fixes it, I'd ask what he did on it so I can post an update on this problem as well.
It's better to let the expert troubleshoot it.
I do suspect the problem in the phone's hardware. I'm pretty confident with all the stock ROM flashing I've done so it's not a software problem.
Thank again for everyone's insights.
Perhaps this case is too much for an amateur to fix.