Can u belive it ... i just got done doing a 2.1 ruu and reroot to try to fix a problem with not being able to get adb with certain roms including zens .9.6 builds ..kangslayer..newest buffed.. SO i figured let me ruu to take care of this ...WRONG...... I only can get adb from zen.9.5 and < fresh 2.12< does anybody have any input..YES DEBUGGING is enabled
Not having any issues with adb using stock or darch.
Can you run adb shell?
no that is the problem
Error device not recgonized
Trouble shooting would say to check you hardware first:
Comp usb port
Usb cable (broken bent or missing pins or torn wires)
Phone usb port
But sense you can access adb shell on other roms its not any of those.
Soo next up would be to check the roms them selves.
Maybe redownload the roms and do a full wipe before flashing ( don't forget to back up)
And see I'd the problem persists
thanks for the input but i have stressed all those options... I might be ebaying the hero earlier than expected... This is a asurion issued phone..my orginal was stolen 2 months ago
Sorry about the theft.
It'd be a shame if you sold your phone and there was a simple fix ):
Hmmm...
Do you have the sdk located in c?
What recovery are you running?
I think i'm having the same issue, but it could just be that i am very novice with the command line in general. I haven't tried to push anything through adb since i did the initial root a few months back. Now if i type in "adb shell" at the C:\ i get the error "adb is not recognized as an internal or external command, operable progam or batch file" What am i missing? Fresh 2.1.2
Okay
Your suppose to be in C:\android-sdk-windows\tools\
Just cd to the above mentioned
Thank you. That was quick and easy.
Your very welcome.
Enjoy the awesomeness that is adb shell
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
now im thinking that this is only a problem with overclocked kernals....
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
damiandarkwater said:
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
Click to expand...
Click to collapse
Yes again because everything works with other roms..i think there is a problem on my end with the phones hardware and the OC kernals..
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
mickdubs said:
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
Click to expand...
Click to collapse
I'm having the same problem. I believe (a somewhat educated guess), the boot process is locking before the adb software on the phone is loaded. if someone can help to get a console output on the screen during boot rather than the green/white htc screen would help.
tkirton said:
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
Click to expand...
Click to collapse
Yes i have tried that with no luck...
Somewhere in the boot process adb is lost like this was said above.
Im just keeping my fingers crossed for adb with the newsest fresh that should be released shortly
so i just flashed the newest (old) version of damage control. NON OC kernal and i got adb access.. So im convinced that this phone is a lemon becuase it was asurion issued and i loose adb with OC kernals. I did have OC kernals running fine on my previous hero that was stolen.
**UPDATE 3:34AM
so after testing out dc.. i tried to flash the newest OC kernal made for DC. Right after flash i lost adb...
Why is the phone loosing ADB on OC KERNALS.. Where phones patched!?
damiandarkwater said:
Your very welcome.
Enjoy the awesomeness that is adb shell
Click to expand...
Click to collapse
Orrrr. You can download and install Regaw's toolbox and it'll make it so you can run abd commands from ANY directory in command box... pretty sweet
But yes, otherwise you need to be in the c:\android-sdk-windows\tools\ folder to run adb commands (or where ever you saved the sdk at)
Related
Hiya ppl,
I've been trying to get some apk's of my phone but no matter what I try I always get an adb: not found.
BTW: when in Fastboot its not working at all (adb) but when i start my device normally I can get into adb, and i can browse my phone
Can somebody give me some tips?
I'm using xROM 1.5r4.
YuYe said:
Hiya ppl,
I've been trying to get some apk's of my phone but no matter what I try I always get an adb: not found.
BTW: when in Fastboot its not working at all (adb) but when i start my device normally I can get into adb, and i can browse my phone
Can somebody give me some tips?
I'm using xROM 1.5r4.
Click to expand...
Click to collapse
Have you ever had ADB setup?
Yeah and it worked like a charm before I always uninstall apps via adb mouting also works.
I'm at an dead end
YuYe said:
Yeah and it worked like a charm before I always uninstall apps via adb mouting also works.
I'm at an dead end
Click to expand...
Click to collapse
Is your drivers still installed? I know at one time windows reverted back the old drivers on mine and had to change it.
YuYe said:
Hiya ppl,
I've been trying to get some apk's of my phone but no matter what I try I always get an adb: not found.
BTW: when in Fastboot its not working at all (adb) but when i start my device normally I can get into adb, and i can browse my phone
Can somebody give me some tips?
I'm using xROM 1.5r4.
Click to expand...
Click to collapse
Yeah, so the problem I see with your screenshot is that you are already in an ADB shell trying to enter ADB shell commands.
Without further complicating matters, this is what you should do.
Close out everything.
Start - Run - CMD
cd\"your sdk folder"
DO NOT ENTER ADB SHELL
now enter your other commands as you were trying. such as:
adb pull /system/sd/app/example.apk c:\app
THANKS !!! YOU ARE THE MAN
worked like a charm, you know I've never foud anywhere that you need to do that without going in the shell.
Or I just missed it in that case sorry.
I've had a MT3G for awhile and just upgraded to a Nexus One. I still have my old phone and can use adb with the MT3G without any issues. When I try using adb with the Nexus one i receive an error insufficient permissions on the device. Here's some more info about my setup:
Nexus One:
Clockwork Mod Recovery
CM6.0.0RC1
USB debugging is enabled
Computer:
Ubuntu 10.04
I have the rules set up for adb
I have tried remounting and restarted adb with root permissions and have still receiving the same error. I've tried connecting to another Ubuntu box and a windows xp box with the same error.
Any help?
What response (if any) do you get to the "adb devices" command?
What exact command are you trying to execute when you get that error?
When i run adb devices i receive this:
List of devices attached
???????????? no permissions
adb shell gives this:
error: insufficient permissions for device
I receive the same output running the commands as user or superuser. I've also killed and started the server as user and root. Remember I'm running the udev rules so I can run these commands as user.
Today I went ahead and reflashed my phone. I downloaded cm6 from xda and frf91 from the same post. Checked the md5sum for the update and then wiped and flashed.
Even after the wipe I'm in the same spot.
Can you access the device via fastboot?
When I first got the device I used fastboot to unlock the bootloader.
now the command
Code:
fastboot reboot
hangs at
Code:
< waiting for device >
I can still reboot the device into recovery and fastboot.
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
last thoughts, as it's been a while since I've used adb on Ubuntu...
Code:
./adb kill-server
./adb start-server
./adb devices
???
./PROFIT
It seems to be somehow an issue with your local adb set up, not anything phone-related. Could even perhaps be a driver issue.
raim1312 said:
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
Click to expand...
Click to collapse
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
i get the same results after killing and starting adb either as user or root. i'll pull out the drivers and android sdk and reinstall. i'll let you know how it goes once its done
codesplice said:
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
Click to expand...
Click to collapse
Yeah sorry about that one. i'm still a newb but willing to learn
i just reinstalled the android sdk and removed the udev rules. gave my pc a reboot and killed then started the adb server.
same issue.
to verify adb was working i plugged my gf's mt3g in and adb found it.
i've never need to reinstall usb drivers in anything but windows so honestly I don't know how to do it in ubuntu. can you point me in the right place?
I'm afraid I'm out of ideas then. I've only had very limited experience using adb on my Ubuntu install
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
raim1312 said:
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
Click to expand...
Click to collapse
Please do. Everything that I was able to find on google relates to a screwy adb server... but being able to adb on another device complicates things. Very interested to see what you figure out on this.
I installed the rom froyou frf50 with radio from here:
http://android.modaco.com/content/g...ed-update-zip-no-radio-option-online-kitchen/
didn't work.
while looking into returning the phone to stock i received an ota update. so i ran it.
the update failed during a signature check.
i tried to follow the instructions here to return to stock: http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
only issue is fastboot will not find my device.
performed a nandroid restore to go back to cm6 frf91.
fastboot still will not find my device.
i'm at a loss here. the device is usable for everything but adb. and adb is the main thing i need. i dont' want to keep whacking at this and cause more issues.
any ideas are welcome. all my data is backed up and the bootloader is already unlocked.
its... working??? i finally got adb to recognize my device.
first i restored the phone back to stock using this: http://forum.xda-developers.com/showthread.php?t=717870
then i replaced the cable i was using for one from a Motorola droid. (since the mt3g has a different usb port i had to use a different cable).
then i ran the adb kill and start server commands as root. and voila. it works.
i remove the cable and go back to the one that came with the phone and it still works. not sure what happened but adt is working as well. so im back up and running. i wish i knew the cause of this frustration but i fear i will never know. anyway thanks for all your help!
Yikes.... take your boat back!!!
Perhaps you ran chmod u+s on adb?
Edit: Yep, that was the problem for me..
I don't know the commands to well, so i just right clicked adb and went to permissions and removed set uid.
seems adb needs started from root, but making the file always run as root doesn't work so well.. I thought it would fix my annoyances with eclipse starting adb with not enough permissions. Perhaps ill chmod u+s eclipse instead.
Oh and btw... nexus one can kiss my a$#. HTC Hero!!
Solution for permission problems:
http://wiki.cyanogenmod.com/index.php?title=Udev
I am looking for anyone who can help me with installing adb on Ubuntu I've posted a topic in Q&A but received no response so I'm asking here I partition my hard drive and installed Ubuntu I've downloaded the sdk and I've gotton as far as placing the tg file in my home directory but still no go I think I'm missing something but don't know what I'm native to windows and I have adb working on that just fine but Ubuntu is all the way different like I said I'm really new to Linux so I'm asking for a step by step guide to install adb on Ubuntu and a list of commands for adb on Linux as well also I've been asking for a while now and still no answer does anyone know how to disable the force In call touch UI in CM6 its checked and blackend out the setting I'm speaking of can b found in setting /call settings I would like to b able to uncheck it also I'm very fond of the bx theme was wondering if anyone could help me to get it to work on CM6 stable any help with any of these would b greatly appreciated thanks
Root-Hack-Mod-Always™
what happens when you execute adb?
if your getting something like "can't execute blah blah" make sure that adb has execute permissions.
#chmod +x adb
its been awhile since I been on ubuntu you may have to sudo to execute chmod on ubuntu.
Wen I plug in my phone it does not recongize it also wen I hit adb says no command adb found did you mean then gives me a list of commands for something I'm not familiar with lol
Root-Hack-Mod-Always™
laie1472 said:
Wen I plug in my phone it does not recongize it also wen I hit adb says no command adb found did you mean then gives me a list of commands for something I'm not familiar with lol
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
first are you executing adb from the folder its in. If so and it says that the command is not found then make sure that the abd executable has executable perms on it.
Sorry if if I'm not precise on the instruction as I'm trying to do it from memory, I haven used linux in about a year or so and most of my nix time is solaris lately.
But you should by able to #chmod +x adb so that its has execute perms.
if you gets errors trying to run chmod try typing sudo first so that you can switch into root.
I'm not sure on running it threw the window its in I opened up terminal its the only thing open besides a search window on how to install this and when I did type in a command I hit sudo didn't try the other commands u gave yet I'm mobile and to my dismay ill b for a few hours but as soon as I get to my laptop I will and post results anything else you can think of is more than welcome to I don't shun knowledge thanks in advanced
Root-Hack-Mod-Always™
this might help getting adb and your phone working in ubuntu, if you need any more assistance pm me and i'll try my best to help.
http://forum.xda-developers.com/showpost.php?p=7874321&postcount=11
codejunkie78 said:
this might help getting adb and your phone working in ubuntu, if you need any more assistance pm me and i'll try my best to help.
http://forum.xda-developers.com/showpost.php?p=7874321&postcount=11
Click to expand...
Click to collapse
This will work. That was posted in the thread I started with the same question. Been running Ubuntu for over a month and use adb all the time.. Thanks again codejunkie!
Man I knew u guys would come threw I love Google but love xda more ill b home in less than an hr can't wait thanks a million
Root-Hack-Mod-Always™
Thought I had posted this here well unfortunately I ripped out a USB port on my laptop. Besides that I had to pop out my hard drive and send it in to HP because of a warranty repair. I should have it back by Friday and I'll post and let you guys know if I got it thanks again for the info
Root-Hack-Mod-Always™
Update
Got it installed and I posted a thread on how we did it in case anyone needs it thanks for the responses and I started a thread about anything hero so feel free to post and check it out all knowledge on heros is most definitely welcomed and encouraged by
Laie1472
Thanks in advanced
Root-Hack-Mod-Always™
flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!
FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?
Questions don't belong in the Development section <---please click link and read....moved to general...
TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.
@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.
No it still wont execute the command
If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"
Thanks il Duce. If I get adb running Ill try it and post back.
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)
TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.
Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
neo_lithic3K said:
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
Click to expand...
Click to collapse
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
bignu77 said:
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
Click to expand...
Click to collapse
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
dragynbane222 said:
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
Click to expand...
Click to collapse
My bad, I worded that wrong it only happens once in the custom recovery and try to ADB sideload the rom, i get that error.
Fastboot boot.img via bootloader works fine.
My trouble starts one in custom recovery and it shows "emulator-5554". Please see attachment.
Thanks
bignu77 said:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
Click to expand...
Click to collapse
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for clearing that up.
The only other thing connected it the cordless mouse reciever.
I also did update sdk platform. as shown in the attached. Yes i am trying to apply update from adb and then sideload command I also tried typing the specific file name instead of the whole path.
It only happens in adb mode. Flashing via fastboot works fine with no emulator error.
Ive been flashing for months using the standard adb method with no hiccups. Now im getting this error
SOLVED
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
bignu77 said:
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
Click to expand...
Click to collapse
Figured it something related to that, I'm happy you fixed it though, enjoy the ROM.:good: