Google Nexus 5 :: Rooting Without Unlocking Bootloader?
Oct 11, 2015
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...
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.
Rooting and unlocking. Up until I rooted my nexus 5 in the hopes to get side by side apps I haven't rooted since my gs2. Anyways I rooted my phone via the nexus 5 root toolkit and unlocked the bootloader and whatnot. I found out that I couldn't do side by side because it wasn't available for my version of android. I attempted to unroot and return to stock and I just unrooted and locked the bootloader. Can't figure out how to return my phone to stock without twrp. Every time I try to do OTA updates it just restarts to twrp and it's super annoying. How to get back to stock so I can do OTA updates?
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 had a new nexus 5 running on android 6.0 ,I was planning on rooting my phone , had the oem bootloader unlocked - the twrp installed , however after flashing the elementalx and beta supersu , my phone was in a bootloop for 4 hours. I did everything as told in the tutorial video for rooting and now i think that by flashing the nexus 5 stock rom it might be useful in recovering my phone... How to flash stock rom on nexus... when I tried getting into the recovery mode it was still in twrp ...
So I flashed M p1 and then updated to p2 without need of root.Now I just needed that for a particular reason and I used NRT root option, but it was too late when I realized that it was flashing the stable version of SuperSU and would not work. Since then I've flashed 2.49 (beta) one that I read somewhere that should clean the files from previous installations, but it's not booting at all. Basically I want to keep the files on SD and applications. So, what should I choose? Deleting SuperSu files from Recovery? Flashing only System back? Any other method available for my scenario.
Rebooting to recovery using twrp doesn't happen? I've tried re flashing recovery with fastboot and even selecting in bootloader boot to recovery after and still just boots into android.. Is it chainfires boot.img causing the problem?
After rooting device (not my first time, but my first time with my nexus 6 which was a virgin) I tried installing a custom font. I downloaded it and tried installing "X" font and said my system storage was full. I tried clearing some stuff but failed. I thought it was an error so i downloaded a new app and failed too.
I verified if my phone was rooted and it is. Later I decided that I wasn't in need of a custom font so I left it at peace, but I remembered about Xposed framework and want it to install it just for the modules , but failed terribly after showing me a message that said "not enough storage space." Broke my heart. I unrooted and OEM locked my phone and re-rooted to no avail. Still the same ol' problem.
When in the root process, I remember while booting into custom recovery temporarily I saw this new message (I had never seen before) that said Something about the system partition to set it to read only for future OTA's processes and I left it untouched.
Also I checked on Titanium back up and other apps. Cache: 256mb-------------- 13.4mb used, 242mb free---Good System: 2GB ---------------------2GB used, about 300KB free---Bad Data (userdata) 26.5Gb----2.5GB used, 24.1GB free---Good Ram---- who cares. Its ok.
I want to have space to install Xposed, all these fonts and stuff. How can I free space or somehow to let my phone now there's more space or idk something.
Like the title says I can't write anything new into my rooted N5's system where it says system is out of space or something like that... I can copy files of KB sizes but not MBs... I have V4A libs and SuperSU in the system and now been trying to put in avast antitheft which is not working... This also happened when I tried to install xposed... BTW mine is stock lmy48i rooted with elemental x... Now I had to delete Google books just to install the antitheft!
My unlocked Nexus 5 during kingroot rooting process my laptop shut down and now its in a boot loop stuck at logo. I can bring up bootloader and ADB but no back up or recovery on phone hard drive.exactly what do I do?
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-220.127.116.11.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?
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?
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.
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?