Develop Bugs

Desperate Help Needed!

So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....

This happened to me, I was not able to solve the issue, even though I could push and pull data to and from the device via ADB. I could still not get past the google logo. I decided to lock the boot loader again and return to the store for a new device.

http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
Sent from my Galaxy Nexus using XDA App

hartford said:
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
Click to expand...
Click to collapse
One more post like this in Dev section and you'll be banned for 3 weeks

Nexus 7 will not function.

I accidently wiped my ROM in twrp while trying to install a new one. I tried to use ADB to push the the file into my nexus 7 but it does not work (I've gone through hours of troubleshooting and nothing worked). So I purchased a OTG cable which twrp noticed but when I tried to install various roms I either get to the google logo and a reboot back into recovery or I get a loop of the starting animation. I have no idea what to do considering none of my computers can notice the device and none of the roms seem to work.

NotARobot91 said:
I accidently wiped my ROM in twrp while trying to install a new one. I tried to use ADB to push the the file into my nexus 7 but it does not work (I've gone through hours of troubleshooting and nothing worked). So I purchased a OTG cable which twrp noticed but when I tried to install various roms I either get to the google logo and a reboot back into recovery or I get a loop of the starting animation. I have no idea what to do considering none of my computers can notice the device and none of the roms seem to work.
Click to expand...
Click to collapse
Have you tried flashing a Factory Image through the bootloader?

Can you try install some custom rom via TWRP?

Nexus 7 (2013) stuck in google logo after downgrading to stock rom 4.4.4 razor

My Nexus 7 (2013) flo comes with Lollipop 5.0.2. I was trying to downgrade to 4.4.4. I followed the online instruction from google. Basically what I was doing was
1. unlock bootloader
2. flash bootloader and stock image from google, razor 4.4.4 using flashing_all.sh
3. I also tried to flash the bootloader and image manually using fastboot command
Everything worked fine, no error message. However, after flashing, the system stuck at the google logo screen. I tried to enter the recovery mode, and it gives several error messages, such as "unable to mount /cache" etc.
Then I tried to flash back the stock image razor 5.0.2 lollipop using the same method. This time, everything worked. I can boot into the system without trouble.
Is there anyone having any idea what happened? Thank you a lot!

you should use nexus root toolkit to flash rom

I have the same problem, did you fix it?

I posted the same problem on reddit's /r/Nexus7. Someone gave the same reply of using Root toolkit which I tried. Same result, stuck on the Google logo. I'm beginning to think this is a major design flaw for some N7's while others were lucky enough not to have the problem. Currently loading Lollipop back and wishing the wifi drivers would work with it. If I can't get it working by the end of the week I'm sending it back while I still can.

[REQ] Help: bootloop after 7.1.1 beta OTA and cannot enter recovery mode

I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.

Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?

DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.

Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK

use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.

DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.

If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app

Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.

If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app

Enter stock recovery then flash the full ota via adb sideload

ADB unable to find my Find7 - but Fastboot works

New to XDA, so hopefully this is in the right place!
My problem
I tried to install a new ROM and it's gone badly wrong. First, I couldn't get the recovery bootloader to launch or to re-install. Then suddenly ADB wasn't working any more, and I was unable to boot up into the system.
Now I get boot loops with the Oppo logo. If I hold down volume up + power, I have access to Fastboot. I can use my Mac to send commands with Fastboot, but I cannot get ADB to find my device. Typing Fastboot getvar all gives me 'All: ' in response, which is not a good sign.
Attempted solutions
I've tried installing TWP and CWM, but both of them just end up booting to a black screen. At one point I tried to flash stock Oppo recovery and got a black and white flickering recovery screen for my trouble, which was unresponsive..so I wiped it and started over. I suspect it was not the correct recovery file, as I really struggle to find what are definitely the correct files now the OppoStyle Forums where I used to download recovery files no longer seem to be active.
After two days of reading various threads and trying solutions, I am really out of ideas now. So any help would be greatly appreciated!
Before embarking on this journey I cleared my phone of anything important, made sure it was rooted and enabled USB debugging. I also wipe everything from Fastboot whenever attempting any fresh flashes.
More context
I've had problems with my Find7 ever since I tried to unify my storage a couple of years back. In the end, I got unified storage to work but on a very old version of ColorOS. I had a lot of problems getting to that point, so from then I decided to just live with the outdated OS. But finally, the frustration of apps not being compatible got to me a few days ago and so I decided to try and install a new ROM. That's when my recent troubles began! I think legacy issues from my initial problems years ago may have contributed to the mess my phone is in now.
So what next?
Ideally, I'd love to get my Find7 completely wiped clean and a modern, stable ROM with unified storage working on it. But at this point, I'd settle for original ColorOS with non-unified storage again if I had to!
Hoping someone here has some suggestions I can try! Can't get worse surely