C:\S.onyTablet.S [FLASHER] v3.0\files>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
275501730014164 offline
if I use any other command,
C:\S.onyTablet.S [FLASHER] v3.0\files>adb reboot
error: device offline.
Does any body having any idea?.
Also if i reconnect, usb device arrival itself not detecting in device manager.
If i want to detect in pc,then i have to run either of UMS extSD or intSD scripts that codi's auto atomtic tool provided to put it in.
Does anybody have any idea?
I got it.
kriyas86 said:
C:\S.onyTablet.S [FLASHER] v3.0\files>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
275501730014164 offline
if I use any other command,
C:\S.onyTablet.S [FLASHER] v3.0\files>adb reboot
error: device offline.
Does any body having any idea?.
Also if i reconnect, usb device arrival itself not detecting in device manager.
If i want to detect in pc,then i have to run either of UMS extSD or intSD scripts that codi's auto atomtic tool provided to put it in.
Does anybody have any idea?
Click to expand...
Click to collapse
Chnage the setting -> storage , right corner of the window there is a setting icon. click it and change to mtp
kriyas86 said:
Chnage the setting -> storage , right corner of the window there is a setting icon. click it and change to mtp
Click to expand...
Click to collapse
Is your tablet seen as a adb device in control panel of your computer
Sent from my SGPT12 using xda app-developers app
BUMP!
Get a newer version of adb.exe, the one you have does not support Android 4.0.3.
Sent from my Nexus 4 using xda app-developers app
Related
Indirect please create a script that does this for us.
-XE
Is this for the Nook Tablet? That's what this forum is for.
Sent from my BNTV250 using Tapatalk
ckevinwelch said:
Is this for the Nook Tablet? That's what this forum is for.
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
Yup, changed the typo. I've been messing with the Touch for a few hours as well.
Not quite sure about "Recovery" Is this installing CWM or is it to recover BN software or what? My assumption is this is an automated CMW install, but it is not clear what it is.
hmm doesn't work for me. I always get the error cannot stat ' ./mods/ntrecoveryv2.img' Not such file or directory
Unable to chmod
Fail
Didnt work for me too! Changed the script to properly point at the .img file, still doesnt reboot into recovery! :-/
rjmohit said:
Didnt work for me too! Changed the script to properly point at the .img file, still doesnt reboot into recovery! :-/
Click to expand...
Click to collapse
Just tested it and fixed the directory error.
imo, change the title to include [CWM] and [Windows] since this script is for the former and only runs on the latter.
Just my 0b10 cents to keep it clear
Nuckin said:
imo, change the title to include [CWM] and [Windows] since this script is for the former and only runs on the latter.
Just my 0b10 cents to keep it clear
Click to expand...
Click to collapse
Thanks, I knew somebody would see the error and address it.
Nuckin said:
imo, change the title to include [CWM] and [Windows] since this script is for the former and only runs on the latter.
Just my 0b10 cents to keep it clear
Click to expand...
Click to collapse
Ok, all better..
working,
did not reboot in recovery but i did it manually
just need to test to make a backup
I might also suggest adding to your read me, to boot into recovery, turn off NT, hold nook button and power button simultaneously until the NT boots into CWM recovery.
Might clarify for the newbies that don't know.
Win7 64, Rooted via Zerg. Drivers setup correctly(or so i assume since i zerg'd and the script recognizes it), i run the .bat, says
Your Nook Tablet is successfully connected!
* daemon not running. starting it now*
* daemon started successfully *
protocol failure
* daemon not running. starting it now *
* daemon started successfully *
Unable to chmod /data/local/ntrecoveryv2.img: No such file or directory
/data/local/ntrecoverv2.img: cannot open for read: no such file or directory
...then the rebooting into recover msg..
it reboots to the exclamation symbol, says "please restart you device and try again. if yyou encounter the same issue, please contact customer service or visit...blah blah...then it shuts down
EDIT: Auto mount is disabled, when i connect the nook, in the device manager it shows "USB Mass Storage Device" in the driver list which I had to uninstall when I zerg'd,( it reinstalls when ever i reconnect the nook). When I uninstall mass storage, and run the script say device not found and can't find the build prop. So it will only see the nook when mass storage is running, and won't when its uninstalled.
When the .bat said it was rebooting into recovery, it just rebooted to desktop. I used quick boot and did the reboot to recovery. All is good. Thanks for the easy install.
You might try disabling automount USB. I know it is not mentioned, but I am pretty sure it is a requirement. That is at the bottom of the list where you checked usb debugging ect..
yes, you need to uncheck automount for the script to work. thats how i installed mine. I also use quickboot to go into recovery, much easier than holding buttons
---------- Post added at 06:52 PM ---------- Previous post was at 06:49 PM ----------
tep065 said:
Win7 64, Rooted via Zerg. Drivers setup correctly(or so i assume since i zerg'd and the script recognizes it), i run the .bat, says
Your Nook Tablet is successfully connected!
* daemon not running. starting it now*
* daemon started successfully *
protocol failure
* daemon not running. starting it now *
* daemon started successfully *
Unable to chmod /data/local/ntrecoveryv2.img: No such file or directory
/data/local/ntrecoverv2.img: cannot open for read: no such file or directory
...then the rebooting into recover msg..
it reboots to the exclamation symbol, says "please restart you device and try again. if yyou encounter the same issue, please contact customer service or visit...blah blah...then it shuts down
EDIT: Auto mount is disabled, when i connect the nook, in the device manager it shows "USB Mass Storage Device" in the driver list which I had to uninstall when I zerg'd,( it reinstalls when ever i reconnect the nook). When I uninstall mass storage, and run the script say device not found and can't find the build prop. So it will only see the nook when mass storage is running, and won't when its uninstalled.
Click to expand...
Click to collapse
Re download the file it was just updated
make sure you have both usb debugging checked (uncheck it and recheck it again) also make sure automount is unchecked as well.
plus make sure your adb drivers are set up correctly.
Both are checked, automount disabled (all done before i started this) drivers SHOULD be good, they are the ones i used to zerg and the script msg says it sees the nook (when USB Mass Storage is running). The nook drives do not mount.
Edit: Using the updated script, i even downloaded it a second time...still get the Protocol failure message and the reboot error, etc from my first post.
Factory resetting, gonna do this with a fresh install. See if I can narrow down the issue.
redownload again previous posts had similar issues. he updated the script
Know-Fear said:
I used quick boot and did the reboot to recovery.
Click to expand...
Click to collapse
I have never used quick boot, but gave it a try, works great. Thanks for the heads up.
tep065 said:
Both are checked, automount disabled (all done before i started this) drivers SHOULD be good, they are the ones i used to zerg and the script msg says it sees the nook (when USB Mass Storage is running). The nook drives do not mount.
Edit: Using the updated script, i even downloaded it a second time...still get the Protocol failure message and the reboot error, etc from my first post.
Factory resetting, gonna do this with a fresh install. See if I can narrow down the issue.
Click to expand...
Click to collapse
Was your ADB working before you tried the CWM flash? (I understand it worked when you rooted it, mine did too, but never worked again after that) If it was working fine, you will need to run the USBdeview or similar to remove any and all USB mass storage device, anything android related and probably anything related to a particular phone. I did this last night and ADB is now running perfectly. Also, make sure you install ADB hijack as well after rooting.
Post back after you restore and get re-rooted as to whether or not ADB is working correctly.
http://matthill.eu/android/root-transformer-prime-jellybean-update/
IT WORKS REALLY!!!! Simple & Easy with the Xperia Tablet S and Jelly Bean 4.1.1
I have tested with my Tablet SGPT122DE/S and i have really Root!
This, I note that this tool is not from me! The tool was written by @djrbliss.
If you want to thank someone then do that after your feeling - at least I thank everyone here on Meaningful information and applications ...
Thanks @xda-Community!
Greets from Germany Leipzig/Schkeuditz
(Download the Motochopper and run the run.bat)
Are you sure?
I just get *daemon started successfully*
ADB Driver
Ah there it occurs to me I'm so another ADB Driver tested ... it comes with the need to see if I still have the locally then I'll post times with the times here ...
Do not forget to turn on USB debugging
I Have a Adb Driver Interface Version 2.0.10.2 from 11.08.2009 (not digitaled signed)....
SWFlyerUK said:
Are you sure?
I just get *daemon started successfully*
Click to expand...
Click to collapse
same here
It appears to be an ADB issue - Just need to install the drivers.
*EDIT* -> Wow, it actually worked! I'm rooted!
sag ich doch das es wirklich funktioniert
I say but that it really works
SWFlyerUK said:
It appears to be an ADB issue - Just need to install the drivers.
*EDIT* -> Wow, it actually worked! I'm rooted!
Click to expand...
Click to collapse
what drivers did you install, these on the link?
thank u
Check this link mate;
http://forum.xda-developers.com/showthread.php?t=1883808
USB Driver
Here the Usb Driver for Adb Interface...
xxliftsupxx said:
http://matthill.eu/android/root-transformer-prime-jellybean-update/
IT WORKS REALLY!!!! Simple & Easy with the Xperia Tablet S and Jelly Bean 4.1.1
I have tested with my Tablet SGPT122DE/S and i have really Root!
Please Push the Thanks Button when it works for your Tablet
Greets from Germany Leipzig/Schkeuditz
(Download the Motochopper and run the run.bat)
Click to expand...
Click to collapse
GREEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAATTTTTTTTTTTT man and many thanks it worked for me :laugh:
Is this after been locked out before from 4.0.3 release6b to 4.1.1 aka the 4.1.1 that everyone have can get rooted if so awesome
Having root has totally transformed the way I use this device.
I can now remove adverts, I have the Xperia Tablet Z keyboard and Home Launcher, tried MB2 but it doens't work, grr!
SWFlyerUK said:
Having root has totally transformed the way I use this device.
I can now remove adverts, I have the Xperia Tablet Z keyboard and Home Launcher, tried MB2 but it doens't work, grr!
Click to expand...
Click to collapse
This is great took all of three mins to root ha ha where did you get the keyboard and home launcher can you post a link
also did you delete the old home launcher
Sent from my SGPT12 using xda app-developers app
works on SGPT132/CN, thank you thank you thank you. I can finally install google play on my stupid tablet
can this be done on a 4.1.1. never rooted xperia tablet or does it have to be a pre-rooted before updating to 4.1.1.??
has anybody tried this and or can confirm this is possible.
sengoku said:
can this be done on a 4.1.1. Never rooted xperia tablet or does it have to be a pre-rooted before updating to 4.1.1.??
Has anybody tried this and or can confirm this is possible.
Click to expand...
Click to collapse
never rooted!!!!! :d yay
Greetings guys ,
I installed the drivers also on a new pc but i am getting stuck at :
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Nothing happens after , as i wrote i tested on 2 pcs
Any help pls ?
Vatis
Great scott, it worked! So elegant root and wayyyyy sooner than I expected!
To the fokls having problems; I found out, that adb.exe in motochopper.zip did not want to play together with my Xperia. So I deleted it, killed adb.exe and copied latest adb.exe from android sdk to motochopper directory. Blam, no problems and I have root.
You may also manualy debug (and even root) by starting cmd.exe and calling commands manually, ie.
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXX device
If this don't show you device, you have no changes to root. If your device shows up, there should be no problems. If you devices is not showing, kill all adb.exe processes and use adb.exe from latest android sdk. Then you can even root manually and see waht step does what:
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb install Superuser.apk
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox
And then manually reboot. Run each command manually one per one, do not copy paste every command as batch. This will teach you a lot But .bat should work.
Kudos to authors of motochopper!
vatis24 said:
Greetings guys ,
I installed the drivers also on a new pc but i am getting stuck at :
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Nothing happens after , as i wrote i tested on 2 pcs
Any help pls ?
Vatis
Click to expand...
Click to collapse
If you under windows 8
1st :
From the Metro Start Screen, open Settings,
Click "Change PC Settings".
Click "General".
Scroll down, and click "Restart now" under "Advanced startup".
Click "Troubleshoot".
Click "Advanced Options".
Click "Startup Settings".
Click [Restart].
Choose "Disable driver signature enforcement" (Usually #7)
2nd
Install device drivers either through the automated (not manualy use the : Install ADB Drivers.exe)
http://www.mediafire.com/?msn16sd5wrb1sdh
3rd
Run as administrator run.bat from motochopper
Normally this should work
Thank you very much for your replies mates.
Worked perfectly.
What i did :
Disabled the Disable driver signature enforcement as jimbxl said ,
installed the Sony tablet ADB driver.
Copy from inside the folder of Sony tablet ADB the adb.exe and the .dll (2 files ) and paste it to motochopper folder.
Cheers all
jimibxl said:
If you under windows 8
1st :
From the Metro Start Screen, open Settings,
Click "Change PC Settings".
Click "General".
Scroll down, and click "Restart now" under "Advanced startup".
Click "Troubleshoot".
Click "Advanced Options".
Click "Startup Settings".
Click [Restart].
Choose "Disable driver signature enforcement" (Usually #7)
2nd
Install device drivers either through the automated (not manualy use the : Install ADB Drivers.exe)
http://www.mediafire.com/?msn16sd5wrb1sdh
3rd
Run as administrator run.bat from motochopper
Normally this should work
Click to expand...
Click to collapse
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
SWFlyerUK said:
Having root has totally transformed the way I use this device.
I can now remove adverts, I have the Xperia Tablet Z keyboard and Home Launcher, tried MB2 but it doens't work, grr!
Click to expand...
Click to collapse
How we can install the new home Launcher swift ?
Cheers
saw the thread over here: http://forum.xda-developers.com/showthread.php?t=2292791
tried all of the same steps (and more) listed in that thread numerous times.
SDK is the latest zip file dated "20130522"
phone DOES have developer mode enabled.
Samsung Kies connects and works fine (using driver bundled in Kies installer)
Windows Explorer maps the device and it can be browsed
Device Manager lists device by name under Portable Devices as well lists "SAMSUNG Mobile USB Composite Device" (driver 2.9.510 date 2013.05.23) under USB controllers
using Koushik Dutta's Universal ADB Driver did not help at all, device then becomes an android device in device manager and neither Kies or adb can connect to it...
Code:
C:\Android_SDK_Windows\sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android_SDK_Windows\sdk\platform-tools>adb devices
List of devices attached
C:\Android_SDK_Windows\sdk\platform-tools>
ideas?
EDIT: SOLVED, mis-tapped in dev options menu (stupid small text made BIG now)... checkmarked 'include bug reports...' instead of 'usb debugging'. off to hang my head in shame
Hi!
I have a problem - ADB see my device as offline on PC. I tried many solves but no one helped me.
My configuration:
PC - Win7 (32), ADB v.1.0.31
Device - Android 4.0.3, ADB v.1.0.29
I don't know what happened but one morning couldn't connect to my device. Please, help!!
Before you lost USB connection, had you connected to it over Wi-Fi using the "adb connect (your IP address here)"? If so, try using [adb disconnect (Your IAP address)]
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
Before you lost USB connection, had you connected to it over Wi-Fi using the "adb connect (your IP address here)"? If so, try using [adb disconnect (Your IAP address)]
Click to expand...
Click to collapse
I rebooted PC and device and nothing changed after this.
And I restored System Restore Point (when the problem didn't exist), but my device still offline. :'(
Now exactly know that something wrong on my device. How make my device to work?
VJVS said:
Now exactly know that something wrong on my device. How make my device to work?
Click to expand...
Click to collapse
If device is detected on your PC, goto to Device Manager, check vendor id of ADB device, then edit adb_usb.ini (%HOMEPATH%/.android/) and add them e.g."0x2207" is vendor id for Rockchip. Restart adb.
lolet said:
If device is detected on your PC, goto to Device Manager, check vendor id of ADB device, then edit adb_usb.ini (%HOMEPATH%/.android/) and add them e.g."0x2207" is vendor id for Rockchip. Restart adb.
Click to expand...
Click to collapse
I have 2 strings:
USB\VID_0BB4&PID_0C03&REV_0255&MI_01
USB\VID_0BB4&PID_0C03&MI_01
In adb_usb.ini I must add just 0x0BB4. Is it right?
I added 0x0BB4 in adb_usb.ini and restart adb on PC. Nothing changed.
I was wrong, my device is OK, because it works on another PC. So I need restore working state my PC.
How to do it?
Well, I have new njuans. I reinstall PC drivers for device, I reinstall Android SDK and ... my device is still offline, though another device ara online and work perfectly. I installed "WiFi ADB Pro" on my device and it's work. My device is online, but it's via WiFi.
What can I do to work via wire?
Anyone managed to find working USB drivers and get their Mate 20 Pro showing up in ADB? If so could you share the drivers as I can't find any.
Edit: for some reason USB debugging turned itself off. It's showing up now.
@Kipp162 did you finally manage to run adb with the HUAWEI Mate 20 Pro? I was not able to do so. All other devices have been no problem but it seems that the HUAWEI Mate 20 Pro needs an extra trick?!
The thing that finally worked for me was installing HiSuite.
cant see device
saturnspike said:
The thing that finally worked for me was installing HiSuite.
Click to expand...
Click to collapse
Hi, how exactly ? I have installed HiSuite, but anyway "adb devices" cant see any device.
(have mate20pro with latest os and emui)
[email protected]:/home/mato# adb kill-server
[email protected]:/home/mato# adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/home/mato# adb devices -l
List of devices attached
[email protected]:/home/mato#
matolog said:
Hi, how exactly ? I have installed HiSuite, but anyway "adb devices" cant see any device.
(have mate20pro with latest os and emui)
[email protected]:/home/mato# adb kill-server
[email protected]:/home/mato# adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/home/mato# adb devices -l
List of devices attached
[email protected]:/home/mato#
Click to expand...
Click to collapse
I have to make sure usb debugging is enabled and when you plug phone up to computer, make sure you select file transfer.
dwojr said:
I have to make sure usb debugging is enabled and when you plug phone up to computer, make sure you select file transfer.
Click to expand...
Click to collapse
yes, debugging was enabled.
well after many attempts I was able to connect. (the connection was problem, must tried many times restart server, after connection adb shell, connection with phone was stable)