Google Nexus 5 :: Radio And Bootloader Of Lollipop
Oct 22, 2015
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?
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.
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-184.108.40.206.27 Carrier Info - None Serial Number - 047.... Signing - Production Sercure Boot - Enabled Lock State - Unlocked
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 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?
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)
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.
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.
Since updating Lollipop to 5.1, Google Now will not recognize contacts with voice. It repeatedly gives me the response, "You don't have contact details for ___." I have deleted and then restored accounts, cleared cache, checked to make sure all settings are correct in Google Now, all to no avail.
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?
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.
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?
I just installed Nameless ROM and am having trouble setting the CPU speeds. I've tried with Device control (built in) and then with No Frills CPU, both with root access, and have not had any success setting my CPU speed. When I set anything on minimum, I exit the app and when I return it goes back to its original value (1574). Same thing with No Frills. I have BusyBox installed and the latest version of SuperSu. I do not have a custom Kernel, but my experience in the past has been quite similar with Franco Kernel and ElementalX kernel across a number of different ROMs.
I've got some random reboots after upgrading on stock Lollipop 5.1 on my Nexus 5.I've used Android 5.0.1 without any reboots or problem, but after upgrading on 5.1 I'm facing many random reboots when I switch from an app (like a game or Hangouts) using Recents or Home button from NavBar (it also happens randomly when I'm using my phone, like writing a message on Hangouts).The reboots I'm talking about are not "soft" but "hard", because bootloader's logo (Google) appears and restarts my phone, so it is caused by Kernel Panic (as you'll see in my last_kmsg) and they occured on both stock and custom rom.
How much free RAM are you guys seeing on your N5's after the lollipop update?
After a fresh boot, and opening an app or two, my free memory is running between 250-450mb. After I open too many apps, some won't open, or others start closing. I am handicapped in using my beloved N5.
Andriod Ver - 5.0 Swiftkey Ver - 220.127.116.11 Phone - Google Nexus 5 (32 gb)
I received the Lollipop update yesterday and since then have also updated Swiftkey. Swiftkey randomly stopped working this morning. When I try to type anywhere the keyboard doesn't open up, I've tried this on the Google search bar, Whatsapp, Snapchat and Notes and all had the same result. On going to the Swiftkey description page from the Input Settings, even the Swiftkey info stays for a few seconds and then it automatically closes. If i got to the settings from the Apps tab in Settings then I can view the app info. I switched to the Google Keyboard and everything is fine.
So I flashed the final build of Lollipop on my Nexus 5, worked great for the first couple of days, now I'm getting a camera error, saying failed to connect to the camera. This only happens with the front-facing camera, and it works fine after a reboot but problem comes back after a day or two.
Back when I had an S3, the same thing would happen, but with the rear camera, I thought it was a hardware issue but now I'm thinking maybe not, since it's happening right after flashing a new OS this time (can't remember if the problem on my S3 was after an OTA, or maybe after rooting and going custom ROM)
I have not updated my N5 to Lollipop for about a week after i got the system update available notification. Now the notification does not show up any more, even i check the System updates in "about phone". So now I am unable to update my N5 by downloading the OTA update. How could i get back this system update notification?