Is it possible to root my Nexus 5x from Recovery Mode?
My phone is stuck in a boot loop, and I can't access my phone's settings. This means (as far as I know...) that I also cannot enable USB Debugging.
I also can't plug it into my computer to access the internal memory because it isn't recognized under normal circumstances, so that means I can't put any installation zips on my phone. However, it does show up in Device Manager as 'Android Bootloader Interface' if I hold down the Power Button + Volume Up keys. It also shows up as 'Android ADB Recovery Interface' if I use 'Apply ADB Update' while in Recovery Mode. Due to this, ADB commands return as 'device not found' or 'error: closed' if I attempt to use ADB commands to push or pull anything onto the internal memory.
As far as I know, the only way to save the contents of my phone is to recover it using ADB, but I can't use ADB unless my phone's rooted... so I've reached quite a conundrum here. Any ideas on what I can do?
Related
I recently tried to flash back from Lego Rom to stock ZVC and have hit some trouble. I used CWM to clear the caches/data, as per usual, but after installing the ZVC rom the phone just boot loops at the Lego Rom boot screen.
Normally, I would jump into recovery, but my volume buttons no longer work (they failed after a screen replacement, I suspect the ribbon cable is damaged). What are my options? Can ADB force it into recovery for me?
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
LordKyleOfEarth said:
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
Click to expand...
Click to collapse
well first of all yes you can reboot recovery using adb.
But if you installed the zvc rooted ROM then why is it booting Lego?
You can install philz or twrp for a full touch recovery and not need volume buttons. You'll still need to use cmd to do "adb reboot recovery" or adb reboot fastboot". You can also flash recovery from adb. Just get a recovery.IMG I think it's adb fastboot flash recovery.IMG or whatever the name of the recovery is.
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
LordKyleOfEarth said:
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
Click to expand...
Click to collapse
I must have not been thinking the whole picture. What can the phone do? What happens when you turn it on, do the volume buttons work at all? Because if you can get into recovery or fastboot at all then something can be done try multiple combinations as much as possible. I'm thinking hold the power button down and plug in USB. Wait for something to happen then let go of power. Does your computer ever recognize something is plugged in? Maybe during boot?
I have a Nexus 32gb 2013 model that I've rooted with Wug's Nexus root toolkit v. 2.04. Everything was all find and dandy when I tried to update to Timer's Rom (not his fault) and I somehow deleted the operating system. The Nexus just shows the "Google" logo with a unlocked logo beneath and nothing happens. I did do a backup when I originally unlocked and rooted the Nexus but when I tried to install the backup, it does nothing. I already tried the DeVeiw thing and it did nothing. Actually it did help my PC recognize my phone again. To make it worse, I tried to install something to the Nexus but the computer won't recognize the Nexus. Neither will it load anything from an OTG cable. I took it to some place in town and they told me although the Nexus charges without any issues, the port might be messed up but I think this was his way of saying he has no idea what's up. Any ideas would be greatly appreciated. P.S. I still have access to TRWP (V. 2.8.4) and under "Restore" I do have a backup in there named cm_flo_userdebug 4.3.1 JLS361 blablabla. I already tried to install that with no luck. Am I boned? Any ideas would be greatly appreciated.
Does your computer see it when it's in fastboot? If so, flash a factory image (with fastboot) and start over.
And don't use toolkits.
No. Sadly it does nothing when I plug it in.
Does your computer recognize it while in bootloader? When in recovery, do you mount /system?
It does nothing when I plug it in. Not sure what you mean by me mounting the system.
1. Try shutting down the tablet all the way (screen black and fully off).
2. Then, hold down the power and volume down button. You should arrive to the "Fastboot" menu. While there, you should flash a recovery. Get TWRP for your device (really nice sideload).
3. Run a fastboot to flash a recovery so you can install an OS, like so:
Code:
fastboot flash openrecovery-twrp-2.8.5.0-flo.img
4. Reboot after installing TWRP. Hold power and volume down again.
5. Use your volume rocker to select "Recovery Mode" and press the power button. TWRP should start up.
6. Go into "Advanced" and select "ADB Sideload".
7. Sideload a ROM to your device by using:
Code:
adb sideload cyanogenmod.zip
Do GAPPS now if you need to.
8. Reboot, clear caches, and get back online.
---
If ADB refuses to sideload, make sure you've installed the proper ADB drivers for the device.
pacificfils said:
1. Try shutting down the tablet all the way (screen black and fully off).
2. Then, hold down the power and volume down button. You should arrive to the "Fastboot" menu. While there, you should flash a recovery. Get TWRP for your device (really nice sideload).
3. Run a fastboot to flash a recovery so you can install an OS, like so:
Code:
fastboot flash openrecovery-twrp-2.8.5.0-flo.img
4. Reboot after installing TWRP. Hold power and volume down again.
5. Use your volume rocker to select "Recovery Mode" and press the power button. TWRP should start up.
6. Go into "Advanced" and select "ADB Sideload".
7. Sideload a ROM to your device by using:
Code:
adb sideload cyanogenmod.zip
Do GAPPS now if you need to.
8. Reboot, clear caches, and get back online.
---
If ADB refuses to sideload, make sure you've installed the proper ADB drivers for the device.
Click to expand...
Click to collapse
I tried doing this but there is no way for me to side load anything because the PC wont recognize it. I think I am boned. I seriously wondering if there is something wrong with the USB connection even though it charges, I cant seem to get the PC to recognize it. The Nexus goes into TWRP but it wont recognize an OTG cable. When I connect it and try to select it, it just doesn't register. I wonder if I need to changed the USB board?Any other ideas before I do that? P.S. thanks for any help guys, I really appreciate any input.
Hello Forum!
Sorry for my English.
My Chinese Nokia N1 is bricked.
Why bricked:
After change file build.prop extracted from file uploaded by XDA user (I can't find a thread), my tablet only boot to screen "Powered by Android".
Nokia can't do power off. Allways reboot after many seconds hold power key.
Next what I do:
ADB working, but i dont have permission to change this file (i have backup build.prop).
I do all (IMO) to change permission to /system (read-only):
- mount -o rw,remount ...
- adb remount
etc.
Don't work power button and volume down.
And I have an idea ...
I run script to root Nokia from XDA.
Look great.
From recovery menu I mount /system to read-write.
After adb shell and mount command i see /system is read-write, but any changes/copy file = operation not permitted.
I try (of course after su).
- busybox mount -o rw,remount ...
- busybox chmod 777 /system
still "operation not permitted"
I'm disappointed.
And I run system/factory reset from recovery menu after run root script.
Now:
- still boot to screen "powered by android"
- adb not working, I don't have device ADB in Windows device manager
- power and volume up give me device: moorefield in windows device manager
- downloaded "Intel Phone Flash Tool Lite", and I see my Nokia after power & volume UP is connected in this software.
What next, what I need for unbrick? If they can...
Please help.
what's your current version?
Xkernels said:
what's your current version?
Click to expand...
Click to collapse
A5CN51C
you're better than me, my device can not even enter recovery mode, it keeps on turning and turning around after Powered by Android animation
Still needs help. I donate if my problem resolved.
Mine was stuck at "power by android" screen, it keeps looping to that screen.
Took me a few days of trying different things, I found the tablet was showing up on "adb devices" when it boots to "power by android" screen.
It shows up after maybe 30sec - 1min after you get to that screen.
When you run this command "adb devices"
If your device shows up.
You can run "adb reboot bootloader" or "adb reboot recovery"
If you device doesn't show up, you will have run "adb kill-server", otherwise it will never show up.
then run " adb devices" again.
Try a few time, if this works, you're in luck.
After you get into the bootloader, you can get into recovery mode, and use sideload to flash a full image.
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529
Pick a full size image newer or the same to your current version.
adb sideload image_filename
kourcomp said:
Mine was stuck at "power by android" screen, it keeps looping to that screen.
Took me a few days of trying different things, I found the tablet was showing up on "adb devices" when it boots to "power by android" screen.
It shows up after maybe 30sec - 1min after you get to that screen.
When you run this command "adb devices"
If your device shows up.
You can run "adb reboot bootloader" or "adb reboot recovery"
If you device doesn't show up, you will have run "adb kill-server", otherwise it will never show up.
then run " adb devices" again.
Try a few time, if this works, you're in luck.
After you get into the bootloader, you can get into recovery mode, and use sideload to flash a full image.
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529
Pick a full size image newer or the same to your current version.
adb sideload image_filename
Click to expand...
Click to collapse
Thanks You for answer.
I do a lot reboot after system/factory reset from recovery menu, and i never got adb device in windows device manager.
Without this device I do not have the ability to gain access to the adb device.
I have a nexus 7 WIFI 2013 (Razor, Flo):
I was trying to get a copy of Nethunter or Kali linux installed on here. I was running CyanogenMod nightly's
Well during one install, I must of wiped the whole tablet clean. It only had dad/media and then subs /0, /obb folders. I'm unable to find any images on the card and nothing else is displayed. I have tried number numerous drivers for my Samsung laptop but when i use my surface it shows nexus 7 and also when i go into bootloader mode it will also show the driver.
I installed droid SDK and also minimal adb and fast boot. I'm unable to push anything to this device. When i run adb devices it shows the device but says unauthorized. I try adb kill-server and adb start-server and still no dice.
I'm looking for any input as to how I can push and image onto this device. I realize I will have to go back to factory and I have all them images. I just cant get it adb authorized yet.
this will only go into recovery mode and boot loader mode. There is no OS if I let it boot it just shows the mod logo and will sit there until the battery dies.
Does anyone have any input on how to get this authorized so I can push files to it. I'm unable to get on the screen and ok the RSA fingerprint and I think that maybe part of my hold up or why it shows unauthorized.
Thanks in advance for all or any input or ideas.
Start TWRP and it will authorize you to push any files anywhere.
I'm unable to get TWRP on this tablet. The main issue is I only have cyodgen mod recovery on the tablet. It will not boot. It will only go into recovery mode/bootloader mode. I'm unable to verify any RSA fingerprints which is causing me an issue getting the tablet authorized for ADB pushes. Does anyone know a way I can get it authorized via ADB without being able to access anything other then recovery mode? I think the RSA fingerprint is whats actually causing me an issue.
cletisvandamm said:
I'm unable to get TWRP on this tablet.
....
I think the RSA fingerprint is whats actually causing me an issue.
Click to expand...
Click to collapse
No need to flash TWRP - just start it directly from RAM:
download twrp-3.0.2-0-flo.img to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn), connect it to your PC
on PC run: fastboot boot twrp-3.0.2-0-flo.img
when TWRP is up, ADB-push your files, no RSA concerns
Here's my situation -
I was using my Whyred (Redmi Note 5 Pro) and it suddenly hung, so i tried forced reboot by long pressing the power key. But after that, the device never booted. It is stuck at MI bootlogo. I tried going to recovery, the recovery is also stuck at the Recovery Bootlogo (ie, OrangeFox Recovery Project logo as i am using OrangeFox Recovery), then i tried going to Fastboot and it shows a blank screeen with only the LCD backlight.
Device gets detected in 'fastboot devices' when in fastboot blank screen and also gets detected in 'adb devices' as a recovery device when stuck at recovery logo from a windows pc. The Bootloader was unlocked and i was using a custom ROM, Havoc OS Mod - last Pie build with OrangeFox Recovery and was rooted using Magisk. I didn't update the rom or firmware since past 4-5 months. I also tried "fastboot boot recovery.img" with 3 different recoveries (twrp,orangefox and skyhawk), but all of them gets stuck at their respective recovery logos and gets detected in adb devices on pc.
I have important files on my internal storage which i want very badly. It wasn't backed up (my bad:crying::crying. So i want to copy/backup the internal storage of the device to my pc before attempting to repair the device and after backing up i want to fix the device.
My Problem -
When the device is struck at recovery logo, i connect it to my pc and it gets detected as a recovery device on running "adb devices" and i can use adb shell. on writing "ls" in adb shell all the different directories gets listed but when i "cd" to storage,sdcard and some other directories they are empty. when i type 'su' in adb shell,it shows "/sbin/sh: su: not found" . "adb root" also doesn't work as it shows to allow permission on device and then terminates. I read online that i need root access in adb to see system files in adb shell which i am not able to get as the device is stuck at bootlogo. i want to use "adb pull" to copy my internal storage to my pc before attempting any repairs.
I have attached the screenshots of "fastboot getvar all" command.
So, looking at my situation, how do i backup my internal storage to my pc? I really want those files on the internal storage.
Is there any way i can get/backup those files from internal storage from fastboot or adb or any other way?
Also, after backing up, how do i fix my device?
It was running fine without much problems before this. The storage was pretty close to being filled up, other than that i don't remember having any other problems with the phone. It hung suddenly while using and after forced rebooting, never booted again. how do i fix it from fastboot or recovery? i am thinking about formatting the device from fastboot and then trying to boot the recovery and then rom. I didn't try it as i wanted to backup internal storage first. Some people in other posts say that they weren't able to fix their device in similar situations. Please suggest the correct way to fix my device.
Please read my problem and help me to fix it. Your help would really mean a lot to me.
This is my first post on xda-developrs so please let me know if am making any mistakes.
Fastboot getvar screenshots (can't post links as i am new user)-
ibb.co/Q82JWdN
ibb.co/4R8j9Jd
ibb.co/sK5Km57
ibb.co/1JGSrdn