Bootlooping Galaxy Nexus - Samsung Galaxy Nexus

I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!

rs18 said:
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
Click to expand...
Click to collapse
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.

Jubakuba said:
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Click to expand...
Click to collapse
Thank you. I'm an idiot. It's been a long while since I've put this into recovery via physical buttons.
By the way, your guide is excellent. How have I not stumbled across this?

Related

[Q] Nexus 7 2013 recovery issue.

Hi there,
I'm not new to rooting and flashing devices, but something went wrong during my last root. I was using CWM to root the most recent paranoid android rom, a 4.4 rom, and after I rebooted, the device started normal and works fine. However, it's completely lost root AND has no recovery. Just the little opened up android guy with his red triangle.
I've tried using the toolkit, but the ADB drivers just are not being recognized. I've tried all of the driver options, and it says that it worked, but when I run the driver test it says failed. When I connect the device as MTP, it shows up as having recognized the device, but I can't actually access the device from the computer. When I try fastboot, nothing happens. The device just goes black and sits like that until I hold the power button down for awhile.
So, the toolkit can't get me back to stock, at least not any way I've tried. And since I can't install a recovery, I can't flash a new rom or stock.
I guess it could be worse, as the device does still work, but I want it fully functional.
Does anyone have any solutions?
Hopefully this is the right place to ask this question.
Thanks in advanced!
lasnaranjas said:
Hi there,
I'm not new to rooting and flashing devices, but something went wrong during my last root. I was using CWM to root the most recent paranoid android rom, a 4.4 rom, and after I rebooted, the device started normal and works fine. However, it's completely lost root AND has no recovery. Just the little opened up android guy with his red triangle.
I've tried using the toolkit, but the ADB drivers just are not being recognized. I've tried all of the driver options, and it says that it worked, but when I run the driver test it says failed. When I connect the device as MTP, it shows up as having recognized the device, but I can't actually access the device from the computer. When I try fastboot, nothing happens. The device just goes black and sits like that until I hold the power button down for awhile.
So, the toolkit can't get me back to stock, at least not any way I've tried. And since I can't install a recovery, I can't flash a new rom or stock.
I guess it could be worse, as the device does still work, but I want it fully functional.
Does anyone have any solutions?
Hopefully this is the right place to ask this question.
Thanks in advanced!
Click to expand...
Click to collapse
Few things:
try another soft reset. power the device on, and then hold the power button down until it restarts.
download superuser/supersu to see if there actually is no root. sometimes it's just being difficult and says there is no root.
Following that, try downloading ROM manager and seeing if it'll flash the recovery.

[Q] Help w/ semi-bricked device (please)

I bought this Verizon Galaxy Nexus a while back to use as a media player on a trip.
It already had Paranoid Android on it.
After the trip, I messed around with it, and stupidly wiped everything but TWRP v2.3.2.1.
Now I have a device that boots into TWRP, but thats it. There is nothing to Restore or Install.
I have downloaded updated ROMs, but when I plug into my PC, the phone isn't visible.
Any advice would be appreciated.
scottfish said:
I bought this Verizon Galaxy Nexus a while back to use as a media player on a trip.
It already had Paranoid Android on it.
After the trip, I messed around with it, and stupidly wiped everything but TWRP v2.3.2.1.
Now I have a device that boots into TWRP, but thats it. There is nothing to Restore or Install.
I have downloaded updated ROMs, but when I plug into my PC, the phone isn't visible.
Any advice would be appreciated.
Click to expand...
Click to collapse
load a rom into memory card.put it onto nexus.if twrp has file manager to copy from memory to internal.or flash by browsing there.and flash.....tada
scottfish said:
I bought this Verizon Galaxy Nexus a while back to use as a media player on a trip.
It already had Paranoid Android on it.
After the trip, I messed around with it, and stupidly wiped everything but TWRP v2.3.2.1.
Now I have a device that boots into TWRP, but thats it. There is nothing to Restore or Install.
I have downloaded updated ROMs, but when I plug into my PC, the phone isn't visible.
Any advice would be appreciated.
Click to expand...
Click to collapse
I have a good feeling that your pc is detecting your phone because of the twrp. This happened to me. I would download the latest TWRP and flash it using fastboot.
Once I updated to TWRP 2.8.0.x, I was able to use adb again in recovery which it seems like you know how to do. If you have any questions about anything, let us know though. Hope this helps man.
INSTRUCTIONS
-Get to the bootloader with volume up + volume down + power.
-Connect the phone to the PC. Enter at the command "fastboot devices" to see it show up.
-Now locate your newly downloaded TWRP.img. Enter:
Code:
fastboot flash recovery <path_to_recovery.img>
Thank you for this.
I actually got a crash course in ADB last night. I was able to pushe several ROMs into memory, but nothing stuck. They all kept failing.
The phone was rooted and had Paranoid Android on it when I got it. i never had success running anything else on it.
I think your instructions will help me get TWRP updated which should help. So far, I pushed the new TWRP image with adb, but didn't know what to do with it.
I will mess around with it more tonight.

