Hi,
When I'm trying to downgrade my desire hd when i run the command i get the below error can someone help -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mark>cd Desktop\Downgrade
C:\Users\Mark\Desktop\Downgrade>adb push psneuter /data/local/tmp
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb push misc_version /data/local/tmp
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell chmod 777 /data/local/tmp/psneuter
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell /data/local/tmp/psneuter
error: device not found
C:\Users\Mark\Desktop\Downgrade>adb shell
error: device not found
C:\Users\Mark\Desktop\Downgrade>
Is your device plugged and set to charge only with usb debugging on?
Yes it is plugged in set to charge with USB debugging switched on.
Restarted my PC ad get the error -
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mark>cd Desktop\Downgrade
C:\Users\Mark\Desktop\Downgrade>adb push psneuter /data/local/tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\Mark\Desktop\Downgrade>
Do you have drivers installed for the device? Can you access it through other means? Are you on Vista?
Sent from Skynet Central Control System, brought to you by HTC
Related
hi,
two days ago i rooted my Nexus One FRF91-Vodafone with these two methods ( forum.xda-developers.com/showthread.php?p=7548842 and forum.xda-developers.com/showthread.php?t=736271). Still some commands of adb don't work and i can't find a solution.
Code:
C:\>cd android/tools
C:\android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT05EP800252 device
C:\android\tools>adb shell
$ su
su
# id
id
uid=0(root) gid=0(root)
# exit
exit
$ exit
exit
C:\android\tools>adb remount
remount failed: Operation not permitted
C:\android\tools>adb root
adbd cannot run as root in production builds
C:\android\tools>
as you can see the device is connected in debug mode and i am rooted but the commands "adb remount" and "adb root" don't work (and maybe some other commands? i don't know). does it happen because the bootloader is still locked? if so, is there a way to have those commands working without unlocking it? if not, what could it be?
sorry for my english
thanks a lot
ok so this is my first time ever doing anything to a android device, i made the gold card following the instructions and stuff, got it and it says gold card successful when i am done.. i have tried the one click and couldnt get it to work either, so this is where i think I get stuck
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd c:\ace-hack-kit-v9
c:\ace-hack-kit-v9>hackerize-ace setup-downgrade
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1270 KB/s (557962 bytes in 0.429s)
572 KB/s (15837 bytes in 0.027s)
Starting adb shell to test temp root, please be patient...
if you see a '#' prompt, okay to proceed
if you see a '$' prompt, temproot failed
type exit at the prompt to continue
The system cannot find the path specified.
error: device not found
error: device not found
c:\ace-hack-kit-v9>hackerize-ace setup-downgrade
1187 KB/s (557962 bytes in 0.459s)
1031 KB/s (15837 bytes in 0.015s)
mmap() failed. Operation not permitted
Starting adb shell to test temp root, please be patient...
if you see a '#' prompt, okay to proceed
if you see a '$' prompt, temproot failed
type exit at the prompt to continue
The system cannot find the path specified.
# exit
exit
--set_version set. VERSION will be changed to: 1.31.405.6
Patching and backing up partition 17...
Error opening backup file.
c:\ace-hack-kit-v9>
i am guessing it is when it says Error opening backup file?
what am i doing wrong?
any suggestions would be greatly appreciated, I have been trying to get my phone rooted for the last 2 days and have not been able to get it. Im pretty frustrated and I dont know what else to do! Am i just missing something obvious. Grr!
please post in the hack kit thread, not start a new one...thread closed.
Whenever I run Pie, I get this:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb push pie.jar /data/local/atvc
4776 KB/s (1538138 bytes in 0.314s)
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb push root.sh /data/local/atvc
23 KB/s (192 bytes in 0.008s)
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb shell chmod 755 /data/local/atv
c/root.sh
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb shell /data/local/atvc/root.sh
rm failed for /data/local/atvc/blop.asec, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>
.
What do I do to fix it?
adisai1 said:
Whenever I run Pie, I get this:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb push pie.jar /data/local/atvc
4776 KB/s (1538138 bytes in 0.314s)
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb push root.sh /data/local/atvc
23 KB/s (192 bytes in 0.008s)
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb shell chmod 755 /data/local/atv
c/root.sh
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>adb shell /data/local/atvc/root.sh
rm failed for /data/local/atvc/blop.asec, No such file or directory
mkdir failed for /data/local/atvc/dalvik-cache, File exists
pie by jcase
want to buy me pie? paypal-> [email protected]
C:\Users\Adi\Desktop\Adi's Stuff\Android\ADB>
.
What do I do to fix it?
Click to expand...
Click to collapse
It has been reported that King/Kingo Root has a working exploit for this phone, though it may be a temp root it can be made persistent.
Try one of their newer versions.
Hello,
I have a TF300t tablet and i have broken it`s digitizer and changed it myself afterwards. I have changed it with the same type of digitizer but it doesn`t work correctly. I read load of threads and i found a way to repair it by changing the touchscreen pcb firmware. I have rooted the tablet and installed adb on my computer. I tried lots of commands and methods but i can`t push the ekt file to the tablet and i can`t remove the older touch screen firmwares. I will summarise everything i am trying in this picture. I will be very thankfull if somebody can figure out where is the problem. I have installed the newest google usb drivers. The ADB finds the device before i get into the shell but not after that, i think that is the main problem but i`m not sure.
Thank you!
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Бойчо>cd C:\adb
C:\ADB>adb devices
List of devices attached
C5OKCT123824 device
C:\ADB>adb shell
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ # adb push ss.rar /system/etc/firmware/touch
adb push ss.rar /system/etc/firmware/touch
error: device not found
1|[email protected]:/ # rm /system/etc/firmware/touch *.ekt
rm /system/etc/firmware/touch *.ekt
rm failed for /system/etc/firmware/touch, Is a directory
255|[email protected]:/ # rm /system/etc/firmware/touch/*.ekt
rm /system/etc/firmware/touch/*.ekt
rm failed for /system/etc/firmware/touch/*.ekt, No such file or directory
255|[email protected]:/ #
NapsterEps said:
Hello,
I have a TF300t tablet and i have broken it`s digitizer and changed it myself afterwards. I have changed it with the same type of digitizer but it doesn`t work correctly. I read load of threads and i found a way to repair it by changing the touchscreen pcb firmware. I have rooted the tablet and installed adb on my computer. I tried lots of commands and methods but i can`t push the ekt file to the tablet and i can`t remove the older touch screen firmwares. I will summarise everything i am trying in this picture. I will be very thankfull if somebody can figure out where is the problem. I have installed the newest google usb drivers. The ADB finds the device before i get into the shell but not after that, i think that is the main problem but i`m not sure.
Thank you!
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Бойчо>cd C:\adb
C:\ADB>adb devices
List of devices attached
C5OKCT123824 device
C:\ADB>adb shell
[email protected]:/ $ su
su
[COLOR="Red"][email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ # adb push ss.rar /system/etc/firmware/touch
adb push ss.rar /system/etc/firmware/touch
error: device not found[/COLOR]
1|[email protected]:/ # rm /system/etc/firmware/touch *.ekt
rm /system/etc/firmware/touch *.ekt
rm failed for /system/etc/firmware/touch, Is a directory
255|[email protected]:/ # rm /system/etc/firmware/touch/*.ekt
rm /system/etc/firmware/touch/*.ekt
rm failed for /system/etc/firmware/touch/*.ekt, No such file or directory
255|[email protected]:/ #
Click to expand...
Click to collapse
The red area is where you went wrong, to push a file with adb you cannot be running in shell .....
So from C:\ADB> run adb push ss.rar /system/etc/firmware/touch/
I am not sure why you are pushing a .rar file to your tablet but this is not for me to decide .....
You may have better luck with that .....
asus zenfone 2 asus_z00ld stock on logo..
i try flash on adb sideload but CMD error....
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Raj\Desktop\asus 2>adb sideload 123.zip
* cannot read '123.zip' *
C:\Users\Raj\Desktop\asus 2
C:\adb>adb devices
List of devices attached
C:\adb>adb devices
List of devices attached
C:\adb>adb devices
List of devices attached
FAAZCY108898 sideload
C:\adb>adb sideload UL-Z00L-WW-1.17.40.1234-user.zip
Total xfer: 0.00x
C:\adb>