Hi,
I have a Galaxy Nexus GT-i9250. I used to use it to play around with ROMs and all. But the last time I flashed a CM11 and DirtyV Kernel, the phone started stuttering during boot and when I tried to flash a new ROM, the ROM just wouldn't take, it just kept coming back to the same version of CM11. I've even tried returning to stock using Root Toolkit and the like but still doesn't work.
Is there a way to fix it? I really really like my Galaxy Nexus, so I'm willing to spend a few bucks, but not too much that it'd make sense to buy another phone.
Go into recovery mode n see if u can just use one of your backups from there
Sent from my Galaxy Nexus using XDA Free mobile app
rob420jones said:
Go into recovery mode n see if u can just use one of your backups from there
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I tried. No luck.
It's a strange thing. A lot of Galaxy Nexus had that kind of problem in these days, and many thread on xda confirms that.
That thing happened to me as well. No luck. No way to fix the problem by software ways for me.
There was no way to unlock the bootloader, I mean, I did it by fastboot but after every reboot it came back locked.
No recovery worked, even a custom recovery booted temporary didn't help. Wipe data etc but after the reboot the device booted as I haven't wipe anything..
Odin didn't work, same as before. It took time, it seems that was working on something, but no luck after reboot, everything was the same as before, as if I haven't done anything.
Couldn't enable usb debug to use ADB 'cause I activate that but after the reboot (guess what?) it was disabled again..
I tried almost every way..
An xda user said that "if you unlock the bootloader and after the reboot it's locked again, the emmc is fried".
So sad
Related
Ok, I am having a VERY strange issue with my gsm galaxy nexus. First off it started acting weird rebooting itself all the freaking time so I got fed up and decided it was time to try a new ROM (currently on stock 4.0.4).
Now here is where the crazyness starts. I tried to root and install CWM but nothing sticks, so I try to ODIN a factory image and when the phone reboots I am back on stock with all my settings and files still in tact like nothing flashed, I try to connect to my computer and transfer a file to my phone and when I reboot or go into recovery the file is gone. I have tried re-locking my bootloader and when I reboot, it is still unlocked. I have even factory reset my phone and all my data is STILL there. I don't understand. It seems as if my memory in my phone is not allowing any writing or something. Please tell me I am not the first to experience this.
Basically no matter what I do or try, my phone stays the exact way I currently have it. PLEASE HELP!!!
I also just noticed that when I enable wifi and then reboot, wifi is disabled and also whenever I reboot, my apps that I have already updated try updating again. It just seems like my storage is not writable.
I think you need to make a video of you doing a factory rest and have it not work. I love paranormal videos.
Have you tried fastboot? If you are using the toolkit, stop, do it manually.
mentose457 said:
I think you need to make a video of you doing a factory rest and have it not work. I love paranormal videos.
Have you tried fastboot? If you are using the toolkit, stop, do it manually.
Click to expand...
Click to collapse
Yes, i have tried fastboot both manually and with the toolkit. I have literally tried everything. This makes NO sense. I have had a ton of android devices so I know how things should be working and this thing is busted.
timgt said:
Yes, i have tried fastboot both manually and with the toolkit. I have literally tried everything. This makes NO sense. I have had a ton of android devices so I know how things should be working and this thing is busted.
Click to expand...
Click to collapse
Format the internal memory ... last option but it might help, good luck
Are you able to boot into the OS still? Does adb work? Does fastboot work?
I just tried running some commands which should have pretty much wiped my device.
I ran
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
When I reboot the phone, all my damn data is still there and everything is in tact.
Interesting...
http://forum.xda-developers.com/showthread.php?p=25483948
Apparently it's common on gsm models.
Sent from a phone...
I also noticed if I try to uninstall any app the phone reboots itself and if it doesn't when I do reboot it myself the app I uninstalled is back.
I think we can all agree there is only one thing that can be causing this: the ghost of Steve Jobs.
I read somewhere that the exact same thing happened to someone with an SII. I don't think they were able to find a solution.
This is very interesting. I'd contact Samsung.
Sent from my Galaxy Nexus
My friend has a possessed iPod touch, it just does things automatically.
Kind of funny to watch though.
Sounds like a bad flash chip. I'd suggest the repartition option in Odin but I'm not sure if it works on the GNex or not. Worth a try if you're desperate
Sent from my Galaxy Nexus using Tapatalk 2
If you do a reset through the settings menu what happens? If nothing it sounds like a bad chip. If it changes that you maybe good to go. I have seen an issue on my wife's phones where it was unable to write to the partition in recovery.
Sent from my Galaxy Nexus using XDA
scoobdude said:
If you do a reset through the settings menu what happens? If nothing it sounds like a bad chip. If it changes that you maybe good to go. I have seen an issue on my wife's phones where it was unable to write to the partition in recovery.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If i do a reset in the menu, it reboots to recovery with a red exclamation so i press all 3 buttons to bring up the menu and try to wipe data/factory reset in the stock recovery and it says it works but when I reboot all my data is still there.
I called Samsung and apparently they wont help me since it is an international version. So basically I have a phone that can't be fixed and will always be in the current state it is in now.
EDIT: I have now found 3 occurrences of this besides mine. One guy with a Galaxy S2, one guy with a Droid X and one guy with a Dell Streak 7. Nobody ever fixed it. Neat
Maybe there are some more option going through the debug port?
Sent from my Galaxy Nexus using XDA
scoobdude said:
Maybe there are some more option going through the debug port?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm limited on the number of commands I can run because I never rooted this phone. Should have been the first thing I did. Figures the only device I never rooted has this happen to it.
Did you try rebooting?
Sent from my Galaxy Nexus using Tapatalk 2
I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...
Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.
sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat
I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?
Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.
I'm thinking of a hardware defect.
Beamed from my Grouper
Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
hulslanderam said:
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
Click to expand...
Click to collapse
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
FIXED
sensation lover said:
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Awesome!
hulslanderam said:
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Click to expand...
Click to collapse
Congrats! That's gotta feel good to resurrect a "dead" phone!
I've tried to use the OMAP flash to fix mine, but I still can't get into Odin mode (even tho the drivers and bat file seem to install successfully). If you have any tips, then please let me know.
Sorry for the bad english...
My Samsung Galaxy Nexus reboots about every 20 seconds if I'm trying to start the System. When I'm in the Recovery (TWRP), everything works fine. Here is a short Video, to show the booting issue:
/watch?v=sGfQDrah55s
(I have not enough posts to post an outside link right now, sorry. But I think you know how to use the part of the youtube URL)
As you can see, sometimes the SGN reboots after a few seconds while showing the bootlogo and sometime (as you can see at the end of the video) it boots until I can make a few things on the system like unlook it. But at least... it always reboots after a short time until the battery is empty.
At the moment, I have a CyanogenMod ROM installed, but it doesn't matter which ROM I'm going to try. Exactly the same bootloop happens with AOKP or SlimROM or even the FactoryImage. I realy don't know how to fix it. I tried so many things until now. The Video is taken with my new Galaxy S4, but the Galaxy Nexus is to good to throw it into the rubbish without any hardware fault...
You need more information? Please ask me!
Thank you for your help.
Jakob Kühne
Did you wipe data before flashing the rom?
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
Did you wipe data before flashing the Rom?
Click to expand...
Click to collapse
Sometimes I wiped it before and sometimes not, I tried it so many times and it doesn't make any change to the boot issue :/.
wipe data and cache then flash whatever rom you want.
if it doesnt work, try to flash stock rom.
That is bad zip.
Sent from my Galaxy Nexus using xda app-developers app
If any method mentioned in earlier post don't work, then follow this guide thorougly.
http://forum.xda-developers.com/showthread.php?t=1626895
So I was working on putting on a new ROM and when I went to install the PA G Apps zip it said in my recovery that I didn't have enough space in the system storage. Which was a little confusing since I had just wiped it like usual through the recovery before I do a ROM. However I was navigating the recovery since it had been a while and just check out some of the things I didn't notice that changed. Went to the Mounts and Storage area, then I guess I touched "Format /system" and when I realized that it moved to asking me if I wanted to format /system I tried to push NO but apparently I have fat fingers and still pushed yes...So now after having rebooted the phone it is stuck at the screen "Google *small unlocked Lock at the bottom*". And now I'm not sure what to do.
Any advice?
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Well the issue is it is stuck...I let it sit for at least 5min or so and it just sat there at that same spot. Is that because I need to reflash it? I have the Galaxy Nexus Toolkit, but I haven't used it as of late since I haven't needed it. If you don't mind going into detail I would appreciate it .
Should also mention if I go into the bootloader, it hangs at "Downloading..." so effectively I can't do anything to reflash my ROM or anything. And I probably should be clear that this all happened AFTER I flashed the new ROM and then remembered I needed the PA G Apps. Should have refreshed my memory with doing this sort of thing since I'm not as experienced as I use to be long ways back.
Ysosrslawl said:
Should also mention if I go into the bootloader, it hangs at "Downloading..."
Click to expand...
Click to collapse
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Ysosrslawl said:
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Click to expand...
Click to collapse
Yeah, make sure you hold BOTH volume keys for bootloader. Hold only VOLUME- for Download mode as you've seen before. If you indeed held both keys but still got to Download mode, chances are you have a broken volume key.
Sent from Google Nexus 4 @ CM11
Yep I'm dumb apparently and misjudged how the buttons were being pressed down...now on to step 2! Hmmm....
Seems like the zip for the ROM isnt in the storage anymore. How do I copy it back on from just being in fastboot mode or recovery? I'm not familiar with ADB at all. I may have figured out the problem so hold on...I think I derped and forgot that I removed the device drivers off my desktop because I wanted to fresh install them way back.
Edit2: Doing this the hard way.
OK SO I feel like a total noob, which I really am. I've never used ADB, never tried pushing files, or anything of the sort. I tried for a very long time to get the Galaxy Nexus toolkit to help me out but it REALLY didn't do ANYTHING for me. None of the options worked like I had hoped, the ONLY thing it did for me was to install the missing drivers I needed. Other than that it was utterly useless. You guys may find this funny, but I really had no idea on how to fix this even in the slightest. Even with the responses put here by some of the community.
However, with a little searching I was able to find the answers to my questions, not found here on XDA unfortunately. What I ended up doing was updating my SDK tools and learning how to open up ADB (had no idea why the adb.exe wasn't just opening for me like I assumed it would). From there I used the sideload option in my recovery to help me get my ROM flashed back on my phone. So now all is well and I can go back to being a noob who just likes to find good looking ROMS and play with them every couple months.
Thanks, my issue is now resolved.