I have an unrooted and locked Galaxy Nexus which seems to have got stuck in a bootloop and won't start. I had some important data on the sdcard which I want to recover. Any suggestions on how I can do so? Here are more details about the problem -
I tried to upgrade it Jelly Bean a few days back and it didn't happen successfully. However after that the phone was still working properly and one day when I switched on my Bluetooth, the device restarted suddenly and it got stuck at the initial animation after showing the Google logo. So effectively the device doesn't boot and I am assuming the boot partition either got erased or corrupted.
I also tried connecting the device to my computer but it doesn't recognize the device. I tried it in Windows, it didn't work and I assumed it to be a driver problem. So I also tried it in Ubuntu but still no luck. However the phone does get recognized in fastboot mode using "fastboot devices" but I cannot get the device to mount nor get "adb devices" to work.
I bought the device into fastboot and tried to start the recovery mode but even that doesn't start and gets stuck at the Google logo. This was strange since I haven't touched the recovery partition at all and in fact the device hasn't even been unlocked.
Related
I've been running Cyanogenmod 9 for a couple of months, but decided to restore to stock so I can try out ICS and the new version of sense. I tried this a while ago but got stuck when when phone wasn't recognised via USB when connected to my laptop. Fastboot would change to Fastboot USB when plugged in, but the phone wasn't picked up. However, on this occasion I was able to restore Cyanogenmod without problems.
I tried this again yesterday with the same result regarding the USB connection, but when I restored Cyanogenmod it now just hangs on the boot screen and won't go further. Prior to this, when I ran the restore function in Clockworkmod, the phone would hang on the HTC splash screen with the beats audio logo on it. I did manage to get the phone to boot into recovery, but rather than the usual menu option I had a message something like "checking SD card..." and then nothing.
I am not sure where to go from here. The only thing I am wondering is if I tried to do this with the battery being too low, and the installation has failed because of this. I do want to go back to the stock OS, but not sure how to go about resolving the USB issue.
UPDATE
Partially solved the problem, in that I've managed to reinstall the cyanogenmod. Still stuck with lack of USB connectivity though.
Wrong section.....
Do you have the Fastboot files all in the same folder and do you have the HTC Sync drivers installed? You need that set up correctly to get a fastboot USB connection.
My suggestion is to simply "fastboot oem lock"
Then flash corresponding RUU to your current HBOOT. You can find out which RUU you need by typing "fastboot getvar version-main"
Hey There,
I'm sort of at my wits end with this issue.
I think I know what I've done wrong. I went to flash a new 10.2 rom, along with Gapps to my original Kindle Fire. However, I forgot to factory reset (more like I started it and then felt like it was taking way too long, so I skipped that step). Anyways, I flash the new roms and reboot the device. Now I'm stuck at the revolving Cyanogen logo (off center and going off the screen).
I forgot to install FireFireFire before any of this (yeah, two dumb things so far). So now when I connect the device to my computer, it shows up as this in KFU:
ADB Status: Online
Boot Status: Unknown
When I try to set fastboot via ADB command prompt commands, it says it can see the device, but can't do anything because it is "offline"
Meanwhile reinstalling drivers does nothing,
rebooting the device while KFU is < waiting for device > does nothing,
changing USB slots does nothing.
Device doesn't show up as connected right away via my PC, either. It takes until the CM logo is running before my PC notices it is there.
I've heard I'll need to buy a fast boot cable and that will instantly fix the device by getting me into TWRP again, but if I can fix this locally I would love to hear a method that doesn't involve waiting weeks for a cable to ship to me.
Thanks in advance!
Today I was going to update my CM10.2 20131127 to CM11 20131207. They are both official nightlies. I checked the md5 after downloading. So I booted into recovery, backuped, and did a full wipe. Then I tried to use adb sideload to flash the zips. This is the first time I used sideload. I followed all steps on the TeamWin website. After transfering the zip to the device, it started flashing. After a couple seconds, the color of the screen changed and dimmed slowly. I waited a while and then unplugged the device and the battery. Then the device is completely unrespondsive. No bootloader, no download mode, not even responding when I plugged it in. ADB and fastboot shows nothing. Can anyone help me?
P.S. I am using TWRP 2.6.3.2
doing a fastboot of the factory images do nothing? what about the battery? is it charged at least?
Good luck
Charging does nothing. I followed the steps for OMAPFlash. After that I am able to boot it sometimes. The screen will freeze and dim after booting into both android and bootloader. My computers won't recognize it when I boot into bootloader. So flashing is not possible.
So I reset it again using OMAPFlash. I will crash after a second or two. I plugged it in, ran the fastboot devices command before it crashed. Fastboot can recognize the serial number before it crashes. 12 ? or nothing after it crashed. Should I restore it to factory and lock it or just send it to some specialist?
P.S. When I charge it, it shows the battery with thunderbolt icon and crashes.
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
SyrStorm said:
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
dottat said:
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
Click to expand...
Click to collapse
I can get into hboot and all that just fine. The phone won't boot, and I can't get into recovery is my problem. Oh and the fact that the computer doesn't recognize my phone in fastboot
Update: I just whipped out a really old computer running Windows XP and I installed the platform-tools and HTC One drivers on it. I hooked the phone up to the computer, and the drivers worked. I flashed TWRP and it flashed successfully according to fastboot, but it won't go into recovery still. What should I do now? I know I can RUU somehow (I'm not really sure how though), but I want to try and avoid that, if possible. Any suggestions? Thanks people!
EDIT: NVM it actually booted! What a success! This stuff is crazy!
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob