Google Nexus 5 :: Bootloop After Rooting Process Power Failure
Dec 18, 2015
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 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 ...
I've been using Nexus 5 since Nov '13, but this is the first time i'm facing a serious issue in my device.I was browsing through Chrome and my Battery was 73%, all of a sudden my device rebooted and here comes the main issue/problem.My device is suffering a boot loop only displaying the google logo for 3-5 seconds and again it reboots.Occasionally the boot animation starts but no success, again it reboots.
I tried to enter fastboot menu, it enters but it doesn't stay there for not more than 2 seconds. So I can't make any choice over there.I tried all the combinations (VOL UP+ Power, VOL DOWN+Power, pressing all the buttons), but its of no use.My device is out of power now.Even when I plug my device to charger/computer its not showing the battery charging animation instead the reboot loop occurs.I suspect it can be a problem with the power button in the board.
My device details: I'm running Stock Android 4.4.4 with stock kernel.(not modified any system files) TWRP recovery V 2.7.1.1 UNLOCKED ( @present Locked) ROOTED. @present Unrooted)
My Nexus 5 is stuck at the flying dots after Lollipop OTA update. Already try factory reset. Cant connect to my Lap (running Windows 10) because it says in the device manager: Unknown USB Device (Device Descriptor Request Failed), so I cant manually update the driver and cant access it with ADB and Fastboot tool. The device has no USB debugging enabled. In the old computer where I used to connect the device and has the drivers installed says the same thing in device manager as my new laptop.
I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: [URL] .... After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission).
Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Nexus on bootloop tried every method ,most of them . Flashing new factory image is also of no good. Cleared cache , factory reset and still on bootloop. On flashing lollipop factory image it gets stuck on boot loop and on flashing KitKat factory image or using any custom ROM like cyanogenmod it gets through boot but is unable to detect sim and apps like play store and camera keep crashing and refuses to open.
A colleague of mine (yes honestly it wasnt me) reported that his Nexus 5 was stuck with as he put it "the wee android man in the middle of the screen" Then, before he give the phone to me to look at he said that he had tried some things with images to get it to work but it didnt work. so truthfully i am not sure what he has done or not done but the phone is stuck as follows:
When you turn the phone on you have the android robot which looks like it is doing an update.
I have gone into bootloader where I have the option to Start, Recovery Mode, Restart Bootloader and Power Off. The lock state in the Fastboot mode shows unlocked.
No matter which option you take (Even Recovery) it just goes back to the android screen that looks like it is trying to update....i cant get to the android with the exclamation mark that would allow me to do a factory reset. At this stage of the game im not worried about any lost data etc.
Well as the title says, I modified framework-res.apk to change navbar dpi (using apktool and copying original META-INF folder and Manifest in my compiled apk). The problem is that when I push the framework to the N5, it wont boot.
Code:
adb reboot recovery adb shell mount system adb push framework-res.apk /system/framework/framework-res.apk adb -d shell chmod 644 /system/framework/framework-res.apk adb reboot
And I also tried to take a logcat when in bootloop (idk if it's stupid or not):
Failed to parse /system/framework/framework-res.apk: Failed to collect certificates from /system/framework/framework-res.apk
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.
I was using the Cataclysm Rom for months without any problems. Today I restarted my phone (I do this every other day, when it gets a little bit slow) and it stuck in bootloop.
I tried wiping dalvik/cache, doing a factory reset, reflashing Cataclysm, nothing worked. So I decided to go back to stock (using [URL] ....) and I'm still stuck in a bootloop every time. I can access and use fastboot/stock recovery in the normal way, but it won't boot.. What I could do?
if I rooted my phone using SuperSU after OEM unlock, so stock rom and recovery just root access, would I be able to apply OTA updates, or sideload them?
A friend gave me his nexus 5 because it have a problem, one day the phone was stuck on boot screen (the flying balls of lollipop) and to add difficulty (can't be easy right?) windows doesn't recognize the phone but it recognize my nexus 5 with the same cable on the same usb port....
I get a "Device Descriptor Request Failed"(the usb port on the nexus seems to be ok) but my nexus get none ... Is it a hardware issue ? I heard that there is issues with nexus 5's motherboard...
I can enter the fastboot and recovery but after a wipe, still stuck..... Not rooted and booloader locked....
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
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?
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...
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.
I'm planing to use Wugfresh Nexus Root Toolkit to do a clean install of the image.. If I have to flash custom kernel, any good one (battery friendly and nice performance).
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.
i remember seeing something like that on this forum before. it was a nice, clean looking home screen and it didn't have the google search bar on the top.
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.
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!
I've received the 5.1.1 update notification twice tonight. Both times it downloaded & successfully verified, but once the install process began, I received an error & the update stopped. What's going on??
My Nexus 5 White suddenly reboots and shows up and stuck at Google Logo startup. It drained battery very quick and turned off while i was going back to home. At home I entered to Bootloader (Vol Down + Power) and then Power+Vol Up for additional menu to Clear cache. It worked and appears it cleared cache and rebooted but it stuck at the logo again.
So I decided to follow guides to Flash everything again. But when I try to flash Cache, Bootloader and System error msg shows up "FAILED (remote: flash write failure)" .
I brought my nexus 5 for almost a year now. yesterday, i was charging my phone via a PC and after disconnecting it from the PC it just started to heatup near the camera area. It became so hot that I was not able to keep in my pocket. Then I tried opening up the dailer to call my friend but it just showed "Process system isn't responding do you want to close it?"
THEN I tried several other apps and these showed up: unfortunately, MTP app stopped
unfortunately, Media Storage has stopped
unfortunately, Settings has stopped
unfortunately, Google play services has stopped
then I tried factory reset but not improvement. during the signin page in the beginning it said Google account manager stopped working, then again process system isn't responding. I tried factory imaging from 4.4.4 kitkat to 5 lollipop. No improvement.
I believe there are some corrupted files that might have updated automatically. i dont want to pay $200 and wait for 3 weeks to get it fixed