Develop Bugs

[Q] Please help with Rage Temproot during Gfree root process

Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?

G2_Gordon_G1 said:
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
Click to expand...
Click to collapse
looks like you screwed up the last command ... didnt write the syntax properly thats why it showed its usage.....
(adb shell chmod 0755 /data/local/tmp/*) this command that is.....
also the last thing showing file not found means the files were never pushed to the phone..... connect your phone to your pc in chagre only and usb debigging connected mode and in command prompt in the adb folder write "adb devices"
it should show somehting like this.....
adb list of devices attached
SH034N34GF
this number over here (SH034N34GF) is an example ... it will show your phone ID... which would be different....
if you see list of devices attached and an empty line below and no serial number as shown in example....
than it means your android usb drivers for adb shell are not set up correctly
in that case ... get the drivers set up properly....
check with adb devices command to confirm your phone is recognized....
than start over with the commands

I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?

read this guide .... on it search for .... "out of date" author explains how to tackle it
G2_Gordon_G1 said:
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
Click to expand...
Click to collapse

hispeedworm said:
read this guide .... on it search for .... "out of date" author explains how to tackle it
Click to expand...
Click to collapse
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?

G2_Gordon_G1 said:
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
Click to expand...
Click to collapse
im uploading my adb... its minimal with just adb fastboot and few other files.... unzip into a folder on your pc.....use these instead of the android sdk and all..
make sure that folder is linked in windows..... Step 4 of the adb for noobs guide..... reinstall the android usb drivers again following the guide.....
when thats done restart and press F8 ... disable signature verification ... when windows loaded... go to command prompt.... do into the adb directory.....than write adb devices....if it shows you device than start over with the commands.... you should not get the error saying out of date... as i just used this adb shell 2 days back to root my desire Z.....
hope this helps

Thanks! Will try again soon!

[Q] Droid X ME811 always failed to root

Hei All, Nubie got problem here, and getting crazy LOL..
I have Droid X ME811, and it has been 2 weeks I've trying to rooting my droid in manual way, im following this awesome steps
and what happen is I always get stuck when I try to restart adb because after restart adb device cant be detected anymore.
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ cd data/local/tmp
cd data/local/tmp
$ chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 rageagainstthecage-arm5.bin
$ ./rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3814, 3814}
[*] Searching for adb ...
[+] Found adb as PID 1170
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
C:\android-sdk-windows\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
(in this step, list always empty)
so I cant go to the next steps, I also try to go back to step $ cd data/local/tmp.
but seems like no different.
need advise

same exact problem here
Followed exact same steps, tried manually with adb, also tried other roms, pc mode, all other modes..nothing seems to work help please! I'm using ubuntu, adb works fine otherwise. Thanks

[Q] "The system cannot find the drive specified" while trying to root Kindle via KFU

[Q] "The system cannot find the drive specified" while trying to root Kindle via KFU
I've been coming across this strange error while trying to root my Kindle Fire. The ADB drivers are working properly and in Device Manager, my Kindle shows up as "Android Composite ADB Interface" -- all well and good. Except I get shown this screen after I try to root it with KFU v0.9.9:
Since I cannot post outside links because I'm new, you will just have to copy and paste this: i.imgur.com/jyHaRA9.png
Sorry
Looking at the source code of run.bat, it seems logical that this portion of code is throwing the error, specifically in the else block.
Code:
:boot_normal
echo. ***********************************************
echo. * Activating Normal (4000) *
echo. ***********************************************
echo.
if "%adb%" == "Offline" (
tools\fastboot -i 0x1949 oem idme bootmode 4000
tools\fastboot -i 0x1949 reboot
echo.
echo. The kindle has been told to reboot in Normal Mode.
echo.
) else (
::We need to check to make sure we are running root.
::Switch ourselves into Recovery
tools\adb wait-for-device
tools\adb push files\nbmode /data/local/nbmode
tools\adb shell chmod 755 /data/local/nbmode
tools\adb shell /data/local/nbmode
tools\adb reboot
echo.
echo. The kindle has been told to reboot in Normal Mode.
echo.
)
GOTO:EOF
Thank you for your time.

[Q] adb - OUYA stuck as read-only, why?

Hello beautiful people.
Keep in mind that I'm using Ubuntu 13.10 to do this. I'm trying to transfer my own bootanimation.zip to the OUYA but I can't because the system is set as read-only. adb recognizes my OUYA, if I use "adb devices" it shows the device, but I can't do anything else with it besides that. I read online that if I use "adb remount", it would mount as read/write. I tried that and I got "remount failed: Operation not permitted". I also read something about "adb root", I can't remember what exactly I had to do with that, but I got this "adbd cannot run as root in production builds".
If any more information is needed, please do ask for it. Help is appreciated. Thanks.

try something like
Code:
adb shell
su
mount -o remount /system

gianptune said:
try something like
Code:
adb shell
su
mount -o remount /system
Click to expand...
Click to collapse
After I used that, I tried to push the bootanimation.zip to the OUYA with:
Code:
adb push bootanimation.zip system/media/
And I got this:
Code:
[email protected]:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ #
It doesn't recognize it...

Hyd- said:
After I used that, I tried to push the bootanimation.zip to the OUYA with:
Code:
adb push bootanimation.zip system/media/
And I got this:
Code:
[email protected]:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ #
It doesn't recognize it...
Click to expand...
Click to collapse
Try adb insecure http://forum.xda-developers.com/showthread.php?t=1687590

djden said:
Try adb insecure http://forum.xda-developers.com/showthread.php?t=1687590
Click to expand...
Click to collapse
I think that worked. I installed that, pushed it to the OUYA while on adb shell and got this:
Code:
1319 KB/s (2971409 bytes in 2.199s)
[email protected]:~$
I couldn't see my bootanimation though, the screen was pitch-black until the "OUYA" voice and logo popped out. I suppose it was an error on my end, I'll have to try with another bootanimation and see. Thanks.
Edit: I tried to push another bootanimation but now it won't recognize it again...
Edit 2: It worked again but without adb shell... I downloaded another bootanimation, and got the same results. Odd...

I'm having the same problem. The above commands presumably changed the filesystem to RW, but now when I try to push my file it says:
cannot stat 'OuyaCWMrecovery6.0.3.2flashable.zip': No such file or directory
I've tried everything I can think of. Restarting everything. Using the entire system path. Trying to leave shell and then run the command (which seems to send it back to r-o filesystem)
trying to rename the zip to make sure I'm typing the full thing correctly.
Any help?

Try doing adb shell as as super user and doing chmod 777 to any relevant directories on your Ouya (like /sdcard/ etc).

Stuck in recovery.

Hi.
dev: d820n Europe
Had rooted lp with twrp but wanted to go back to stock.
Dl this
http://forum.xda-developers.com/desire-820/general/recovery-stock-recovery-lollipop-5-0-1-t3236989
and now i only can boot to recovery, but twrp. can't boot normal, or bootloader.
Tried to reinstall boot from backed up KK but still nothing...
boots when connected to pc and vol up + power boots recovery (managed to install twrp2.8 XianShiDeNiWo)
boots vol up + power 8 sec+ to recovery.
C:\adb>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adb>
C:\adb>adb shell reboot
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: reboot: not found
Click to expand...
Click to collapse
all those still reboots to recovery
Any ideas what can I do?