Weird Problem! Cant unlock/factory reset .. - Samsung Galaxy Nexus

My sisters gnex is acting strange.
I try to unlock bootloader.. it says unlocked, and when rebooted, says again locked.. (in fastboot)
Also when i try to reset the phone(factory reset), using stock recovery, or the option in the settings, NOTHING happens!!!
The phone reboots, and it is in the same state it was a couple of days ago with:
gps opened, 3g enabled...
Whatever i do to the phone, it restores to that state...
Also some random reboots occured in the past, and phone again went to this state, no matter what changes you do on the phone. eg my sister put face unlock.. and after a random reboot we got:
previous unlock method and.. gps on, 3g enabled..
Any ideas???
Phone is on 4.0.4, and IMM76K..
3.0.8 kernel.
Stock

now, i unistalled all apps, restarted, and ALL was back there...
even gps was open...
It seems we cannot do any change....

I would return it, and get a new one.
Sent from my i9250

isnt any solution to this?
fastboot command for factory reset is:
fastboot erase userdata
and ..
fastboot erase cache
?

Related

[Q] Nexus Prime continuously rebooting

I brought my Nexus Prime from Korea last month.
A few hours ago I was listening to music on my phone when it rebooted. After that it came back on for roughly 10 seconds before rebooting again.
I uninstalled a game from my phone roughly 30 minutes before this error happened.
I cannot use my phone now, I get a few seconds of use out of it before its stuck in a continuous reboot cycle.
I have tried letting it cool down (it was a hot day), removing the simcard and changing batteries. Not sure what else I can do with only a few seconds of use.
Model number - SHW-M420S
Is anyone able to help me get out of this reboot cycle?
Try to back up important things and do factory reset. Is your phone rooted? CWM recovery installed? If so, before doing factory restore you could try wiping cache/dalvik cache first.
Sent from my super Galaxy Nexus plusĀ®
Luckily its still a new phone, so there isn't much on it.
The phone is rooted in that I cannot access it in any way. Even connecting to a computer is useless as its only on for a few seconds before it reboots itself.
CWM recovery isn't installed, will be when the phone is working again though!
Is there a way to wipe the cache/dalvik cache or factory reset while the phone is off?
fastboot will allow you to erase data,userdata, as well as flash a custom recovery like cwm or a full rom.
bk201
edit: boot your device with POWER+VOLUP+VOLDOWN into fastboot. search google and/or xda for some fastboot tutorials.
I had this problem awhile back. It was a bum phone with hardware issue. I had to exchange it. Yours may be in the same boat.
I will try a fastboot later today and let you know the outcome, thank you.
If all else fails I'll send it back to Korea for new hardware I guess.
I ran into this problem a while ago. I had to restore the phone to stock using the image from Google. Haven't had a problem since

Phone not booting

Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!
ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.

Weirdest problem with the 816

So I am keen on how to fix bootloops and going back to stock/rooting, etc...
My friend asked me if I could fix his phone for him, so I said why not. Thing is, it's the weirdest problem I ever faced with a phone, EVER.
The problem is the phone boots normally, I unlock the pattern, some seconds later it turns off and reboots. So I said hey why not boot into safe mode, perhaps it's an app causing all of this, so I did, worked perfectly, turns out "Google Play Services" was "forcing close" and suddenly phone turns off. I uninstalled all updates, cleared data, cache, everything and installed EVERY SINGLE APP on the phone and removed pattern, then rebooted phone. BUT, when i rebooted, the pattern was back, language was back to arabic (I changed it to english when in safe mode), ALL APPS were back, and the updates to Google Play Services were back. It's like I didn't do anything. So I said before it turns off I'm goin to try 1 thing, so I immediately went into settings and managed to uninstall updates for Google Play Services and cleared cache data, even to all google apps, and then I re-uninstalled all applications (out of safe mode), I thought perhaps when irebooted from safe mode, everything was back, now that I'm goin to reboot out of safe mode, this will work. So I rebooted, and guess what? EVERY SINGLE APP was back, system language back to arabic, AGAIN, and pattern was back and GPServices updates were back.
So I said hey, let's factory reset. SO I went into safe mode, I hit factory reset, phone reboots to recovery (vol up + power ) > Factory reset done > wipe cache partition done > reboot : EVERYTHING WAS THE SAME. I am completely shocked. I tried doing Factory reset out of safe mode too, same result. So I said hey, let's unlock this thing and just flash a stock rom, that'll fix it indeed. I went into fastboot and tried flashing the unlock token, the confirmation page appeared, clicked "YES", phone reboots: PATTERN AND EVERYTHING STILL THERE, while they shouldn't be since unlock performs a Factory reset, so I went back to fastboot and it indeed was NOT unlocked, I tried many times and it failed every single time I tried.
So I said hey, download AVG Antiviirus and run it perhaps it can find the problem, so I did and ran it, couldn't find anything, rebooted phone and AVG was gone. So I said, hey, again, download Google Play Services and install it on your phone, perhaps it will permanently override the one existing and it will fix the problem (it didn't, it would disappear and the old G.P.S reappear as soon as I reboot). So I said hey, you got the OTA Zip, it has the firmware, perhaps flashing that firmware will shake things up, most probably brick the phone but perhaps will let me unlock it. So I went into fastboot > fastboot oem RebootRUU > phone reboots normally, I CAN'T even access RebootRUU.
So as you can see I probably tried everything one can do in this situation.

