Hi all,
I am trying to root my Tablet Z SGP312 build no. 10.1.C.0.370 with Doomlord's easy rooting tool v13.
I have installed the ADB driver on my tablet.
I have also disabled the PC companion and enabled the USB debugging mode and install unknown sources under the device administration.
Once I activated the runme.dat with my tablet connected to my PC, i followed the steps as shown and reached a point where I have to type the shell following shell commands:
cd /data/local/tmp
chmod 777 doomed
./doomed
I typed and entered the above commands one by one, but with no response from both the cmd and my tablet after typing ./doomed. I am not too sure what I have done wrongly. It would be great if someone could help me on this matter. Thank you.
Related
Hi guys,
I am totally new to Android and it's my first post here also.
I 've just purchased my Xperia Arc S and follow the guide here to root my phone.
http://forum.xda-developers.com/showthread.php?t=1409269
Sadly, I failed from the very first step: installing adb driver:
There are 2 linked guides from the above post:
1st one:
http://forum.xda-developers.com/showthread.php?t=502010
I followed the pdf guide and wonder what to do after adb shell? it shows a "$" and asks for my command, I don't know what to type in, and I think it has not done anything to my phone either.
2nd guide:
http://forum.xda-developers.com/showthread.php?t=910008
The author of this post all talks about nookcolor. I tried and when I plugin my phone windows does not ask for anything.
What should I do now?
And btw, how can I check that abd driver has been installed correctly?
Thank you.
to check adb drivers. connect ur phone in normal mode with usb debugging selected.
nw in the windows command window type adb devices [enter]
nw some alphanumneric shd come.
to check if u r rooted. type su [enter] . nw $ shd turn to # .
Sent from my Nexus One using Tapatalk
Downgraded to .42 and rooted successfully
I'm a nube and trying to root my Coby Kyros MID 7036. I get as far as using the adb shell command: chmod 0755 rageagainstthecage-arm5.bin ./rageagainstthecage-arm5.bin. After that, it gets stuck at "adb connection will be reset. restart adb server on desktop and re-login." Then I close the elevated cmd, open a new one and restart the adb server. Typing in the same adb shell command, I get past "adb connection will be reset", but my device is marked as offline. I end up having to restart the device to get it online, but then I just repeat the process! What do I do?
ijmeurer said:
I'm a nube and trying to root my Coby Kyros MID 7036. I get as far as using the adb shell command: chmod 0755 rageagainstthecage-arm5.bin ./rageagainstthecage-arm5.bin. After that, it gets stuck at "adb connection will be reset. restart adb server on desktop and re-login." Then I close the elevated cmd, open a new one and restart the adb server. Typing in the same adb shell command, I get past "adb connection will be reset", but my device is marked as offline. I end up having to restart the device to get it online, but then I just repeat the process! What do I do?
Click to expand...
Click to collapse
Try this when it prompts you to restart the connection - don't close the terminal and use:
adb kill-server
adb start-server
and then try and continue.
There's more rooting info and a system dump if you get into serious trouble here: http://www.androidtablets.net/forum...ead-first-development-index-root-utility.html
Hi there!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me...
hi
i have rca tablet andrond 4.2
trying to follow a youtube post on how to enable adhoc
when i go to cmd prompt and enter adb shell and hit enter
it says device not found
i installed the adb drivers and in device manager i see androind tablet : android composite adb inrterface
my tablet is rooted and i have installed busy box
why is this not working?
i have windows vista
hi not sure if anyone in here is familiar with adb since noone has responded
anyways i was able to get something to come up... when i enter adb shell at command prompt i get a long list of details
adb seems to be installed but still does not recognize my tablet
im really confused here...im trying to get my tablet to see adhoc and was following max lee you tube video on how to enable adhoc on android but his process is not working
can someone help me make my android see adhoc?
Hello everyone, hope you're fine,
Unfortunately, I had bad luck and utterly smashed my device display (Samsung Galaxy A72) which has a PIN to unlock the device access.
My problem here is that I'm unable to accept the authorization for adb connection, just can't touch the accept popup (which I suppose is "being displayed" on the broken screen).
There is by any chance, a way to send a touch signal using the adb prompt?
The current status when I try any command except the
Code:
$ adb devices
is:
Code:
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
In case I can get this resolved, the next steps would be to try to send the adb input keyevent accordingly in order to unlock it by PIN.
Thx in advance to anyone who is able to help
Note: I'm using Linux or Mac, so MS Windows wouldn't help too much.