Database Develop

Unable to Sideload... ADB options show up instead!

I attempted to sideload using TWRP 2.5.0.0 and my current recovery, CWM 6.0.3.1, and it always fails... As I type adb sideload zipname.zip, the whole list of commands to use with cmd appears and it scrolls to the bottom... Anyone had this happen? Or know what I may be doing wrong? Please help, I wanna master this, should I one day really need it... Thanks in advance!

In recovery you used the adb sideload option before the command?
However, use the adb push for copy the rom into your phone and after flash this
Code:
adb push nameofrom.zip /sdcard/0
or
Code:
adb push nameofrom.zip /data/media

Guich said:
In recovery you used the adb sideload option before the command?
However, use the adb push for copy the rom into your phone and after flash this
Code:
adb push nameofrom.zip /sdcard/0
or
Code:
adb push nameofrom.zip /data/media
Click to expand...
Click to collapse
I am having the same problem. When in recovery and choosing "install zip from sideload", adb devices is not showing the device connected..

I attempted to sideload using TWRP 2.5.0.0 and my current recovery, CWM 6.0.3.1, and it always fails... As I type adb sideload zipname.zip, the whole list of commands to use with cmd appears and it scrolls to the bottom
Click to expand...
Click to collapse
I seems as you have old version adb on PC. Not recognized argument "sideload" and adb displays all command list for help.
Check version by "adb version" must be 1.0.29 or higher.
I am having the same problem. When in recovery and choosing "install zip from sideload", adb devices is not showing the device connected
Click to expand...
Click to collapse
It's not the same problem. When you just entered in custom recovery adb shall show your device, by "adb devices".
What show in device manager on PC, when you are in recovery?

Format System - Phone Wont Connect

Well I did something stupid, I was getting ready to give my phone to a friend and in my haste to make sure everything was deleted, I formatted /system in CWM recovery. I dont have any backups left on it either.
Now, I just need to flash a new rom, but I cant get my phone to connect to a computer in order to transfer the rom over.
It shows up immediately in Device Manager under Android USB Devices > My HTC, but it does not show up as a separate drive in My Computer.
Ive made sure the driver is up to date.
Anyone have any ideas?

culturistic said:
Well I did something stupid, I was getting ready to give my phone to a friend and in my haste to make sure everything was deleted, I formatted /system in CWM recovery. I dont have any backups left on it either.
Now, I just need to flash a new rom, but I cant get my phone to connect to a computer in order to transfer the rom over.
It shows up immediately in Device Manager under Android USB Devices > My HTC, but it does not show up as a separate drive in My Computer.
Ive made sure the driver is up to date.
Anyone have any ideas?
Click to expand...
Click to collapse
you cant connect your device to computer in MTP mode because you are not having any rom
try adb sideloading rom or adb push rom in custom recovery like TWRP or CWM (i used TWRP) in order to upload rom to sdcard
For Adb sideloading rom
> Reboot into TWRP
> in TWRP click "advanced" and navigate to "Sideload"
> Swipe to start Sideload
> now type "adb sideload romzip.zip"
wait until 100% then reboot back to recovery to flash the rom
If Adb sideload doesnt work..try Adb push
> Reboot into TWRP
> type "adb push rom.zip"
it might take sometime may be less than 5min to sideload or push the rom..dont cancel the command prompt after typing the above commands

Harish_Kumar said:
you cant connect your device to computer in MTP mode because you are not having any rom
try adb sideloading rom or adb push rom in custom recovery like TWRP or CWM (i used TWRP) in order to upload rom to sdcard
Click to expand...
Click to collapse
Awesome, thanks a million!

sdcard wiped, Rom in loop

Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "

p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
when I had that problem, I ended up wiping everything and then rebooted to recovery and it finally worked.

p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
Try what @JudgeFutta said. The error's most likely due to corrupt partitions.

p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
Try to get in Recovery and from mount option mount system and then try it will work or try this
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Be sure u r in Recovery when using ADB Push command.

Thanks guys. What i found out is that i had a corrupt partition so I formated the sdcard since there was nothing on it and it worked. I pushed the rom through adb but i didnt do the sideload method. I have liquid smooth on it now but I want a sense rom. any suggestions for a good one?

p1mpin said:
Thanks guys. What i found out is that i had a corrupt partition so I formated the sdcard since there was nothing on it and it worked. I pushed the rom through adb but i didnt do the sideload method. I have liquid smooth on it now but I want a sense rom. any suggestions for a good one?
Click to expand...
Click to collapse
Why not try the best Sense rom available. http://forum.xda-developers.com/showthread.php?t=2502430
Gd luck

User420s said:
Why not try the best Sense rom available. http://forum.xda-developers.com/showthread.php?t=2502430
Gd luck
Click to expand...
Click to collapse
@p1mpin Can vouch for that ROM, it's amazing. Might also want to flash Kangaroo Kernel while you're at it. It'll give you great battery life.

[Q] 6 Hours later - Still Bricked.

Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!

haqsaber said:
Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!
Click to expand...
Click to collapse
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.

alray said:
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.
Click to expand...
Click to collapse
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
I flashed the ROM using this command: fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
then after the transfer was done typed: fastboot erase cache
as of now when I type adb devices into the command prompt my phone is being detected which is an improvement from last night! Thanks!

haqsaber said:
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
Click to expand...
Click to collapse
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.

alray said:
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.
Click to expand...
Click to collapse
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?

haqsaber said:
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?
Click to expand...
Click to collapse
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.

alray said:
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.
Click to expand...
Click to collapse
And that worked! Thank you so much!!

sideload error no device

sorry if this is the wrong place...this is my problem
I got an old tablet off someone that i want to bring back to life, its an ares 8, model #NXA8QC116. unfortunately the sd card slot is broken so using it is out of the question..I have TWRP 3.0.2 on it and im trying to flash SU to it via "adb sideload."
when in system using "adb devices" it shows the device as well as in recovery mode, but when i try to use the sideload feature in TWRP i get a "ADB sideload failed no devices/emulators found error..if i try "adb devices here it does not show a device..im not sure if this is the problem. Also i cant FLASH SU BECAUSE IT IS NOT SHOWING UP IN twrp nor are any other zips which ive read is because of the encryption is still enabled? i have the disable encryption .zip but cant flash that eaither due to my same problem of .zips not showing up.
All the device drivers and adb+fastboot are setup properly as far as i can tell but i get the error no matter what i do.
my questions are..
1. is there and OTHER method i can use to flash SU.zip or the decryption.zip file without the use of an SD card?
2. does anyone have any ideas on how i can go about fixing the no devices/emulators found error while in sideload mode?
thank you very much for your anticipated reply!
1. is there any OTHER way to flash SU using