[Q] Cant get to shell! - Droid X General

here's my problem:
c:\Droid\tools>adb push busybox /sdcard/busybox
adb server is out of date. killing...
* daemon started successfully *
1827 KB/s (1926944 bytes in 1.029s)
c:\Droid\tools>adb push exploid /sqlite_stmt_journals/exploid
adb server is out of date. killing...
* daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
Than i get this on the second go:
c:\Droid\tools>adb push exploid /sqlite_stmt_journals/exploid
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'exploid' to '/sqlite_stmt_journals/exploid': No such file or dir
ectory
I looked into the root folders and found no sqlite_stmt_journals dir there. Should there be one? If anyone can tell me how to get past this would be appriciated .

Related

ADB: device not found

Hi ,
I installed Android from package http://trash.eneqe.com/Leo/hd2_froyo.tar.gz to my HD2, and install/configuration adb on Desktop and Ubuntu follow below instruction:
http://wiki.cyanogenmod.com/index.php/Install_the_Latest_Android_sdk#Windows.
on Desktop side: there have not any notification about to install USB driver
I will got below error message after connect HD2 both in Desktop and Ubuntu.
[email protected]:~/sdk/tools$ sudo ./adb kill-server
[email protected]:~/sdk/tools$ sudo ./adb start-server
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:~/sdk/tools$ sudo ./adb devices
List of devices attached
[email protected]:~/sdk/tools$ sudo ./adb usb
error: device not found
[email protected]:~/sdk/tools$
My desktop is Win 7, Ubuntu version is 10.04.
I need your help, thank you!

Problems fully re-rooting phone.