Phone soft bricked after applying software updates

Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.

Find 7a won't boot to recovery, not recognised in USB at all

Hi all,
I'm turning to forums now because I'm desperately in need of help.
I have an Oppo Find 7a which I bought about 9 months ago. When I first got it I tried flashing Cyanogenmod to it (unsuccessfully), and then tried rooting the phone. I have since unrooted the phone, and am running Color OS v 1.2.5i and really really need to update. Problem is, I cannot seem to update the operating system. Here's what happens:
Phone fails to boot to recovery
In my attempts to install Cyanogenmod, I installed a custom recovery. However I couldn't get Cyanogenmod to flash properly, so I tried reverting to the stock recovery. Did that, which seemed to work fine. However, since rooting and unrooting my phone, I cannot boot into reocovery at all. When turning off the phone and then pressing power+volume down to try and boot in, the "OPPO" logo comes up as if trying to boot into recovery, then the phone just turns off and boots into normal OS. Have tried many things but can't seem to get into recovery at all. This means that when an OS update is detected (which it is), the phone tries to reboot into recovery to install the update and cannot. So I'm stuck on a very buggy OS and can't do anything to update. Before you suggest adb+fastboot solutions, please read below:
Phone not recognised in PC at all
When plugging the phone into a PC via usb cable literally nothing happens (aside from the phone detecting it is charging). The phone does not mount as a volume in Windows, the phone is not detected as a device in device manager, as far as the computer is concerned, the phone is not even there. I have tried having the phone plugged in and installing all the proper adb drivers, but this has still yielded no results. And yes USB debugging is definitely enabled on the phone. I don't know why, but for some reason I literally cannot plug my phone into a PC anymore which limits me a LOT in terms of fixing the problem above.
Basically I really need to update the OS on this phone and am compeltely stuck: nothing seems to work. Can anyone help me out here. What do I need to do?? Any help is greatly appreciated.
seem adb device in windows device manager when the phone plug USB at bootloader?
if yes, you can use adb+fastboot solution

Phone Potentially Bricked Please Help

So I've had a read through other threads on different sites and youtube videos etc.
Basically I was trying to root my phone using magisk following the video where TK roots a oneplus 5, but was switching out the software for the oneplus 3 version of twrp.
All was going well, connected phone to pc, unlocked it, copied the files across, flashed and installed twrp then when it rebooted after installing twrp it came up with an error saying that "dm-verirty" is not started in enforcing mode, and the phone wouldn't boot past that.
I relocked the OEM, as I couldn't get it to recovery mode (stock) so tried that and now I can get it into recovery mode.
It will happily go into fastboot mode, have tried reflashing stock recovery and trying to update the os via adb.
Have been looking at the Mega Unbrick Guide - but can't get my phone to show up on my pc to even begin there.
Would appreciate any and all help, plus tips for what to do after I get it back to stock as I'm still keen to root my phone but don't want to screw it up again and have to go through all of this again.
The Mega Unbrick guide is your best hope. Did you install all the drivers on your PC? Specially the Qualcomm ones? Also, make sure to press the volume up button like it says in the instructions for 40 seconds. Otherwise it doesn't show up. If all fails, try using a different PC.

Categories

Resources