after the reboot the only thing my screen ever displays is garbled colored pixels even after pulling the battery. Fastboot still works just fine, so I tried wiping everything and reflashing but it still never shows anything but this screen. I even tried reflashing older versions of the bootloader and nothing works.
I was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not: Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there.
So, I turned on my phone and now it goes straight to the bootloader. So, when I select "Start" option, screen turns black (can still see backlight shining though). It was sitting there for hours, but screen stayed black.
I did have a rooted phone, but I hadn't tinkered with it for about 6 months.
Just wanted to upgrade my sisters phone which was running an old 5.1 version (custom rom, so the phone was unlocked and rooted already) to an android 6.0.1 custom rom. So I flashed newest twrp and flashed 6.0.1 bootloader and radio.img via fastboot using wugfresh tool and the files from the thread on here. now when trying to get into recovery, I am stuck at the google logo.
I have a nexus 5 that I was preparing to hand down to my wife. I had transfered everything over to my new phone, and initiated a factory reset. It rebooted to the "erasing" screen, and sat there for about 20 minutes, before switching to the dead android screen (w/ red triangle.) I thought that was odd, did some searching, and tried the recovery mode from the bootloader. That produced the same results. So now I'm stuck.
From the boot loader I can access the following options:
Start -> Erases for ~20 minutes, then dead android Restart Bootloader -> Screen goes blank, phone vibrates, and then back to the bootloader screen Recovery Mode -> Erases for ~20 minutes, then dead android Power off -> turns off the phone
I called Google, and the tech support hadn't heard of anything like this. Because it's almost two years old, he transferred me to LG's tech support, who basically said find a local repair shop, or they could RMA it for an unknown cost.I'm pretty sure the phone is bricked at this point, which is frustrating, because it was running stock android - completely unmodified. I think I might have rooted it once, months ago, but I can't imagine that that would have caused this issue. I had even received and installed Marshmallow OTA, and it was running perfectly.
Anyway, some program I might be able to use on the PC to regain access to my device.
Literally the only information I can provide about the phone at this point in time is as follows: Product_Name - hammerhead Variant - hammerhead D820(H) 32GB HW Version - rev_11 Bootloader Version - HHZ12k Baseband Version - H8974A-126.96.36.199.27 Carrier Info - None Serial Number - 047.... Signing - Production Sercure Boot - Enabled Lock State - Unlocked
so I was trying to flash the latest Nexus build to my Nexus 6, but the bootloader was taking 10+ mins to flash, so I tried closing out of cmd and then restarting my phone into bootloader. Unfortunately, now, my computer doesn't recognize my phone, saying that the drivers are no bueno, so that when i type fastboot devices nothing shows up.
my Nexus 5 has recently run into a problem where it suddenly decided to get stuck in a bootloop. I figured I could just reflash the stock rom via the boot loader with the wugfresh root toolkit but that unfortunately didn't work. But by doing this I noticed that my bootloader was not staying unlocked when I try to unlock it. Every time I unlock the boot loader and it restarts the bootloader automatically re-locks. I then proceeded to try and manually flashing the stock rom files individually and unlocking the bootloader each time I flash a file which was really annoying. It still hasn't worked and I'm starting to get worried because I've also started to notice my recovery can't really factory reset or wipe the cache. Instead I get this message at the bottom of the screen:
E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/log E:Can't open /ache/recovery/log E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/last_log E:Can't open /ache/recovery/last_log E:failed to mount /cache (Invalid argument) E:Can't mount /ache/recovery/last_install E:Can't open /ache/recovery/last_install E:failed to mount /cache (Invalid argument)
So now I'm completely stumped, could this be the end of my Nexus 5?
I wanted to test marshmallow so I decided flash xtra smoth rom by daniel84cs.as I am coming from lollipop so I flashed bootloader and radio of marshmallow but then I stuck into bootloop somehow I managed to get my backup restored now I am back to lollipop as I have done a factory rest before restoring so I should need to flash lollipop bootloader and radio again or I am good to go?
Will rooting my nexus 5 without unlocking the boot-loader void my t mobile warranty? My Phone is an LG Nexus 5 running the latest Version of lollipop and the only reason i want to root it is to be able to connect my ps3 controller to it and play emulators or minecraft...
step 4 is where things get funky, when I tell bootloader to load recovery mode the phone restarts and then boots normally.I've been hacking at this for a few hours, and ended up loading the boot.img file more than once (see steps below) -- the original attempt worked and would access recovery mode the "load from zip" option wasn't available to I started tinkering, at one point I told it to restart from recovery mode -- it listed updating 7 files after which it had flashed itself back to factory defaults.I then flashed the boot loader a 2nd time it stopped accessing recovery mode
since then I've tried - download Quick Boot app (crashes when trying to load recovery mode) - flashed with fresh factory image - numerous attempts to restart into bootloader - voodoo chanting (not really but that's next)
My nexus 5 just turned off and is stuck on the boot animation. I am able to access the bootloader and have already tried to wipe cache and performed factory data reset but the phone is still stuck on the boot animation. I have tried to unlock the bootloader with 1-click-nexus-5-bootloader-unlock as well as CF-Auto-Root-hammerhead-hammerhead-nexus5 tools but after I accept to unlock the bootloader, the phone reboots and gets stuck on the boot animation. The bootloader status remains locked.
I've a Nexus 5, stock rom 4.4.4, rooted. Since 3 or 4 days I have unwanted reboots. And today, my nexus powered off and didn't want to reboot.
Even I press the power button for a long time (more than a couple of minutes) , nothing happened. The only thing I got, is when the device is plugged on usb charger : the nexus boot on the google logo then switch off and boot again on the google logo then switch off again and again and again....
I can't access bootloader or recovery... If the device is bricked, I just want to recover my. Is the flash memory could be recovered?
Is it possible to make a backup of bootloader? If it is, how? I am not talking about kernel (boot.img is the kernel, correct?), system, recovery, or data. Bootloader.My Nexus 5 came with bootloader version hhz11n. The factory image from Google (4.4.4) has bootloader version hhz11k.
How different these two are, but since hhz11n image can't be found anywhere, I want to back it up before flashing to Lollipop or Marshmallow.
My Nexus is still running 4.4.4, bootloader unlocked, rooted, with TWRP installed.
Is there anyway on kitkat 4.4.2 to root the phone without opening the bootloader or setting my device on USM (USB Mass STorage)?I think not as I'm searching on google since 2 days but still maybe some genius around here has something for me ?I need to do some recovery on my device but I can't because I'm not root.
I have flashed various version 5 stock firmware's and the latest 6.0 using nexus tool kit, as well as specifically flashing only stock recovery using the tool kit and I cannot load into the stock recovery. I've spent hours looking for information on manually flashing the stock recovery without the tool kit but have found the instructions very vauge. Any information on flashing manually only the recovery would be very useful or information on why I may be having this issue.
I know every time i flash a rom it only shows about half of my internal storage. I have a 32gb version. So I end up having to go into a recovery "temp flashed" using the tool kit in order to clear some information and then i get my 32gb's back.
I"m wondering if the space being auto allocated or partitioned is interfering with the flash of the recovery..
I forgot my unlock pattern and I don't have my device in ADM ... But the bootloader is unlocked, so I think I can install any image I want, right? Could this be a way to get into my device? So any solution to unlock my device without doing a hard reset?
My rom is very slow during flash: now I use xubuntu in virtual machine ( I try also Ubuntu, but the problem has remained ). For me insn't a problem of Rom, because this problem is present also with only aosp code, but is of my environment ( configured with guide in XDA ) .
I had cynogen mod installed and my phone rooted. Then all of a sudden i get a boot loop. I tried to flash but I receive an error FAILED <unable to flash write>. im able to go into recovery and boot loader. In my team win recovery in the terminal I get multiple errors saying "E:unable to mount '/data", "E:unable to mount /ata/media/TWRP/ .twrps when trying to read settings file" ,"E: No valid storage partitions found for MTP" (when i try to enable mtp), "E:unable to mount '/persist" and "E:unable to mount storage"
I used to be a Blackberry user, and backing up and updating the device was as easy as plugging it into the computer and running Blackberry Link. This will be the first time I try to backup and my Nexus.
I'd like to follow the guide that was posted on this blog about installing 5.0 from the factory image ( i can't post the link, but its safeurl is 'android-50-hits-nexus-devices-heres-how-update'), but I'd like to backup all my apps, their settings, texts, pictures, etc first, then flash it to get a fresh install then restore the backups.
i have a nexus 5 rooted on stock android 5.1.1 . I am trying to flash the 5.1.1 factory image to unroot my device. But unfortunately i just get this message when its trying to flash the system.img and my device is now bricked target reported max download size of 1073741824 bytes load file:could not allocate 1073741824 bytes error: cannot load 'system.img' : not enough space.
I used adb to install TWRP onto my Nexus 5. Now it is in a bootloop, and TWRP does not seem to be able to mount anything. When it reboots it looks like it automatically goes to the TWRP where it says it is running OpenRecoveryScript but it is unable to mount anything. I tried a boot start to Recovery and it worked but when i tried a factory reset it says the same thing.
Got the new Nexus 5 and found that flash video playing is totally incompatible with the Android 4.4 Kitkat, no t in Dolphin, not in Firefox and other browsers. This is too bad and I can't imagine it just happened.
I digged into the code since then and found that some critical APIs have been removed from Android 4.4 that flash uses.
open failed: cannot locate symbol"_ZN7android10Vectorlmpl19reservedVectorlmpl 6Ev" referenced by "libflashplayer.so:..
After several days of coding, I finally found a way out with a hacked flash player. Being so excited and i can't wait wo share it. Here is the guide about how to install the hacked one and how to play flash content in the sites in Dolphin Browser.
1) Download Dolphin Browser
Surprised, Dolphin just push a 10.2.0 update version to me and I found Dolphin Jetpack was built-in. This means you don't have to install 2 separate APK now.
Here is the Download Link: [URL] .....
Warning: [/B]You must have Dolphin Jetpack on in the settings to enjoy it. As far as I have noticed, Dolphin Jetpack better solves the compatibility with flash player, such as crash issue & freeze issue in full screen.
2) Download the hacked flash player HERE
Warning: Make sure that you have uninstall the flash player installed in your device and then install the hacked one for compatibility reason.
If your devices refused to install apk outside Google Play, you may set in your device (Settings> Securities> Unknown resources) to allow installation of apps from unknown sources.
3) Make sure that the flash setting in Dolphin Browser (Click Menu>Settings>Web Content>Flash Player) is on.
Flash Player is not officially supported and therefore the speed of loading of flash video may be slow. However, I have tried many sites such as YouTube and Hulu. They all work properly with satisfactory results.
I've been having issues with my rear camera on Nexus 5 (my front facing camera works fine). Currently the camera and the flash will not work and basically stopped working some time around the upgrade to lollipop. While on lollipop, I tried uninstalling the app updates, restarting, clearing the cache... Now, I'm currently running 6.0 and still the camera/flash are not working. Tonight I tried wiping the phone and reverting all the way back to kitkat 4.4.4 to see if that would fix it. I tried this multiple times, wiping and reflashing to various versions ranging from 4.4.0 to 6.0 to see if any would somehow fix the camera issue, but none worked.
At this point, I'm back on 6.0 and its still not working. My phone doesn't even show the default camera app in the app drawer. I have to access it through the shortcut on the lock screen and when I do I get the "Can't connect to the camera" message. I'm assuming its a hardware issue at this point. From what I can tell, the flash is not part of the camera module, so if the camera itself broke, it seems like the camera flash should still be recognized and functional (its not in my case, not even an option for the default flashlight on the taskbar pull-down screen). I am wondering if its worth buying an oem replacement camera module and installing it to see if this fixes the issues.
I am trying to flash 4.4.3 to my N5, but fashboot flash command is stuck at "sending.." and the fastboot screen is stuck at "downloading..." If I hold the power button to reboot the phone then it boots fine.