Hi there,
So I'm trying to re-root my HTC Legend from Virgin Mobile. I had success with rooting it the first time using a guide from techenclave (it seemed to be the most complete, most robust, and most user-friendly guide out there..). This guide also merged a lot of the accumulated information on the internet and was the only one (that I could find) that mentioned to use MMC0 if MMC1 didn't work whilst making a goldcard.
I did this on January 9th.
However, January 22nd, the mod I was using (cyanogen 6.2.1) started to have problems, widgets were getting corrupted and certain links stopped working properly..so I decided to start it over from scratch by re-flashing with RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed.exe
It worked, so I'm back. I tried following all the instructions again, which brings me to now.
I make it past step1, then the phone reboots back to the bootloader. I load to Recovery mode (the phone has a little /!\ in the corner), when I type "step2-windows.bat", random results seem to pop up.
Code:
C:\froyoinstall\r4-legend-root>step2-windows
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
push: files/etc/mtab -> /etc/mtab
push: files/etc/fstab -> /etc/fstab
push: files/sbin/wipe -> /sbin/wipe
push: files/sbin/unyaffs -> /sbin/unyaffs
push: files/sbin/ums_toggle -> /sbin/ums_toggle
push: files/sbin/um -> /sbin/um
push: files/sbin/tune2fs -> /sbin/tune2fs
push: files/sbin/toolbox -> /sbin/toolbox
push: files/sbin/sdparted -> /sbin/sdparted
push: files/sbin/recovery -> /sbin/recovery
push: files/sbin/reboot -> /sbin/reboot
push: files/sbin/parted -> /sbin/parted
push: files/sbin/nandroid-mobile.sh -> /sbin/nandroid-mobile.sh
push: files/sbin/mkyaffs2image -> /sbin/mkyaffs2image
push: files/sbin/mke2fs -> /sbin/mke2fs
push: files/sbin/log2sd -> /sbin/log2sd
push: files/sbin/fs -> /sbin/fs
push: files/sbin/flash_image -> /sbin/flash_image
push: files/sbin/fix_permissions -> /sbin/fix_permissions
push: files/sbin/e2fsck -> /sbin/e2fsck
push: files/sbin/dump_image -> /sbin/dump_image
push: files/sbin/busybox -> /sbin/busybox
push: files/sbin/backuptool.sh -> /sbin/backuptool.sh
push: files/sbin/adbd -> /sbin/adbd
push: files/system/bin/sh -> /system/bin/sh
push: files/system/bin/linker -> /system/bin/linker
push: files/system/lib/libstdc++.so -> /system/lib/libstdc++.so
push: files/system/lib/libm.so -> /system/lib/libm.so
push: files/system/lib/liblog.so -> /system/lib/liblog.so
push: files/system/lib/libcutils.so -> /system/lib/libcutils.so
push: files/system/lib/libc.so -> /system/lib/libc.so
31 files pushed. 0 files skipped.
1417 KB/s (3734509 bytes in 2.573s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Pushing update file to device sdcard - this may take a few minutes...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Now wipe and apply rootedupdate.zip from the recovery image menu.
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\froyoinstall\r4-legend-root>
this is what happened the second time I did it:
Code:
C:\froyoinstall\r4-legend-root>step2-windows
Legend Root Step 2
Pushing required files to device...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Pushing update file to device sdcard - this may take a few minutes...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Now wipe and apply rootedupdate.zip from the recovery image menu.
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\froyoinstall\r4-legend-root>
When I did it a third time, the first results happened again (but keep in mind it's totally random, it could go to the first one or the second one)
So, I searched up and noticed my adb.exe was certainly out of date, so I loaded Android's SDK Manager and it downloaded "revision 2" of the "platform-tools" kit, which did not help at all.
Booting the phone loads the stock ROM that HAS root access, but ROM Manager will not reboot to ClockworkMod's Recovery (despite successfully flashing).
Any advice or help would be totally appreciated, I've been scratching my head on this for the past little while.
UPDATE:
I noticed when rebooting the phone to the bootloader, it states "S-ON" .. do I need to shut that off? I'll try AlphaRev to see if that fixes things.
UPDATE 2:
I don't know..through sheer persistence and luck.. (I think mostly just luck) I swapped out SD Cards, and now Step 2 worked. I did this step before and it didn't..but now I am all good.
You can lock this topic, now. Thank you.

[SOLVED] Kindle fire rooting error

I rooted it yesterday then I reset the phone
I want to root now the same method doesn't work
when I write
adb root
command it gives me
adbd cannot run as root in the production builds
why??
what is the error is this in files or what
how you try to root your kf?
did you use burrito root3?
*********************
skip to the next replay
yes I tried it with those steps
http://www.androidpolice.com/2012/0...r-6-2-2-update/comment-page-1/#comment-169037
this is my try plz help me
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \kindleADB
C:\kindleADB>adb devices
List of devices attached
2A9C002600000001 device
C:\kindleADB>adb push BurritoRoot2.bin /data/local/
13 KB/s (0 bytes in 13317.001s)
C:\kindleADB>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\kindleADB>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[COLOR="Blue"][1] Killed am broadcast -a ...
[/COLOR]Please run "adb root" and enjoy
C:\kindleADB>adb root
[COLOR="blue"]adbd cannot run as root in production builds
[/COLOR]
C:\kindleADB>
with this method others had also troubles - would try to use burritoroot3:
http://forum.xda-developers.com/showthread.php?t=1410223
Where I will find
BurritoRoot3.bin
look here
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \
C:\>cd android/platform-tools
C:\android\platform-tools>adb kill-server
C:\android\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2A9C002600000001 device
C:\android\platform-tools>adb push BurritoRoot2.bin /data/local/
13 KB/s (13317 bytes in 1.000s)
C:\android\platform-tools>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>
C:\android\platform-tools>as
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>
C:\android\platform-tools>adb devices
List of devices attached
2A9C002600000001 device
C:\android\platform-tools>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\android\platform-tools>adb shell chmod 777 /data/local/tmp
C:\android\platform-tools>adb install BurritoRoot3.apk
3307 KB/s (1164225 bytes in 0.343s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
C:\android\platform-tools>adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
[COLOR="Blue"]Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
[1] Killed am broadcast -a ...
Installing Superuser APP, if it errors as already exists, please ignore the erro
r.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[/COLOR]
C:\android\platform-tools>
the blue means no any result
no bin - it's a completly new method - please read the op (1st post) of the above linked in thread
wait - still reading your updated post
okay look to my previous post i tried it and the result is above
everything seems to be fine as in your previous post:
Code:
Installing Superuser APP, if it errors as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
it says you should ignore the error cause you have allready installed the superuser app
yeah it installed
should I continue??AND Ignore this error
YES - it says to ignore the error
Not working!!
what do you mean with "not working" ?
if you stopped the process in the middle you can not resume
you have to redo the whole process including the 2 commands:
adb shell /data/local/tmp/BurritoRoot3.bin --root
and
adb shell /data/local/tmp/BurritoRoot3.bin --install
if you'r told from the program to do so
I don't know what happened but someone told me to reset the kf
then when I tried the order that was the output
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Amr Radwan>cd \kindleADB
C:\kindleADB>adb shell chmod 777 /data/local/tmp
C:\kindleADB>adb install BurritoRoot3.apk
2273 KB/s (0 bytes in 1164225.000s)
[1] Killed pm install /data...
C:\kindleADB>
to restart was probably not the best idea - anyway:
the error message looks like he uninstalled it now
retry:
adb install BurritoRoot3.apk
what's the output ?
b63 said:
what do you mean with "not working" ?
if you stopped the process in the middle you can not resume
you have to redo the whole process including the 2 commands:
adb shell /data/local/tmp/BurritoRoot3.bin --root
and
adb shell /data/local/tmp/BurritoRoot3.bin --install
if you'r told from the program to do so
Click to expand...
Click to collapse
thank you so much, i was having a problem with this, i used 2 lines above and everything went smooth
respect
okay I will try now
look
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>cd \kindleADB
C:\kindleADB>adb push BurritoRoot2.bin /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
216 KB/s (0 bytes in 13317.000s)
C:\kindleADB>adb shell chmod 777 /data/local/BurritoRoot2.bin
C:\kindleADB>adb shell /data/local/BurritoRoot2.bin
BurritoRoot 2.0 - by jcase/TeamAndirc
Want to support my projects? or my wine habbit?
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=U3JKACE7SN7
RC
[1] Killed am broadcast -a ...
Please run "adb root" and enjoy
C:\kindleADB>adb root
adbd cannot run as root in production builds
C:\kindleADB>adb shell chmod 777 /data/local/tmp
C:\kindleADB>adb install BurritoRoot3.apk
can't find 'BurritoRoot3.apk' to install
C:\kindleADB>adb install BurritoRoot3.apk
573 KB/s (0 bytes in 1164225.001s)
[1] Killed pm install /data...
C:\kindleADB>

[HELP] Root

Hi!
I need help with root Acre Iconia tab a500... I use this guide for root on linux (ubuntu 12.10).
I follow all instructions. All is fine but I stucked on last step.
Here is my error (bold font) in terminal:
Thanks for help!
Code:
[email protected]:~/root$ chmod +x ./root.sh
[email protected]:~/root$ ./root.sh -d
ICS Root Linux V1.1 (Functionally Equivalent to Windows version 5.1)
Welcome to blackthund3r's Linux A500 Root Tool for the leaked releases of Ice Cream Sandwich 4.0.3
Supported leak ve rsions:
*0.019.00
*0.022.00
*1.031.00
~~~~~~~~~
WARNING: I TAKE NO RESPONSIBILITY FOR YOU OR YOUR EQUIPMENT WHILST USING THIS TOOL!
DEBUG MODE
FOR TESTING ADB CONNECTION. DOES NOT MODIFY THE TABLET
Press any key to continue...
[+] Killing any adb processes
[+] Starting adb server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Listing devices
List of devices attached
14902506315 device
Is your device listed? (y/n) y
[+] Your ADB connection is fine. Proceed to root your device!
[email protected]:~/root$ ./root.sh -h
ICS Root Linux V1.1 (Functionally Equivalent to Windows version 5.1)
Welcome to blackthund3r's Linux A500 Root Tool for the leaked releases of Ice Cream Sandwich 4.0.3
Supported leak ve rsions:
*0.019.00
*0.022.00
*1.031.00
~~~~~~~~~
WARNING: I TAKE NO RESPONSIBILITY FOR YOU OR YOUR EQUIPMENT WHILST USING THIS TOOL!
USAGE:
-h | --help: Shows this usage message
-r | --root: root the device (Installs busybox, su, Superuser.apk & remount app)
-t | --trebuchet: Install Trebuchet (CM9 launcher)
-f | --facelock: Install FaceLock (Experimental and only partially working at the moment
-a | --RemoveAcerNidus: Remove AcerNidus Crash Report App
-s | --RemoveStockRecoveryReflash: Remove auto-reflash of stock recovery in preparation to flash CWM in APX mode
-u1 | --AcerRing1: Install Acer Ring on 0.019.00
-u2 | --AcerRing2: Install Acer Ring on 0.022.00
-u3 | --AcerRing3: Install Acer Ring on 1.031.00
-b | --bash: Install bash on the tablet
-c | --complete: Does the whole lot!
-d | --debug: Debug mode. Tests the ADB connection
[email protected]:~/root$ ./root.sh -r
ICS Root Linux V1.1 (Functionally Equivalent to Windows version 5.1)
Welcome to blackthund3r's Linux A500 Root Tool for the leaked releases of Ice Cream Sandwich 4.0.3
Supported leak ve rsions:
*0.019.00
*0.022.00
*1.031.00
~~~~~~~~~
WARNING: I TAKE NO RESPONSIBILITY FOR YOU OR YOUR EQUIPMENT WHILST USING THIS TOOL!
Press any key to run!
Running in 5 seconds
5
4
Ready...
Set...
Go!
Running!!
[+] Killing all old adb processes
[+] Starting ADB Server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Listing Devices
List of devices attached
14902506315 device
Is your device listed? (y/n) y
[+] Uploading exploit
1088 KB/s (37273 bytes in 0.033s)
[+] Uploading busybox
1293 KB/s (821340 bytes in 0.620s)
[+] Setting permissions
[+] Creating directories
[+] Uploading files...
[B]./root.sh: řádek 161: [: ==: očekáván unární operátor
547 KB/s (22364 bytes in 0.039s)
1126 KB/s (843503 bytes in 0.731s)
0 KB/s (40 bytes in 0.040s)
537 KB/s (21584 bytes in 0.039s)
12 KB/s (519 bytes in 0.040s)
./root.sh: řádek 282: chyba syntaxe: nenadálý konec souboru[/B]
[email protected]:~/root$

[Q:SOLVED] su : not found; rooted without root access

Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery (after rooting with motochopper). I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?
gr4v1ty said:
Hello.
Some of you might already have heard this question, but didn't seem to find an specific answer for my phone > Canadian S4 SGH I377M running Android 4.3
After the first time, I've tried installing a custom recovery. I've got an error because I wasn't granted root access. Tried to see with an app : no root access neither. Verified with a terminal : no root access. Tried re-rooting, it shows the following message :
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *[*] Device found.[*] Pushing exploit...
4439 KB/s (1283460 bytes in 0.282s)[*] Pushing root tools...
4758 KB/s (366952 bytes in 0.075s)
3837 KB/s (1867568 bytes in 0.475s)
2829 KB/s (1578585 bytes in 0.544s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS][*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.[*] Cleaning up...[*] Exploit complete. Press enter to reboot and exit.
What is there left to do?
Click to expand...
Click to collapse
What methods have you tried? Did you try the Chainfire Auto Root?
DeadlySin9 said:
What methods have you tried? Did you try the Chainfire Auto Root?
Click to expand...
Click to collapse
It was motochopper. Sorry forgot to mention. Also here the output of the root checker pro app
Code:
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - is NOT installed.
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-I337M device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
EDIT : Solved by using CF-Auto-root : http://forum.xda-developers.com/showthread.php?t=2293800
Sent from my SGH-I337M using Tapatalk

Categories

Resources