Database Develop

[Q] unable to root my tattoo whit one click

when i try i got this messege in the log, it looks lige the program is unable to access my system folder on the device.
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
329 KB/s (5392 bytes in 0.016s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock3
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Out of memory[/COLOR]
OK
Pushing superuser.apk...
failed to copy 'superuser.apk' to '/system/app/superuser.apk': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
THREAD CLOSED
ask ur question in the Q & A Thread or the 1 click thread

kongen1280 said:
when i try i got this messege in the log, it looks lige the program is unable to access my system folder on the device.
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
329 KB/s (5392 bytes in 0.016s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/mtdblock3
OK
Remounting system with read-write access...
OK
Pushing su...
failed to copy 'su' to '/system/bin/su': Out of memory[/COLOR]
OK
Pushing superuser.apk...
failed to copy 'superuser.apk' to '/system/app/superuser.apk': Out of memory
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Remounting system with read-only access...
OK
Device was not rooted!
FAILED
Click to expand...
Click to collapse
Try rooting with the unrevoked setting

howabout try use the "1-click" instead of fiddeling with ADB?
http://forum.xda-developers.com/showthread.php?t=761507

[Q] pls help pls some error occured when rooting with super one click

SuperOneClick v1.8.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.1-update1
OK
Pushing psneuter...
1078 KB/s (585731 bytes in 0.530s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1056 KB/s (1062992 bytes in 0.983s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs ro 0 0
FAILED
tell me what is this ?? is my phone rooted ? but i think no help pls

Try the newest version of SuperOneClick at http://forum.xda-developers.com/showthread.php?t=803682

Make sure .NET Framework v2.0 or above is installed on your PC if you're on windows.
Make sure that Android drivers for your phone are properly installed.
Make sure you run SuperOneClick as administrator.
And yes use the latest version.

Quick question

Quick noob question everyone, if I have an unlocked bootloader and custom recovery, am I rooted? Because busybox and superuser still aren't giving me command prompts. I'm on stock ics
Sent from my HTC PH39100 using XDA

Long story short no your not rooted but you did the hard part already just follow this guide you'll be rooted in under 2 minutes http://forum.xda-developers.com/showthread.php?t=1498003

THANKS!
Sent from my HTC PH39100 using XDA

I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Adb isn't set up properly or may need to ne run as administrator
Sent from my HTC PH39100 using xda premium

MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.

If you could get back to stick gb, Google zergrush root. Its a tempt root for users who still have their boot loader locked. But in your case, it should be locked.
Sent from my HTC PH39100 using XDA

jigajay said:
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
Click to expand...
Click to collapse
All In One automatically reboots into recovery, runs the batch then responds with "device not found" after each command.
I did try what you said. I booted into bootloader, then ran the perm root from AIO, but got the same "device not found" result.
---------- Post added at 05:46 PM ---------- Previous post was at 05:10 PM ----------
After much reading, booting and rebooting, I managed to get this response from All In One:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
* server not running *
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
349 KB/s (22364 bytes in 0.062s)
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
4800 KB/s (843503 bytes in 0.171s)
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
However, no still no root. I've kept up to date with the AIO forum. Read the "under construction SuperGuide cover to cover. I have done exactly what many others have, except no joy for me. It appears I may have the only AT&T Vivid in the world that will not root.

http://forum.xda-developers.com/showthread.php?t=1529669
Flash that in boot loader. If it says update presses yes then you're back to gingerbread.
Sent from my HTC PH39100 using XDA

http://forum.xda-developers.com/showthread.php?t=1341162
Use that to root your phone. Follow instructions carefully.
Sent from my HTC PH39100 using XDA

[Q] Can't S-off !!!

I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me

What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium

jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
sharkman3d said:
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^ What he said!!!!!!!! ^^^^^^^^^^^^^^^^
More information please.

Sorry I'm on 2.01.0001

What error did you get?

jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?

I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)

InsertDumbNick said:
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
Click to expand...
Click to collapse
Yes, it was the first i tried...

Is the RUU you have the correct one for your region? The fact you are choosing not to make a goldcard could be having an effect.

Type this command into cmd while your phone is in fastboot mode 'fastboot oem lock'. I did that before I run the process.
Sent from my HTC Incredible S using xda premium

jules290496 said:
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
Click to expand...
Click to collapse
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.

tpbklake said:
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
Click to expand...
Click to collapse
No, i don't see any # and i tried whith and without goldcard

jules290496 said:
No, i don't see any # and i tried whith and without goldcard
Click to expand...
Click to collapse
Yeah, the whole key to the script is getting temp root access so that the mainver can be modified to 2.00.0000.
If that doesn't work, the whole goldcard and RUU thing will not work.
The best thing you could try is to open a command window and try manually typing the commands in and post the command window to help isolate the issue.

I think i will give up, thanks anyway

jules290496 said:
I think i will give up, thanks anyway
Click to expand...
Click to collapse
You have a custom recovery installed?

No, i don't now how to do it without revolutionary...

jules290496 said:
No, i don't now how to do it without revolutionary...
Click to expand...
Click to collapse
So the phone is completely stock, just unlocked bootloader?

Yes it's completely stock

jules290496 said:
Yes it's completely stock
Click to expand...
Click to collapse
Try locking the bootloader and doing a factory reset. Boot into recovery once, turn fastboot off and USB debugging on and run the newest version (3.2) of the script again.

Ok, i will try

how to enable init.d support?

im using stock 4.1.1 (rooted), i know batakang & joker support init.d but i prefer stock & want to mod it a little.
script manager does make few script's work, but cannot supercharge n stuff like that without init.d
i tried using the init.d enabler script but doesn't work & also pimp my rom uses the init.d enabler script so that doesn't work either.
so any1 have any ideas on how to enable init.d support for stock 4.1.1

I wrote a little guide and the required files in a .zip hosted on my Dropbox.
If you want an auto-mated Windows batch file to install it AND adbd insecured...
Use the Ext4 bat file.

im a little noob to do it manually so i tried the bat file method, which failed & here's the error,
Make sure your phone is NOT set to USB Mass Storage.
Make sure USB Debugging is enabled.
Make sure you are ROOTED before doing this.
Press any key to continue.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
4548 KB/s (145332 bytes in 0.031s)
23 KB/s (370 bytes in 0.015s)
3896 KB/s (1867568 bytes in 0.468s)
0 KB/s (37 bytes in 1.000s)
0 KB/s (138 bytes in 1.000s)
cp: /system/xbin/busybox: No such file or directory
rm failed for /system/xbin/run-parts, No such file or directory
link failed No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Rebooting. When it shows 'remount sucessful' it means it worked.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
my Atrix HD is rooted, made sure usb debugging is on, also tried installing busybox to system/xbin but in stock JB it only installs in system/bin so tried changing the lines with xbin to bin in "InstallerForExt4Devices.bat" but still does not work.
thanks for the help but i guess this phone is not for noobs

coldfear00 said:
im a little noob to do it manually so i tried the bat file method, which failed & here's the error,
Make sure your phone is NOT set to USB Mass Storage.
Make sure USB Debugging is enabled.
Make sure you are ROOTED before doing this.
Press any key to continue.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
4548 KB/s (145332 bytes in 0.031s)
23 KB/s (370 bytes in 0.015s)
3896 KB/s (1867568 bytes in 0.468s)
0 KB/s (37 bytes in 1.000s)
0 KB/s (138 bytes in 1.000s)
cp: /system/xbin/busybox: No such file or directory
rm failed for /system/xbin/run-parts, No such file or directory
link failed No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Rebooting. When it shows 'remount sucessful' it means it worked.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
my Atrix HD is rooted, made sure usb debugging is on, also tried installing busybox to system/xbin but in stock JB it only installs in system/bin so tried changing the lines with xbin to bin in "InstallerForExt4Devices.bat" but still does not work.
thanks for the help but i guess this phone is not for noobs
Click to expand...
Click to collapse
Try the busy box installer from play store.
Sent from my MotoAHD Maxx

Youngunn2008 said:
Try the busy box installer from play store.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
i have busybox pro from Gplay also enabled adbd insecure but still no use

You need the "normal install" not the smart install
Sent from my phone.

Markyzz said:
You need the "normal install" not the smart install
Sent from my phone.
Click to expand...
Click to collapse
i always do normal install of busybox.

coldfear00 said:
i always do normal install of busybox.
Click to expand...
Click to collapse
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx

Youngunn2008 said:
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
Yup. IIRC I just manually copied the files into xbin and init.d worked after that.
Sent from my phone.

Youngunn2008 said:
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
when i select system/xbin installation fails, only installs in system/bin
Markyzz said:
Yup. IIRC I just manually copied the files into xbin and init.d worked after that.
Sent from my phone.
Click to expand...
Click to collapse
good for you bro, i also tried the same but no use.

im giving up on this phone, going for nexus 4

accidentally double post, sorry