Develop Bugs

Trouble with Sideloading 4.2.2

Hi am trying to sideload the GNex's 4.2.2 update and i can't seem to get it to sideload onto my phone. I updated all the drivers and installed them, updated the android sdk, i did a "adb devices" check on the CMD and it shows the device.
I am currently running the stock 4.1.1 on my phone.
I am not rooted and do not want to root the phone because i do not want to have to wipe the phone. I get the device into recovery mode and get it ready to sideload. I am doing it from the platform-tools folder of the SDK folder. type the correct command "adb sideload 5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip and then i get the whole adb help menu pop up and does not install the update.
Does anyone know what i am doing wrong? (please don't say not rooting it lol) i have tried it on 2 different computers and i am still getting the same results. Any suggestions or tips would be appreciated.
Update: i just used the "adb devices" command it right after it said that the adb server was out of date and was killing it. then the device connected.

You have to pull up the recovery menu when in recovery and select the sideload option. The key combination I don't know. I did it after looking it up but don't know exactly how I did it.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
You have to pull up the recovery menu when in recovery and select the sideload option. The key combination I don't know. I did it after looking it up but don't know exactly how I did it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply, I do select "install using adb" once in recovery then connect the phone to the computer.

When the help message pops up in adb, what version is listed at the top [I have 1.0.31]? I know you said you updated your sdk, but it sounds like adb does not recognize the sideload command. Perhaps you have more than one version of adb in the folder you'e working out of?

[Q] Trouble with flashing new recovery

Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-

Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app

Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery

Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.

It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.

I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.

zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img

spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u

Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.

Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.

Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app

Can you ADB push files to the sd card without an OS installed???

I just accidentally wiped my SD card and my system and now I don't know how to get a rom onto my phone due to the lack of an SD card slot. Can anyone help me get a rom on the internal so I can flash? I have TWRP still but I have no clue how to get a rom to my sd card. Am I screwed? Cause I read a forum that had to have usb-debugging on and I have no system lol. Thank you guys so much

You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app

mrgnex said:
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing

jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
First use TWRP not fastboot. Once you are in recovery plug the phone in and type "adb devices" (without the quotes) in command prompt or terminal. If it returns with letters and numbers (can't remember might be a combination of both) your good to go. Type "adb push c:\downloads\Rom.zip /sdcard" type out the directory where the file is instead of downloads change it to where your rom is. If you type adb devices and nothing happens you need to work on your drivers.

jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

mickeyflip said:
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Cool story he's trying to use adb not fastboot two totally different things.

DR3W5K1 said:
Cool story he's trying to use adb not fastboot two totally different things.
Click to expand...
Click to collapse
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...

mickeyflip said:
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
Click to expand...
Click to collapse
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.

DR3W5K1 said:
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
Click to expand...
Click to collapse
No worries - it's possible that they do. But the drivers I linked are the ones that worked for me consistently. The Samsung ones seemed to stop working each time I disconnected the handset and plugged it back in via USB.
In any case, those are the only ones I have installed right now and everything is working great for me connection/recognition wise.
Any luck yet jtl_777?
To push files to the handset, use the command: adb push filename.ext destination-folder
Explained further here: http://developer.android.com/tools/help/adb.html#copyfiles

Just for future reference so people reading these threads don't get super confused, your computer won't recognize your phone through adb commands unless you are in adb sideload through your custom recovery, or if you're booted up and running in an operating system. You could also use adb push commands in your custom recovery. This has nothing to do with drivers or whatnot. If in bootloader your device isn't recognized through adb commands, that's completely normal, because it never would be, but your device should be recognized in bootloader with fastboot commands.
IF your phone is NOT recognized in your booted up phone, or in adb sideload through your custom recovery, or with adb push commands in your custom recovery, with adb commands, then you have driver issues.
ALSO IF your phone is NOT recognized while in bootloader, with fastboot commands, then you have driver issues.
To answer the OP's question:
If you have an unlocked bootloader and you are in TWRP, you can mount your phone onto your computer and copy and paste the rom zip onto the phone and then install it through TWRP once on the phone. If that doesn't work, then you can try using adb push commands while in TWRP (or maybe need to be in adb sideload through TWRP) to push the rom to your sd card and then run it through TWRP. If that doesn't work, you can also try flashing the rom zip through bootloader with fastboot commands, but all these commands might be device specific, that's why I won't tell you the commands I know for the HTC One X, but the processes are the same no matter what. Hope that helps

You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5

Pirateghost said:
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Click to expand...
Click to collapse
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.

EsoteRIcalfreaK said:
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
Click to expand...
Click to collapse
Adb shell as well as numerous other commands work just fine
Sent from my Nexus 5

adb sideload problem

Hi everyone,
just to clarify that It's my first time I try to unlock and root my phone, so no much knowledge.
I basically followed the steps to unlock the bootloader.
Everything worked perfectly, I reached the recovery, went on 'apply update from ADB'.
But then, when I enter in cmd: 'adb sideload <whatever the filename>'
it prints out the Android Debug Bridge instructions rather than transferring the zip file to my phone, and the phone keeps on asking "now send the package you want to apply to the device with adb sideload filename "
N.B.: the phone is recognized by adb, even when I enter adb devices, it is recognized
Any help?

did you try issuing the adb sideload command BEFORE pressing the button in recovery?
I had this issue before when trying sideload, in fact I think it WOULDN'T work if I started it via recovery FIRST. it has been a long time since I did this though, but I swear I remember not even having to press the button in recovery, I think it just automatically started once I issued the command from computer.

Yea, just tried it and same results

which recovery version are you using?(CWM or TWRP? and which version also)
and which adb version do you have on your computer? are you certain it is the latest available? did you install it through the Android SDK?

LG Nexus 5X V7.1.2 B/N: N2G47Z ( No Command No Custom Recovery )

Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!

DarkXShadowX21 said:
Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk

In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
jugoslavpetrovic said:
In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you guys for the help! I successfully rooted my Nexus 5X! It's time to go exploring into the roots! :good: