I keep on getting this error when trying to flash a custom ROM into my phone. Is there a way to manually apply the ROM?
I tried booting into recovery then conecting my phone through usb and running the following commands through cmd: "adb push update.zip /sdcard/update.zip". then it tells me if I want to push "update.zipj", but once I press enter it gives me, "error: device not found"
Here's the cmd log:
Code:
C:\Users\Admin>cd\
C:\>cd\android\android-sdk\tools
C:\Android\android-sdk\tools>adb devices
List of devices attached
000000000000 recovery
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zip
protocol failure
C:\Android\android-sdk\tools>
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zipj
error: device not found
C:\Android\android-sdk\tools>
Am I doing the manual flashing corrrectly? I figured manually flashing the ROM would stop the error from coming up. Could someone either show me or point me in the right direction on how to fix this error and/or possibly how to manually flash the ROM in detail. I've already searched and I keep seeing threads with people asking for similar problems but with no real answer.
any help is appreciated.
1. adb push does not flash a ROM - just copies the file to the SD card
2. Looks like you are in recovery and you cannot push a file, unless you mount the SD card in recovery
Not sure what you mean "manually apply the ROM". ROM flash has to be manual, there's nothing automatic about it.
And, if you had really searched... I am sure you would have found atleast 10 references on how to flash a ROM.
Anyways, here's a link that will give you enough information to just about do anything with your CDMA Hero: http://forum.xda-developers.com/showthread.php?t=1063843. BTW, this is a sticky right at the top of where you posted this question...
BOOM. lol. Also the status 0 is an improper mount command, or you have a bad version of busybox. What zip were you trying to flash out if curiosity? And are you rooted, if so how did you do it?
What I meant when I said "manually" I meant to do it through command prompt instead of Rom manager or through recovery. And I was mainly searching for a fix for the status error I was getting. Which there is no info about that in the link you posted, however it does help with flashing my Rom through command prompt. :]
@il duce It's called "nfx speedy kingdom". I've been using the salsa builds in the development section, but I came across this Rom and it says it has everything working including Bluetooth so I wanted to test it out. Ill try using the tutorial on flashing roms without an sdcard and see if it works.
1. By the looks of it, adb is not recognizing your device... so, first and foremost you will have to setup everything properly for adb to connect
2. Even if adb recognizes the device, to the best of my knowledge, you cannot flash anything through adb, you must have confused it with fastboot. And, that too is possible only if you have engineering spl
One of the links from the thread you linked to show how to push the rom to system/data and use cmd to flash it from there, but the rom I'm trying to flash is over 300mb so it doesn't fit :/
I guess I'll try contacting the dev and see if he knows of a solution, might be that the file isn't correctly packed or signed?
edit: flashing using RA recovery it gives me the following:
Code:
E:Missing file:
system/lib/libvoAMRWBDec.so
E:Verification failed
Installation aborted
Does that mean it's the ROM that's corrupted?
Dude wtf... thats an evo rom.
Also, andy is correct 100%. Cease and desist before you bork your phone.
o_o he has it under heroc roms.
http://sprint.hero.ptyork.com/?cat=1
Edit: Sorry everyone for the questions, I just pm'd nfinitefx and he cleared out everything for me.
Related
I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?
If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?
How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.
ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks
Did you fix this yet?
Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!
Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!
Ok so the SD card slot on my phone is toast. Is it possible to install a rom thru the USB cable without using the SD card? =/
Hmm... Ok I have two ideas that i'll quickly check out. One of which will require you to wipe your data/factory reset in recovery, the other if I did get it to work wouldn't require any wiping unless you wanted to.
I'll try 'em both out and tell you if I have any luck doing so
Alright, so here we go..
Results
First idea without having to wipe: no go
Second idea with wiping: WORKS
After doing some digging around the AmonRA github to look for the commands it actually performs while in recovery I figured out exactly how to do what I wanted.
(namely THIS PAGE for those of you who are interested in seeing the exact page I found them on)
How to Flash a ROM Without an SD Card
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork - I recommend Darch's unofficial (refer to my signature if you need it)
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\kyoukoROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "kyoukoROM.zip" with the name you're using)
Code:
adb push ./kyoukoROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:mau5.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
If someone thinks I should post this in the development section as a [GUIDE] let me know and I'll post it there too
Yup I think so marking as a fav this is good knowledge thanks for the post
Root-Hack-Mod-Always™
Post it! This would be a HUGE help to people
Sent from my HERO200 using XDA App
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
andythegreenguy said:
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
Click to expand...
Click to collapse
Good idea, hopefully it'll help a lot more people there. I'll post it there and change up a couple things (the darch recovery part)
And idk how to edit the wiki
Amazing response! I will have to give this a try thank you!!! I still have a month left before my upgrade and I wanted to be able to change my ROM. Thanks again!
FYI Rom Manager will not flash a clockwork recovery without an SD card, gives an error... looking into other ways to flash a recovery...
I have HTC Hero CDMA obviously lol
but anyways i have the latest HBOOT without S-OFF and i have a corrupt recovery i have tried restoring with the latest offical RUU with no luck as i get the 170 usb error connection error
Why not just reflash your recovery ???
#Root-Hack\Mod*Always_
""Shooter on Deck""
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
evoandroidevo said:
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
Click to expand...
Click to collapse
Go to my signature and click on the CWM link. Then unzip a version and place the recovery.img on the root of your SD card. Now download Busybox installer, and terminal emulator. Install busybox and after installing open terminal emulator and then enter these commands:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される。
i did all that installed busybox and all that stuff and i always get flash_image not found or something like that
EDIT:
Got it to work jsut need to go to 2.27.651.5 instead of 2.27.651.6
I seem to be having nearly this exact same problem. Maybe If I can flash a recovery to my hero I wont need to create a thread of my own asking for help.
What did you mean by "need to go to 2.27.651.5 instead of 2.27.651.6"?
I have root... or at least the "su" command in terminal gives me a #. I have placed the recovery image on the root directory of my sd just as dastin said and run the command but I am getting the flash_image not found error.
That's the RUU version.
Sent from my PG86100 using xda premium
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Jacob_newton said:
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Click to expand...
Click to collapse
Install busybox.
私のEVO 3Dから送信される。
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Jacob_newton said:
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Click to expand...
Click to collapse
Why not just flash the recovery ??? From terminal,hooot, or adb.
#Root-Hack\Mod*Always_
""Shooter on Deck""
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Jacob_newton said:
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Click to expand...
Click to collapse
Were did you place the recovery img at ??
#Root-Hack\Mod*Always_
""Shooter on Deck""
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Jacob_newton said:
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Click to expand...
Click to collapse
Let me ask you this are you trying to flash this from terminal or from adb ?? If there isn't a copy of the recovery img in your adb tools folder then trying to flash it threw adb wouldn't take because the image isn't there. Since the img is on your SD card then you should flash it threw terminal if your not trying it already. If you want to flash it threw adb then place a copy of the recovery img in your adb tools folder and then run the commands from cmd terminal VIA pc/laptop. Also have you made sure that the recovery img is named correctly ?? Also will you post your setup, as in rom,kernel,baseband/radio, and hboot. Also how did you obtain root ??? Thanks
#Root_Hack-Mod*Always\
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
I think you should ruu back to stock and reroot again. Reason why I suggest this is because of how you gained root. If something wasn't done correctly we could be at this for hours and days trying to figure this out. But before you take that route I'll send you a pm with something I would like you to try that might work.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Click to expand...
Click to collapse
Quick??? Are you able to boot up into your Rom ???
#Root-Hack_Mod*Always\
I'm not sure what you mean by that, but I decided to flash stock the other night so now I'm going to try and re-root and flash a custom ROM.
I am considering this method for re-rooting: http://forum.xda-developers.com/showthread.php?t=909258&highlight=root
Any suggestions before I get started?
What I meant by have to be on the 2.27.651.5 RUU instead of 2.27.651.6 RUU as the flash_image is not in thr 2.27.651.6 RUU so you need to be on the 5 version of stock in order to use flash_image
Sent from my Shooter using XDA
I have a problem I wanted to upload a rom Omni 4.4.1 but during the installation of the phone memory I have this error:
--Install: /emmc/omni.zip
Finding update package...
Opening update package...
E:Can't open /emmc/omni.zip
(bad)
Installation Aborted
Click to expand...
Click to collapse
If I type adb adb Sideload omni.zip is the same. The error occurs with every Rom. only salvation is to upload rom Xperia-Z-ized_NOTE_v1.0 by adb, this one installs. I have a kernel with CWM Philz. Sooner I used rom Xperia-Z-ized_ note but I wanted to change it.Other roms do not install by 'adb Sideload' only the Xperia.
Sorry for my english
Because you are on Philz Recovery which is for 4.1.2 Jellybean, you're not able to flash OmniROM. You need to do the steps described in this thread http://forum.xda-developers.com/showthread.php?t=2531957.
Or, to quote father chas, Who had the following to say about people who do not read the OP.
chasmodo said:
Or if you don't want to do that, then:
1. grab your Note firmly with your right hand
2. go to the bathroom
3. put your Note below the water level in the toilet bowl
4. keep it there until you see no more bubbles coming out.
Click to expand...
Click to collapse
Or, as an alternative,
chasmodo said:
Well, there are only two things you can do as far as I can tell:
1. put your Note right in front of your right hand side wheel, shift into first gear, release the clutch, drive; shift into reverse, drive back; repeat until you can hear no more crunching sounds, or
2. learn to read and/or search
Click to expand...
Click to collapse
Maybe, i took his words out of context, but it is my interpretation of them that matters. You have sinned.
Now, atone for your sins, and do as father said: 2. learn to read and/or search
I have uploaded the kernel r4 for jb4.3 but still it is the same and you can not upload any rom, the same error, and this still Adb does not see the phone ....
Ánd did you reboot the recovery after uploading said kernel?
Did you try downloading the zip again? What all roms did you try to install using the r4 recovery? Did you first format /system?
Already running
All I did like the guides, but on the memory is not installed. I have uploaded the drivers manually and adb command 'adb Sideload omni.zip' I uploaded rom and gaps.
When I select install zip from sdcard0 it is still the same error.
Also, THIS
http://androidroot.org/watch_video.php?v=SRH8HS176N5N
And definitely try to re-download the files, It wouldnt suprise me if this is a bad download.
myju said:
Already running
All I did like the guides, but on the memory is not installed. I have uploaded the drivers manually and adb command 'adb Sideload omni.zip' I uploaded rom and gaps.
When I select install zip from sdcard0 it is still the same error.
Click to expand...
Click to collapse
What is already running? Did you install any other rom file like cm? Why does you omni rom zip say omni.zip? Did you rename it of did something else with the zip?
I changed the file name to not write such a long ADB.
A longer roms to install, after downloading directly to the phone memory goes without a problem.
Thank you very much for your help :victory:
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