whats the next step after device manager recognizes android devices?
What program do i open up so I can start altering scripts, especially for adhoc?
thankx
specifically, which program in sdk android tools do i use for adb to alter scripts
specifically, which program in sdk android tools do i use for adb to alter scripts
This isn't the Q&A section or general section.
Apply your question(s) in the proper sub-forum, cause you picked the wrong one.
Posting in the wrong forum might result in a temporary vacation
Post moved to general forum.
Q&A for [Root 4.4.X] Pie for Motorola devices
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Root 4.4.X] Pie for Motorola devices. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Nope
Hi, I went through everything with it, ran each command, and it performed as expected, however when I run super SU, it tells me it's not rooted.
Use towelpieroot. ?
---------- Post added at 09:38 AM ---------- Previous post was at 09:37 AM ----------
And if you're on 4.4.4, it won't work. There's no root yet for 4.4.4 on a locked bootloader.
And no, you can't downgrade without a great risk of bricking.
Sorry!
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
You should check the one stop shop root thread sticky in general section for your options.
device offline
Godbless Pie Root, however i still encounter TA620LGCI offline and dont know how to make it go online. I could really use some help. Im working with a verizon droid mini xt 1030.
HEELP
When i open the pie.jar its giving me error message saying The Java JAR file "pie.jar" could not be launched check the console for possible error messages.
Kidd x Pri said:
When i open the pie.jar its giving me error message saying The Java JAR file "pie.jar" could not be launched check the console for possible error messages.
Click to expand...
Click to collapse
See 2 posts above yours. ?
what if /data/local/atvc doesn't exist?
I'm using the AT&T ZTE Z667 (aka Zinger) and some folks have said that this script works to temproot it. However, I can't seem to get it to work. For starters, the directory /data/local/atvc doesn't exist or perhaps the shell user doesn't have access to it.
I've found the writable folder /data/local/tmp and have put the files there, first modifying root.sh to point to that directory rather than atvc.
The script does seem to run correctly and the shell is terminated, which seems normal. But when I come back in with adb shell and run "su", I am not root.
Any ideas would be appreciated... I'm not sure if the reason for this is that I chose a different folder than atvc, or something else.
brfe said:
I'm using the AT&T ZTE Z667 (aka Zinger) and some folks have said that this script works to temproot it. However, I can't seem to get it to work. For starters, the directory /data/local/atvc doesn't exist or perhaps the shell user doesn't have access to it.
I've found the writable folder /data/local/tmp and have put the files there, first modifying root.sh to point to that directory rather than atvc.
The script does seem to run correctly and the shell is terminated, which seems normal. But when I come back in with adb shell and run "su", I am not root.
Any ideas would be appreciated... I'm not sure if the reason for this is that I chose a different folder than atvc, or something else.
Click to expand...
Click to collapse
Brfe, did you ever figure this out?
Sent from my Z667T using XDA Free mobile app
2 exact Moto Gs but...
two different results when trying to root. Both are XT1028 Moto G on 4.4.2, builds and kernel exactly the same specs. My plan was to use Pieroot and then Sunshine to unlock bootloader. 1 worked perfectly by the numbers, the other one will not allow root. I've tried Pieroot (ADB push from laptop), Towelpieroot and Kingroot (both apk). Phone locks up and reboots. I have to get a temp root to use Sunshine, any ideas what is going on?
Edit: NM, got it. Finally root took with ADB and pieroot. Ran Sunshine installer and rebooted, unlocked bootloader. Side loaded CWM and debloated stock rom and now everything is perfect.
Thank you very much, jcase, this tool helps a lot on my droid mini. Also, it works well on my moto g (xt1028 by verizon). However I need to find some approach to remove write protection of xt1028, as MotoWpNoMo-0.0.4 doesn't work.
If you know any solution to remove write protection for xt1028, please kindly tell me? Thanks in advance.
[Q&A] SoupKit (again)...When you're fed up with trying to get ADB to connect in Wind
Q&A for SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Trouble with Soupkit Kindle fire first gen
Hi all,
I am pretty much a noob when It comes to Linux although I have installed a few times. Currently I am running xubuntu 14.04 LTS. I have followed the instructions for installing soupkit and rootplus but I don't seem to be able to use the adb or fastboot that are included in the soupkit zip. When I try to use the "adb devices" command the terminal returns "bash: /home/nate/bin/SoupKit/files/adb: No such file or directory".
At this point I am just not sure what to do next. Any help is much appreciated. Thx
Q&A for ***** JTAG PINs & DUMP *****
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for ***** JTAG PINs & DUMP *****. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
-W_O_L_F- said:
Medusa has working dump for Ativ S. I used it.
Ok, what I used:
1) ATF Nitro
2) Molex adapter for it
3) Free dump from Medusa section on Bootloader 2.0
What I did:
1) Read full (16GB) dump from the phone. It takes whole day even in maximum turbo mode (30MHz). You can read only first 256MB ROM if you don't need your data.
2) Opened image from Medusa (or your dump). With any tool you need to find out where all 3 MODEM partitions and DPP are (offsets).
3) Extract those 4 partitions from YOUR DUMP.
4) Write first 128MB of Medusa dump to the phone.
5) Write your 4 partitions above it. (don't forget to enter offsets)
6) Boot your phone into Download Mode and reflash normally.
MODEMs and DPP are unique to your phone!
All this was done via ATFJ.exe and Lumia WP8 Custom R/W as a template.
Click to expand...
Click to collapse
Can U explain what can i do for these things? Or what is this overall. thx
Q&A for [HOW-TO] ADB via VirtualBox USB passthrough (Windows host to Ubuntu guest)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOW-TO] ADB via VirtualBox USB passthrough (Windows host to Ubuntu guest). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Galaxy Nexus with 4.3 is seen offline inside VirtualBox/Ubuntu 14.04
Hi,
I'm trying to access a Galaxy Nexus hooked up to a Windows machine through VirtualBox running Ubuntu 14.04.
I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=570452, but the devices keeps showing offline:
adb devices
List of devices attached
0146B5681401101C offline
Here is what lsusb gives me:
Bus 001 Device 004: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
When I don't run VB, windows adb gives me:
adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0146B5681401101C device
Any idea?
Thanks.
I know this doesn't answer your question but I will say I often have had issues using a USB device through a virtual machine. My best suggestion is to set up a dual boot environment or just stick with a single operating system.
But ideas on how to fix is probably a permission problem, be sure you have the required permissions set up in advance