I'm trying to root the xoom using the method here: http://forum.xda-developers.com/showthread.php?t=1170760 but on the screen where I'm to press the volume down key first to change the option, I pressed the volume up key. this cancelled the unlock and shows a message stating "device unlock operation aborted". Now I can't do anything with the tablet. adb will not recognize the device and I can not reboot with the power button.
Anybody have any ideas?
EDIT: Found in another thread how to do a soft boot, that allowed it to reboot correctly.
Related
Long story short, I tried to unroot my phone and now when I try to boot my phone, it just says Google. Nothing else happens.
When I open the bootloader and go to recovery, I get the little android with the warning triangle above his head.
If I press the power button and up again, I can go to apply update from sd/card.
Navigate to clockwordmod/download/ and choose any other rom that I have downloaded I get an error saying E:signature verification failed installation aborted.
I have noticed that in the bootloader it says: LOCK STATE - LOCKED
When I hold volume up/down keys at same time and and plug usb into computer, I get the "Unlock Bootloader" Screen, but no option to unlock the bootloader at the bottom as there should be, and I can't do anything from this screen.
I cannot access my phones internal sd card from my computer because I cannot enable usb debugging. At least I think that is what the problem is, When I connect phone to computer via usb PDA.net gives message HTC Sync Error.
Any help would be great, this is my first android phone and I don't know what to do from here. Been googling stuff for a few hours with no luck.
My phone seems to be stuck in download mode. I'm trying to get it to recovery, all attempts result in it going back to download.
I just don't know how to get something else showing on here.
Background: Phone was rooted on Kitkat but I lost the root when I upgraded to Lollipop.
Was trying to root the phone with via the one click (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951) which seems simple enough. However, my phone would not enter into download mode so I couldn't continue the steps. I found someone with my exact problem right here on XDA (http://forum.xda-developers.com/showpost.php?p=57125760&postcount=9) and in doing what he did, my phone DID enter into download mode, just got stuck in it.
Edit: In pressing Volume Down and Power off and on (press them, release them, press them, release them, etc) an unknown white screen that reads "Factory Data Reset" and a "yes" and "no" has came up. I don't know if I replaced my CWM recovery with this weird thing, in doing what the XDA poster said?? Even if I press "yes", the download mode screen comes back upon restart.
2nd edit: I did get it working. Left the phone connected to the LGMobile Support Tool while I tried the "Upgrade Recovery" again and after a few tries of that it turned on all by itself. Will try rooting again, hopefully succesfully this time
Hi I'm hoping someone can help or at least point me in the right direction if i've missed a thread, i'm on Windows 7 64bit.
I appear to be stuck in a boot loop on my original Shield Tablet, stuck on nvidia screen when i try to go into recovery mode i get the "dead android" picture.
I have tried to unlock the bootloader and i get FAILED <remote: <>, device shows up under fastboot devices command, device shows up as Android Bootloader Interface in Device Manager.
I've searched the forums and seen this problem but everyone else seems to be able to unlock easily, this is the same but no replies https://forum.xda-developers.com/shield-tablet/help/nvidia-shield-unlock-bootloader-failed-t3178865.
Any help anyone can give me would be appreciated. Thanks in advance.
Check the recovery images section for your device here: https://developer.nvidia.com/shield-open-source
Instructions to unlock the bootloader:
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse
You need to already have adb set up and the Shield connected to the PC to do this. If you don't have USB debugging enabled, this may not be possible, but you should still be able to get into recovery by booting the tablet with Vol- and power button (hold volume - and then just press the power button, don't hold both at the same time).
Yes I've tried that (I know the steps of unlocking the bootloader) that's when i get the FAILED error. When I try to enter recovery I get the "dead" Android picture.
Heya peoples, I have a problem and am hoping for some help in a work around.
I am trying to root my J3 but my volume up button does not work. I have adb installed, and the correct drivers for my phone. I can use adb command to reboot to the bootloader and it brings me to the Odin "downloading" screen. I can then use the program to install TWRP so I can root. Everything goes fine up until this point. After TWRP is installed there is a single massive problem I am hoping there is a work around for. My volume up button does not work. I can only reboot to recover using adb once the phone boots up, and I read that if you let that happen it overwrites TWRP with the stock recovery (which is what happens when I do this). I read that you have to reboot directly from the downloading screen into recovery using Vol up and home and power. But I can't do that since my Vol up doesn't work. When I am at the download screen after installing TWRP none of the adb commands work so I can't reboot directly to recovery to access TWRP the first time. I hope this all makes since, and I hope someone has some advice because as far as I can tell I can't continue passed this point without a working volume up button.
A little more info in case it matters. When using adb command prompt I have to type ".\adb" instead of "adb" as the tutorials say. When I do ".\adb devices" my device shows up as connected. After rebooting to the bootloader using adb, typing ".\fastboot devices" shows nothing is attached, and any command I try to put in results in "waiting on devices". Checking the device management at this point does not show any unknown usb devices (one guide I read said if fastboot wasn't recognizing to check to update drivers if something was showing as unknown usb".
Basically hoping there is some way of booting directly to recovery from bootloader without having to use the vol up key combination so I can access TWRP for the first time. Any help at all is appreciated. I realize having a working volume button would take all the headache out of this but unfortunately fixing it is not an option at the moment.
Edit: I have also unlocked the bootloader using the Crom Services app from samsung, and have developer options and usb debugging enable.
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
CopaseticDream said:
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
Click to expand...
Click to collapse
Can this device even be rooted? Doesn't virgin lock their devices?
In any case if you flash twrp to the boot partition (rename it to boot.img) it'll boot directly to twrp then just use twrp to flash to the recovery partition.
Reflash the stock boot.img back to the boot partition.
I tried to root my Moto G5s+ to install a more lightweight ROM.
I reset my phone and didn't even add a pin.
Unlocking the bootloader worked
Then I tried to install TWRP, it failed 3 times
Then I tried to boot the phone, it asked for a password
I didn't even add a password
When I tried to go into recovery mode, it said "No Command"
So i can't even use my phone now, Atleast it was my alt phone.
Look inside here:
How to Fix Android Recovery Mode No Command Error
The no command Android error has popped up for many users when in the recovery mode. But before we start, lets understand why it exists.
www.wawcase.com
At the no command screen press and HOLD the volume up and power key together and once you see the recovery menu release the keys.