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?
Related
so i had just htc dev unocked my one x, now i was using hasoons tool, and when i tried to flash a recovery in fastboot with commands, everything in the prompt said okay.. flashed successful and so on, and the bar on the top right hand side of my phone flickered as if to load, but didint. now when i go to recovery mode, it gives me the splash screen with some red letter **** about distrabution, then reboots. ive tried flashing every possible recovery for the one x, including stock, and seems to do nothing, help??
pic is the screen rite b4 reboot (thats what i get when i reboot into recovery)
EDIT:: now im stuck at the screen in the picture, will not boot into anything else, will not be recognized by adb. PLEASE HELP!!!!
EDIT EDIT: i can power off, and get back into fast boot with volume off, but im almost asuming i just have no recovery..... and it will NOT! boot into the phone no matter what, only booting into that screen... what the **** do i do lol this is kind of a panic now
Have you tried reflashing stock recovery? Also shouldn't you be in the AT&T One X forum unless of course you have the international version of the One X.
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
ixi_devo_ixi said:
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
Click to expand...
Click to collapse
You're suppose to flash stock recovery in fastboot.
I know, I tried when it was getting recognized, now I can't even pick it up with adb
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
ixi_devo_ixi said:
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
Click to expand...
Click to collapse
First of all ADB only works in RECOVERY mode not directly in bootloader. So do the following steps & instal custom rom (Any1 u like).
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!
I rooted and installed an ICS ROM several months back on my Fire. One morning the wife brings it in and says my son got it stuck in some weird mode. Turns out it is stuck on the TWRP yellow triangle and does not seem to be able to get into recovery mode. I have done that several times before so I am pretty confident I am not messing that up. Just the power button never turns orange and eventually the device just turns off. My computer see the USB device but ADB does not. I did `android update adb` and then added '0x1949' to '~/.android/adb_usb.ini'. Do I have any options left or is it bricked?
Thank you to anyone who takes the time to read this. Especially to any who can reply with suggestions.
nnutter said:
I rooted and installed an ICS ROM several months back on my Fire. One morning the wife brings it in and says my son got it stuck in some weird mode. Turns out it is stuck on the TWRP yellow triangle and does not seem to be able to get into recovery mode. I have done that several times before so I am pretty confident I am not messing that up. Just the power button never turns orange and eventually the device just turns off. My computer see the USB device but ADB does not. I did `android update adb` and then added '0x1949' to '~/.android/adb_usb.ini'. Do I have any options left or is it bricked?
Thank you to anyone who takes the time to read this. Especially to any who can reply with suggestions.
Click to expand...
Click to collapse
Download TWRP and FFF1.4
TWRP
http://forum.xda-developers.com/showthread.php?t=1592681
FFF1.4
http://forum.xda-developers.com/showthread.php?t=1632375
ADB will not work because you're in fastboot mode. Use fastboot commands to install the new TWRP and change the bootmode.
Code:
fastboot flash recovery /path/to/recovery.img
fastboot oem idme bootmode 5001
Hold the power button to perform a hard shutdown and restart the device. You should then be able to launch recovery using the power button. If not, you'll have to flash the bootloader as well. If this is the case, be extremely careful you don't pull the USB cable during the flash or you will really brick your device.
Also, it is very important to know that the version of FFF you'll download comes in a .zip format to be flashed in recovery. Don not flash the .zip file directly to your bootloader partition. Instead, unzip it and find the "fff-u-boot_v1.4.bin" located in the cache folder and flash it.
Code:
fastboot flash bootloader /path/to/fff-u-boot_v1.4.bin
fastboot reboot
If you were able to access recovery just by reinstalling it with the first command, push the FFF1.4.zip file to your sdcard and flash it in recovery. Just remember not to wipe anything before installation. That will help you to fix your bootmode problems a lot easier in the future by holding the power button untill the boot options appear at the bottom.
soupmagnet said:
Download TWRP and FFF1.4
ADB will not work because you're in fastboot mode. Use fastboot commands to install the new TWRP and change the bootmode.
Code:
fastboot flash recovery /path/to/recovery.img
fastboot oem idme bootmode 5001
Hold the power button to perform a hard shutdown and restart the device. You should then be able to launch recovery using the power button.
Click to expand...
Click to collapse
Thank you! I am back in recovery!
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,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
gogobaba said:
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
Click to expand...
Click to collapse
Search for FWUL from Steadfasterx.
download-> flash->connect-> open Comannd-> type "fastboot flash recovery recovery.img" or "fastboot reboot system"
Which command are you using for installing TWRP in ADB?
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
elektrosoundwave said:
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
Click to expand...
Click to collapse
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
koivth said:
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
Click to expand...
Click to collapse
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
elektrosoundwave said:
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
Click to expand...
Click to collapse
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
koivth said:
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
Click to expand...
Click to collapse
That's where that first screenshot came from. I will try the reboot bootloader tonight. They sort of recognize my phone, but I can't get them to flash anything. This isn't my first rodeo with borked phones, but I don't think I've had this much trouble since I placed the wrong boot animation on my Droid 4 many years ago.
:victory: :highfive: It's flashing right now. You don't know how much I appreciate it.
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Is your bootloader unlocked?
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Before you can flash the factory image, you have to unlock the bootloader by issuing this command first: 'fastboot flashing unlock'