[Q] Phone randomly crashes, trying to root now.

I had the phone for about a month now, i bought it on ebay it stated it was New, i check and it is still locked S-On.
But just randomly it started to crash and reboot. I tried all the basic steps, remove apps but every time it reboots it reloads everything back on it.
I tried both hard reset and factory reset both did not work. I'm noticing that i cant turn off fast boot because once it crashes and reboots, all the setting and apps go back to the way it was. Now I'm trying to root it to see if that would cure the problem and thinking possibly an update got corrupted or something and i know once you root it, it will erase all internal data.
While trying to root it, i got all the way to loading the bootloader and once i selected yes to unlock bootloader, it restarted but nothing happened it went back to the way it was. I've tried to delete/erase my data and cache through windows command but keeps saying it failed. Also now i cant start the bootloader over again.
Any ideas what i can try or do? is there an Hboot loader since I'm not able to turn off the fast boot in the setting?
I'm very new to rooting but catching on quickly.

Bootlooped 30min, then came back. Memory corrupted? How do I check?

Okay, today evening, my Nexus 5X rebootet already 5 times while I was using it just as every evening (browsing web, watching youtube, nothing special).
After the second reboot, it actually vibrated two times during the boot animation (after entering the decryption pin) like it usually only does when powering it up.
After the third reboot, it bootlooped for more than 30min (!!) ... Just the bootloader (white google logo), then ~3s black screen, then vibrating and Google Logo again!
Entering boot menu was possible... I used it to power off and reboot, but didn't help. I was just letting it bootloop while I searched my old Nexus 4 to reactivate it
After the 30min or more bootlooping (by the time I already found my Nexus 4 and reinstalled its battery ) the Nexus 5X asked for decryption pin.... I entered it, it rebootet. It asked again. If finally bootet.
After ~3min of use (just enough for a whatsapp backup) it rebootet again and bootlooped again for ~15min. And same again.
Now it is back once again - for the moment.
I need help, what can I do now, except backing up all relevant data?
It is stock android, not rooted, bootloader locked
Can I somehow test the memory? See why it rebooted?
It NEVER rebooted before since I own it...
Thx
The device rebooted after few minutes yesterday... It still overcomes the first bootloop from time to time after dozens of bootloops but then crashes most of the time after I was able to enter the pin. Since yesterday, it only managed to finish booting two times but always rebooted after few minutes.
Is this the famous BLOD? Haven't heard of it until today (sorry) ...
I actually had OEM unlock enabled in the developer menu, so I could actually unlock the bootloader...
Can I verify that it actually is the BLOD by unlocking the bootloader and temporary booting the modified boot image using fastboot? I don't want to flash something at the moment, because I might get it replaced... I can lock the bootloader again afterwards, right?
I think it might be possible to use "fastboot boot boot.img" (using the 4-core kernel image) from the bootloader screen. That won't install anything.
Thx. However, it requires me to unlock the bootloader and delete all data, since there is no 4-core kernel provided/signed by google, right? I will be able to lock the bootloader again afterwards, as long as I won't flash a different kernel (or reflash the stock kernel), right?
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
caifaz said:
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
Click to expand...
Click to collapse
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
RFZ said:
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
Click to expand...
Click to collapse
you're welcome, there is no need to flash a bootloader, just flash the TWRP recovery (modded for 4 cores), restart to recovery and then flash EX kernel (modded for 4 cores) according to you SO version.
I have fixed a phone 2 years ago using this instructions
Okay, I just verified it... The device boots fine with the 4 core kernel. I then reflashed the stock image, locked the bootloader, and it bootloops again. Will send it back to the store now and hope I'll get a refund/replacement :fingers-crossed:

Categories

Resources