Hi
So, I want to sideload a zip file, but of some reason, it doesn't work! I've done this a few times ago, but at that time I were on Windows 7. Atm. I'm on Windows 8. I can get my X+ into sideload (TWRP) without problems. But I'm not sure if it's starting correct.
Starting ADB sideloa feature...
Click to expand...
Click to collapse
And it keeps doing that.. No confirm that it's started. However, usually it works without writing any confirmation.
On the command prommt it writes:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
But I dont want it do be via the local network. It should be via USB. How do I change that? My guess were ADB usb but that wasn't for any use.
Anyone?
Related
Hi all
I'm currently trying to root my x10i, I carried out the first step with no troubles however whenever I enter my device into usb debugging mode I get the following error when loading the step2.bat
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
"select option 6 SDCARD UPDATE"
Press any key to continue . . .
Click to expand...
Click to collapse
Has anyone else experienced this problem? I'm sure the correct driver is installed as the system knows the ADB driver is present.
Thanks
-Sean
Same exact thing .. stuck on HTC EVO white screen 4 G will nto go any further.
sur3sh0t said:
Hi all
I'm currently trying to root my x10i, I carried out the first step with no troubles however whenever I enter my device into usb debugging mode I get the following error when loading the step2.bat
Has anyone else experienced this problem? I'm sure the correct driver is installed as the system knows the ADB driver is present.
Thanks
-Sean
Click to expand...
Click to collapse
Moved as not android development
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Please help!
fezir said:
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Click to expand...
Click to collapse
I hate to sound like a noob, but I am having the same problem!!!!
I went through the developer forum and found a response from "Ciddy", on the matter, this is the link { http://forum.xda-developers.com/showpost.php?p=21049320&postcount=89 } , this seemed to work for several other people, but not me.
This is what happens:
1. Uninstall Asus Sync (BTW Asus Sync does not detect the TP for me either).
2. Hit Win+R, enter "devmgmt.msc" (no quotes), brings up device manager.
3. Connect the prime, when it shows up in device manager, select it and hit Del.
Then search for new hardware and install the supplied drivers.
4. After the first reboot of the prime, check the device manager, it should show Asus MTP device [ THIS IS WHERE THE DEVICE MANAGER DISPLAYS Transformer Prime TF201, NOT Asus MTP device] with a notification; update its driver from the Viper pack.
ADB does not detect the TP in command promt. Windows 7 64x. Everything is updated, I have ADB from rooting HTC's and several other android device's. I have reset the TP to factory default's twice. and I have read and read, and have not found anything, PLEASE HELP!
** PS. I am only able to transfer files with Windows Explorer.
*** Calling Asus Support was pointless, they aren't even familial with ADB.
I have the Android SDK/Eclipse loaded on my machine so ADB is fine for me, of course. So, cannot help in your situation.
I wonder if you have considered downloading the Android Terminal Emulator from the market and just entering your commands directly on the Prime? The first time I rooted a phone, that's the way I did it, since I had no clue what ADB was. Not a permanent solution to your problem, but perhaps it can get you by for now.
Of course, I may be missing something as to why this won't work...
Edit: I read up on the TPSparky root and Viperboy's tool ... pretty sure at this point that what I am saying above will not work.
Resolved
I resolved the issue. There is still something blocking me from ADBing into the tablet with my Windows PC but I tried on an Ubuntu box and it worked perfectly. I am now successfully rooted.
How did you solve it?
yoinjo said:
How did you solve it?
Click to expand...
Click to collapse
I used a computer running Ubuntu. Never got it working with my Windows laptop.
I installed http://forum.xda-developers.com/showthread.php?t=1426502 drivers and now my TF201 shows under Android Devices (Asus Transformer Prime ADB Interfaces). ADB however still returns error: device not found
So I've solved the problem too.
I've used an old 32bit XP computer with 2.0 USB
I had that problem....i sovled it.......it was me...i forgot to go into settings on the TP and under dev options make sure USB debugging is checked.....after i did that everything went smooth
Sent from my Transformer Prime TF201 using Tapatalk
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Any update on this?
When having started the tab normally it gets recognised with device id.
When in fastboot mode - nothing
I installed several driver but the tab does not get recognised (2PCs win7)
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
i got here same problem, any progress on this one? did you already found a way to fix this issue? thanks.
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
Sorry for asking an obvious question but are you in recovery when you are trying to do adb? If you are then download the nvflash file from dev thread, unzip it, open the folder until you see the adb.exe file.
Press and hold shift on the keyboard, right click in the window and select command prompt here.
Now do adb devices it should show up.
I am having the same problem. I have tried all available drivers on internet from number of forums. Still no luck . I have also tried from Windows 8 64 Bit and Windows 32 Bit laptops. From the same laptop, I was able to connect my Xperia U and it showed under "adb devices". What am I missing? I need to install custom ROM. Please help.
Did anyone solved this problem? I have Win 7 64-bit and have been following a thread on installing Crombi-KK
After adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard, Hairybean TWRP was installed and now i need to boot into fastboot
but adb is no longer working.
I tried reinstalling drivers for TF201 but no adb access.
update1:
Ok. I managed to solve the first problem with no ADB access. In recovery I clicked to Reboot, and clicked System. While system was rebooting I was holding Power Down and got into fastboot mode. I lost ADB access but apparently still have fastboot access so I have proceeded with the instructions to flash blob
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob, then
fastboot -i 0x0b05 reboot-bootloader
In recovery the instructions say format next, so now I am currently formatting, so I will update everyone who need this.
I still don't know why I lost ADB access which I had. Some people here suggested ubuntu but I don't have it.
After formatting I will need ADB to push crombi to device, but I twrp recognizes SD card so if I don't get ADB access after formating I will
try to copy crombi-kk to SD card and then flash it from recovery. I will write what happened when formatting is done.
update2:
After format which took 30 minutes I suddenly have ADB access. Wtf??? Anyway I pushed crombi-kk zip on the tablet and flash it. After 5 minutes of flashing everything working great. Will send a donation. Tablet with stock 4.1.1 was slow 4.4 is great. Thanks everyone who made it possible.
Hi comrades!
Ihave unlocked prime 32dock.
Yesterday I tried to flash the firmware KJY2010 Primalicious 9.4.2.21.
1) First, I installed the CWM 5.8.2.0 - successfully
2) rebooted several times - everything was OK. The factory firmware loaded.
3) Then I found the instructions KJY2010 Primalicious 9.4.2.21 - is successfully established.
4) The new firmware is loaded. I set up wifi, google account and decided to reboot.
5) After rebooting, I was constantly load in the CWM.
I go to instruction Brick 1a
adb give me this result:
Code:
c:\Tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
c:\Tools>
I try 2 other Prime usb driver - result the same. (In device manager Asus transformer Prime set OK, whithout any warnings)
I try do this under Linux - result the same.
What else can i do in this situation?
I have backup image and i try do restore - result the same.
I try wipe data - result the same.
Please HELP.
See this thread to get your Prime recognized by adb:
http://forum.xda-developers.com/showthread.php?t=1426502
thanks
tedr108 said:
See this thread to get your Prime recognized by adb:
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
big thanks.
I already tried this driver yesterday, but was inattentive. did not remove the old drivers first.
Who made everything clear to the user manual (deleted the driver and rebooted the computer).
It worked! Thank you and the author of the driver! My tablet is restored.
I had this problem with my prime with it 1a bricked. so i tried it on my laptop instead of my desktop and was able to adb. Think my desktop needs a reimage but i was not in the mood to do it.
yurmala22 said:
big thanks.
I already tried this driver yesterday, but was inattentive. did not remove the old drivers first.
Who made everything clear to the user manual (deleted the driver and rebooted the computer).
It worked! Thank you and the author of the driver! My tablet is restored.
Click to expand...
Click to collapse
FIXED!
Hiya mate, any chane you can write down your procedure if thats cool, ive got the exact same issue as you,
- ive deleted anything that looks like a driver pack from asus in my add remove program (im on xp)
- ive uninstalled the driver from the listing in the device manager (Android Phone > Asus Transformer Prime ADB Interface) which comes up when i hook up the tab while its in CWM
-restarted comp, connect my tab, point xp's driver install program to the universal naked driver folder
- all set, yet still getting the device not found
I have adb folder in C:\ directory
CMD into the run menu
CD change C:\
cd adb
adb shell
daemon not running. starting it now on port5037
daemon started successfully
error: device not found
Been looking around for a while now, pulling my hair out, a few snippets here and there, some have been successfull, but no detail on how they got it fixed
Out of all of them, your situation best describes the one im in at the moment, am i missing something?
Hoping you or anyone really, have a solution, and perhaps help anyone else who might get into a similar situation
By the way, for the record, my brick occured because i stupidly Factory/Reset using the ROMS ( Virtuous Prime/Stock kernel) menu, rather then CMW's Factory/Reset
Any help would be mucho appreciated
Edit: Sorry ive just realised how old the thread is, hope no one minds, if not
-Tried asus sync
-Tried pdanet?(is that right?) drivers
- Hoping for a solution that doesnt involve deleting internal sd card content as ive got 1 or two nand backups im in the process of streamlining, if thats possible that is
Edit 2
Ok, managed to get past the device not found part,
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Installed another version of adb(link above, follow instructions), i guess the adb i was using was a dud
Edit 3
Fiiinaly fixed it, problem was adb, for anyone who might have similar symptoms try installing and following the instructions in the link just up there ^^^^
And to be thorough, follow the instructions written by Diamondback (option 1a)
http://forum.xda-developers.com/showthread.php?t=1514088
Heres the snippet, if Diamondback dont mind?
Once adb's installed correctly
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
There you go folks, if a noob like me can do it.......well, you get the idea
Hello,
I tried to flash the viper one x+ rom on my device but it turned out terrible. I folowed the process but finally i couldn't flash the rom i don't know why. After a few tries my phone started to not get signal and i couldn't turn on wifi. Somehow i made it work but after that i got a very stupid idea. I wanted to copy the files of the rom on my phone using the venom recovery (TWRP). Now there is no OS on my phone and from my storage everything is missing escept the TWRP folder. I thought there will be my backup but it disappeared. Can anyone help me please?
http://forum.xda-developers.com/showthread.php?p=35897865#post35897865
this post might help you a bit
read post #4
also try to search hasoon toolkit to help you fix you prob
:fingers-crossed:
It didn't work. When I'm trying now it sais that my phone is not connected but it must be connected because I could flash the recovery.
so my computer is recognizing my phone as an adb device but the adb sideloader can't find the device. And writes this: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
i dont know what to do :/
I made it! Using just cmd. If you put the rom in the sdk platform tools and start there a cmd and in twrp recovery on your phone go to advanced adb sideload start it and in cmd write adb devices it should write that your device is in sideload then write adb sideload <rom name>.zip (that must be put in the sdk folder) and it will sideload your rom. If adb devices cant find your phone or it writes that it is in recovery reply the command a few times until it writes sideload. After that you are ready to go. I hope it will help somone.
I am not sure I should post my problem here, but it seemed approperate to me. If not, please tell me where to post this.
I try to install DualRecovery on my Tablet Z2 (SGP521). Up till step 2 everything is going fine. Deamon is running, device is found and it sends the recovery files. Step 3: creating target sockets.... OK! and then Done!
A lot of x's and then my device is rebooting and the following message:
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
But my device takes like 5 minutes to boot. Before my device is completely booted I get the message:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Unrooted installation failed, please press 1
once the device finished rebooting to retry.
Is the problem the boot time of 5 minutes or is it really failing regardless of the boot time??
Barium said:
I am not sure I should post my problem here, but it seemed approperate to me. If not, please tell me where to post this.
I try to install DualRecovery on my Tablet Z2 (SGP521). Up till step 2 everything is going fine. Deamon is running, device is found and it sends the recovery files. Step 3: creating target sockets.... OK! and then Done!
A lot of x's and then my device is rebooting and the following message:
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
But my device takes like 5 minutes to boot. Before my device is completely booted I get the message:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Unrooted installation failed, please press 1
once the device finished rebooting to retry.
Is the problem the boot time of 5 minutes or is it really failing regardless of the boot time??
Click to expand...
Click to collapse
You didn't mentioned your firmware version but Dualrecovery ain't compatible with your device latest stock firmwares.
kulvertti said:
You didn't mentioned your firmware version but Dualrecovery ain't compatible with your device latest stock firmwares.
Click to expand...
Click to collapse
Indeed... The tablet is on Android version 5.0.2; build number 23.1.A.1.28. So it should work, right?
Barium said:
Indeed... The tablet is on Android version 5.0.2; build number 23.1.A.1.28. So it should work, right?
Click to expand...
Click to collapse
Yes, it should work. After checking that there is no other adb (or Sony) -process runing in the backround try to install it again. Maybe several times.
kulvertti said:
Yes, it should work. After checking that there is no other adb (or Sony) -process runing in the backround try to install it again. Maybe several times.
Click to expand...
Click to collapse
And does it matter that the bootloader is locked? The service menu says: "Unlocking Bootloader Allowed:NO". Normally it says YES, but the DualRecovery should also work with a locked bootloader, right?
Barium said:
And does it matter that the bootloader is locked? The service menu says: "Unlocking Bootloader Allowed:NO". Normally it says YES, but the DualRecovery should also work with a locked bootloader, right?
Click to expand...
Click to collapse
Correct.